Welcome! Log In Create A New Profile

Advanced

Newer uBoot as workaround to 3.2 kernel problem?

Posted by davygravy 
Re: Newer uBoot as workaround to 3.2 kernel problem?
June 11, 2012 04:46PM
Following an upgrade of uBoot, I have successfully upgraded my Docstar to kernel 3.2.0-2 (latest wheezy).

Thanks for the great work guys.
Re: Newer uBoot as workaround to 3.2 kernel problem?
June 15, 2012 09:30AM
@davy
Quote

I want to look at code and see what is up. AFAICR, I didn't hard code in the MAC/hw address, but I'll double check. EDIT: just checked - it isn't in the code . And as far as I can see, that isn't a Dockstar... here's why...
It probably came from other uboot then. Prior to using Jeff's I was using OpenWRT uboot. Doesn't matter. It was just a bit odd.

@Jeff
Quote

> I am more than happy to test as many images as you're willing to build. I think the new builds are great and I'm eager to roll them out.
Thank you again, Jeff, for hosting davy's uboot and for this wonderful site! When I first got my Dockstar the only reason was that it was so cheap ($30!), and that it was much more powerful than my Buffalo router so I could offload the web server from the router. But thanks to you and your site I was able to switch from OpenWRT to Debian, and then upgrade to the GoFlex Net when it came out! Your work is greatly appreciated by countless numbers of untold people like me who rarely, if ever, have a need to visit this forum.

Quote

It's official, Davy's images are the new default!
Awesome! Just awesome.

@davy

Thanks again for all your hard work! Your new uboot's have been working flawlessly for a good while now.

I have two GoFlex Net's with external 2Gb 3.5 SATA hdd's. They serve as MythTV backend and slave backend, and web server, media server etc. I retired the Dockstar and sold it on eBay. But, unfortunately, it was returned in a bricked state as the guy tried, and failed, to reload the uboot. I reloaded the uboot via the JTAG procedure and now it works fine again. Anybody trying that procedure needs to be aware that a relocatable uboot like Jeff's is needed during the "boot from memory" portion.

I decided to go ahead and keep the Dockstar. It's not worth the trouble to try and sell it again on eBay. So I am going to use it as an ARM development platform. Compiling vanilla Kirkwood kernels and some small tools has already been a success. My next project is to actually succeed in getting a working uboot compiled after my failed prior attempt.



Edited 7 time(s). Last edit at 06/20/2012 05:01PM by gnexus.
Re: Newer uBoot as workaround to 3.2 kernel problem?
July 19, 2012 05:32PM
I've just come to upgrade u-boot on my 4 Dockstar and on my GoFlex net.
It works perfectly. Thank you very much for what you have done.

For the Goflex Net, to be able to boot with SATA, I had to adjust some variables:

fw_setenv sata_device '0:1'
fw_setenv sata_root '/dev/sda1'
fw_setenv sata_rootfstype 'ext3'
fw_setenv sata_rootdelay '10'
fw_setenv sata_set_bootargs 'setenv bootargs console=$console root=$sata_root rootdelay=$sata_rootdelay rootfstype=$sata_rootfstype $mtdparts $sata_custom_params'
fw_setenv sata_boot 'ide reset; mw 0x800000 0 1; ext2load ide $sata_device 0x800000 /boot/uImage; if ext2load ide $sata_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
fw_setenv sata_bootcmd 'run sata_set_bootargs; run sata_boot'
fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset'
Re: Newer uBoot as workaround to 3.2 kernel problem?
July 25, 2012 02:51PM
I compiled a new u-boot with no problems. I can use kwboot to load it and boot my kernel but I can not seem to get it properly loaded into flash. I followed this

make mrproper
make nsa320_config
make u-boot.kwb
dd if=u-boot.kwb of=uboot.mtd0.kwb bs=512k conv=sync

NSA320> tftpboot 0x800000 uboot.mtd0.kwb
Using egiga0 device
TFTP from server 192.168.1.101; our IP address is 192.168.1.120
Filename 'uboot.mtd0.kwb'.
Load address: 0x800000
Loading: #######################################################################################################
done
Bytes transferred = 524288 (80000 hex)
NSA320> nand erase 0x0 0x80000

NAND erase: device 0 offset 0x0, size 0x80000
Erasing at 0x60000 -- 100% complete.
OK
NSA320> nand write.e 0x800000 0x0 0x80000

NAND write: device 0 offset 0x0, size 0x80000
524288 bytes written: OK
NSA320> reset
resetting ...


And that is all. Even if I cycle power nothing happens. Any advice??
Re: Newer uBoot as workaround to 3.2 kernel problem?
July 26, 2012 07:31PM
Hi. Have lurked a year or so but joined up today so I could thank Davygravy for the great work. Also of course, Jeff for all he's done, too much to list. Installed the new uboot last night on my Dockstar and this morning began running the ArchArm 3.4.6 kernel, no problem. Also, you guys have got that environment thing worked out it appears, just did a diff between my backed up env and current, there ain't no diff. I just simply answered N to the question at the end, as Jeff posted earlier. It was all really no muss no fuss. I really had no problem with the "frozen" 3.10 Arch kernel, but I know how lonely it can get as you drift further & further out to sea on that tiny, melting iceberg :)

Thanks guys!

sputnik



Edited 1 time(s). Last edit at 07/26/2012 07:33PM by sputnik.
Hello everybody. I have a couple of questions. I have UBit 0.6 installed which supports booting from sata.
Does this new version of U-boot support booting from sata?

If not, what could I do to have new U-Boot so that I could boot >=3.2 kernel and boot from sata?

Thanks!
Re: Newer uBoot as workaround to 3.2 kernel problem?
August 03, 2012 02:19PM
I finally had some free time and decided to update the bootloader on my GoFlex Net. Everything went fine, such that now I'm running "U-Boot 2011.12 (Apr 18 2012 - 23:08:20)". At this point I'd like to thank davygravy and Jeff for their efforts to patch U-Boot for newer kernels and provide an easy install procedure. Since this might be interesting to others, I'd like to describe my update procedure in more details.

My GoFlex Net was running with UBIT v0.6 and Debian Squeeze. First, I wanted to update the bootloader using netconsole, but luckily I noticed that after doing "tftp 0x8000 xxx.kwb" my GF Net accepted at most one or two commands before loosing connection. I have no idea what the reason was, but such a behavior was surely not safe to perform an update. Then I noticed that Jeff already updated his "install_uboot_mtd0.sh" script and I decided to give it a try.

That's what I did from Debian Squeeze
su
fw_printenv > /root/fw_printenv.txt
cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh 
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh --no-uboot-check

the "--no-uboot-check" key was neccessary because I had UBIT v0.6 and Jeff's script refused to recognize it. Here's the log of Jeff's script
!!!!!!  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.

By typing ok, you agree to assume all liabilities and risks 
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
--2012-08-03 21:54:21--  http://jeff.doozan.com/uboot/valid-uboot.md5
Resolving jeff.doozan.com... 50.116.34.13
Connecting to jeff.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://projects.doozan.com/uboot/valid-uboot.md5 [following]
--2012-08-03 21:54:21--  http://projects.doozan.com/uboot/valid-uboot.md5
Resolving projects.doozan.com... 50.116.34.13
Connecting to projects.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1133 (1,1K) [text/plain]
Saving to: `/tmp/valid-uboot.md5'

100%[====================================================================================================================>] 1.133       --.-K/s   in 0s      

2012-08-03 21:54:22 (31,7 MB/s) - `/tmp/valid-uboot.md5' saved [1133/1133]

## Unknown uBoot detected on mtd0: ad2f48df8285fe9703b260c7e39ab2ad
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
2
Selected Seagate GoFlex Net

# Installing uBoot
## Installing goflexnet davygravy-2012-04-19
--2012-08-03 21:54:28--  http://download.doozan.com/uboot/files/uboot/uboot.mtd0.goflexnet.davygravy-2012-04-19.kwb.md5
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/tmp/uboot.mtd0.kwb.md5'

    [ <=>                                                                                                                 ] 32          --.-K/s   in 0s      

2012-08-03 21:54:28 (1,08 MB/s) - `/tmp/uboot.mtd0.kwb.md5' saved [32]

--2012-08-03 21:54:28--  http://download.doozan.com/uboot/files/uboot/uboot.mtd0.goflexnet.davygravy-2012-04-19.kwb
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 524288 (512K) []
Saving to: `/tmp/uboot.mtd0.kwb'

100%[====================================================================================================================>] 524.288      252K/s   in 2,0s    

2012-08-03 21:54:31 (252 KB/s) - `/tmp/uboot.mtd0.kwb' saved [524288/524288]

Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
--2012-08-03 21:54:31--  http://download.doozan.com/uboot/files/uboot/uboot.mtd0.goflexnet.davygravy-2012-04-19.kwb.md5
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/tmp/uboot.mtd0.kwb.md5'

    [ <=>                                                                                                                 ] 32          --.-K/s   in 0s      

2012-08-03 21:54:31 (1,05 MB/s) - `/tmp/uboot.mtd0.kwb.md5' saved [32]

# Verified successfully!

# Installing uBoot environment
--2012-08-03 21:54:32--  http://download.doozan.com/uboot/files/environment/uboot.environment.md5
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/tmp/uboot.environment.md5'

    [ <=>                                                                                                                 ] 32          --.-K/s   in 0s      

2012-08-03 21:54:32 (1,07 MB/s) - `/tmp/uboot.environment.md5' saved [32]

--2012-08-03 21:54:32--  http://download.doozan.com/uboot/files/environment/uboot.environment
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 131072 (128K) []
Saving to: `/tmp/uboot.environment'

100%[====================================================================================================================>] 131.072      120K/s   in 1,1s    

2012-08-03 21:54:33 (120 KB/s) - `/tmp/uboot.environment' saved [131072/131072]

Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
--2012-08-03 21:54:33--  http://download.doozan.com/uboot/files/environment/uboot.environment.md5
Resolving download.doozan.com... 50.116.34.13
Connecting to download.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/tmp/uboot.environment.md5'

    [ <=>                                                                                                                 ] 32          --.-K/s   in 0s      

2012-08-03 21:54:34 (1,06 MB/s) - `/tmp/uboot.environment.md5' saved [32]

and here's the output of fw_printenv just after updating to the new U-Boot

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=XX:XX:XX:XX:XX:XX
arcNumber=3089

To activate netconsole on the new U-Boot I did the following

ipaddr=10.0.10.6
ncip=10.10.10.5
ncipk=10.10.10.4
serverip=10.10.10.3
preboot=run nc_test nc_start
nc_test=ping $ncip
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version

After that I rebooted my GF Net. Of course, netconsole worked as expected, such that
using
sudo ifconfig eth0:0 10.10.10.5 && nc -lu 10.10.10.5 6666
I could monitor the boot process. That's how it looks like in my case
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
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 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1744
UBI: number of bad PEBs:         8
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1723
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1602176 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
8052291 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.0.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1602112 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Linux-3.0.0
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8052227 Bytes = 7.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

I'm very content with the simplicity of the update procedure. Thanks guys!
Re: Newer uBoot as workaround to 3.2 kernel problem?
August 04, 2012 08:44AM
One more thing. I noticed that after upadting to the latest U-Boot the kernel was obviously unable to mount rootfs correctly such that the system didn't boot. After connecting serial console and monitoring boot process directly, I immediately was able to recognize the problem

Waiting 10sec before mounting root device...
scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer           7.01 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: [sda] 7905279 512-byte logical blocks: (4.04 GB/3.76 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] Attached SCSI removable disk
EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
List of all partitions:
1f00            1024 mtdblock0  (driver?)
1f01            4096 mtdblock1  (driver?)
1f02           32768 mtdblock2  (driver?)
1f03          224256 mtdblock3  (driver?)
0800         3952639 sda  driver: sd
  0801         3406848 sda1 00000000-0000-0000-0000-000000000sda1
  0802          543744 sda2 00000000-0000-0000-0000-000000000sda2
No filesystem could mount root, tried:  ext2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
[<c00366c0>] (unwind_backtrace+0x0/0xec) from [<c0433258>] (panic+0x4c/0x180)
[<c0433258>] (panic+0x4c/0x180) from [<c0008f40>] (mount_block_root+0x1d4/0x21c)
[<c0008f40>] (mount_block_root+0x1d4/0x21c) from [<c000902c>] (mount_root+0xa4/0xc8)
[<c000902c>] (mount_root+0xa4/0xc8) from [<c00091b4>] (prepare_namespace+0x164/0x1c8)
[<c00091b4>] (prepare_namespace+0x164/0x1c8) from [<c0008450>] (kernel_init+0x10c/0x150)
[<c0008450>] (kernel_init+0x10c/0x150) from [<c0032484>] (kernel_thread_exit+0x0/0x8)

The problem is "usb_rootfstype=ext2" in U-Boot environment. On my systems I use ext4 and sometimes ext3 but never ext2. With UBIT v0.6 this never was a problem, even though there I had "usb_rootfstype=ext2" too.

Anyway, after entering
setenv usb_rootfstype ext4
saveenv
reset
in the Marvell prompt, everything works as usual.
cyb
Re: Newer uBoot as workaround to 3.2 kernel problem?
August 08, 2012 03:55PM
Just want to confirm Vlad's guide (thanks for that) for updating from UBIT 0.6 to current U-Boot. Everything works fine with my GoFlex Net.
Re: Newer uBoot as workaround to 3.2 kernel problem?
August 09, 2012 12:34PM
One more feedback.

Today I bought a second brand new GoFlex Net (not hacked) and decided to unlock it via direct serial connection. After booting to that crippled Linux GF Net has, I downloaded and executed Jeff's U-Boot script.

bash
cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh

Everything worked flawlessly. Of course I chose to disable Pogoplug Services and changed arcNumber to 3089. Big thanks to Jeff for offering such an easy procedure to unlock GF Net.

If you're interested, here's the complete log:

picocom v1.4

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Terminal ready


U-Boot 1.1.4  Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00691750

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: DISCOVERY:0.1

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-02-08  23:13:14 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1978884 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.
[    0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #76 Mon Feb 8 15:13:08 PST 2010
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] CE: Received CE uboot parameters:
[    0.000000] CE:    BOARDID: DISCOVERY:0.1
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB 0MB 0MB 0MB = 128MB total
[    0.000000] Memory: 125824KB available (3592K code, 253K data, 124K init)
[    0.240000] Mount-cache hash table entries: 512
[    0.240000] CPU: Testing write buffer coherency: ok
[    0.240000] NET: Registered protocol family 16
[    0.240000] 
[    0.240000] CPU Interface
[    0.240000] -------------
[    0.240000] SDRAM_CS0 ....base 00000000, size 128MB 
[    0.240000] SDRAM_CS1 ....disable
[    0.240000] SDRAM_CS2 ....disable
[    0.240000] SDRAM_CS3 ....disable
[    0.240000] PEX0_MEM ....base e8000000, size 128MB 
[    0.240000] PEX0_IO ....base f2000000, size   1MB 
[    0.240000] INTER_REGS ....base f1000000, size   1MB 
[    0.240000] NFLASH_CS ....base fa000000, size   2MB 
[    0.240000] SPI_CS ....base f4000000, size  16MB 
[    0.240000] BOOT_ROM_CS ....no such
[    0.240000] DEV_BOOTCS ....no such
[    0.240000] CRYPT_ENG ....base f0000000, size   2MB 
[    0.240000] 
[    0.240000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A1 LE
[    0.240000] 
[    0.240000]  Detected Tclk 200000000 and SysClk 400000000 
[    0.240000] MV Buttons Device Load
[    0.240000] Marvell USB EHCI Host controller #0: c0539600
[    0.740000] PEX0 interface detected no Link.
[    0.740000] PCI: bus0: Fast back to back transfers enabled
[    0.740000] SCSI subsystem initialized
[    0.740000] usbcore: registered new interface driver usbfs
[    0.740000] usbcore: registered new interface driver hub
[    0.740000] usbcore: registered new device driver usb
[    0.740000] NET: Registered protocol family 2
[    0.750000] Time: kw_clocksource clocksource has been installed.
[    0.840000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.840000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.840000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.840000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.840000] TCP reno registered
[    0.870000] RTC has been updated!!!
[    0.870000] RTC registered
[    0.870000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.870000]   o RAID 5 Xor calculation
[    0.870000]   o kernel memcpy
[    0.870000]   o kenrel memzero
[    0.870000] Number of XOR engines to use: 4
[    0.870000] cesadev_init(c00117b0)
[    0.870000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.870000] MV Buttons Driver Load
[    0.870000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.870000] squashfs: LZMA suppport for slax.org by jro
[    0.870000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.870000] io scheduler noop registered
[    0.870000] io scheduler anticipatory registered (default)
[    0.880000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.890000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.910000] Loading Marvell Ethernet Driver:
[    0.920000]   o Cached descriptors in DRAM
[    0.920000]   o DRAM SW cache-coherency
[    0.930000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.930000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.940000]   o TCP segmentation offload enabled
[    0.940000]   o Receive checksum offload enabled
[    0.950000]   o Transmit checksum offload enabled
[    0.950000]   o Network Fast Processing (Routing) supported
[    0.960000]   o Driver ERROR statistics enabled
[    0.960000]   o Driver INFO statistics enabled
[    0.970000]   o Proc tool API enabled
[    0.970000]   o Rx descripors: q0=128
[    0.970000]   o Tx descripors: q0=532
[    0.980000]   o Loading network interface(s):
[    0.980000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000] 
[    0.990000] Warning: Giga 1 is Powered Off
[    0.990000] 
[    0.990000] mvFpRuleDb (c7f13000): 1024 entries, 4096 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.010000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.020000] Integrated Sata device found
[    1.050000] scsi0 : Marvell SCSI to SATA adapter
[    1.050000] scsi1 : Marvell SCSI to SATA adapter
[    1.060000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.070000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    1.080000] Scanning device for bad blocks
[    1.170000] Using static partition definition
[    1.170000] Creating 4 MTD partitions on "nand_mtd":
[    1.180000] 0x00000000-0x00100000 : "u-boot"
[    1.180000] 0x00100000-0x00500000 : "uImage"
[    1.190000] 0x00500000-0x02500000 : "root"
[    1.190000] 0x02500000-0x10000000 : "data"
[    1.200000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.200000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.240000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.260000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.260000] usb usb1: configuration #1 chosen from 1 choice
[    1.270000] hub 1-0:1.0: USB hub found
[    1.270000] hub 1-0:1.0: 1 port detected
[    1.390000] USB Universal Host Controller Interface driver v3.0
[    1.390000] usbcore: registered new interface driver usblp
[    1.400000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    1.400000] Initializing USB Mass Storage driver...
[    1.410000] usbcore: registered new interface driver usb-storage
[    1.420000] USB Mass Storage support registered.
[    1.420000] mice: PS/2 mouse device common for all mice
[    1.430000] i2c /dev entries driver
[    1.430000] Linux telephony interface: v1.00
[    1.430000] md: linear personality registered for level -1
[    1.440000] md: raid0 personality registered for level 0
[    1.440000] md: raid1 personality registered for level 1
[    1.620000] raid6: int32x1     98 MB/s
[    1.790000] raid6: int32x2    114 MB/s
[    1.960000] raid6: int32x4    122 MB/s
[    2.130000] raid6: int32x8    110 MB/s
[    2.130000] raid6: using algorithm int32x4 (122 MB/s)
[    2.130000] md: raid6 personality registered for level 6
[    2.140000] md: raid5 personality registered for level 5
[    2.140000] md: raid4 personality registered for level 4
[    2.150000] raid5: measuring checksumming speed
[    2.200000]    arm4regs  :  1084.400 MB/sec
[    2.250000]    8regs     :   755.200 MB/sec
[    2.300000]    32regs    :   900.000 MB/sec
[    2.300000] raid5: using function: arm4regs (1084.400 MB/sec)
[    2.310000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.310000] dm_crypt using the OCF package.
[    2.320000] sdhci: Secure Digital Host Controller Interface driver
[    2.320000] sdhci: Copyright(c) Pierre Ossman
[    2.330000] usbcore: registered new interface driver usbhid
[    2.330000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.340000] TCP cubic registered
[    2.340000] NET: Registered protocol family 1
[    2.350000] NET: Registered protocol family 17
[    2.350000] md: Autodetecting RAID arrays.
[    2.360000] md: autorun ...
[    2.360000] md: ... autorun DONE.
[    5.520000] Empty flash at 0x00e55270 ends at 0x00e55800
[    5.620000] VFS: Mounted root (jffs2 filesystem) readonly.
[    5.630000] Freeing init memory: 124K
init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)
starting pid 264, tty '': '/etc/init.d/rcS'
[    7.110000] eth0: link down
[    7.110000] eth0: started
udhcpc (v1.7.0) started
HWADDR 00 0xXX 0xXX 0xXX 0xXX 0xXX
PIP0 105
PIP1 251
Sending discover...
Sending discover...
[   10.840000] eth0: link up, full duplex, speed 1 Gbps
Sending discover...
HWADDR 00 0xXX 0xXX 0xXX 0xXX 0xXX
PIP0 105
PIP1 251
Unexpected Argument: leasefail
interface=eth0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PWD=/
SHLVL=1
HOME=/
_=/bin/printenv
No lease, forking to background
Loading fs modules:          [   16.600000] fuse init (API version 7.8)
Success
[   16.880000] ufsd: module license 'Commercial product' taints kernel.
[   17.050000] ufsd: driver 8.1 (011_A) LBD=ON with ioctl loaded at bf040000
[   17.050000] NTFS read/write support included
[   17.050000] Hfs+/HfsX read/write support included
Loading tun.ko:              [   17.070000] tun: Universal TUN/TAP device driver, 1.6
[   17.080000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Success
Loading xce.ko:              [   17.100000] Cloud Engines XCE Init [Version: 2.0.5.10]
[   17.110000] XCE: CPU MEMORY MAP:
[   17.110000] XCE:   -- 0x00001000 - 0xbeffffff (3055 MB)  User Space Mappings
[   17.120000] XCE:   -- 0xbf000000 - 0xbfffffff (  16 MB)  Kernel module space
[   17.130000] XCE:   -- 0xc0000000 - 0xc7ffffff ( 128 MB)  Kernel direct-mapped ram
[   17.130000] XCE:   -- 0xc8800000 - 0xe7ffffff ( 504 MB)  Kernel vmalloc space
[   17.140000] XCE:   -- 0xe8000000 - 0xfeffffff ( 367 MB)  Kernel platform space
[   17.150000] XCE: CPU FEATURES:
[   17.150000] XCE:   -- I Cache:         enabled
[   17.160000] XCE:   -- D Cache:         enabled
[   17.160000] XCE:   -- Branch Predict:  disabled
[   17.170000] XCE:   -- MMU:             enabled
[   17.170000] XCE:   -- Alignment Abort: enabled
[   17.170000] XCE:   -- ICache Prefetch: enabled
[   17.180000] XCE:   -- DCache Prefetch: enabled
[   17.180000] XCE:   -- L2 Cache:        enabled
[   17.190000] XCE:   -- L2 Prefetch:     disabled
[   17.190000] XCE:   -- L2 Writethrough: disabled
[   17.200000] XCE:   -- Write Allocate:  disabled
[   17.200000] XCE:   -- Streaming:       disabled
[   17.210000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   17.210000] XCE: Loaded Property Size: 2048
[   17.220000] XCE:    - 'cesvcid' -> 'XXXXXXXXXXXXXXXXXXXXXXXXX'
[   17.220000] XCE:    - 'ceserialno' -> 'XXXXXXXX'
[   17.230000] XCE:    - 'ceboardver' -> 'DISCOVERY:0.1'
[   17.230000] XCE: Current GPIO State:
[   17.240000] XCE:  GPIO L OUT:    0xeff00000
[   17.240000] XCE:  GPIO L OE:     0xffffffff
[   17.250000] XCE:  GPIO L BLINK:  0x00000000
[   17.250000] XCE:  GPIO L POL:    0x00000000
[   17.250000] XCE:  GPIO L IN:     0xfff00080
[   17.260000] XCE:  GPIO H OUT:    0xfffcc00f
[   17.260000] XCE:  GPIO H OE:     0xfffc000f
[   17.270000] XCE:  GPIO H BLINK:  0x00000000
[   17.270000] XCE:  GPIO H POL:    0x00000000
[   17.270000] XCE:  GPIO H IN:     0x0000c00d
[   17.280000] XCE: Kernel thread starting PID: 346
Success
Starting hbplug:             Success
starting pid 348, tty '': '/bin/sh'
-sh-3.2# [   18.140000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   18.150000] XCE: BLPARAMS: reading 2048 bytes @ a0800
[   18.160000] XCE: BLPARAMS: reading 2048 bytes @ a1000
[   18.160000] XCE: BLPARAMS: reading 2048 bytes @ a1800

-sh-3.2# ls
bin      etc      linuxrc  proc     sbin     tmp      var
dev      lib      mnt      root     sys      usr
-sh-3.2# [   22.090000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   22.100000] XCE: BLPARAMS: reading 2048 bytes @ a0800
[   22.100000] XCE: BLPARAMS: reading 2048 bytes @ a1000
[   22.110000] XCE: BLPARAMS: reading 2048 bytes @ a1800
w
-sh: w: command not found
-sh-3.2# wget 
bin/     etc/     linuxrc  proc/    sbin/    tmp/     var/     
dev/     lib/     mnt/     root/    sys/     usr/     
-sh-3.2# [   27.210000] XCE: XCE: LED -> CONNECTED
cd 
-sh-3.2# cd /tmp
-sh-3.2# ls
hbplug.log   resolv.conf  smb.conf     var
-sh-3.2# bash
bash-3.2# ls
hbplug.log   resolv.conf  smb.conf     var
bash-3.2# cd /tmp
bash-3.2# ls
hbplug.log   resolv.conf  smb.conf     var
bash-3.2# pwd
/tmp
bash-3.2# wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh 
Connecting to projects.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |*******************************| 18406  --:--:-- ETA
bash-3.2# chmod +x install_uboot_mtd0.sh
bash-3.2# ./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.

By typing ok, you agree to assume all liabilities and risks 
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...

# Installing /usr/sbin/nandwrite...
Connecting to download.doozan.com (50.116.34.13:80)
nandwrite.md5        100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
nandwrite            100% |*******************************| 11500  --:--:-- ETA
# Successfully installed /usr/sbin/nandwrite.
# checking for /usr/sbin/nanddump...

# Installing /usr/sbin/nanddump...
Connecting to download.doozan.com (50.116.34.13:80)
nanddump.md5         100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
nanddump             100% |*******************************| 21286  --:--:-- ETA
# Successfully installed /usr/sbin/nanddump.
# checking for /usr/sbin/flash_erase...

# Installing /usr/sbin/flash_erase...
Connecting to download.doozan.com (50.116.34.13:80)
flash_erase.md5      100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
flash_erase          100% |*******************************| 12819  --:--:-- ETA
# Successfully installed /usr/sbin/flash_erase.
# checking for /usr/sbin/fw_printenv...

# Installing /usr/sbin/fw_printenv...
Connecting to download.doozan.com (50.116.34.13:80)
fw_printenv.md5      100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
fw_printenv          100% |*******************************|   652k 00:00:00 ETA
# Successfully installed /usr/sbin/fw_printenv.
# checking for /etc/fw_env.config...

# Installing /etc/fw_env.config...
Connecting to download.doozan.com (50.116.34.13:80)
fw_env.config.md5    100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
fw_env.config        100% |*******************************|   329  --:--:-- ETA
# Successfully installed /etc/fw_env.config.

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Valid uBoot detected: [goflexnet original]



DISABLE POGOPLUG SERVICES

The pogoplug service includes an auto-update feature which could
be used to cripple or disable your device.  It is recommended
that you disable this service.

NOTE: The pogoplug service is proprietary software
created by Cloud Engines.  It is not available for use
in other distributions and will not be available in
your new linux installation even if you choose not to disable it.

Would you like to disable the pogoplug services? [Y/n] Y
Applying fixes to the pogoplug environment...
Disabling the pogoplug service...
Done fixing pogoplug environment.

# checking for /uboot-original-mtd0.kwb...

# Installing /uboot-original-mtd0.kwb...
Connecting to download.doozan.com (50.116.34.13:80)
uboot-original-mtd0. 100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot-original-mtd0. 100% |*******************************|   512k 00:00:00 ETA
# Successfully installed /uboot-original-mtd0.kwb.
# checking for /usr/sbin/blparam...

# Installing /usr/sbin/blparam...
Connecting to download.doozan.com (50.116.34.13:80)
blparam.md5          100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
blparam              100% |*******************************| 14168  00:00:00 ETA
# Successfully installed /usr/sbin/blparam.

# Installing uBoot
## Installing goflexnet davygravy-2012-04-19
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb       100% |*******************************|   512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
# Verified successfully!

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment    100% |*******************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************|    32  --:--:-- ETA


# Setting arcNumber to 2097 (SheevaPlug)
# Note: if you have a kernel that supports your platform, you should use the proper arcNumber.
# You can set the correct arcNumber by running the following command:
/usr/sbin/fw_setenv arcNumber 3089

# uBoot installation has completed successfully.
bash-3.2# /usr/sbin/fw_setenv arcNumber 3089
bash-3.2# reboot
The system is going down NOW!
Sending SIGTERM to all processes
Requesting system reboot
[  160.520000] md: stopping all md devices.
[  161.520000] Restarting system.
[  161.520000] Reseting !!



Edited 1 time(s). Last edit at 08/09/2012 02:39PM by Vlad.
Re: Newer uBoot as workaround to 3.2 kernel problem?
August 10, 2012 10:48AM
arbie2 Wrote:
-------------------------------------------------------
> Thank you, thank you! Your new uboot procedure
> works with my GoFlex Net.
>
> With a USB stick and no SATA drive, it boots from
> the USB stick.
> With no USB stick and one SATA drive, it boots
> from the SATA in either slot.

> With no USB stick and two SATA drives, it boots
> from the right-slot SATA.
>
> It's difficult to argue with success.
>
> However, I do note the following anomaly booting
> ArchLinuxARM:
>
> With a USB stick and one SATA drive, it boots from
> the SATA in either slot. -- OOPS!
> With a USB stick and two SATA drives, it boots
> from the USB stick.
>
> With my Dockstars, I always carry an emergency USB
> stick to boot from for repairing a failed/
> failing disk drive. I though that the GoFlex Net
> would boot from the USB stick regardless of
> whether a SATA drive was present. Apparently
> not.
>
> For now, I'll carry a spare SATA drive for GoFlex
> Net emergencies. However, my (yet to be
> received) GoFlex Home has only one SATA, and my
> two SATA drive solution won't work for
> emergencies. How are people handling SATA disk
> problems on their GoFlex Home?

How can you do that? could you post your fw_printenv seetings? mine only boots from the right slot.
Re: Newer uBoot as workaround to 3.2 kernel problem?
October 03, 2012 10:09AM
I flashed this uboot to my dockstar using Jeff's script, and it appeared to flash ok. When I reboot, I get the following message when trying to start the kernel from usb (watching via serial):
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1432436 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4702937 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1432372 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4702873 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x00000bb6).

Available machine support:

ID (hex)        NAME
00000690        Marvell DB-88F6281-BP Development Board
00000691        Marvell RD-88F6192-NAS Development Board
00000692        Marvell RD-88F6281 Reference Board
00000a76        Marvell eSATA SheevaPlug Reference Board
00000831        Marvell SheevaPlug Reference Board
00000a63        Marvell GuruPlug Reference Board
0000085b        QNAP TS-119/TS-219
000009c6        QNAP TS-41x
00000b44        Marvell OpenRD Ultimate Board
00000939        Marvell OpenRD Client Board
00000915        Marvell OpenRD Base Board
00000b1e        HP t5325 Thin Client

Please check your kernel config and/or bootloader.
I assume this "machine ID (r1 = 0x00000bb6)" is related to arcNumber. bb6 hex is 2998 decimal. At the "u-boot>>" prompt, "printenv arcNumber" gives 2097, which in hex is 831--one of the IDs listed for Available machine support.

What do I need to do to be able to boot?
Re: Newer uBoot as workaround to 3.2 kernel problem?
October 28, 2012 10:58AM
This looks like a very old kernel that doesn't have any support for the Dockstar. That appears to be the problem - perhaps the only one.

=====================================================


Re: Newer uBoot as workaround to 3.2 kernel problem?
November 01, 2012 02:35PM
davygravy Wrote:
-------------------------------------------------------
> We know that folks running ArchLinuxARM and others use the u-boot that is piped out of this site, and we want to be a seamless change for them, as well.

Any plans of Uboot supporting "intelligent" boot choice on GoFlex Net, when both USB and SATA drives are hooked in? Currently it works on Debian by using LABEL env param, but doesn't work out of the box on ArchLinux ARM. You were seemingly determined to support both OSs, since most folks would have difficulty fixing it on their own. :)

Also, can you post a list of Hush Shell commands implemented in Jeff's & your Uboot version?



Edited 4 time(s). Last edit at 11/01/2012 03:49PM by sambul14.
Re: Newer uBoot as workaround to 3.2 kernel problem?
November 01, 2012 08:52PM
TBH, I'm currently involved w/ a possible new job/position shift, as well as several other responsibilities... I can't put any more time into it right now...

=====================================================


Re: Newer uBoot as workaround to 3.2 kernel problem?
November 04, 2012 07:32AM
If you ever have time in the foreseeable future, you may want to look among others at this approach combined with one of those to identify a suitable drive with rootfs to boot from when several USB and SATA drives are hooked to GFN.

Another way to address the issue would be adding to Uboot tools a corresponding tool capable of scanning and listing all drives with rootfs hooked to GFN & GFH and other such Plugs.



Edited 1 time(s). Last edit at 11/04/2012 07:33AM by sambul14.
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 01, 2012 02:44AM
@sambul14: I've read some of your posts. The only solution I found is checking for the presence of an usb drive via trying to load the kernel from that place. If it is ok then root=/dev/sdb1, else root=/dev/sda1. If you remove SATA drive this approach doesn't work, but you DON'T really need to do that, or maybe yes?

The other option is install a little distro on nand space, this will avoid all your problems cause your GFN will boot everytime from nand, and just some shell scripting will be needed to handle your other mountpoints...

Quote

Another way to address the issue would be adding to Uboot tools a corresponding tool capable of scanning and listing all drives with rootfs hooked to GFN & GFH and other such Plugs.

This is NOT EASY & NOT NEEDED for daily basis work.

-- I've installed the distro in nand in all my plugcomputers (emdebian | armedslack | buildroot ) and minimized the bootloader enviroment & vars to what I need (just nand read.e & setenv bootargs & bootm).
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 01, 2012 08:23PM
Replying to my own previous post here, and to Handy1 who PMed me regarding this...

I will re-research the issue of GPT and 64bit support. IIRC, it requires at least two settings changed on the config.h file...

CONFIG_EFI_PARTITION (which may be a misnomer - perhaps GPT would be a better name for it) and CONFIG_SYS_64BIT_LBA .

Once I roll some trial uboot images, and test that they will boot normal stuff, then I can put them out there for a few of you to try with 3TB drives and a GPT layout.

The may of the rescue images that I built and posted lately have GPT support.

=====================================================


Re: Newer uBoot as workaround to 3.2 kernel problem?
December 25, 2012 10:23AM
I wnated to flash the uboot to my goflex net but all I am getting is following Error when i am executing the flash Script!

ubit0-6:/tmp# ./install_uboot_mtd0.sh --no-uboot-check


!!!!!!  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.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

-n If you agree, type 'ok' and press ENTER to continue:
ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |********************************************************************************************************************************|  1133  --:--:-- ETA
./install_uboot_mtd0.sh: line 250: head: not found
## Unknown uBoot detected on mtd0: 77ce1df732843774e5257b615ba8a9db
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
2
Selected Seagate GoFlex Net
./install_uboot_mtd0.sh: line 342: head: not found
./install_uboot_mtd0.sh: line 342: sed: not found

# Installing uBoot
## Installing goflexnet
Connecting to download.doozan.com (50.116.34.13:80)
wget: server returned error: HTTP/1.1 404 Not Found
Connecting to download.doozan.com (50.116.34.13:80)
wget: server returned error: HTTP/1.1 404 Not Found
## uBoot could not be downloaded, or the MD5 does not match.
## Exiting. No changes were made to mtd0.
ubit0-6:/tmp#

What am I doing wrong!?

And another question. On My GoflexNet I want to flash the Uboot to I am only getting this after issuing "fw_printenv" command:

ubit0-6:/tmp# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
ubit0-6:/tmp#


Thank you and greetings
Ron
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 29, 2012 11:23PM
I'm getting the exact same errors as BigRon :(

404 not found when running the script, and fw_printenv also says Bad CRC :( Using GoFlex Home :(

-Jamie M.
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 30, 2012 11:02AM
@Ron,

It's unusual that your prompt is "ubit0-6:". Did you run installation script from Pogoplug stock OS ? how did you begin? Booting without USB, loged in with SSH? ....

Also, why did you use the option "--no-uboot-check"? what happened before that caused you've decided to run the installation with this option? Normally, this option is not needed.
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 30, 2012 11:53AM
bodhi Wrote:
-------------------------------------------------------
> @Ron,
>
> It's unusual that your prompt is "ubit0-6:". Did
> you run installation script from Pogoplug stock OS
> ? how did you begin? Booting without USB, loged in
> with SSH? ....
>
> Also, why did you use the option
> "--no-uboot-check"? what happened before that
> caused you've decided to run the installation with
> this option? Normally, this option is not needed.
--------
My Seagate GoFlex Home is freshly done from these instructions, installing ubit 0.6, etc. etc: http://archlinuxarm.org/platforms/armv5/seagate-goflex-home#qt-platform_tabs-ui-tabs3

To install the new uboot script, it said you had to use --no-uboot-check

-Jamie M.
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 31, 2012 01:29AM
toysareforboys Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > @Ron,
> >
> > It's unusual that your prompt is "ubit0-6:".
> Did
> > you run installation script from Pogoplug stock
> OS
> > ? how did you begin? Booting without USB, loged
> in
> > with SSH? ....
> >
> > Also, why did you use the option
> > "--no-uboot-check"? what happened before that
> > caused you've decided to run the installation
> with
> > this option? Normally, this option is not
> needed.
> --------
> My Seagate GoFlex Home is freshly done from these
> instructions, installing ubit 0.6, etc. etc:
> http://archlinuxarm.org/platforms/armv5/seagate-go
> flex-home#qt-platform_tabs-ui-tabs3
>
> To install the new uboot script, it said you had
> to use --no-uboot-check
>
> -Jamie M.

Ah! you don't really need to install uBit. Installing uBoot will make it a little more straight forward, and works with both Debian and Arch (However, uBit should work, too). But not too many people run that to install Debian. We usually just run the install_uboot_mtd right from the stock Pogo OS.

Can you try to boot back to stock Pogo and run uBoot installation script from there. These errors should not happen (it indicates that the sed and head commands could not be found in the OS where you run installation):

./install_uboot_mtd0.sh: line 342: head: not found
./install_uboot_mtd0.sh: line 342: sed: not found
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 31, 2012 01:34AM
My friend was able to connect in remotely and get me all fixed up. Upgraded uboot to the latest version and upgraded my kernel, made a 20mb partition at the end of my drive for /boot and converted the rest to EXT4. Everything working sweet now :) Sorry, no idea how he did it, was going too fast for me to take notes :(

Linux version 3.6.10-1-ARCH (nobody@panda2) (gcc version 4.7.2 (GCC)
#1 PREEMPT Wed Dec 12 15:26:33 UTC 2012

http://tafb.yi.org

-Jamie M.
Re: Newer uBoot as workaround to 3.2 kernel problem?
December 31, 2012 07:24AM
The Arch GoFlex instructions don't say to skip the uboot check anywhere that I've seen. Could you post a link to where you saw that bit?

Davy, if you're respinning the uboot images, would you be up for doing some with Device Tree support enabled for testing?
Re: Newer uBoot as workaround to 3.2 kernel problem?
January 16, 2013 05:14AM
Kurlon Wrote:
-------------------------------------------------------
> The Arch GoFlex instructions don't say to skip the
> uboot check anywhere that I've seen. Could you
> post a link to where you saw that bit?

He probably meant this: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3355
Re: Newer uBoot as workaround to 3.2 kernel problem?
January 16, 2013 05:22AM
I might have found an issue with this uBoot:
Either there's something wrong with the kernel patch or uBoot doesn't pass proper arcNumber to the kernel on some devices. There's was a post in this where somebody could boot the kernel and the arcNumber wasn't what he set it to.
In my case (and others over at archlinuxarm reported similar problems) Pogoplug E02 gets recognised as SheevaPlug Reference Board even though arcNumber is set properly

dmesg | grep Machine
[    0.000000] Machine: Marvell SheevaPlug Reference Board

fw_printenv | grep arcNumber
arcNumber=3542

On my GoFlex Home, however everything is fine:

dmesg | grep Machine
[    0.000000] Machine: Seagate GoFlex Home

fw_printenv | grep arcNumber
arcNumber=3338

I've noticed that right after upgrading uBoot a while ago LED was orange as though arcNumber was not set properly, even though with the older uBoot and the same kernel LED was green. I didn't really pay attention at the time though.

Seeing how there are 2 different uBoot images for GoFlex and Pogoplug maybe something was forgotten in the Pogoplug version?



Edited 2 time(s). Last edit at 01/16/2013 05:29AM by moonman.
Re: Newer uBoot as workaround to 3.2 kernel problem?
January 16, 2013 07:18AM
moonman Wrote:
-------------------------------------------------------
> I might have found an issue with this uBoot:
> Either there's something wrong with the kernel
> patch or uBoot doesn't pass proper arcNumber to
> the kernel on some devices. There's was a post in
> this where somebody could boot the kernel and the
> arcNumber wasn't what he set it to.
> In my case (and others over at archlinuxarm
> reported similar problems) Pogoplug E02 gets
> recognised as SheevaPlug Reference Board even
> though arcNumber is set properly
>
>
> dmesg | grep Machine
> [    0.000000] Machine: Marvell SheevaPlug
> Reference Board
>
>
>
> fw_printenv | grep arcNumber
> arcNumber=3542
>
>
> On my GoFlex Home, however everything is fine:
>
>
> dmesg | grep Machine
> [    0.000000] Machine: Seagate GoFlex Home
>
>
>
> fw_printenv | grep arcNumber
> arcNumber=3338
>
>
> I've noticed that right after upgrading uBoot a
> while ago LED was orange as though arcNumber was
> not set properly, even though with the older uBoot
> and the same kernel LED was green. I didn't really
> pay attention at the time though.
>
> Seeing how there are 2 different uBoot images for
> GoFlex and Pogoplug maybe something was forgotten
> in the Pogoplug version?

Yes. Davy was aware of this, as I recall, and had a patched uBoot version. The work around right now for Pogo E02 is to also set the machid to the appropriate number. I've posted this somewhere in this forum.

Addendum:

Try this: fw_setenv machid dd6



Edited 1 time(s). Last edit at 01/16/2013 07:22AM by bodhi.
Re: Newer uBoot as workaround to 3.2 kernel problem?
January 16, 2013 07:39PM
Thank you bodhi, the fix works great.
Re: Newer uBoot as workaround to 3.2 kernel problem?
January 22, 2013 03:44PM
It's been a while since I've hacked on my arm hardware, but I still have a couple of pristine PogoPlug E02s which need to be jail broken and have their uBoot reflashed so that they can eventually become the backup hardware for when my existing servers bite the dust. I am wondering what is the latest uBoot that I should use for this purpose. I am still running Squeeze here, not Wheezy, so I need a uBoot which will boot Squeeze, but I'd prefer to install one which will handle Wheezy and the later kernels for when I eventually upgrade. Is the top post of this thread by davygravy still the best version and the one I should be using? I can use tftp to install it, as davygravy suggests, but I'd prefer to use an installer if one is available. (Fewer possibilities for cockpit errors.) So, can someone please point me to the latest and greatest uBoot and installer?

Thanks in advance.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: