Hi chessplayer, > I just germanized and beautified your basic install, as I always do to get my own base system. Cool :) Thanks for pointing out, I did not notice that. Will take a look, perhaps something has changed in the mainline code. And you probably refered to this above: the same info can be extracted from dmesg, too. root@tldDebian:~# dmesg | grep -i bogomips [ 19.63369by bodhi - Debian
Kuduku, That setenv is only temporary. To make it permanent, save the env. I prefer to do this in Debian fw_setenv usb_rootfstypeby bodhi - Debian
Hi kuduku, Perhaps retracing your steps: if you've created the rootfs as root user? is the pen drive partition Ext3? if you've confirmed these are correct. Try this also: remove the usb_rootfstype env in serial console before booting. setenv usb_rootfstypeby bodhi - Debian
Kuduku, It's not your archNumber or machid. arcNumber 2097 is fine for booting Pogoplug E02. Note these: [ 10.627259] scsi 0:0:0:0: Direct-Access USB2.0 CARD-READER 1.01 PQ: 0 ANSI: 2 and mount: mounting /dev/disk/by-label/rootfs on /root failed: Invalid argument I think your card reader is a little slow to be fully up. Likely udev (i.e. initrd), did not get the rootby bodhi - Debian
kuduku, Continue using rootfs 3.14.0-kirkwood-tld-1. Label the USB drive partition, and set U-Boot envs as described here: http://forum.doozan.com/read.php?3,8044,8152#msg-8152 The basic idea is to tell Linux to find the rootfs with label "rootfs".by bodhi - Debian
Of course, but I have not finished reading this part of the code either, never had to :-) so please take that with a bunch of grains of salt! On the surface, it seems so. Furthermore, the U-Boot location in RAM could also be calculated and placed at somewhere in higher or lower memory. If it's placed at lower memory then it must falls in where the 5MB is, then your guess is more correct. Iby bodhi - uBoot
- Partition boot flag does not really matter, but it's good to set it to active anyway. - This is a Certified Refurbished GF Home? did you check the power adapter to see if it is the GF Home 2V 2A apdapter? - Bus error is one of the symptoms when the drive is failing. What brand of USB thumb is this one?by bodhi - Debian
I think you probably mixed up the 2 locations (NAND vs. RAM) U-Boot is at higher memory (see include/configs/ox820.h): #define CONFIG_SYS_TEXT_BASE 0x64000000by bodhi - uBoot
I think 5MB is a bit high, too. There should be data in the first 5MB before where the kernel is loaded, but it would not be that big. However, I think this is one of those undocumented details. I'm guessing 5MB is just a convention to make it large enough so it would not run out of space for dynamic data like boot parameters (i.e. they don't know what the kernel users will include in bby bodhi - uBoot
narddawg, QuoteI tar -xjvf the latest Debian-3.14 rootfs to the root of the usb drive as root user? must be root user, sudo won't work. When you see IO errors occur frequently, then probably the USB thumb is failing.by bodhi - Debian
Yes I did misunderstand your post :)by bodhi - uBoot
Perhaps the reason is in include/configs/ox820.h. But my calculation for some address did not match up!by bodhi - uBoot
I have not looked at the new U-Boot source yet, so not sure either. But am wondering where in RAM is U-Boot relocated to. Could that be the reason?by bodhi - uBoot
Make sure that U-Boot env for rootfstype is set to ext3 #fw_printenv usb_rootfstype usb_rootfstype=ext3 Better yet, post your output of fw_printenv and we'll verify if anything peculiar, if you'd like to.by bodhi - Debian
Looks like your USB thumb drive has gone bad or was mounted as RO for other reason. Check the mount status, see if the rootfs was mounted as ro: mountby bodhi - Debian
@ingmar_k, I finally have some time to take my PogoPro off line and play with it :). I've read most of the posts in the "A new kernel for oxnas" thread at Arch site. Thanks navym/kref, ingmar_k and others for valuable information about the effort to get this to run the latest kernel. Using kref GitHub source, I've built the kernel 3.12.13 oxnas and it works great with mby bodhi - uBoot
dinlaca, You have missed a crucial step by installing this U-Boot manually from stock U-Boot. The manual instruction indicated that the starting point is after you have already installed U-Boot with Jeff's script and now want to upgrade. Jeff's script installs U-Boot image and also flashes a good U-Boot envs image which include all the envs needed to boot with USB. Quote This assby bodhi - uBoot
Hi Malc, I tried to compile this U-Boot using your patch above, applied on top of Pogo CE source. It was compiled natively (I've changed the Makefile to comment out CROSS_COMPLE). I got this error, any idea why? I'm guessing that I missed an include file somewhere that contains the #define for some of the values. arm-linux-gnueabi-gcc -DMV_SEC_256K -DMV_BOOTSIZE_16M -DMV_LARGE_by bodhi - uBoot
karolp, Please post in this NSA325 thread: http://forum.doozan.com/read.php?2,14351 Somebody might have ideas how to troubleshoot this. Even though this kernel has NSA310 patch, it is basically still untested (not enough feedback, so I have no idea if it works well or not).by bodhi - Debian
Kernel linux-3.14.0-kirkwood-tld-2 package was uploaded. Please see 1st post for download link.by bodhi - Debian
This is encouraging. On a whim, I plugged the Sandisk ReadyCache into the Pogo V4 booting with stock Marvell/ALARM U-Boot, and it recognized the disk and booted without problem! U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFD60 Soc: 88F6192 A1 (DDR2) CPU running @ 800Mhz L2 running @ 400Mhz SysClock = 20by bodhi - Debian
Hi laprjns, netconsole does work in uboot.2014.01-tld-1 for dockstar. Is there anything peculiar about the 3rd setup hardware-wise, e.g. bridge, switch...? To look at u-boot version without serial console: grep -a --null-data U-Boot /dev/mtd0roby bodhi - uBoot
kraqh3d, Yes, the Stora is in addition to all other Kirkwood plugs. Aggree, I would boot the NSA320 with a pristine rootfs 3.14.0-tld-1 on USB, upgrade it to tld-2 kernel, and take the USB to the Stora. Boot the Stora and interrupt serial console, set arcNumber to the Stora's, and set bootargs to appropriate settings, and boot it without saving envs.by bodhi - uBoot
kraqh3d , Bummer! I wonder what is the difference between your Stora and heychrist's Stora, could it be the boot ROM version?. And have you tried booting with stock U-Boot, and the basic 3.14.0-tld-1 rootfs, with 3.14.0-tld-2 kernel installed on top, on a USB thumb? And I had seen similar initrd problem on my plug in the past. I think it's a bug in the process of creating the Debiby bodhi - uBoot
Val532, Here is the u-boot image for the Lacie D2Net_V2. uboot.2014.01-tld-1.d2net_v2.bodhi.tar md5: 7cbefcb8042c4fdc7711deefa846a97f I don't have the Lacie, so cannot test it. So please do not flash to mtd0. Boot with UART first as instructed by davygravy. Also, please post the entire boot log when you can connect UART and boot.by bodhi - uBoot
Goetz, > Do I've to do anything special when loading uboot > with JTAG? Same as I responded to other poster here in Debian section: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirateby bodhi - uBoot
Have you looked at this post? http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirateby bodhi - Debian
narddawg314, - Sync is so that it flush all the writes to the USB. - No need to change any network settings, it's dhcp. I think you are probably having some kind of network or hw related problem. Check your ethernet cable, make sure you're booting with only the USB attached... things like that.by bodhi - Debian
Some time you have to ctrl-c and kwboot again for several times before the handshake woks! E.g. The Pogo V4 needs 3 to 20 tries before the handshake occurs.by bodhi - uBoot
kraqh3d, Simplest way is to use the kwboot I posted in the 1st post http://forum.doozan.com/read.php?3,12381 that if you can connect serial cable from another kirkwood plug.by bodhi - uBoot