Hi All,
I know there are a few CF card posts, but my problem is slighty different. I have followed the app note and can successfully load VMLINUX and exec root=/dev/hda1 with no worries.
This is the kernel that I am running with:
Linux version 2.4.17-rmk2-lineo5
The system boots up, and all looks ok until BusyBox loads. Here is what I am getting after booting:
----------------------------------
init started: BusyBox v0.52 (2004.07.23-06:32+0000) multi-call binary
*** Running rc.modules
*** Running rc.serial
*** Attempting to start S15inet
Starting inetd
Done
*** Attempting to start S20network
Setting up link for loopback
Done
Setting up link for eth0
Done
*** Attempting to start S23portmap
Starting rpc.portmap
Done
*** Attempting to start S35dhcpcd
*** Running rc.local
Process '/sbin/getty -L ttyAM1 115200 vt100' (pid 28) exited. Scheduling it for restart.
Process '/sbin/getty -L ttyAM1 115200 vt100' (pid 29) exited. Scheduling it for restart.
----------------------------------
It then locks up at this point.
When I boot using tftp (the fs on the CF card is copied exactly from the rootfs as per the app note) it works fine and boots up with no problems (ie, the /sbin/getty.... loads up no problems and I log into the localhost and run my code). My only conclusion is that there is a problem accessing part of the CF card or writting to the CF card. If I reset at this point and try again, I get the "kernel panic" problem that others have posted. I've tried 2 CF cards (both 128MB), one a "SanDisk", the other an "NCP". Checking the partition back on my linux box, the partition itself is destroyed, from what I assume to be an incorrect unmount due to the system locking up.
I've successfully loaded VMLINUX from the CF card and then used tftp to boot from and it has worked fine, so I conclude that the msdos partition is working fine, but the ext2 partition is having some issues.
Can anyone suggest anything?
Cheers,
Simon
|