Did you already update your uBoot? http://forum.doozan.com/read.php?3,6965 But be careful - for some reason I needed to change my machid after this update to get any kernel up and running. But I assume, you have a working serial console, don't you?by Sven - Debian
All credits go to Jeff and Davygravy: http://forum.doozan.com/read.php?2,524 But in newer crosscompile you'll need to use a workaround to compile armel packages... I'll try to find my steps to use tomorrow... (but I found it somewhere here or using Google...)by Sven - Debian
I tried to keep it as small as possible, but you're right - I could have compiled it at least with IPv6 modules... You could do so yourself using the provided DIFF to apply the changes to the original kernel: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.8.4.tar.bz2 Otherwise please apply all your changes to the .config and send this, so I'll compile it for you. If you arby Sven - Debian
You could try my 3.8.4 with NSA320 enabled: https://www.dropbox.com/sh/ifotsfsca9kqg7q/Dda2OXWSdZby Sven - Debian
It just takes the files out of /dev/sda1 - and inside /boot/ dir. But your boot is located on a separate partition: Quote/dev/sda1 on /boot So a simple workaround to avoid these problems is to put a symbolic link named 'boot' to point to itself on this partition. Don't know why this was renamed to boot1 on your partition and there was another boot dir on it...by Sven - Debian
Well - but it still looks funny. 'mkimage' reports the same sizes as you can see in the listing, but uBoot does read other files: QuoteLoading file "/boot/uImage" from usb device 0:1 (usbda1) 2081852 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 5035488 bytes read What's the content of /boot/boot? And can you additionally tell us someby Sven - Debian
QuoteLoading file "/boot/uImage" from usb device 0:1 (usbda1) 1 bytes read Found bootable drive on usb 0:1 Loading file "/boot/uImage" from usb device 0:1 (usbda1) 2081852 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 5035488 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.0.32 And you're suby Sven - Debian
Bamboo, you may also try my intermediate version: https://www.dropbox.com/s/pyumlkft1tb5qu3/linux-image-3.8.4-dockstar_1.1_armel.deb Although I did some more cut down to get a smaller kernel which I didn't upload so far, this one should work with all Kirkwood devices. I did a successful upgrade to Wheezy on my USB stick and it's still running fine... so give it a try!by Sven - Debian
shv Wrote: ------------------------------------------------------- > With the kernel of the rescue system and > arcNumber/machid set to 3542/dd6 the LED is > controled. The color is green if it is switched > on. The same behaviour I have with bodhys kernel > 3.2.28. With 3.3.2 kernel and arcNumber/machid set > to 2097/831 this LED seam to be controled as well > but thby Sven - Debian
@mindspawn: Did you read this: http://forum.doozan.com/read.php?2,72,3527#msg-3527 ?by Sven - Debian
QuoteJeff Configure UBIFS booting fw_setenv set_bootargs_ubi 'setenv bootargs console=$console ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs $mtdparts init=/sbin/init-ro' fw_setenv bootcmd_ubi 'run set_bootargs_ubi; ubi part data; ubifsmount rootfs; ubifsload 0x800000 /boot/uImage; ubifsload 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000' # Configure new bootloader toby Sven - Debian