[SOLVED] Ask for issue: Warning: unable to open an initial console.
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ask for issue: Warning: unable to open an initial console.
MIPS architecture CPU, squashfs filesystem.
It looks like the ramdisk rootfs mounted and accessed normal.
But could not open an initial console during init_post() in kernel boot.
Anyone could give me some suggestion?
Thanks.
The boot message is as below, and printk work in kernel space but printf not work in user space.
U-Boot 1.3.2 (Dec 16 2011 - 16:23:03)
Board: BCM95300X
CPU Type: 0x5300 Rev. 0x1
CPU Speed: 400 MHz
DRAM: 128 MB
Flash: 32 MB
PCI[0]: Initializing host
01 01 14e4 b143 0200 00
PCI[1]: Initializing host
02 01 14e4 b143 0200 00
In: serial
Out: serial
Err: serial
Net: et
Loader version : 1.0.11.0
Product : Unknown ! PID = 1, BID = 1
Loading Runtime Image File : c1-packagev12.16.15.52.bin
Image version: 12.16.15.52
Image Name:
Created: 2011-12-16 08:25:17 UTC
Verifying Checksum ... OK
Loading Multi-File Image ... OK
Saving Environment to Flash...
done
nvram_commit: will write 94 bytes from 87f664b0
write 94 bytes to bc0e0000
Initial Accton Module. <--// the message during insmod module in /etc/rc //-->
K_L_IPCMEM_Initialize <--// the message during insmod module in /etc/rc //-->
vbase = a6400000, pbase = 6400000 <--// the message during insmod module in /etc/rc //-->
pbase = 6400000 <--// the message during insmod module in /etc/rc //-->
K_L_IPCMEM_Create_InterCSC_Relation <--// the message during insmod module in /etc/rc //-->
The root cause is unhealthy binary map files in the rootfs.
Since the binaries and libraries should be stripped for size, the map files for them are stored in the rootfs. But some the map file is unhealthy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.