After emerging showconsole-1.07 and setting RC_BOOTLOG to yes in /etc/conf.d/rc for logging the boot messages, I get an error message saying: blogd: console=/dev/tty1, stdin=/dev/tty1, must differ, boot logging disabled and nothing gets logged to /var/log/boot.msg I have tried to manually run "showconsole </dev/tty2" from /dev/tty1 and it returns /dev/tty2, so showconsole seems to work fine. But if I run "showconsole </dev/console", it always return the same as "showconsole": the device of the running terminal. Reproducible: Always Steps to Reproduce: Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-gentoo-r3 i686) ================================================================= System uname: 2.6.13-gentoo-r3 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://linuv.uv.es/mirror/gentoo/ http://ftp.caliu.info/pub/gentoo/ ftp://ftp.caliu.info/pub/gentoo/" LANG="en_US.utf8" LC_ALL="en_US.utf8" LINGUAS="en es" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X aalib alsa apm arts artswrappersuid audiofile avi berkdb bidi bitmap-fonts cdparanoia cdr crypt cups curl dhcp divx4linux dvd dvdr edl eds emboss encode esd fam flac font-server foomaticdb fortran gdbm gif gimpprint gpg gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib irmc java jpeg kde kdeenablefinal libcaca libg++ libwww mad mailwrapper mikmod mmx mmxext motif mozilla mp3 mpeg ncurses network nls nodroproot ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime rdesktop readline real rtc samba scanner sdl slang smime spell sse ssl tcltk tcpd threads tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis wxwindows xml xml2 xprint xv xvid zlib video_cards_radeon linguas_en linguas_es userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS
post your grub.conf/lilo.conf
Created attachment 70269 [details] grub.conf
More info given
it probably breaks because of your splash theme if you disable the splash stuff, does blogd work ?
I disabled splash theme and it also failed, but after removing "CONSOLE=/dev/tty1" from the kernel line in grub.conf it works fine. It seems that the splash screen is also working fine after deleting "CONSOLE=/dev/tty1". So problem solved. Thanks.
ive documented that boot splash interferes with bootlog in /etc/conf.d/rc unless spock feels like looking into this further, i'm going to leave it at that
The latest version of splashutils instructs the user to use 'console=tty1' instead of 'CONSOLE=/dev/tty1', which has the side effect of automatically fixing the problem described in this bug.
