HighTower, To run new kernel/rootfs on HDD, you will need to install new U-Boot and install new kernel on your current rootfs, or get the new rootfs that I uploaded and use that. Running new U-Boot using UART is the same as running U-Boot from NAND. There is no difference after U-Boot is loaded. So there is no need to install U-Boot first. Just boot the box with new U-Boot using UART, and iby bodhi - Debian
HighTower, > so, I'm still wonder what to do next.. i checked > via uart that new uboot can be used. > You could flash u-boot in serial console. However, running new U-boot with old kernel is really overkilled, there is no point in doing that, IMO. So it is best to stay with UART booting, try to get the new Debian rootfs running first. After that, the rest is pretty easy.by bodhi - Debian
OK. Let's go back to the basic. The idea is to make the output of your printenv looks like mine. yours: baudrate=115200 bootargs=root=/dev/nfs nfsroot=: ip=::::::off bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 ethact=egiga0 ethaddr=00:25:31:04:88:1D machid=dby bodhi - uBoot
I've just notice this. It does not look like a typical /root directory either. Do these files show up if you look at /root in another Linux box? ext2ls mmc 0:1 /root <DIR> 4096 . <DIR> 4096 .. <DIR> 4096 empty <DIR> 4096 games <DIR> 4096 opt <DIR> 4096 spool <SYM> 10 mail <SYM> 6by bodhi - uBoot
Looker, Yes, the u-boot envs that are needed to boot USB drive are not defined at all, they were gone! Below are what usually defined: ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand parby bodhi - uBoot
Looker, You are in good shape as long as you can see the u-boot prompt like that! I think your u-boot envs might have been messed up for whatever reason. So the first step is to get a listing for that at the u-boot prompt > printenv Most definitely, you only need to adjust u-boot envs to correctly boot the Arch rootfs on USB.by bodhi - uBoot
velo, Pls see my questions updated above. Copying /boot/uImage to /uImage as a work around is a nice temporary solution! but I'm still wondering why there is a difference.by bodhi - uBoot
Have you tried the latest Arch rootfs ? Both Debian and Arch have /boot/uImage, so the difference as shown is strange indeed. Update: Were both extracted into the same SD card? what fs is the card (ext2/ext3)?by bodhi - uBoot
HighTower, To use fw_setenv and fw_printenv, you must install u-boot-tools package first. apt-get install u-boot-tools And make sure your Debian env config file is consistent with this u-boot: # cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000by bodhi - Debian
My pleasure :) It took some minor retrofitting to rebase this Oxnas 3.12 kernel to 3.14 (common PCIe kernel interface changes). I did try to look at OpenWrt patch, but due to my unfamiliarity with it, I could not see exactly what changes they've made!by bodhi - Debian
Nice! you can see the links I posted previously for how heychrist set u-boot envs and the new 3.14 kernel I've uploaded. This U-boot set the envs at 0xC0000 which is the same as other Kirkwood boxes, but the Stora uses a different location, so you need to set them manually and save at least once to get rid of the error message: *** Warning - bad CRC, using default environment BTW, Iby bodhi - Debian
Kernel linux-3.14.0-oxnas-tld-5 package was uploaded. Please see 1st post for download link.by bodhi - Debian
FYI. openssl update. https://www.debian.org/security/2014/dsa-2931by bodhi - Debian
The easiest thing to do is to create a rootfs on USB thumb drive, get it from here: http://forum.doozan.com/read.php?2,12096 Boot with this, and then while in Debian you can figure out why the Rescue system did not boot. If you're trying to install a new Debian system, then you can continue using this rootfs, too, as a a starting point.by bodhi - Rescue System
U-Boot 2013.10 image was uploaded. Please see 1st post for download link and instruction.by bodhi - uBoot
Try this ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.01-tld-1.netgear_ms2110.mtd0.kwb -pby bodhi - Debian
HighTower, Sorry you're out of luck here! I don't know if there is any kwboot that was built for Intel boxes. You could try to search for that. It's important because this is the recovery path when and if anything goes wrong. I don't know if the Stora can be recovered using JTAG (since I don't own one).by bodhi - Debian
HighTower, See this thread for new u-boot: http://forum.doozan.com/read.php?3,12381 This thread for latest kernel and rootfs: http://forum.doozan.com/read.php?2,12096 And this was the Stora u-boot working thread: http://forum.doozan.com/read.php?3,14931 If you decide to install u-boot, make sure that you can boot with UART first. Your boot ROM version is 00000121, so it shoud be abby bodhi - Debian
velo, The MAC address printed on the sticker is the right one, always. You'll need to set it in your network interfaces config file (in Debian it is in /etc/network/interfaces). Or set it in your u-boot env: fw_setenv ethaddr xx:xx:xx:xx:x If one was assigned and it's not the same as one on the sticker, then it was assigned by the kernel, or u-boot temporarily.by bodhi - uBoot
I've also posted this problem at Arch site to get more feedback. ---------------------------------------------------------------- Netconsole problem in kernel 3.12.13 oxnas. Did anybody set up netconsole in Arch successfully? I'm seeing this problem running Debian and I thought it is probaly in Arch, too. Apparently, the carrier detect happened so fast that it was deemed untrustwby bodhi - Debian
Thanks ingmar! hmm, wondering why my patch was not successful. I'll try again.by bodhi - Debian
velo, 1. After you've connected the serial cable hardware, you can use putty on Windows, Terminal on Mac, or picocom, screen,... on Linux (there are many other programs on Linux). See varkey's instruction on his website (it's for the GoFlex Net, but the communication settings are the same for all Kirkwood plugs, and the Pogo V4 is one): http://varkey.in/seagate-goflex-net-seriby bodhi - uBoot
Here is post that has Pogo V3 Classic DTB attached (it's untested). It might work with the Pogo Pro kernel. http://forum.doozan.com/read.php?3,15912,16053#msg-16053 And I've updated 1st post to add more info.by bodhi - Debian
@Ingmar, No, I haven't. I did try to bring it to 3.14, but patching has some strange problem and I have not looked further. I thought the openwrt is a straight patch from kref sources. Perhaps you know there is more patch on top ?by bodhi - Debian
thebladerunner, The kernel/rootfs that I uploaded in this thread is the latest out there. Thanks to kref works. The summary for the current status re Pogo V3: - new U-Boot is available (but I have not uploaded it yet). See here. - new Debian kernel and wheezy rootfs are available. - installation must be done manually (no script) You are running the B01, which does not have PCI, I assuby bodhi - Debian
Rootfs Debian-3.12.13-oxnas-tld-5 was uploaded. Please see 1st post for download link.by bodhi - Debian
Arnaud, You should check your USB rootfs for errors with fsck. Also list your files with so that it sorted by time stamp, ls -l is a little hard to read (while I am trying to read French :). ls -lartby bodhi - Debian
helpless, The symptom indicates that you're probably running an old U-Boot (perhaps 2009)? Old U-Boot does not work with kernel 3.2.xx and later. If that's true, you should restore your usb stick to the previous back up before the upgrade, and then install the latest kernel here: http://forum.doozan.com/read.php?2,12096 Make sure you have a back up stick, too. Since your kernel iby bodhi - Debian
Kernel linux-3.12.13-oxnas-tld-5 package was uploaded. Please see 1st post for download link.by bodhi - Debian
DavideDG, I've included all LM sensors in the kernel as modules. You might check to see if the specific LM sensors for NSA325 V2 are loaded. CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM70=m CONFIG_SENSORS_LM73=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_by bodhi - Debian