dinjo Wrote: ------------------------------------------------------- > Any help here on wget im getting 20% of my > download speed. No idea. It could be the site that you wget from is slow, have you tried wget with different sites?by bodhi - Debian
Awesome! Next question: which DTB you have used to append to the uImage? the link you posted above could not be translated to English!by bodhi - Debian
There is a newer u-boot for NSA320: http://forum.doozan.com/read.php?3,12381,16787#msg-16787 But you need to try with UART booting first to make sure it works before flashing to NAND. It has not been tried on NSA320S before so I don't know if it will work. So be careful!by bodhi - Debian
Jörg, IIRC, your u-boot version set rootfstype to Ext2. Ext3 would work, but just to make it consistent you should use Ext2.by bodhi - uBoot
balbes150, Cool! can you post the output of dmesg? and boot log if you have serial console.by bodhi - Debian
Jörg, Everything looks good. You are running davygravy 2012 u-boot and the envs were flashed successfully. davygravy's Pogo E02 u-boot does not flash LED during booting. Look for the Pogo in your network (it's dynamic IP) router. Or if you have smartphone, use Fing to scan all the nodes in the network. Next step If you can't find it: Do you have a log of how you created tby bodhi - uBoot
Buttzy, Do you have serial console log for this? dmesg is not enough, rootfs mounting progress is shown only in serial console.by bodhi - Debian
Buttzy, So the problem is only after you've installed OMV? booting USB with the basic rootfs is OK?by bodhi - Debian
punker Wrote: ------------------------------------------------------- > Hi, > > is there a kernel for my iConnect with bluetooth > support? > > lg Yes. http://forum.doozan.com/read.php?2,12096by bodhi - Debian
OK, You can SSH in to the pogo again and do this: http://forum.doozan.com/read.php?3,18917,18935#msg-18935 Remember to keep the log of everything.by bodhi - uBoot
Jörg, Execute with full path: /usr/local/cloudengines/bin/blparam > /tmp/u-boot-envs.txtby bodhi - uBoot
Buttzy, It sounds as though there is no power to the USB port.by bodhi - Debian
Buttzy, Your dmesg looks OK: [ 1.838190] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.844847] ehci-pci: EHCI PCI platform driver [ 1.849391] ehci-orion: EHCI orion driver [ 1.853641] orion-ehci f1050000.ehci: EHCI Host Controller [ 1.859174] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 1.867110] orion-ehci f10by bodhi - Debian
cr2013, The envs look quite ugly :) I know people have set it up this way long time ago to get it working with stock u-boot. Now it is no longer necessary when you install new u-boot. Back to the problem. This is suspected: bootargs=console=ttyS0,115200 ramdisk=32768 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f40000by bodhi - Debian
@duncan_h and others, I've updated the instruction regarding the uEnv.txt in the 1st post. I've modified it slightly to make it a little easier to remove the devices that are not availble (so you won't see the error messages about non-existing devices). D.1 Modify u-boot envsby bodhi - uBoot
Buttzy, Yes, with davygravy's u-boot (which does not have FDT support), the DTB must be appended to uImage. Everything looks great to me, espcially this about USB [ 2.243635] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 2.405385] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 2.412145] usb 1-1: New USB device strings: Mfr=0, Product=1, Sby bodhi - Debian
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