aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2015-09-03 20:42:27 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-09-06 15:24:23 +0100
commit0352841cd92f6316bcac092e2fff9d28c352b36b (patch)
tree713f442983d22fa11da6f7361c3249af97b8ef13 /meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
parent37741c539f5d3021e59828b49e968cd42b89a368 (diff)
downloadopenembedded-core-contrib-0352841cd92f6316bcac092e2fff9d28c352b36b.tar.gz
initramfs-framework: create /dev/console
Some kernels, for example linux-yocto 3.19 for qemux86, fail to execute /init in an initramfs unless there is already a /dev/console char device in the initramfs. Booting then fails with: Kernel panic - not syncing: /dev/console is missing or not a character device! Please ensure your rootfs is properly configured The panic itself comes from a linux-yocto specific patch to kernel_init_freeable in init/main.c, but even without it, that function will print an error when /dev/console is missing. The kernel's Documentation/initrd.txt also mentions creating that device. It remained unclear why this is not a problem on other machines. On intel-corei7-64 from meta-intel, something (the kernel?) creates /dev/console and /dev/[012] before transfering control to the init script. In that case, creating /dev/console in advance is not necessary, but does not cause any problem either. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb')
0 files changed, 0 insertions, 0 deletions