Jörg, This install_uboot_mtd0.sh can not be run on the laptop. This u-boot installation script must be run on the pogoplug itself. My recommendation: 1. Make rootfs on another Linux box, use a single Ext3 partition (following instruction in the kernel thread I posted above). 2. SSH into the Pogo OS and run: cd /tmp wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.shby bodhi - uBoot
> > Fdisk /dev/sdb, o, n, 1st partition using full > disk, w > mkfs.ext2 /dev/sdb1 (tried both ext2 and ext3 with > no change) > e2label /dev/sdb1 rootfs > mount /dev/sdb1 /meda/sdb1 > cd /media/sdb1 > tar -xjf > /home/user/Debian-3.17.0-kirkwood-tld-1-rootfs-bod > hi.tar.bz2 > > <insert whole FDT mkimage procedure here, placing > iconneby bodhi - Debian
Thanks Wzl!by bodhi - uBoot
duncan_h, Cool! thanks for reporting your observation. These default envs are my initial cut, they have a lot of room for improvement :) I plan to update them to make it boot a little cleaner (to remove misleading messages such as you saw). > A serverip entry in uEnv.txt doesnt change the > netconsole server, because that gets started in > preboot, before it is reset in > boby bodhi - uBoot
Jörg, > The LED is blinking orange and than stay solid green. > Without an USB key the Pogo OS starts normal and I > can SSH. Then it is easy. 1. Download the basic Debian rootfs 3.16 or 3.17. Following the instruction, put it on the USB thumb drive and see if you can boot with it. 2. If you can't boot into Debian, then boot to Pogo OS, ssh in and get the envby bodhi - uBoot
droidbox, The new u-boot version would solve your problem with the bad NAND block at 0x000c0000: http://forum.doozan.com/read.php?3,12381 See the instruction in section B and D. Basically, you need to copy the file uboot.2014.07-tld-2.environment to uEnv.txt and put it in /boot directory.by bodhi - uBoot
I've uploaded 2014.07-tld-2 U-Boot images. Please see 1st post for download links. Note that the Netgear Stora and Sheevaplug are still under testing and need feedback. Testers wanted!by bodhi - uBoot
Jörg, When asking for solution, it's best to state the problem first. Your post does not have much information that enable others to see what the problem is. Gree LED ligth blinking and and then stay solid usually means the rootfs can not be mounted. But it is just an educated guess. Here are the information you will need to provide: 1. Pogoplug model 2. How many drives are plugged iby bodhi - uBoot
Buttzy, It's hard to tell what the problem was without seeing the log. But as a reminder, if booting kernel 3.17 with stock u-boot, dtb must be embedded inside uImage. And with this booting method, u-boot envs changes must be the same as in kernel 3.16. If you can boot the new u-boot with UART, then I would upgrade it.by bodhi - Debian
droidbox Wrote: ------------------------------------------------------- > Hi, i have install the 3.17 kernel on my booting > debian stick. now i see this message > > 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 > (Re)by bodhi - uBoot
droidbox, cat dts/kirkwood-goflexnet.dtb >> zImage.fdt should be cat dts/kirkwood-pogo_e02.dtb >> zImage.fdtby bodhi - uBoot
1. Booting problem: Quote(Only thing I did differently was added a 256MB swap as part #2 at the end of the disk and filled the rest of the space with an Ext3, #1, labelled rootfs. Not sure how much that changes things but am taking a wild guess of not much), and untar'd the rootfs to it. Of course it did! the error you have below is with mounting rootfs. [ 12.714310] VFS: Cannot opby bodhi - Debian
Adam I always recommend upgrade u-uboot to take advantage of new features. But with pogo e02 you have to be extra careful, because recovery path is Jtag. There is no UART booting.by bodhi - Debian
Adam, > if you would still like me to post the list of > u-boot envs, i will, but right now im just super > pumped that they are working! No need to. > cd /tmp > wget > http://projects.doozan.com/uboot/install_uboot_mtd > 0.sh > chmod +x install_uboot_mtd0.sh > ./install_uboot_mtd0.sh > > after the script was done, i put in the new flash > dby bodhi - Debian
Buttzy10169 Wrote: ------------------------------------------------------- > Thanks Bodhi. > > Will the commands for flashing be the same as for > absintos? > > And any idea on the usb's problem? It's same as in this thread: http://forum.doozan.com/read.php?3,12381 Sorry I am not sure what USB problem?by bodhi - Debian
cr2013, You can do all that with new u-boot and new Debian rootfs. But the first step is to connect serial console and get the listing of your u-boot envs: Interrupt serial console at countdown, and then > printenv Steps: 1. Try to boot the new Debian rootfs first 2. Update u-boot 3. Modify u-boot envs to boot correct drive in multiple drives configuration.by bodhi - Debian
Adam, Don't worry about the errors you saw. Just download the latest rootfs (3.17). And put it on an EXT2 drive and boot with it. And please get a list of your u-boot envs and post here (there is further improvement to do, especially whether the rootfs type is ext2 or ext3) If you can't boot with the new rootfs, then in netconsole, use: printenv If you booted into Debian, usby bodhi - Debian
droidbox, These are the relevant default envs: arcNumber=2097 bootcmd=run bootcmd_usb; usb stop; run bootcmd_pogo; reset bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot; usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi; set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootby bodhi - uBoot
I think perhaps it's time to do a serious merge from Kirkwood config to OXNAS config. Ingmar has not said so yet again, but I can read mind :))by bodhi - Debian
droidbox, You are running Jeff/davygravy u-boot build so I need to see the default envs. Please interrupt serial console and print out your u-boot envs: u-boot>> printenvby bodhi - uBoot
@droidbox, You can't completely repair this. The bad block is at the env location for this u-boot version. And also is for my u-boot build images. It's a common location we've chosen for these Kirkwood boxes. However, there is a work around that will allow you to boot successfully. I'll post the instruction later today.by bodhi - uBoot
jfp, Not very detailed, but this is all we got: http://www.denx.de/wiki/view/DULG/CommandLineParsingby bodhi - uBoot
@Sagittarius, > EDIT: booting on a USB key made it possible. It is OK now?by bodhi - uBoot
droidbox Wrote: ------------------------------------------------------- > Hey bodi, > > thanks for your answer. I read the guide, but it > is for a Pogo V4/Mobile Device. > I have a Pogoplug E02. > > It is right? > > droidbox Yes. Just use it as a guide for comparing bootcmd. Pogo V4 has different mtdparts, archNumber, machid (so don't use that). Buby bodhi - uBoot
Buttzy, Looks good to me. U-boot is in the 1st 1M and no bad block in it. But please try UART booting first to make sure you have a rescue mechanism. Also, remember to save your envs listing, you will need to copy/paste them back in serial console (new u-boot envs are at different location).by bodhi - Debian
automatux, I'll build the next version and include it.by bodhi - Debian
automatux, Do you know the modules names?by bodhi - Debian
Take a look at this post: http://forum.doozan.com/read.php?3,16148,16148#msg-16148 And use it as a guide to fix your missing envs,by bodhi - uBoot
@Don, I've been using the Pogos cluster mostly as compile farm for home use. As far as other distributed processing researches using these, I'm afraid that I can't discuss.by bodhi - Debian
Mark, Very good serial console instruction by varkey (it's for a GoFlex Net, but should give you an idea in general for how to unbrick these pogoplugs). You might have to do some soldering if your plug does not have a header. http://varkey.in/seagate-goflex-net-serial-connection/ The link you posted above is very good, too. Which plug do you have? If you decide to purchase and cby bodhi - Debian