Can you elaborate on the "mainline" comment? Does that mean the necessary changes are already included in the default uboot sources (http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary)? So if I download the latest uboot (v2012.07) and compile it with an appropriate toolkit I should get the same behavior that I get from using the images installed by the generica E02 install sby chackoc - uBoot
The following thread suggests a method for reverting, but I've never done it and I have no idea if it works. Also there is some discussion about future firmware updates from pogo possibly bricking the device down the road. http://archlinuxarm.org/forum/viewtopic.php?f=18&t=5388 So it does look possible but I would research the method a lot more before trying it. Also if you wby chackoc - uBoot
I was able to "fix" it by getting a cable and using it to manually modify the Arch install. If your uboot installed successfully, and the only issue is a bad block 6 preventing the env install, then I would imagine you'll be at the same position I was: Arch is loading successfully but since you weren't able to set the networking env variables the machine is loading the deby chackoc - uBoot
I've got an E02 that's currently running Arch from a USB thumb drive. A couple of the daily jobs running on the box require swap. At the moment I'm using a swapfile but as I understand it running a swapfile on a USB thumb drive can kill the drive quickly. Does anyone know anything about running swap on the NAND? I don't really know what NAND is so are there any issues wiby chackoc - Debian
I looked into this. Turns out the env value for ethaddr was already set but it still wasn't coming through to the Arch installation. I was still getting a random MAC (and thus IP from the router) every time. I ended up addressing the problem by using a PRE_UP command with macchanger to manually set the ethernet address prior to bringing up the interface. Appears to be working and I nby chackoc - uBoot
I don't think anything I did actually worked. As far as I can tell my env is still unusable because Block 6 is corrupted and uboot falls back to defaults. That's why I can't address the MAC issue, set up netconsole, etc. I'm simply able to work around the issue now so I'll likely focus on that rather than finding a way to get access to a user-modifiable env. In any caby chackoc - uBoot
Just to close this off, I got the cable and had a look at the bootup. It turns out arch was actually booting ok despite the corrupt block 6. There was a problem with the networking service that was preventing networking from working. This, combined with the fact that the LED stayed orange, led me to erroneously believe that arch wasn't even booting. I ended up fixing the networking iby chackoc - uBoot
Looks like the cable will take a while to get here so I'm going to stick this project on the back burner for now. Thanks again for all the help bodhi.by chackoc - uBoot
That makes sense. The compile instructions here (http://projects.doozan.com/uboot/build_uboot.htm) seem pretty straightforward and the patch mentioned (http://projects.doozan.com/uboot/patches/mach-pinkpogo.patch) does indeed appear to hardcode 0xc0000 as the position of the env. As long as those instructions aren't outdated recompiling with a modified patch seems plausible. Unfortunaby chackoc - uBoot
When I SSH into the new box the envs look ok (i.e. fw_printenv works and shows the stuff I added in). Are you saying that it boots up with default envs and then somewhere later in the boot process it picks up the custom stuff? Or is fw_printenv showing some theoretical environment that doesn't actually correspond to the running environment? I did notice that even when rebooting into theby chackoc - uBoot
No luck on reboot. LED stayed orange and there was nothing on my nc. I did notice that a new device showed up on my router with a random mac address so it ended up getting an IP other than the one i set as ipaddr with fw_setenv. That probably had something to do with not seeing any netconsole output. That device wasn't pingable though so not much I can do to test it. I'll play arby chackoc - uBoot
Thanks for the sanity check bodhi. I ran the modified script. It failed at first but then I cleared out the existing /tmp/uboot.environment file and it worked. (I guess wget was seeing the existing file and not redownloading a fresh copy?) I also corrected /etc/fw_env.config (thanks for that, never would have found it without the mention). Now when I rerun the modified install script evby chackoc - uBoot
I have a black E02. The install script appears to install uboot ok but fails when trying to install the environment. ... 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... # Vaby chackoc - uBoot