Look here for a much cleaner solution: http://forum.doozan.com/read.php?2,5552,5552 You don't need to modify with the init script from the initrd image. The init script does this already by default if you just simply pass the kernel the root locaton using a label. For your example above, you just need to pass the kernel "root=LABEL=rootfs".by kraqh3d - Debian
Oh yeah, kernel.org was hacked a little while ago. The kernel tree is being maintained at github for the time being: https://github.com/torvalds/linuxby kraqh3d - Debian
Yeah I agree. Replacing the kernel should be pretty safe. The only issue I can think of is if you try to load some non-mainline binary kernel module that you installed through apt, as it'll be built against the standard debian kernel. While the kernel's user land ABI is very stable, the kernel's module ABI is always subject to change. But I don't think anything would breaby kraqh3d - Debian
@MartinH, Look up a few posts. You'll see one from marcov_. His method is to place the uImage and uInitrd in the nand on mtd3. It'll always find the kernel and initrd image to aid in the continuation of the boot process. Basically it allows for sticks that won't boot directly to still house the root filesystem. http://forum.doozan.com/read.php?2,5552 And in this GoFlex Neby kraqh3d - Debian
You could potentially run into some dependency checking issues later when adding or upgrading debian packages since the kernel and it's modules are not known by the package manager. Admittedly this is rare as there usually aren't kernel dependencies so it should work. And since the kernel ABI to user land ABI is pretty stable, I suspect it would only be an issue if you tried to instalby kraqh3d - Debian
You can get debian on there, but its going to take some futzing around. First, you install Arch. It copies it's custom oxnas kernel into /dev/mtd1. (Two copies of it for redudnancy I presume.) From a running Arch install, you can install Debian onto another stick. You're going to need to copy /lib/modules/2.6.31.6_SMP_820 from your Arch rootfs to where you have Debian. If all goesby kraqh3d - Debian
Well, you don't necessarily need an initrd image to boot. It provides some helpers, mostly to load the root fs if the kernel doesn't have those modules built in. I don't know where your OpenWrt expects to find its root filesystem. Everything I've read today seems to state that it should be in the nand but you're likely passing it a root=/dev/sda1 parameter from jeffby kraqh3d - uBoot
@bodhi *After* writing the uboot environment to nand, you need to set ethaddr, arcNumber, and then the netconsole stuff. Your netconsole config doesn't exist because you did it before writing the environment. And it won;t work without ethaddr.by kraqh3d - uBoot
Of course it can be done. And it'll probably work. But I wouldn't attempt it without a backup. So make a cop of your Squeeze boot stick. Boot the copy. Edit /etc/apt/sources.list to reference wheezy instead of stable or squeeze. apt-get update apt-get dist-upgrade Cross your fingers and wait. When it's done, you'll need to generate new uImage and uInitrd filby kraqh3d - Debian
1. I don't have a GoFlex but I believe that is normal from reading other posts. 2. apt-get install uboot-envtools uboot-mkimage (I'm pretty sure those are packages. I still have no power from the storm that ravaged the north east US so I can't check my device.) uboot-envtools provides fw_printevn and fw_setenv uboot-mkimage provides mkimage which is needed to produce uboby kraqh3d - Debian
You'll need serial console access to further debug.by kraqh3d - uBoot
You'll have to enable some kind of logging to figure out what's up. You can install syslog to capture everything. You can use serial console which will get all kernel messages. Or use the linux (not uboot) netconsole option to send the kernel messages to another host.by kraqh3d - Debian
Good. I extracted the kirkwood initrd for giggles. It's got the same init script as the stock 686 initrd. I would've been surprised if it didn't work. You can't just change usb_root and save the environment. The problem is that it gets modified when usb_scan is run. The easiest way to make it permanent is to modify the usb_init line. It defaults to: usb_init=runby kraqh3d - Debian
Ok I was just checking. If you don't add netconsole to the kernel parameters, you won't get anything after "Starting Kernel..." from u-Boot.by kraqh3d - Debian
Did you set the set label of your root partition to ROOTFS? ls -lF /dev/disk/by-label This should work as this is how all the major distro's boot. They pass the kernel a root parameter that specifies either a LABEL or UUID, and then the kernel lets the initrd resolve it to a device via /dev/disk/by-label or /dev/disk/by-uuid. We can extract the initrd image and see. It should be iby kraqh3d - Debian
You won't get any netconsole messages from the kernel unless you also add netconsole configuration to the kernel parameter list. This even requires that you specify the destination MAC address as there's no ARP resolution available yet.by kraqh3d - Debian
Yes! Please try passing the kernel the root as a LABEL. I'm very curious to know if this will work around this annoyance with the GoFlex Net. It works fine with my Dockstar so I'm pretty sure it'll work for the GoFlex Net. You can test it out safely with either serial console or net console access. The procedure outlined at the bottom of that thread is non permanent.by kraqh3d - Debian
Try another switch port and/or change your cabling, especially swapping with a known good one. When auto-negotiation doesn't work correctly, you get a half-duplex connection, and it will totally kill your throughput.by kraqh3d - Debian
That's very low. I've bench marked networked I/O at over 11 MB/s for reading and over 9 MB/s for writing (and that's with the --sync mount flag.) There are some tuning parameters but I never bothered as that's nearly maxing out the 100 mbps ethernet connection and was good enough for me. Asynchronous writes should bring the write speed nearer to the read speed, but I neverby kraqh3d - Debian
dpkg --list | grep linux-image The new pkg version should be 2.6.32-35. It should be safe. That's what I'm running. But I don't recall upgrade creating new uImage and uInitrd's, maybe this is new? I've always had to create them manually myself with mkimage after a kernel update so I'm not 100% sure. If you don't have a serial cable, build one. You wiby kraqh3d - Debian
You could remove "errors=remount-ro", but I wouldn't advise it. That's to protect the root fs by trying to prevent further damage.by kraqh3d - Debian
Yes, that's why I gave you that suggestion. The default fstab includes the remount as readonly on error. But those errors on mtdblock1 are unrelated. That mtd "partition" is where the stock pogo kernel is located. What device is your root parition? Do this on a terminal and see what it catches (assuming its /dev/sda) busybox logread -f | grep /dev/sda You can also have iby kraqh3d - Debian
It's probably encountering some error and re-mounting read-only. You probably don't have any logging enabled, right, so we can't find out why. Install busybox-syslogd. It'll capture log messages to a small ring buffer in memory. You view at the log with "busybox logread". It has a "-f" option to view it live. You're going to need to catch thby kraqh3d - Debian
Try "tune2fs -l". It has an entry called Filesystem State that should report "clean".by kraqh3d - Debian
Regarding B... You're missing the dependencies. The source should include some README or INSTALL or something file that details what the dependancies are. You'll need to find the coorespoding "-dev" packages from apt and install them. It's probably a good idea to install any multimedia packages from debian-multimedia anyway. Regarding C... Did you install the debian-by kraqh3d - Debian
I suspect the usbserial driver will be present but I've not tried. When you plug one in, if it's recognized, you should get a new device of named /dev/ttyUSB0 (as there shouldn't be one already there.)by kraqh3d - Debian
cat /etc/debian_version if its 5.x then you're still running lenny. to upgrade to squeeze, replace all instances of "lenny" with "squeeze" in etc/apt/sources.list sudo apt-get update sudo apt-get dist-upgrade the last step would be to create new uImage and uInitrd images from the new kernel and initrd images in /boot backup the existing /boot/uImage and /boot/uIby kraqh3d - Debian
http://forum.doozan.com/read.php?2,4323 Read this thread. The problem is a change in the hashing algorithm. A fix is included in there.by kraqh3d - uBoot
Interesting... That means you're doing something wrong, or something is blocking the packets. But it's not obvious what that may be. Your "nc" config from above looks good. The other thing I could think of is some firewall or packet filter that's blocking the udp messages. Unless you can figure out why you're not getting any netconsole messages from the working oby kraqh3d - uBoot