Hello!
I have a problem as shown below:
VFS: Mounted root (jffs2 filesystem) on device 31:11.Freeing init memory: 144Kinit started: BusyBox v1.13.2 (2010-06-21 12:46:04 IST)Bad inittab entry at line 5can't open /dev/si: No such file or directorycan't open /dev/~~: No such file or directorycan't open /dev/l0: No such file or directorycan't open /dev/l1: No such file or directorycan't open /dev/l2: No such file or directorycan't open /dev/l3: No such file or directorycan't open /dev/l4: No such file or directorycan't open /dev/l5: No such file or directorycan't open /dev/l6: No such file or directorycan't open /dev/z6: No such file or directorycan't open /dev/S: No such file or directorycan't open /dev/1: No such file or directoryprocess '/sbin/sulogin' (pid 1040) exited. Scheduling for restart.process '/sbin/getty 115200 ttyS0' (pid 1041) exited. Scheduling for restart.process '/sbin/getty 38400 tty1' (pid 1042) exited. Scheduling for restart.
I use DVSDK_3_10 on my DM36X EVM board, and the rootfs is extract from arago-demo-image-dm365-evm.tar.gz . All the software resource are download from TI website , it should not be anything wrong.
I have the exact same problem right now on the DM6467. I'll let you know if I figure it out. You do the same please.
Thanks,
Brent
I have fixed my similar issue with my RAM files system. I noticed that when booting the filesystem from NFS, I did not have the "BusyBox" line during boot. Basically the initramfs is trying to initialize with busybox. To get around this I added "rdinit=/sbin/init" to my bootargs. Now the boot process looks exactly like boot process from NFS and everything boots normally.
Now for a FFS, I'm not sure if there is another bootarg you need or if you can just do "init=/sbin/init" in your bootargs. I found rdinit in the kernel documentation. I would check there for FFS if "init=/sbin/init" does not work.
-Brent
Thanks for your answer
Appear above problems because i add a bootarg "init=/linuxrc" before when i use my own file system, they disappeared after remove the bootarg.
thank you very much!
It's very userful for me,I had the same problem on my dm368, now I fixed it!
Thank you very much!