bodhi, > > Kernel 3.12.0-5 on the other hand boots up > > without > > problems from bootcmd whithout having to > > interfere > > in uboot. > What is the difference between your rootf and > this? I copied the rootfs from my SheevaPlug. It is a debian squeeze updated to wheezy with loads packets installed... > > > > My bootcmd looks likby NobuoT - Debian
*Sigh*... Next problem: Everything looked good so I removed the rs232, put the NAS back together and saved bootcmd to nand in uboot to automatically boot from sata disk. And... it didn't boot up. -__- After uboot jumps into the kernel, it resets about 20sec into the boot process on different steps without any warning or hint to any problem on console or in any of the logs. Seems like thisby NobuoT - Debian
Wow, thanks bodhi! That did it. Would have taken me ages to figure that out otherwise. x)by NobuoT - Debian
Found out a few things... I attached 2 console logs. 1 is the "normal" boot log where eth0 doesn't show up 2 is a log where I accidentally kept the default bootargs with root=/dev/nfs Setting root=/dev/nfs of course stopped debian from booting, but when it dropped me to busybox, eth0 magically appeared. So I guess the problem is somewhere in my initramfs / init scripts. Inby NobuoT - Debian
Hi bodhi Hm... Can't see much difference except Buttzy uses 3.13.2-nsa-325 kernel whereas I use 3.13.1-kirkwood-tld-2. The only other real difference with ethernet I can see is that Buttzy is using gbit ethernet and his log has lines like [ 39.568368] NET: Registered protocol family 10 [ 39.787229] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down [ 39.793289] IPv6: ADDRCONFby NobuoT - Debian
Had a bit time to play with my nsa325v2 again and realised, eth0 doesn't get initialized? I tried kernels 3.12.0-tld-5 and 3.13.1-tld-2. The only line in whole boot process that contains 'eth0' is apparently root@Sheeva:~# dmesg | grep 'eth0' [ 3.915009] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:50:43:00:02:02 Also the nsa3xx hwmon drby NobuoT - Debian