After upgrading to nvidia-kernel/glx 1.0.8756, the nvidia driver no longer detected monitor resolutions and frequencies here at all (the only available mode was 1024x768@70hz). I didn't modify xorg.conf at all when upgrading, but when the modes didn't work I tried explicitly setting 'Option "UseEDID" "True"', with no effect. Simply downgrading to 1.0.8178 fixed the problem, making all modes available again (ranging from 320x175 to 1400x1050, 60 to 85 hz). # emerge --info Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r5 x86_64) ================================================================= System uname: 2.6.15-gentoo-r5 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r7 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.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-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/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="ftp://trumpetti.atm.tut.fi/gentoo/ http://mirror.gentoo.no/" LANG="nb_NO" LC_ALL="nb_NO" LINGUAS="nb no en" 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="amd64 16bit 7zip S3TC X Xaw3d a52 aac aalib acl acpi alsa apache2 applet artworkextra asf audiofile avi bash-completion berkdb bitmap-fonts browserplugin bzip2 cairo ccache cdparanoia cdr cli crypt css ctype cups curl dba dbus dga dri dvd dvdr dvdread eds elf emboss encode ethereal exif expat fam fame fastbuild fat ffmpeg flac flash foomaticdb force-cgi-redirect fortran ftp gcj gd gdb gif gimp glitz glut glx gnome gpm graphviz gstreamer gtk gtk2 gtkhtml guile gzip h323 hal i8x0 idn ieee1394 imagemagick imap imlib imlib2 intl ipv6 isdnlog jabber jack jack-tmpfs java javascript jpeg junit kde kdeenablefinal kqemu lame lcms libcaca libwww linguas_nb linuxthreads-tls logitech-mouse lua lzo lzw lzw-tiff mad matroska md5sum memlimit mhash mikmod ming mjpeg mmap mng mod modplug mono mozilla mp3 mp4live mpeg mpeg2 mplayer music musicbrainz ncurses nforce2 nls nptl nsplugin ntfs nvidia nvram objc ocaml ogg oggvorbis openal opengl openssh openssl oss pam pcre pdflib perl physfs png pnp posix povray pppd python qemu-fast qt quicktime rar readline samba scanner sdk sdl session sharedext sharedmem sid simplexml slang smp sms soap sockets speex spell spl sse-filters ssl startup-notification stencil-buffer subtitles subversion svg sysfs tcpd tga theora thesaurus threads tiff timidity tokenizer transcode truetype truetype-fonts type1 type1-fonts udev usb videos vorbis wma wma123 wxwindows x264 xanim xine xml xml2 xmms xpm xrandr xscreensaver xsl xv xvid yv12 zip zlib linguas_no linguas_en userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LDFLAGS
The same thing happens here. Now I cant work in linux in X11 because at 70hz my monitor displays a very bad image. # emerge info Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64) ================================================================= System uname: 2.6.15-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.14 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 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.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.roedu.net/pub/mirrors/gentoo.org" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="amd64 X a52 aac alsa audiofile avi bitmap-fonts bzip2 cdr cli crypt ctype curl dba dri dvd dvdr emboss encode exif expat fam fastbuild ffmpeg flac font-server foomaticdb force-cgi-redirect ftp gd gif glut gmp gphoto2 gstreamer gtk2 idn imlib isdnlog jpeg kde kdeenablefinal lcms live lm_sensors lzw lzw-tiff mad memlimit mng mp3 mpeg musicbrainz ncurses network nodrm nptl ogg oggvorbis openal opengl oss pam pdflib png posix pppd quicktime readline rtc samba sdl session simplexml soap sockets spl sqlite ssl subversion tiff tokenizer truetype truetype-fonts type1-fonts udev usb vorbis wmf xml xml2 xpm xsl xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Well - so, due to some ingenious upstream, you can no longer have modes named like Mode "1024x768" honored by this drivers version. Name them in a unique way (like Mode "uhthissucks" and they'll get honored...
(In reply to comment #2) > Well - so, due to some ingenious upstream, you can no longer have modes named > like Mode "1024x768" honored by this drivers version. Name them in a unique way > (like Mode "uhthissucks" and they'll get honored... > It seems that not even this works. Please have a look at: http://bugs.gentoo.org/show_bug.cgi?id=129361#c2
(In reply to comment #2) > Well - so, due to some ingenious upstream, you can no longer have modes named > like Mode "1024x768" honored by this drivers version. Name them in a unique way > (like Mode "uhthissucks" and they'll get honored... It can't just be a naming problem, as I have no modes listed in my xorg.conf at all. In stead, I'm letting the driver autodetect modes using EDID. This works fine with 8178, but not with 8756.
*** Bug 129361 has been marked as a duplicate of this bug. ***
No longer. It is not really a duplicate.
I don't have any ModeLine either. My monitor always worked out of the box on linux/windows (1024x768@85Hz). I wanted to double check something but this is funny :) I noticed that if the X server starts while the monitor is shut down then (when I start the monitor) it has 1024x768@85Hz but if I have it open when I restart X (ctrl-backspace) it goes again to 1024x768@70Hz. I don't know how much informative this...
Really don't know if it can help, but... I had some problems when upgrading from 1.0.8178 to 1.0.8756. I had to use: Option "ExactModeTimingsDVI" "true" for my display to be correct. Note that I use also: Option "UseEDID" "false" ...due to a bug in my monitor that does not return correct EDID values.
Option "ExactModeTimingsDVI" "true" Option "UseEDID" "false" Using both of the options above solved the problems for me too. Any update on the upstream on this problem ?
Setting UseEDID to false doesn't really solve the problem for those of us who *want* the driver to use EDID .. (People seem to be talking about two different bugs here)
This bug is still present in 1.0.8767. Something did change, as I get 1024x768 @ 85 hz with 1.0.8767 in stead of the 70 hz I got with 1.0.8756, but 1.0.8767 still does not detect any other EDID monitor modes.
Still broken in 1.0.8774.
Does this still occur w/ 9631/9746?
For me, 9631 is ok 9746 is not. Below are excerpts of my xorg log. xorg.conf does not change. xorg.conf Section "Device" Identifier "NVIDIA 7900GT" Driver "nvidia" Option "HWcursor" "true" #Option "XvmcUsesTextures" "true" Option "AllowGLXWithComposite" "true" Option "AddARGBGLXVisuals" "true" Option "NoLogo" "false" Option "RenderAccel" "true" Option "CursorShadow" "true" Option "BackingStore" "true" Option "UseEDID" "true" Option "ExactModeTimingsDVI" "true" EndSection Section "Screen" Identifier "Screen 1" Device "NVIDIA 7900GT" Monitor "AL1916W" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1440 x 900" ViewPort 0 0 EndSubsection EndSection Xorg.0.log 9631: (--) NVIDIA(0): --- EDID for Acer AL1916W (DFP-0) --- (--) NVIDIA(0): EDID Version : 1.3 (--) NVIDIA(0): Manufacturer : ACR (--) NVIDIA(0): Monitor Name : Acer AL1916W (--) NVIDIA(0): Product ID : 44416 (--) NVIDIA(0): 32-bit Serial Number : 0 (--) NVIDIA(0): Serial Number String : 641022774000 (--) NVIDIA(0): Manufacture Date : 2006, week 41 (--) NVIDIA(0): DPMS Capabilities : Standby Suspend Active Off (--) NVIDIA(0): Prefer first detailed timing : No (--) NVIDIA(0): Supports GTF : No (--) NVIDIA(0): Maximum Image Size : 410mm x 260mm (--) NVIDIA(0): Valid HSync Range : 31 kHz - 84 kHz (--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 76 Hz (--) NVIDIA(0): EDID maximum pixel clock : 156.0 MHz (II) NVIDIA(0): Validating Mode "1440x900": (II) NVIDIA(0): 1440 x 900 @ 60 Hz (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 89.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1440, 1488 (II) NVIDIA(0): HSyncEnd, HTotal : 1520, 1600 (II) NVIDIA(0): VRes, VSyncStart : 900, 903 (II) NVIDIA(0): VSyncEnd, VTotal : 909, 926 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): Assigned Display Device: DFP-0 (II) NVIDIA(0): Requested modes: (II) NVIDIA(0): "1440 x 900" (II) NVIDIA(0): Validated modes: (II) NVIDIA(0): MetaMode "1440 x 900": (II) NVIDIA(0): Bounding Box: [0, 0, 1440, 900] (II) NVIDIA(0): Acer AL1916W (DFP-0): "1440 x 900" (II) NVIDIA(0): Size : 1440 x 900 (II) NVIDIA(0): Offset : +0 +0 (II) NVIDIA(0): Panning Domain: @ 1440 x 900 (II) NVIDIA(0): Position : [0, 0, 1440, 900] (II) NVIDIA(0): Virtual screen size determined to be 1440 x 900 Xorg.0.log 9746 (--) NVIDIA(0): --- EDID for Acer AL1916W (DFP-0) --- (--) NVIDIA(0): EDID Version : 1.3 (--) NVIDIA(0): Manufacturer : ACR (--) NVIDIA(0): Monitor Name : Acer AL1916W (--) NVIDIA(0): Product ID : 44416 (--) NVIDIA(0): 32-bit Serial Number : 0 (--) NVIDIA(0): Serial Number String : 641022774000 (--) NVIDIA(0): Manufacture Date : 2006, week 41 (--) NVIDIA(0): DPMS Capabilities : Standby Suspend Active Off (--) NVIDIA(0): Prefer first detailed timing : No (--) NVIDIA(0): Supports GTF : No (--) NVIDIA(0): Maximum Image Size : 410mm x 260mm (--) NVIDIA(0): Valid HSync Range : 31.0 kHz - 84.0 kHz (--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 76 Hz (--) NVIDIA(0): EDID maximum pixel clock : 156.0 MHz (II) NVIDIA(0): Validating Mode "1440x900": (II) NVIDIA(0): 1440 x 900 @ 60 Hz (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 89.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1440, 1488 (II) NVIDIA(0): HSyncEnd, HTotal : 1520, 1600 (II) NVIDIA(0): VRes, VSyncStart : 900, 903 (II) NVIDIA(0): VSyncEnd, VTotal : 909, 926 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: Mode (1440 x 900) is too large for DFP (WW) NVIDIA(0): Native Resolution (Max: 1400 x 1050). (II) NVIDIA(0): Assigned Display Device: DFP-0 (II) NVIDIA(0): Requested modes: (II) NVIDIA(0): "1440 x 900" (WW) NVIDIA(0): No valid modes for "1440 x 900"; removing.
Have you tried with nvidia-drivers-1.0.9755-r1 ? I don't have this problem :-/, Have you tried disabling DynamicTwinView ?
(In reply to comment #14) > For me, 9631 is ok 9746 is not. >........ > (WW) NVIDIA(0): Mode is rejected: Mode (1440 x 900) is too large for DFP > (WW) NVIDIA(0): Native Resolution (Max: 1400 x 1050). > > (II) NVIDIA(0): Assigned Display Device: DFP-0 > (II) NVIDIA(0): Requested modes: > (II) NVIDIA(0): "1440 x 900" > (WW) NVIDIA(0): No valid modes for "1440 x 900"; removing. > Please, check the following: http://www.nvnews.net/vbulletin/showthread.php?t=83658 Good luck!
As per the nVidia forum post linked that provided a solution from an nVidia employee, this bug can be closed. The issue is a configuration problem as some configuration settings have changed in newer nVidia driver versions.
