Re: Boot failure, 2.6.10-rc2

[Bob Gill <gillb4@telusplanet.net>]

On Tue, 2004-11-16 at 20:36 +0100, Jan Engelhardt wrote:
> >Hi.  When booting 2.6.10-rc2, I get
> >Warning: unable to open an initial console
> >(and the boot process then stalls).
> >
> >My system has the following already configured:
> >crw-------  1 bob root 5, 1 Nov 16 10:10 /dev/console
> 
> Are you sure /dev/console exists when the kernel boots?
> (It is thy duty to ask this...)
> 
> I wonder, because there is no configurator (menuconfig) option to en-/disable
> the driver for /dev/console -- it's *always* in. In 2.6.8, and I have not seen
> any changes to drivers/char/tty_io.c:tty_init() - where it is added - in
> further kernels yet.
> 
> >My kernel configuration includes the following:
> >CONFIG_UNIX98_PTYS=y
> >CONFIG_LEGACY_PTYS=y
> >CONFIG_LEGACY_PTY_COUNT=256

> But to be on the safe side, enable:
> 
> CONFIG_VT=y
> CONFIG_VT_CONSOLE=y
> 
OK, another part of my standard build script (which is now failing to
boot) includes:
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
...
> As I read from kernel/printk.c, the console= parameter seems to set up a
> -serial line-, also see Documentation/serial-console.txt and
> kernel-parameters.txt.
> 

> How, after all, did you run into this error? Directly after upgrading (if
> applicable)?
No, the standard (old) kernel that comes with Fedora Core 3 is working
ok, but I prefer to run my own custom kernels.  The official Fedora line
is that it's wrong to build your own kernel, and you are silly for
wanting to do so, but I like to build/run them anyway.
> 
> 
> Jan Engelhardt

Thanks for your reply though.  Your question as to whether /dev/console
exists at boot time is making me question whether /dev/console exists at
boot time.
-- 
Bob Gill <gillb4@telusplanet.net>