Tiny6410 : /init: line 103: can't open /r/dev/console: no such f

André
Hi,

I am getting crazy, having the "/init: line 103: can't open /r/dev/console:
no such file" when trying to mount rootfs with NFS.
I spent hours to search on the web, found many topics but I can't correct
the issue.

I am using :
Host : Ubuntu 12.10 64b
Compiled u-boot 2011-10, source provided on dvda
Compiles kernel 2.6.38, source provided on dvda (with KERNEL_CONFIGS=DEBUG)
(I am not a specialist on kernel !!)

When I use my compiled u-boot and kernel installed in the NAND (loaded by
superboot), system starts correctly and I can play with
qtopia/Android/Ubuntu.

When I try to use rootfs (qtopia but also emdebian) with NFS (uboot+kernel
installed in NAND), I am getting the error.

I think my NFS is properly seted as I can connect from other PC on the host
containing the NFS server.

NFS exports file :
/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212
172.30.98.0/255.255.255.0(rw,fsid=0,no_subtree_check,sync,no_root_squash)
/home/ancatel/linux_embeded/tiny6410/debian-mini6410/rootfs
172.30.98.0/255.255.255.0(rw,fsid=0,no_subtree_check,sync,no_root_squash)

In addition, to ovoid rights issues, I did a chmod -R 777 on NFS shares.

End of content of /var/sys/syslog :
May 22 00:50:33 aspirine2 rpc.mountd[1566]: authenticated mount request
from 172.30.98.109:668 for
/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212
(/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212)
May 22 00:50:33 aspirine2 rpc.mountd[1566]:
/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212 and
/home/ancatel/linux_embeded/tiny6410/debian-mini6410/rootfs have same
filehandle for 172.30.98.0/255.255.255.0, using first
May 22 00:52:50 aspirine2 rpc.mountd[1566]: authenticated mount request
from 172.30.98.109:668 for
/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212
(/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212)
May 22 00:54:18 aspirine2 rpc.mountd[1566]: authenticated mount request
from 172.30.98.109:668 for
/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212
(/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-20111212)

u-boot printenv :
bootargs=noinitrd rootwait console=ttySAC0,115200 root=/dev/nfs mem=256M
nfsroot=172.30.98.102:/home/ancatel/linux_embeded/tiny6410/rootfs_qtopia_qt4-201
11212
rw ip=dhcp

End of log :
s3c-fimc: controller 0 registered successfully
s3c-fimc: controller 1 registered successfully
FIMC Driver, 2010 ported by FriendlyARM http://www.arm9.net
ov965x: probe
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: ov965x: Product ID fb:fb Manufacturer ID fb:fb
parent clock for camera: 266.000 MHz, divisor: 11
[CAM]RESET CAM.
one_wire_status: 4
S3C6400 MFC Driver, (c) 2007 Samsung Electronics, 2010 ported by
FriendlyARM http://www.arm9.net
 S3C6400 MFC Driver init OK. 
S3C PostProcessor Driver v3.12, (c) 2009 Samsung Electronics
S3C6410 TV encoder Driver, (c) 2008 Samsung Electronics
 S3C6410 TV encoder Driver init OK. 
S3C6410 TV scaler Driver, (c) 2008 Samsung Electronics
 S3C6410 TV scaler Driver init OK. 
S3C Rotator Driver, (c) 2008 Samsung Electronics
s3c_rotator_probe called
s3c_rotator_probe success
one_wire_status: 4
S3C JPEG Driver, (c) 2007 Samsung Electronics
s3c_g2d_probe called
 s3c_g2d_probe Success
 S3C G2D Init : Done
S3C G3D Driver, (c) 2007-2009 Samsung Electronics
s3c_g3d version : 0x1050000
 S3C G3D Init : Done
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
one_wire_status: 4
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133000000 Hz)
one_wire_status: 4
s3c-sdhci s3c-sdhci.1: clock source 2: mmc_bus (24000000 Hz)
mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
asoc: wm9713-hifi <-> samsung-ac97 mapping ok
ALSA device list:
  #0: MINI6410
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c-rtc s3c64xx-rtc: setting system clock to 2013-05-22 00:54:54 UTC
(1369184094)
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 172.30.98.1, my address is 172.30.98.109
IP-Config: Complete:
     device=eth0, addr=172.30.98.109, mask=255.255.255.0, gw=172.30.98.1,
     host=172.30.98.109, domain=test, nis-domain=(none),
     bootserver=172.30.98.1, rootserver=172.30.98.102, rootpath=
Freeing init memory: 1408K
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c0177c44>] (unwind_backtrace+0x0/0xe4) from [<c0514824>]
(panic+0x58/0x174)
[<c0514824>] (panic+0x58/0x174) from [<c0189e48>] (do_exit+0x68/0x5e4)
[<c0189e48>] (do_exit+0x68/0x5e4) from [<c018a688>]
(do_group_exit+0x90/0xc4)
[<c018a688>] (do_group_exit+0x90/0xc4) from [<c018a6cc>]
(sys_exit_group+0x10/0x18)
one_wire_status: 2
[<c018a6cc>] (sys_exit_group+0x10/0x18) from [<c01725e0>]
(ret_fast_syscall+0x0/0x30)
one_wire_status: 4

Any idea ?
thanks in advance

André
I found the solution for qtopia :
===> mknod dev/console c 5 1
Now, system is working !

But the issue still persist for emdebian for which the /dev contains all
entries...

Elessarrst
I had exactly same problem. 

After a couple of days I've found the solution.

DO NOT extract the rootfs_qtopia_qt4-20141020.tar.gz with GUI EXTRACTOR
(LIKE ARCHIVE MANAGER)

USE ONLY CONSOLE AND "tar xvzf ./rootfs_qtopia_qt4-20141020.tar.gz" to
extract your files.