When I boot my new system with gensplash, the console is OK up until X is started via gdm. Afterward all consoles are "smeared" and "broken". I try to give you all relevant data in the hopes to get some clues for my problem. System is stable (kernel 2.6.22-r2, xorg-x11 7.2), I'm using a Nvidia 8500GT (nvidia-drivers 100.14.09) with an Asus P5K motherboard. Framebuffer is vesafb with these relevant kernel options "vga=0x318 video=vesafb:mtrr:3,ywrap splash=silent,theme:AquaMatrix CONSOLE=/dev/tty1". Reproducible: Always Steps to Reproduce: 1. Use my hardware configuration 2. boot with gensplash 3. start X Actual Results: The consoles get borked after start of X Expected Results: Consoles should be fine hive ~ # emerge --info Portage 2.1.2.12 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r5 i686) ================================================================= System uname: 2.6.22-gentoo-r5 i686 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Gentoo Base System release 1.12.9 Timestamp of tree: Fri, 24 Aug 2007 17:50:01 +0000 ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/ " LANG="en_US.UTF-8" LINGUAS="de en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/sunrise /usr/portage/local/layman/initng /usr/portage/local/layman/custom-kernels" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acl acpi alsa bash-completion berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread eds emboss encode esd evo fam firefox fortran gdbm gif gimp gphoto2 gpm gstreamer gtk gtk2 hal iconv ipv6 java javascript jpeg kerberos lm_sensors mad midi mikmod mmx mmxext mozilla mp3 mpeg mudflap ncurses nls nptl nptlonly nvidia ogg opengl openmp oss pam pcre pdf perl png pppd python qt3support quicktime readline reflection scanner sdl session spell spl sse sse2 ssl ssse3 startup-notification svg tcpd tiff truetype truetype-fonts type1-fonts unicode usb userlocales vim-pager vim-with-x vorbis win32codecs wmf x86 xcomposite xface xml xorg xv xvmc zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" CAMERAS="kodak" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de en" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 129089 [details] Xorg log I add the Xorg log. Perhaps it contains some clues I do not see.
Please try running without the splash= kernel command line parameter and let me know whether it changes anything.
(In reply to comment #2) > Please try running without the splash= kernel command line parameter and let me > know whether it changes anything. > Command line is now: kernel /vmlinuz root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3 udev vga=0x318 video=vesafb:mtrr:3,ywrap CONSOLE=/dev/tty1 CONSOLEFONT="lat9w-16" CONSOLETRANSLATION="8859-1_to_uni" quiet Console is still broken, so it seems, that this is not connected to gensplash but rather to a conflict of vesafb and X, doesn't it? I also tried vesafb-tng, but this does not work, too. Marc
It looks like you're using the binary nvidia drivers, is that correct? Also, you might want to try uvesafb: http://dev.gentoo.org/~spock/projects/uvesafb/ (have a look at the forums for patches for gentoo-sources)
(In reply to comment #4) A couple of suggestions: 1. Try avoiding the vesa module load at boot and use vanilla text terminal. You need to comment out "vesafb" line in /etc/module.autoload/kernel-2.6 If your kernel has compiled in automatic module load, then that alone won't help and you will have to temporarily rename "vesafb.ko" module somewhere in /lib/modules/_Your-kernel" to something else. 2. Check out about AGPgart used- is machine using kernel's compiled-in/separate-module or is it using nvidia's proprietary module ? I think that should be visible in kernel's ring buffer right after nvidia's kernel module load 3. It might very well be that you changed something criticall in kernel or machine, but have left in old version of nvidia module, so it might need to be compiled again. With X inactive ( working in console), do : modprobe -r nvidia && emerge nvidia-drivers && depmod -a & modprobe nvidia then, with new module loaded, try running X 3a. When compiling new driver, check that your /usr/src/linux softlink is pointing toward the source tree of the kernel you are actually using ( usename -a )
(In reply to comment #4) > It looks like you're using the binary nvidia drivers, is that correct? Yes, the stable one (x11-drivers/nvidia-drivers-100.14.09). > > Also, you might want to try uvesafb: > http://dev.gentoo.org/~spock/projects/uvesafb/ I will try it. > > (have a look at the forums for patches for gentoo-sources) I make my own patched gentoo-sources, since I want to add unionfs, too. (In reply to comment #5) 1.) not using vesafb will certainly help me not breaking my console, but I would like to have a boot splash, so I need some fb. Any suggestions (beside uvesafb)? 2.) How do I do this? I mean, checking the "kernel's ring buffer"? Is this dmesg? There I only got this: "[...] nvidia: module license 'NVIDIA' taints kernel. hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:01:00.0 to 64 NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.09 Sat May 26 00:47:07 PDT 2007 ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 [...]" Does this say anything to you? 3.) It is a fresh install with fresh sources. The proprietary binary nvidia driver was compiled after boot into new kernel without X running. Link to sources was set with eselect. So everything seems OK. Thanks for suggestions. I will try uvesafb tomorrow. Marc
(In reply to comment #6) > Yes, the stable one (x11-drivers/nvidia-drivers-100.14.09). You might also want to try it with the latest available version (100.14.11). > 1.) not using vesafb will certainly help me not breaking my console, but I > would like to have a boot splash, so I need some fb. Any suggestions (beside > uvesafb)? vesafb and uvesafb are usually the only available options. The only other one that could potentially work is nvidiafb, but it's known to be completely broken with the binary X drivers. > 2.) How do I do this? I mean, checking the "kernel's ring buffer"? Is this > dmesg? There I only got this: It is. > Does this say anything to you? I don't see anything important there.
(In reply to comment #7) > (In reply to comment #6) > > > Yes, the stable one (x11-drivers/nvidia-drivers-100.14.09). > > You might also want to try it with the latest available version (100.14.11). > I did and it solved my problem (still using vesafb) :-) Thanks for the help. Marc
