Re: Newer uBoot as workaround to 3.2 kernel problem? January 22, 2013 05:45PM |
Registered: 12 years ago Posts: 5 |
Re: Newer uBoot as workaround to 3.2 kernel problem? January 22, 2013 10:41PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? January 24, 2013 06:09PM |
Registered: 13 years ago Posts: 264 |
Re: Newer uBoot as workaround to 3.2 kernel problem? January 25, 2013 08:41AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? February 16, 2013 04:30PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 10, 2013 09:24AM |
Registered: 14 years ago Posts: 136 |
Re: Newer uBoot as workaround to 3.2 kernel problem? May 10, 2013 05:16PM |
Registered: 13 years ago Posts: 157 |
U-Boot 2011.12 (May 03 2012 - 17:04:23) ZyXEL NSA320 2-Bay Power Media Server arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 0 Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: ST3320413AS Firm: JC45 Ser#: Z2A84WH4 Type: Hard Disk Supports 48-bit addressing Capacity: 305245.3 MB = 298.0 GB (625142448 x 512) Device 1: Model: ST3320413AS Firm: JC66 Ser#: Z2AJ97AK Type: Hard Disk Supports 48-bit addressing Capacity: 305245.3 MB = 298.0 GB (625142448 x 512) Loading file "/boot/uImage" from ide device 0:1 (hda1) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - ide 0:1 ** Loading file "/boot/uInitrd" from ide device 0:1 (hda1) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - ide 0:1 ** Wrong Image Format for bootm command Error occured, error code = 108 ERROR: can't get kernel image! Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: ST3320413AS Firm: JC45 Ser#: Z2A84WH4 Type: Hard Disk Supports 48-bit addressing Capacity: 305245.3 MB = 298.0 GB (625142448 x 512) Device 1: Model: ST3320413AS Firm: JC66 Ser#: Z2AJ97AK Type: Hard Disk Supports 48-bit addressing Capacity: 305245.3 MB = 298.0 GB (625142448 x 512) ** Bad partition 1 ** ** Bad partition 1 ** Wrong Image Format for bootm command Error occured, error code = 108 ERROR: can't get kernel image!
root@debian-kirkwood-wide:~# ./install_uboot_mtd0.sh !!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!! If you lose power to your device while running this script, it could be left in an unusable state. This script will replace the bootloader on /dev/mtd0. This installer will only work on the following devices: Seagate Dockstar Seagate GoFlex Net Seagate GoFlex Home Pogoplug v1 Pogoplug Pink (v2) Do not run this installer on any other device.
Re: Newer uBoot as workaround to 3.2 kernel problem? May 10, 2013 05:42PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? June 26, 2013 11:30AM |
Registered: 11 years ago Posts: 1,303 |
Re: Newer uBoot as workaround to 3.2 kernel problem? June 26, 2013 11:19PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? June 27, 2013 05:53PM |
Registered: 11 years ago Posts: 1,303 |
Re: Newer uBoot as workaround to 3.2 kernel problem? June 28, 2013 12:19AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? June 28, 2013 09:20AM |
Registered: 11 years ago Posts: 1,303 |
rsuinux
Re: Newer uBoot as workaround to 3.2 kernel problem? January 23, 2014 10:50AM |
dmesg | grep Linux [ 0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #57 Mon Aug 31 16:31:01 PDT 2009and my arc number is
fw_printenv | grep arc arcNumber=2998In my harddisk, the kernel is vmlinuz-3.1.10-dockstar-shyd
md5sum uboot-mtd0-dump e18a2c7e308c249bc16f55bbaad31f50 uboot-mtd0-dump
Re: Newer uBoot as workaround to 3.2 kernel problem? January 23, 2014 06:03PM |
Registered: 13 years ago Posts: 161 |
e18a2c7e308c249bc16f55bbaad31f50 dockstar davygravy-2012-02-12-current
rsuinux
Re: Newer uBoot as workaround to 3.2 kernel problem? January 24, 2014 04:05AM |
dockstar -> [ in hardisk 2,5"] sda1 -> |/vmlinuz with link for /boot/vmlinuz-xxx |/initrd with link for /boot/initrd-xxx |/boot/uImage |/boot/uInitrd |/.....Currently, I create a usb key with a new squeeze, with dockstar.debian-squeeze.sh
Re: Newer uBoot as workaround to 3.2 kernel problem? January 24, 2014 05:03AM |
Registered: 10 years ago Posts: 1 |
Re: Newer uBoot as workaround to 3.2 kernel problem? February 12, 2014 09:51AM |
Registered: 10 years ago Posts: 1 |
Re: Newer uBoot as workaround to 3.2 kernel problem? February 12, 2014 03:43PM |
Admin Registered: 13 years ago Posts: 18,821 |
santiago
Re: Newer uBoot as workaround to 3.2 kernel problem? August 27, 2014 10:38PM |
santiago
Re: Newer uBoot as workaround to 3.2 kernel problem? August 28, 2014 02:05AM |
Re: Newer uBoot as workaround to 3.2 kernel problem? August 28, 2014 03:08PM |
Registered: 12 years ago Posts: 232 |