Problem with 3.13.1 NFS rootfs above solved! I've rebuilt with mvmdio and mv643xx_eth modules included in the kernel directly (previously loaded by initrd), and no longer see the error, the kernel is now booting with NFS rootfs. Will upload newer version shortly.by bodhi - Debian
freebird, > Is there a way to get the rootfs to a USB stick > directly (rather than via deb files) or flash the > updated uBoot from within the current uBoot > environment? Yes for both. The installation for the rootfs can be done using any Linux box. If the only one available is this GoFlex Home, then you can use a Linux Live CD on a PC or Mac. The latest rootfs and insby bodhi - uBoot
Freebird, Your uBoot is too old. It won't work with that rootfs. You can either: - update uBoot Or - use a different rootfs You can find both in the links in my signature. But I would try the rootfs first.by bodhi - uBoot
Please see this post if you're using NFS rootfs. The problem was solved.by bodhi - Debian
Heads up!!! Kernel 3.13 seems to have problem with booting NFS root. As I can tell from serial console, it seems that initrd probed modules mvmdio and mv643xx_eth in wrong order. kernel 3.12.0-kirkwood-tld-5 [ 2.556718] udevd[62]: starting version 175 [ 2.650231] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 2.736122] usb 1-1: new high-speed USB device numbby bodhi - Debian
S Sharma, Cool! Glad it works well upgrading from squeeze…. Are you running old uBoot? if not sure, run this command grep -a --null-data U-Boot /dev/mtd0ro Note: don't be alarmed if seeing NAND error messages in dmesg when running this command! (the error was because mtd0 is not a normal partition).by bodhi - Debian
radsfaninlv, You do need a serial cable, if netconsole was not set up. Boot with serial console and look at uBoot envs, you might have typos in one of those uBoot envs, if you have been changing them. If you can't spot the error, post the output of uBoot command printenv.by bodhi - Rescue System
kiryl, Don't connect 3.3V, should connect only TX, RX, and GND.by bodhi - uBoot
Earl, apt-get update is successful, then the sources are OK. Did it happen after you upgraded the kernel? if yes then I would backup the rootfs first, and then do apt-get upgrade. Try install again after that.by bodhi - Debian
Kernel 3.13.1-kirkwood-tld-1 package was uploaded. Please see first post for download link.by bodhi - Debian
@milhouse31, I've ran the same dd test on the GoFlex Net USB thumb drive root@HomeMBP:/localdisk# dd if=/dev/zero of=./test count=50000 50000+0 records in 50000+0 records out 25600000 bytes (26 MB) copied, 1.51012 s, 17.0 MB/s No disk write slow down problem in 3.12.x or 3.13.1.by bodhi - Debian
Heychris, > Personally I've attempted many times, but am just > not quite finding the problem. I've also uart > restored dozens of times. So UART booting does work on the Netgear Stora? That would make upgrading uBoot much easier. What was the problem you've seen while booting your new uBoot? and what uBoot version did you build?by bodhi - uBoot
Atesz, See first post of this thread for how to download the latest rootfs (3.12.0-kirkwood-tld-3, updated 14 Dec 2013), and installation to a USB pen drive.by bodhi - Debian
Atesz Wrote: ------------------------------------------------------- > Hi. > > Can I try this debian linux without install? So > only run from USB pendrive? I will not touch > original firmware and data in HDD. Can you help > for me? May be. Which plug do you have? are you running stock FW and OS?by bodhi - Debian
nekitip, QuoteI hope you are making patch already with this new data. No :) I meant to say the config file indicated that the IDE LED triggers are already in place. I've done all I can there. The tld-3 patch version works for NSA320 and NSA325. So for NSA310, I don't know why it did not work for you! because I don't have the NSA310 so I can't really say with certainty wheby bodhi - Debian
kiryl Wrote: ------------------------------------------------------- > Hi, > > I know there are patches available for compiling > version 1.1.5 => > u-boot-marvell-ms2110 <= but the > final compiled u-boot.kwb file seems to be too > small, something about 150KiB, while the original > is much bigger (or maybe it is just a mtd0 > backup), something aboutby bodhi - uBoot
Earl, 1. To turn the status LED to green for normal operation, put these statement in your /etc/rc.local (before the exit 0): # turn on LED if [ -d /sys/class/leds/status:green:health ]; then echo default-on > /sys/class/leds/status:green:health/trigger if [ -d /sys/class/leds/status:orange:fault ]; then echo none > /sys/class/leds/status:orange:fault/trigger fi fby bodhi - uBoot
cat config-3.12.0-kirkwood-tld-5 | grep LEDS_TRIGGER CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_ONESHOT=y CONFIG_LEDS_TRIGGER_IDE_DISK=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y CONFIG_LEDS_TRIGGER_BACKLIGHT=m # CONFIG_LEDS_TRIGGER_CPU is not set CONFIG_LEDS_TRIGGER_GPIO=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y CONFIG_LEDS_TRIGGER_TRANSIENT=m # CONFIG_LEDS_TRIGGER_CAMERAby bodhi - Debian
@nekitip It's true that for a few kirkwood devices, no patch is needed. Because those dts were already in the mainline, as basic reference boards. In those cases, they can be installed directly. But they will not have correct LEDs, and/or other sensors supports. A majority of the Kirwood plugs don't have dts in mainline, yet. In some cases, the reference board can be used, but it lacby bodhi - Debian
johnklos Wrote: ------------------------------------------------------- > The IP was actually in the u-boot environment > before I changed anything (I kept a copy of the > original output): > ipaddr=192.168.58.233 > serverip=192.168.58.188 These are not relevant if you're not running tftp, nfs, or netconsole (these values are not default, but most likely were set byby bodhi - uBoot
Earl, The reason is that you are running GoFlex Net uBoot by davygravy (installed by Jeff's script). This works because the GoFlex Home is a closed cousin of the GF Net. The LEDs must be set in Debian using Goflex Net settings, you can find the trigger in /sys/class/leds. If you're not sure, post the output of ls -lR /sys/class/leds Rescue system is another story, since you haby bodhi - uBoot
The Stora stock uBoot is quite old. Running newer uBoot in memory will not work. I'll take a peek in uBoot source to see if anything is similar to this box. You can also Google it to see if anybody has created uBoot patch.by bodhi - uBoot
ubermacin Wrote: ------------------------------------------------------- > > debconf: unable to initialize frontend: Dialog > debconf: (No usable dialog-like program is > installed, so the dialog based frontend cannot be > used. at > /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line > 76.) > debconf: falling back to frontend: Readline > Done. > Setting uby bodhi - Debian
nekitp Wrote: > If you are lucky, it wil also blink leds. On > nsa310 it does not. > cat /sys/class/leds/nsa310:green:hdd/trigger > shows > none nand-disk timer oneshot heartbeat gpio > default-on > but no sata-disk, or at least ide-disk Did you compile with the patch? if not then that was the reason.by bodhi - Debian
Your rescue system arcNumber must be something other than the GoFlex Home (3338). Looks like it's a Dockstar. Check it with: fw_printenv arcNumber But before setting this arcNumber, make sure you can boot it with a kernel that supports it (I don't know if your rescue system supports it) . But first, make sure you can boot with the rootfs above (it works for most Kirwood plugs). Iby bodhi - uBoot
earl, If it's a GoFlex Home then try UART booting: http://forum.doozan.com/read.php?3,7852,7852 And you can use uBoot image from this thread for UART booting: http://forum.doozan.com/read.php?3,12381 After verifying that it booted, put this rootfs on a USB thumb drive: http://forum.doozan.com/read.php?2,12096 If everything boots OK into Debian, then while in Debian, flash thisby bodhi - uBoot
Yes, setup tftp on another Linux or OSX box and flash the current uBoot image. In the example below, 192.168.0.100 is the ip address of the other Linux box 192.168.0.200 is the ip address of this Dockstar (assuming it is the Dockstar) uboot.kwb is the uBoot image that is retrieved by Jeff script (http://projects.doozan.com/uboot/install_uboot_mtd0.sh) for the Dockstar. and all commanby bodhi - uBoot
ingmar_k Wrote: ------------------------------------------------------- > Great to hear that my little theory worked out > like expected. Nice solution!by bodhi - uBoot
nekitip, See this post by pbg4 for setting NSA3xx LEDs. http://forum.doozan.com/read.php?2,12096,13642#msg-13642 It is the normal way to control the LEDs in all these Linux ARM boxes. The color for each LED is whatever you want it to be. Setting them in the kernel is unecessary. The necessary part is to specify the addresses in the code so that the /sys/class/leds triggers are available. Rby bodhi - Debian
@nekitip, It's very possible that I've missed part of the NSA310 patch. It was extracted from Arch Linux ARM patch. Don't worry about pointing out problems! I don't have any of the NSA3xx series boxes and have no way of testing the patch, so other users have been testing these boxes and reported problems in this thread. Especially the NSA310, only you and another user haveby bodhi - Debian