Seems all my 3D graphics (opengl rasterized, etc) are all screwed-up. Stuff almost looks like ASCII Artwork!!! 2D desktop is fine. Glxgears is fine. FlightGear graphics are all screwed-up (including fgrun). Enemy Terrirtory graphics is all screwed-up. (For kicks, I removed all composite extensions and normalized all settings within xorg.conf's Device and Modules sections to no avail) For the past months, I've just masked >x11-drivers/nvidia-drivers-169* figuring this would probably get fixed sooner or later, but it still persists!
Found the solution. Right after writing this puppy up, realized I was executing nvidia-settings on X startup. Setting within nvidia-settings inhibits this 3D graphic screw-up bug by setting the following within nvidia-settings graphical frontend: OpenGL Settings > Image Settings > High Performance To temporarily resolve, probably either avoid running nvidia-settings all together, or set this setting to something lower then the "High Performance" setting using the slider bar within the nvidia-settings graphical frontend. If somebody frequents Nvidia's Linux Forums, please post/forward this bug to them on my behalf. Thanks! Once forwarded, please mark this bug as "Won't Fix"... cuz it's probably an issue with the binary driver. (One guess, an integer value was pushed around within the nvidia-drivers-169* series and this old integer value is now still being accessed by the old nvidia-settings application.)
For kicks, I am using =media-video/nvidia-settings-169.07 (latest apparent release). <shrugs>
169.07 is not the latest release and not the stable release. 169.09-r1 is marked stable and 169.12 is the latest release. NVIDIA only provides their X11 drivers in a binary fashion, as such there is not much debugging or troubleshooting Gentoo can do with issues reported about them. You can use nvidia-bug-report.sh to generate some information to e-mail over to NVIDIA @ linux-bugs@nvidia.com and you may also wish to consider exploring NVIDIA's Linux driver forum @ http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 To further assist in debugging the issue and to have more information to provide NVIDIA (and have a better chance that your issue will get fixed in the future), you can attempt to debug your X server. To debug your server properly, please follow the documentation outline here, http://www.x.org/wiki/Development/Documentation/ServerDebugging The above link does not contain references to how to perform this properly on Gentoo. In a nutshell, you must rebuild X and it's libraries with USE=debug, add -ggdb to your CFLAGS, and add splitdebug to FEATURES. More information about this can be found at http://www.gentoo.org/proj/en/qa/backtraces.xml Since this bug is with nvidia-drivers, which is a package that Gentoo has minimal control over, this bug will be marked as UPSTREAM. However, in the event that you debug your X server and can produce a backtrace, please feel free to post it here and if it is unrelated to nvidia-drivers you or a Gentoo developer can re-open this bug and address the issue where it truly lies.
From what I'm seeing, here are the latest releases of each package: =media-video/nvidia-settings-169.07 =x11-drivers/nvidia-drivers-169.12 (I think you thought I had typed "nvidia-driver-169.07" which was incorrect.) I did some searching around and found a newer release of nvidia-settings: ftp://download.nvidia.com/XFree86/nvidia-settings/ nvidia-settings-169.12.tar.gz 1249KB 02/15/08 (<-- Latest in Portage) nvidia-settings-171.05.tar.gz 1249KB 01/23/08
nvidia-drivers != nvidia-settings
Updated nvidia-settings and found it contains no fix for this issue. (Just posted an updated ebuild for nvidia-settings-171.05 -- See Bug #213204) Please note, I'm seeing this bug with any versions of =x11-drivers/nvidia-drivers-169*. The quick way to hack around this bug is using my Comment #1. (Doug, you're the one who suggested at the top of Comment #3, "169.07 is not the latest release and not the stable release" in reference to me using nvidia-settings-169.07. ;-) Since this is game related material to me & not productivity related, not too concerned who or how this info gets resolved upstream. Information only from me. I'm already well aware of this being closed/binary code. ... I'm off for now. Can close/file_upstream.
