[ydl-gen] Upgrade 4.01 -> 4.1: odd boot behaviour

Albrecht Dreß albrecht.dress at arcor.de
Sun Mar 12 07:27:58 MST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

as my system contains *tons* of self-compiled stuff not included in the  
official disto, I upgraded from YDL 4.01 to YDL 4.1 rpm's. Mostly the new  
system seems to run fine, but I found an odd behaviour of the boot  
process. If I boot the YDL 4.1 kernel, I see boot messages as usual. If I  
boot a self-compiled 2.5.15 (stripped down to my requirements, and without  
initrd) I only see the message "Warning: unable to open an initial  
console". The system comes up properly, /except/ that the console charset  
is not loaded, and neither info about the boot process nor a chance to go  
into single user mode.

As this used to work with 4.01's rc.sysinit, I guess I missed something  
either in the kernel. Or do I need the initrd? Searching the web, I found  
some hints that /dev/null and/or /dev/console might be missing, but adding  
commands to the beginning of rc.sysinit to explicitly create them in this  
case doesn't help.

Any ideas?

Thanks in advance,
Albrecht.

- -- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
        Phone (+49) 228 6199571  -  mailto:albrecht.dress at arcor.de
   GnuPG public key:  http://www.mynetcologne.de/~nc-dreszal/pubkey.asc
_________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFEFC/4n/9unNAn/9ERAveNAKCFrPP9cgsNu1caKhVDl+jp+yZxmgCeMfPx
0otK3MVfNRulqKIBAclFFhE=
=rX3r
-----END PGP SIGNATURE-----



More information about the yellowdog-general mailing list