Mini6410 - can't open /r/dev/console: no such file

I'm using the 2.6.38 kernel source and 4.5.1 toolchain provided by
FriendlyARM to build a kernel for the mini6410. The kernel will work 1 out
of every 5 boots, the errors generated when it fails are:

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 

Thanks,
 - David

After a bit of digging, I found the file FriendlyARM.cpio in the scripts
directory. It appears this file is an initramfs image and has the script
that is generating the error.

Turns out the problem can be solved by just disabling the initramfs image
in the kernel config. Hope this helps someone else.

Hi David, that's one solution but it depends whether there is anything in
the CPIO that could break things if it's missing, usually, all of the
touchscreen setup is done in there, disabling the initramfs can cause the
ts to not work especially if it uses ts_lib.  However, if it's all working
for you, more power to ya :-)

What is /r/dev/console? I only know /dev/console.

Is this mini6410 specific? From mini2440 i never heard of that...

/r/ is the root device where the initramfs builds the root filesystem ready
for handover to the switchroot function.

Ah, ok. Thank you Reggie!