Turns out the solution to this problem is quite simple, the problem lies in an initramfs image in the kernel source directory called FriendlyARM.cpio. This file is not needed when using the mini6410 BSP and it can be disabled in the kernel config without causing any problems. - David
On Thu, Mar 7, 2013 at 1:16 PM, david <[email protected]> wrote: > Almost forgot to add the bootargs. I'm using "root=/dev/mmcblk0p1 rootwait > console=ttySAC0,115200" > - David > > > On Thu, Mar 7, 2013 at 12:20 PM, david <[email protected]> wrote: > >> I've attached the relevant parts of the dmesg output for both a failed >> load and a successful load. I've attached the full output of both boot logs >> as attachments also. >> - David >> >> Failed Boot: >> Freeing init memory: 1376K >> mmc0: new SD card at address e624 >> mmcblk0: mmc0:e624 SU02G 1.84 GiB >> mmcblk0: p1 >> mount: mounting /dev/mmcblk0p1 on /r failed: No such device or address >> 1Wire touchscreen OK >> /init: line 103: can't open /r/dev/console: no such file >> Kernel panic - not syncing: Attempted to kill init! >> [<c016fde8>] (unwind_backtrace+0x0/0xe4) from [<c033e200>] >> (panic+0x68/0x184) >> [<c033e200>] (panic+0x68/0x184) from [<c0180aac>] (do_exit+0x68/0x668) >> [<c0180aac>] (do_exit+0x68/0x668) from [<c01813d8>] >> (do_group_exit+0xb0/0xe4) >> [<c01813d8>] (do_group_exit+0xb0/0xe4) from [<c018141c>] >> (sys_exit_group+0x10/0x18) >> [<c018141c>] (sys_exit_group+0x10/0x18) from [<c016a640>] >> (ret_fast_syscall+0x0/0x30) >> one_wire_status: 2 >> >> >> >> Successful Boot: >> Freeing init memory: 1376K >> mmc0: new SD card at address e624 >> mmcblk0: mmc0:e624 SU02G 1.84 GiB >> mmcblk0: p1 >> EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is >> recommended >> 1Wire touchscreen OK >> init started: BusyBox v1.20.2 (2013-03-07 01:03:05 EST) >> starting pid 382, tty '/dev/console': '/etc/init.d/rcS' >> mounting filesystems...done. >> running rc.d services... >> > >
