The nv driver fails to work for me.
Either at rhgb, or at X startup if rhgb is disabled, it shows a bunch of green
stripes on gray background. Then white stripes are added a bit later.
The consoles (CTRL-ALT-F*) do not refresh properly, and will get "stuck" not
displaying what I type, until I switch to a different console, and back to the
The nvidia driver does not suffer from the same problem. However, killing X from
a nv-driver startup, and switching to nvidia results to odd behavior, such as
(1) dimmed console, and (2) losing the ability to switch to a console (black
I see no error message in the X log other than this:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(I use the nvidia libGL, and also, the nvidia GLX extension is installed).
I've seen this bug before, and then it was fixed, I believe here:
* Wed Jan 18 2006 Mike A. Harris <firstname.lastname@example.org> 1.0.1-1
- Updated to xserver 1.0.1 from X11R7.0
... It must have been reintroduced after that, or the nvidia libGL is breaking
something (which doesn't make much sense to me)
Asus A8N-SLI motherboard (64-bit, PCI-E) with single card
Nvidia GeForce 6800 GS, 256RAM:
(--) PCI:*(1:0:0) nVidia Corporation NV41.0 rev 162, Mem @ 0xd0000000/24,
0xc0000000/28, 0xd1000000/24, BIOS @ 0xd2000000/17
More info on request..
Please report this issue to X.Org developers by filing a bug report in
the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "NEEDINFO_REPORTER", awaiting X.Org bug URL
Thanks for the upstream bug URL. We'll track the driver bug in the X.Org
bugzilla now, however in order to work around the problem in the existing
driver until a real fix is available, we need to know the exact PCI ID
of your chip.
Please attach your X server log file and config file to the report as
uncompressed attachments using the link below.
moving to upstream, will pull fix from there once one exists.