@Neptune, I think the reason it did not boot was because you running an older version of U-Boot: U-Boot 2010.09 (Feb 16 2011 - 18:42:02) UBIT v0.6 by Jeff Doozan and Peter Carmichael And your Arch rootfs has kernel 3.14: Image Name: Linux-3.14.4-1-ARCH Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3965072 Bytes = 3.8 MiB This U-Boot is too old for yourby bodhi - Rescue System
agiorgio Wrote: ------------------------------------------------------- > The plug was running Debian Squeeze, and I > replaced the root filesystem on the USB hard disk > with shv's Wheezy one. That seemed to work > perfectly. It's been a while since I hacked that > plug to run Debian, and I don't remember exactly > what I did. I'll probably end upby bodhi - Debian
basti523, > The front led is not glowing, never. when i push > the reset button on the motherboard the ethernet > port led is blinking one time and then nothing. I'm afraid it sounds like you've messed up your NAND mtd0 where u-boot is. The Pogo E02 does not have UART booting, AFAIK. The only way to recover is JTAG. On the very slim chance that somehow your Pogo E02by bodhi - uBoot
agiorgio, Quote> I decided to upgrade this pogoplug to Debian Wheezy Did you follow a procedure, instruction …? which u-boot is currently on your Pogo? if not, which system were you running before, and what exactly did you do before seeing CRC error with fw_printenv? There is not enough information, so a wrong advice could mess up your u-boot envs and brick your box!by bodhi - Debian
@varkey, Yes it does! bootcmd is set up to boot USB, SD, SATA in that order. So if you plug in only SATA it will boot SATA.by bodhi - uBoot
agiorgio, > I don't have a serial cable, so I'm nervous about > running fw_setenv and rendering the unit > unbootable. Any tips? Pls describe what are you trying to do, preferably with the full log. The CRC error usually indicates that the envs area in NAND has not been saved, therefore has no checksum.by bodhi - Debian
nnSlick, > I guess after we installed your new 2014.7 uBoot, > we can use the fw_setenv command to change the mtd > partition layout, am I correct? Yes. You can repartition anyway you'd like if you don't care to run stock FW. And after you've installed new U-Boot, always keep the first partition (mtd0) untouched. The rest of NAND can be anyway you'd like, andby bodhi - Debian
grayman4hire, You should try my latest u-boot Pogo V4 build. ./kwboot-tool/kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p And here is how you boot the Pogo Mobile (it is different from other Kirkwood boxes, a little bit flaky): - Start kwboot on a different Linux box using the above command. - Power up the Pogo V4/Mobile. - Within 1-2 seconds when the spiby bodhi - uBoot
@shv, Thanks. I will give it a try when my direct connect 22pin-eSATA cable arrive.by bodhi - uBoot
@shv, I do have both ethaddr and /etc/network/interfaces set to the same value. No problem on kernel 3.15.3. And it is the same rootfs that I have since squeeze. I think if you look at serial console output closely, it might give out some hints.by bodhi - Debian
grayman4hire, On which box and what is the source for this u-boot.bin?by bodhi - uBoot
shv, > Is there anything special for Debian modules? Not really. I was just curious and not aware about your build (since I put the Pogo Pro on the back burner for a while).by bodhi - uBoot
@shv, Cool! did you compile that kernel? i.e. the modules in /lib/modules are Debian modules ? > /boot/uImage_2.6.31.14_OX820_1.2_shv.Pro;by bodhi - uBoot
shv, Quotenetwork startup is not working. Does the /etc/network/interfaces contain the MAC address? Quotehwaddress ether XX:XX:XX:XX:XX:XXby bodhi - Debian
ingmar_k, Quote> I woud guess that the implemented DMA mechanism > simply was better suited to the CPU, in the stock > kernel patches. Agree. That sounds very probable to me too. Too bad if we have to go back to Ext2 to get the performance back.by bodhi - Debian
agiorgio, Quote> I rebooted back into my working Debian install, > but this time I had both the USB stick and HDD > plugged in. If I check the kernel dmesg, I see > this interesting set of entries about my disks. I > wonder why this drive is being detected as using > 512-byte sectors? I think because of this: Quote> [ 47.836848] sdb: unknown partition tableby bodhi - Debian
@shv, Nice works! interesting to see the hard numbers. Have you tried Ext2 to see if read performance is back to normal? @ingmar_k, QuoteStill very interesting to see that the old kernel performs best, when it comes to SATA.. Indeed! I'm wondering could the OXNAS SATA driver be improved somehow.by bodhi - Debian
@shv, Not at the moment. We can boot 2.6.3xx Arch Linux ARM kernel but not Debian.by bodhi - uBoot
@shv, Awesome! thanks for letting me now. So either my eSATA enclosure is not recognized, or the u-boot-spl.bin was not dd correctly (which I'd doubt to be the case because I used WarheadsSE's disk_create script to do that).by bodhi - uBoot
@shv, I did not want to commit to GitHub before testing. I'm having problem booting with the SATA spl. It did not get loaded by ROM during powered up. I don't know if my eSata enclosure is the culprit or not (I don't have a 22 pin-eSATA+power cable to try a direct connect right now). Here attached is the updated board/ox820/ox820.c file. You could try to rebuild with it. If yby bodhi - Debian
QuoteIII why in the hell you need arch with that machinegun-like question fire rate? I've always thought of arch-users as of doers not talkers. I mean if you don't know how to use the tool, maybe you shouldn't? ) LOL. @vaidyasr, I'm banning you from this thread :)) Kidding aside, again, pls post in a new thread for questions that are not related to this U-Boot.by bodhi - uBoot
@shv, I found an inconsistency between NAND and FAT compilation options. That was why the LED flashing code that I've added compiled for NAND but not for FAT. U-Boot has built OK now. Would you like to test it?by bodhi - Debian
absintos, > zyxel nas320 btw…. Then try UART booting with the new u-boot test build I've justed uploaded: http://forum.doozan.com/read.php?3,12381,16787#msg-16787 I have high hope that it will boot the latest kernel.by bodhi - Debian
agiorgio Wrote: ------------------------------------------------------- > I don't have a log, but I'm willing to start over > with a clean Debian install. I'm willing to do > anything short of destroying the data partition on > that drive. Could I just create a new ext3/ext4 > fs and untar a Debian rootfs onto it? If so, do > you have a link to a Debianby bodhi - Debian
shv Wrote: ------------------------------------------------------- > bodhi, > if I try to compile your git sources with ext4 or > fat configuration it stops due to compilation > problems. NAND and SATA configuration seams to be > OK. > > -shv I've just found the same thing. There's compilation problem with FAT. I'm not sure yet but I think #defineby bodhi - Debian
@agiorgio, Sounds like a problem with disk partition/file system preparation, if you have the log of what you did, please post here.by bodhi - Debian
@NSA320 users, U-Boot testers wanted! http://forum.doozan.com/read.php?3,12381,16787#msg-16787by bodhi - uBoot
grayman4hire Wrote: ------------------------------------------------------- > Thanks for posting this. > > Can you clarify if this is for the Pogoplug Series > 4 or Mobile or does it even matter? > > Also, what are the instructions for restoring the > various mtd partitions back? Thanks I think it's the same for V4 or Mobile (you would have to try to confirmby bodhi - uBoot
Shv, I dont think my spl image works in SATA mode. But you could try. NAND and SATA versions are built differently. I'd doubt that it would work.by bodhi - Debian
grayman4hire, > I'm a little confused regarding the mtd > partitions. So can we leave the mtd partition as > stock? You could set them back to stock, I don't see any problem with doing that.by bodhi - uBoot