I can confirm that the "machid" setting in the uBoot environment seems to cause boot problem. When I set it the machine will not boot (I believe only on 3.x kernels). When I clear it the machine will boot again. Has anyone else seen this? Is it possible to get the kernel to recognize the device correctly, mainly so I can make the light on the front work?by millerdev - Debian
Thanks so much for your help, @bodhi. I downloaded and prepared a new USB drive with Davy's NSA320 rootfs. At first it did not boot (just like all of the other times). So I decided it was time to re-flash the uBoot. This is exactly what I did for anyone else having a similar issue: cd /tmp wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh eby millerdev - Debian
@bodhi, Thank you for helping me out with this. I tried to configure the netconsole module again but still nothing. Note that I was not able to test it with the 2.6 kernel because I do not have an initrd.img-2.6... file (I only have uImage and uInitrd copied from another installation running 2.6). So I used initrd.img-3.2.0-4-kirkwood, which is the kernel that got installed by Jeff'by millerdev - Debian
Thanks @bodhi, I already tried to enable netconsole using the instructions on the thread you linked, but didn't have any luck. I'll try that again to see if I missed a step. Can I safely assume that the bootloader is not the problem? I read in several places that 3.2+ kernel will not boot with certain older boot loaders due to an L2cache issue. Would that issue be evident in the netcby millerdev - Debian