Newer uBoot as workaround to 3.2 kernel problem? You can now upgrade your older U-Boot using [url=http://forum.doozan.com/read.php?3,6965,8189#msg-8189][b]Jeff's U-Boot Updater Script[/b][/url] ... [b][color=#FF0000]but first[/color][/b] : 1. You may want check that your [b]netconsole[/b] or [b]serial console[/b] connection is working correctly, just in case. 2. [b]Before[/b] upgrading your U-Boot, it is a good idea to print out your U-Boot env and keep a copy of it as a file. This is especially important if you have made even the slightest alteration to the stock env. [u]After the installer finishes running [b][color=#3300FF][i]but before you reboot[/i][/color][/b][/u], make sure you check that you have your original values... a few of the values might have to be restored. ... [i]and if you don't want to do it by an automated script[/i] ... [b]MANUAL Directions for Upgrading Your U-Boot are Below!![/b] Kernel 3.2.y introduced a default setting for the kernel that affects kirkwood machines in particular, because of an unintended u-boot behavior with regard to the Level2Cache and decompression of the kernel image. Call it a latent bug in u-boot, a regression in the kernel, or whatever... the defconfig kirkwood kernel build of 3.2.y (and by extension, higher versions) will fail to boot in most/many cases. This left us with the choice between: [list] [*] not being able to boot a stock/normal debootstrapped Wheezy install (which will have a 3.2 or 3.3 kernel), and [u]not being able to boot into future stock Debian Kirkwood kernels[/u], or [*] [u]creating updated u-boot[/u] binaries that use the already-tested L2CacheDisable patch from Michael Walle (thanks Mike!) to the newest stable u-boot so [u]that a normal default kernel will boot[/u]. [/list] Since the kernel is updated more often than u-boot, it seems like it would be more of a hassle to kludge around it and compile a "special flavor" kernel just for kirkwood users. Working together, a few of us have put together patches and some basic testing to come up with updated u-boot images. [i]A big thank you to Robert Mugabe and Pazos.[/i] Our criteria were simple: [list=1] [*] make it boot 3.2 kernels and higher, with default (non-expert) config settings, as well as the older 2.6 and pre-3.2 stock Debian kernels, [*] base it on the newest possible stable u-boot release, in order to make future adjustments easier, [*] make it a drop-in replacement, fitting the footprint of Jeff's (etal) u-boot builds, [*] allow the Pogoplug software/firmware to function normally if a bootable rootfs on USB or SATA is not found, just as with Jeff's [*] no new features that would change the profile and, use the same u-boot environment space and values in NAND [*] fix a bug on SATA machines where a drive was not recognized correctly [/list] In short, "Keep It Simple, Stupid!", as much as possible. We know that folks running ArchLinuxARM and others use the u-boot that is piped out of this site, and we want to to be a seamless change for them, as well. At the moment, the following machines seem pretty much taken care of: [list] [*] [b]Dockstar[/b] [*] [b]Pogoplug V1/E01[/b] {same u-boot as Dockstar} [*] [b]Pogoplug V2/E02[/b] [*] [b]GoFlex Net[/b] & [b]GoFlex Home[/b] [/list] [Pazos tells me that the stock u-boot on his Iomega iConnect seems to boot 3.2 and higher kernels just fine, so at the moment, there is no reason to build a newer u-boot for it.] =========================================================================================== =========================================================================================== [b][u]Manual Directions for upgrading the u-boot on your Dockstar, Pogoplug, or GoFlex Net/Home[/u][/b]: 0. By doing any of the steps below, [color=#FF9900]you agree to hold me blameless[/color]. I've flashed my devices w/ my u-boots quite a few times now, but there are no promises. If you make a mistake, or if the power to your Kirkwood device goes off/fails while you are flashing it, your device might be bricked, recoverable only by JTAG. You have been warned. You are nevertheless invited to continue, but only if you accept risk and responsibility. 1. Prepare your equipment, data files and your brain. a. Backup your data and any contents you wish to keep. b. Read through to the end, and make sure you understand each step, and how to recover in case of a bad erase. c. Print out the contents of your NAND U-Boot env variables to a text file, or use nanddump. In either case, note your MAC address (aka hardware address, or [b]ethaddr[/b]). Make a mental note to yourself and check that is unchanged after the upgrade process. [mine didn't change ever, but YMMV] 2. You should consider having a serial cable/adapter so that you can connect to your Pogoplug, Dockstar or other Kirkwood device, for emergency recovery. 3. Either enable netconsole and confirm its functionality, or use a serial cable/adapter, so that you can control u-boot on your Kirkwood device. Make sure you understand how netconsole works before venturing into this, also. 4. Set up a tftp server on your desktop/laptop/other-computer. Confirm that tftp transfers are working before flashing anything. 5. Based on which machine you have, download and [b]_[color=#CC0000]untar/gunzip[/color]_[/b] one of these uboot.mtd0.kwb binaries: [list] [*] for [b][color=#FF0066]Dockstar[/color][/b] and [b][color=#FF9900]Pogoplug V1/E01[/color][/b] [wallwart-ish] : [url=http://dl.dropbox.com/u/1015928/Kirkwood/uboot/newer-uboots-nonEFI_GPT-TESTED/uboot.mtd0.kwb-2011.12-dockstar-L2Coff.tar.gz]dockstar and Pogoplug V[b]1[/b]/E0[b]1[/b] u-boot replacement[/url] filename=uboot.mtd0.kwb-2011.12-dockstar-L2Coff.kwb [*] for [b][color=#00FF00]Pogoplug V2/E02[/color][/b] : [url=http://dl.dropbox.com/u/1015928/Kirkwood/uboot/newer-uboots-nonEFI_GPT-TESTED/uboot.mtd0.kwb-2011.12-pogo_e02-L2Coff.tar.gz]Pogoplug V[b]2[/b]/E0[b]2[/b] u-boot replacement[/url] filename=uboot.mtd0.kwb-2011.12-pogo_e02-L2Coff.kwb [*] for [b][color=#0000FF]GoFlex Net/Home[/color][/b] : [url=http://dl.dropbox.com/u/1015928/Kirkwood/uboot/newer-uboots-nonEFI_GPT-TESTED/uboot.mtd0.kwb-2011.12-goflexnet-L2Coff-IDEpatched.tar.gz]GoFlex[b]Net/Home[/b] u-boot replacement[/url] filename=uboot.mtd0.kwb-2011.12-goflexnet-L2Coff-IDEpatched.kwb [/list] Put the desired uboot binary in the root directory of your tftp server. [i]*These images are based on 2011.12 source code, have all Jeff's features and capabilities, will boot the newer 3.2 (& higher) kernel, and contain a few minor fixes. I'll post patches ASAP. I'd originally thought to rework the patches based on 2012.6-ish source, but no further crucial changes would result from waiting for this, so its time to finish this.[/i] 6. (Re)Boot your Kirkwood device. Assuming it has one of Jeff's u-boot builds in NAND, when it powers up, you will see something like: [code] U-Boot 2010.09 (Oct 23 2010 - 11:51:16) Marvell-PinkPogo by Jeff Doozan SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 Marvell>> Marvell>> [/code] Press any key to stop the boot process. You may have to press the key several times, or even hold it down for several seconds. [b]a.[/b] Once you see the [b]Marvell>>[/b] prompt, check that you can pull in the image via tftp. Execute: [code] tftpboot 0x800000 [/code] where is taken from the matching filename above If this is successful, you should see something like this: [code] Marvell>> tftpboot 0x800000 uboot.pogoplugE02-arcNumfixed-L2Coff.kwb tftpboot 0x800000 uboot.pogoplugE02-arcNumfixed-L2Coff.kwb Using egiga0 device TFTP from server 192.168.11.149; our IP address is 192.168.11.150 Filename 'uboot.pogoplugE02-arcNumfixed-L2Coff.kwb'. Load address: 0x800000 Loading: #################################### done Bytes transferred = 524288 (80000 hex) [/code] The "Bytes transferred" value should be hex 80000 (decimal 524288) - if you don't get that value, then something is wrong. [b][color=#FF0000]STOP[/color][/b]: Before going further double or triple check to make sure you have selected the correct filename that corresponds with your Kirkwood machine [Dockstar, Pogoplug E02, GoFlex Net/Home]. Flashing the wrong file in your machine will possibly brick it. Double check before going further. The filenames [b]_must_ match[/b]. The "Bytes transferred" value [b]_must_ match[/b]. [color=#CC0000]If not, you should stop here and go no further.[/color] [b]b.[/b] Erase and flash; execute [code] nand erase 0x0 0x80000 nand write.e 0x800000 0x0 0x80000 [/code] If you have an erase/block problem, read through Jeff's original u-boot thread to see how people got around that problem. If the nand write went as planned, you should see something like this: [code] Marvell>> nand erase 0x0 0x80000 nand erase 0x0 0x80000 NAND erase: device 0 offset 0x0, size 0x80000 Erasing at 0x60000 -- 100% complete. OK Marvell>> nand write.e 0x800000 0x0 0x80000 nand write.e 0x800000 0x0 0x80000 NAND write: device 0 offset 0x0, size 0x80000 524288 bytes written: OK [/code] [b]c.[/b] If all is well, reset. [code] Marvell>> reset [/code] Your device should reboot now, but you will see newer uboot version information in the console or netconsole window: [code] U-Boot 2011.12 (May 28 2012 - 11:59:39) Pogoplug E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 [/code] You will now be able to boot a stock Debian 3.2 (or higher) kernel without having the decompression error that would cause so many Kirkwood machines to hang at boot time. If you followed this howto command-for-command, you [i]should[/i] not have to alter or restore any u-boot env variables. Of course, YMMV. ========================================================================================= This makes it look more official: we might be SOL if the 3.2 regression is indeed handled as "really just a latent bug in uboot". http://thread.gmane.org/gmane.linux.ports.arm.kernel/127951/focus=151172 Is anyone game to apply the L2cache disable patch? It looks like it may become a necessary upgrade if users want to use the mainline kernel inthe future. =========================== Has anyone tried this relatively new uBoot on their Dockstar? It looks like it was rolled by tbm (@debian.org)... http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html Hmmmm... sounds like a familiar problem: http://www.plugcomputer.org/plugforum/index.php?topic=5897.0 http://forum.doozan.com/read.php?3,6965,6965#msg-6965 Sun, 19 May 2013 05:47:57 -0400 Phorum 5.2.18 http://forum.doozan.com/read.php?3,6965,12423#msg-12423 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,12423#msg-12423
No, it's not safe to update uBoot for your NSA320 using the offical script. Unless you have assurance from Davy that you can use this standard installation script. But I don't think it will work.]]> bodhi uBoot Fri, 10 May 2013 18:42:17 -0400 http://forum.doozan.com/read.php?3,6965,12421#msg-12421 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,12421#msg-12421
I am currently trying to get a Zyxel NSA320 up and running. Using davy's basic setup, I am able to boot from a USB-drive, but the exact same rootfs on the first SATA drive gives: 

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!

No I am wondering whether I can safely upgrade to the official uBoot. I am somewhat put off by its output: 

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.

It would be just great if this listed the Zyxel NSA3xy devices ...

So:

a) Is it safe to update uBoot? (my guess: yes, since otherwise davy's rescue system post would not make much sense, would it?)
b) Will that take care of the SATA boot problem?


Help, as always, greatly appreciated.

Cheers,

chessplayer]]> chessplayer uBoot Fri, 10 May 2013 18:16:06 -0400 http://forum.doozan.com/read.php?3,6965,11794#msg-11794 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11794#msg-11794
Everything back to normal now! :)]]> varkey uBoot Sun, 10 Mar 2013 10:24:50 -0400 http://forum.doozan.com/read.php?3,6965,11527#msg-11527 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11527#msg-11527 -------------------------------------------------------
> 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?

Looking at kernel 3.6.x.x arch/arm/mach-kirkwood/, there is a mix of device tree implementation and old mach-types devices such as Dockstar and Sheevaplug. Would this new uBoot work with 3.6.x.x ?]]> bodhi uBoot Sat, 16 Feb 2013 17:30:01 -0500 http://forum.doozan.com/read.php?3,6965,11333#msg-11333 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11333#msg-11333
The fw_setenv machid dd6 statement is to correct an oversight in the current uBoot (Davy confirmed this). On Pogoplug E02, setting arcNumber to 3542 alone does not make uBoot pass along the archNumber to the kernel. So the work around is to also set machid explicitly using fw_setenv.

archNumber 3542 only works if you have a kernel with the Pogoplug E02 patch. If you have a vanilla kernel, then arcNumber must be set to 2097. So in this case, the HW is recognized as SheevaPlug Reference Board.

Yes, with arcNumber 2097, you can still control the LED, but as you've found, the LED does not turn green, and the control is limited. OTOH, if arcNumber is 3542, and the kernel supports it, then you can control the LED better (e.g. green, orange, blinking, and so on).

bodhi]]> bodhi uBoot Fri, 25 Jan 2013 09:41:13 -0500 http://forum.doozan.com/read.php?3,6965,11327#msg-11327 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11327#msg-11327
Unfortunately, for me, setting "machid=dd6" in the uBoot environment (with "archNumber=3542") did not work. It would act like it was booting, but wouldn't come up. (The front LED never illuminated after the uBoot passed control the the kernel.) I didn't investigate; I presume it had something to do with my using the 2.6 kernel instead of 3.2 and just deleted the machid setting from the environment.

However, for the record, could one of you explain what having "machid=dd6" set buys you? It looks to me like I'm still able to control the front LED -- turn it on and off -- even if the hardware is declared a SheevaPlug Reference Board. I can only turn it on as orange, but I think there is only an orange LED on the board, right?

So for now, I'm leaving the uBoot environment intact, but I now have two additional PogoPlugs ready to deploy if I need them. Thanks again for your help!]]> restamp uBoot Thu, 24 Jan 2013 19:09:11 -0500 http://forum.doozan.com/read.php?3,6965,11282#msg-11282 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11282#msg-11282 -------------------------------------------------------
> 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.

Welcome back restamp :) the latest uBoot has been incorporated to Jeff script. So you can just run http://projects.doozan.com/uboot/install_uboot_mtd0.sh to install uBoot only. It will boot Squeeze. Or you can run the completed http://projects.doozan.com/debian/dockstar.debian-squeeze.sh on your new Pogo E02 as before, to install both uBoot and Squeeze.

Also note that the machid for E02 was not set correctly in this uBoot version, so when you change arcNumber you should also change machid as described in a couple posts above.]]> bodhi uBoot Tue, 22 Jan 2013 23:41:52 -0500 http://forum.doozan.com/read.php?3,6965,11279#msg-11279 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11279#msg-11279 moonman uBoot Tue, 22 Jan 2013 18:45:20 -0500 http://forum.doozan.com/read.php?3,6965,11278#msg-11278 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11278#msg-11278
Thanks in advance.]]> restamp uBoot Tue, 22 Jan 2013 17:44:28 -0500 http://forum.doozan.com/read.php?3,6965,11178#msg-11178 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11178#msg-11178 moonman uBoot Wed, 16 Jan 2013 21:39:09 -0500 http://forum.doozan.com/read.php?3,6965,11171#msg-11171 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11171#msg-11171 -------------------------------------------------------
> 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]]> bodhi uBoot Wed, 16 Jan 2013 09:18:17 -0500 http://forum.doozan.com/read.php?3,6965,11170#msg-11170 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11170#msg-11170 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?]]> moonman uBoot Wed, 16 Jan 2013 07:22:50 -0500 http://forum.doozan.com/read.php?3,6965,11169#msg-11169 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11169#msg-11169 -------------------------------------------------------
> 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]]> moonman uBoot Wed, 16 Jan 2013 07:14:54 -0500 http://forum.doozan.com/read.php?3,6965,11025#msg-11025 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11025#msg-11025
Davy, if you're respinning the uboot images, would you be up for doing some with Device Tree support enabled for testing?]]> Kurlon uBoot Mon, 31 Dec 2012 09:24:49 -0500 http://forum.doozan.com/read.php?3,6965,11024#msg-11024 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11024#msg-11024
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.]]> toysareforboys uBoot Mon, 31 Dec 2012 03:34:10 -0500 http://forum.doozan.com/read.php?3,6965,11023#msg-11023 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11023#msg-11023 -------------------------------------------------------
> 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
]]> bodhi uBoot Mon, 31 Dec 2012 03:29:36 -0500 http://forum.doozan.com/read.php?3,6965,11020#msg-11020 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11020#msg-11020 -------------------------------------------------------
> @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.]]> toysareforboys uBoot Sun, 30 Dec 2012 13:53:22 -0500 http://forum.doozan.com/read.php?3,6965,11019#msg-11019 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11019#msg-11019
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.]]> bodhi uBoot Sun, 30 Dec 2012 13:02:44 -0500 http://forum.doozan.com/read.php?3,6965,11017#msg-11017 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,11017#msg-11017
404 not found when running the script, and fw_printenv also says Bad CRC :( Using GoFlex Home :(

-Jamie M.]]> toysareforboys uBoot Sun, 30 Dec 2012 01:23:53 -0500 http://forum.doozan.com/read.php?3,6965,10976#msg-10976 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10976#msg-10976 
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]]> BigRon uBoot Tue, 25 Dec 2012 12:23:28 -0500 http://forum.doozan.com/read.php?3,6965,10785#msg-10785 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10785#msg-10785
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.]]> davygravy uBoot Sat, 01 Dec 2012 22:23:18 -0500 http://forum.doozan.com/read.php?3,6965,10779#msg-10779 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10779#msg-10779
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).]]> pazos uBoot Sat, 01 Dec 2012 04:44:41 -0500 http://forum.doozan.com/read.php?3,6965,10556#msg-10556 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10556#msg-10556 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.]]> sambul14 uBoot Sun, 04 Nov 2012 09:32:16 -0500 http://forum.doozan.com/read.php?3,6965,10514#msg-10514 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10514#msg-10514 davygravy uBoot Thu, 01 Nov 2012 22:52:50 -0400 http://forum.doozan.com/read.php?3,6965,10502#msg-10502 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10502#msg-10502 -------------------------------------------------------
> 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?]]> sambul14 uBoot Thu, 01 Nov 2012 16:35:51 -0400 http://forum.doozan.com/read.php?3,6965,10405#msg-10405 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,10405#msg-10405 davygravy uBoot Sun, 28 Oct 2012 12:58:44 -0400 http://forum.doozan.com/read.php?3,6965,9784#msg-9784 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,9784#msg-9784 
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?]]> lyzby uBoot Wed, 03 Oct 2012 12:09:18 -0400 http://forum.doozan.com/read.php?3,6965,9208#msg-9208 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,9208#msg-9208 -------------------------------------------------------
> 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.]]> ysg2k5 uBoot Fri, 10 Aug 2012 12:48:49 -0400 http://forum.doozan.com/read.php?3,6965,9186#msg-9186 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,9186#msg-9186
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 !!
]]> Vlad uBoot Thu, 09 Aug 2012 14:34:17 -0400 http://forum.doozan.com/read.php?3,6965,9159#msg-9159 Re: Newer uBoot as workaround to 3.2 kernel problem? http://forum.doozan.com/read.php?3,6965,9159#msg-9159 cyb uBoot Wed, 08 Aug 2012 17:55:21 -0400