Arch Linux

pocm

Member

Registered: 2010-08-02

Posts: 15

Custom kernel breaks bootlogd - but why?

I have an arch system which works fine when booting a standard kernel, but using my custom kernel all boot messages cease after it launches bootlogd from /etc/rc.sysinit. The file /var/log/boot is created as normal, and has all of the output from sysinit and rc.multi you'd expect to see, and no errors show up there or in any other log file which would explain why bootlogd fails to write to the console. Before and after bootlogd, the console behavior is perfectly normal. I have already made sure to enable the most relevant-looking kernel config options, including:

CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_TTY_PRINTK=y
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y

The full kernel config is here. Any advice? Thanks!

Last edited by pocm (2011-08-12 18:47:24)