XWindows does not start after "nvidia-drivers-180.22" installation. But by using driver "nvidia-drivers-177.82" XWindow works fine. Bellow you can find the output of XWindows starting. Step by step: emerge nvidia-drivers-180.22 rmmod nvidia modprobe nvidia startx X: symbol lookup error: /usr/lib64/xorg/modules/extensions//libglx.so: undefined symbol: _nv000002gl XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. Reproducible: Always Steps to Reproduce: 1.emerge nvidia-drivers-180.22 2.rmmod nvidia 3.modprobe nvidia 4.startx Actual Results: startx xauth: creating new authority file /root/.serverauth.23245 X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: UNKNOWN Current Operating System: Linux notikl 2.6.27.7 #4 SMP Fri Dec 5 23:56:21 MSK 2008 x86_64 Build Date: 16 November 2008 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 17 15:34:57 2009 (==) Using config file: "/etc/X11/xorg.conf" (II) Module already built-in X: symbol lookup error: /usr/lib64/xorg/modules/extensions//libglx.so: undefined symbol: _nv000002gl XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. uname -a Linux notikl 2.6.27.7 #4 SMP Fri Dec 5 23:56:21 MSK 2008 x86_64 Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz GenuineIntel GNU/Linux emerge --info Portage 2.1.6.4 (default/linux/amd64/2008.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.27.7 x86_64) ================================================================= System uname: Linux-2.6.27.7-x86_64-Intel-R-_Core-TM-2_Duo_CPU_P8400_@_2.26GHz-with-glibc2.2.5 Timestamp of tree: Sat, 17 Jan 2009 11:00:05 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.4_p6, 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -mtune=nocona -mfpmath=sse -mmmx -msse -msse2 -msse3 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=nocona -mtune=nocona -mfpmath=sse -mmmx -msse -msse2 -msse3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="ru_RU.UTF-8" LC_ALL="" LDFLAGS="-Wl,-O1" LINGUAS="en ru" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="7zip X a52 aac acl acpi alsa amd64 amr ares arts automount berkdb bittorrent bluetooth bzip2 cdda cddb cdio cdparanoia cdr cg chardet cjk cli cracklib crypt css cups dbus djvu dri dv dvb dvd dvdr dvdread encode exif ffmpeg firefox flac fontconfig fortran ftp gdbm geoip gif gnutls gpm gzip hal iconv icq id3tag imagemagick imlib innodb isdnlog java java6 javascript jbig jpeg jpeg2k kde kdeprefix laptop libv4l2 lm_sensors lzo matroska metalink midi mmx mmxext mp3 mpeg mplayer mudflap multilib musepack mysql nas ncurses network networkmanager nls nptl nptlonly nsplugin nvidia ogg opengl openmp pam pcre pdf perl png pppd python qt3 qt4 quicktime raw rdesktop readline reflection samba sdl session slang smp speex spell spl srt sse sse2 sse3 sse4 ssl ssse3 stream svg sysfs syslog tcpd theora threads tiff truetype twolame unicode unrar unzip usb v4l v4l2 vcd vorbis wavpack wifi wmf x264 xattr xine xml xorg xpm xulrunner xv xvid xvmc zip zlib zvbi" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="*" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en ru" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I have a similar behaviour here after upgrading to nvidia-drivers-180.22. If I start gdm or kdm, it fails with: Failded to start the X-server... But there is no error (EE) in /var/log/Xorg.o.log. I can only find the following warnings: (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050" (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid (WW) NVIDIA(0): HorizSync range (53.398-64.075 kHz) would exclude this (WW) NVIDIA(0): mode's HorizSync (42.7 kHz); ignoring HorizSync check for (WW) NVIDIA(0): mode "1680x1050". (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050" (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid (WW) NVIDIA(0): VertRefresh range (50.000-60.000 Hz) would exclude this (WW) NVIDIA(0): mode's VertRefresh (40.1 Hz); ignoring VertRefresh check (WW) NVIDIA(0): for mode "1680x1050". (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050" (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid (WW) NVIDIA(0): HorizSync range (53.398-64.075 kHz) would exclude this (WW) NVIDIA(0): mode's HorizSync (42.7 kHz); ignoring HorizSync check for (WW) NVIDIA(0): mode "1680x1050". (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050" (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid (WW) NVIDIA(0): VertRefresh range (50.000-60.000 Hz) would exclude this (WW) NVIDIA(0): mode's VertRefresh (40.1 Hz); ignoring VertRefresh check (WW) NVIDIA(0): for mode "1680x1050". If I simply try to call startx or xdm, it works. And I get 3200 fps with glxgears. If I reboot sometimes, I can start kdm or gdm. But after login, I get again the console, at least mostly. Sometimes I still reach the desktop. Any idea why nvidia-drivers-180.2 and gdm or kdm play so bad with another. I still found one difference in Xorg.0.log in case of working or not working. In case of not working there are some additional lines at the end, starting with 'UnloadModule: "synaptics"' Any hint?
Created attachment 178892 [details] Xorg.0.log in case of error
@Sergey: Did you run `eselect opengl' afterwards?
Comment on attachment 178892 [details] Xorg.0.log in case of error @Juergen: That looks like an entirely different problem - open a new bug report, please.
(In reply to comment #3) > @Sergey: Did you run `eselect opengl' afterwards? > I run 'eselect opengl set nvidia' after driver instalation. The output is :'Switching to nvidia OpenGL interface... done' But this command includes into driver instalation script and executes automatically.(' * Adding module to moduledb. Switching to nvidia OpenGL interface... done')
(In reply to comment #4) > (From update of attachment 178892 [details] [edit]) > > @Juergen: That looks like an entirely different problem - open a new bug > report, please. > 1.I've found out libraries of nvidia-drivers-177.Then I've deleted them. 2. emerge nvidia-drivers The problem was solved.