Xorg nv Driver uses wrong sync frequencies with GeForce 6150SE nForce 430

[Scott Talbert]

Binary package hint: xserver-xorg-video-nv

This problem occurs in Ubuntu 8.06 using the open source nv xorg driver. Basically the lower half of the screen flashes (it's hard to describe exactly - see the attachment for a video) while this driver is in use with an nVidia GeForce 6150SE nForce 430 video card. When I switch to the proprietary nVidia driver, this problem goes away.

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1)
     Subsystem: Giga-byte Technology Unknown device [1458:5001]
00:0d.0 VGA compatible controller [0300]: nVidia Corporation GeForce 6100 nForce 430 [10de:03d0] (rev a2) (prog-if 00 [VGA controller])
     Subsystem: Giga-byte Technology Unknown device [1458:d000]

[Scott Talbert (swt-techie)]

Ooops, I meant Ubuntu 8.04 (Hardy).

[K. Deniz Ogut (kdenizogut)]

I have a similar problem: Ubuntu 8.04 with nvidia Go 7600 graphic card. Problem is, screen flashes (like a blink) some 4 times a minute. I have the packages "Non-free Linux 2.6.24 modules on x86/x86_64" and "nvidia-glx-new" installed which I believe to be the proper choices. I have another distro installed on the same laptop and it does not show this behavior so I think its not an absolute hardware specific problem which can not be solved under Linux. I can supply you with further info if you ask me for the outputs of some command but please write the commands in full. Regards.

[Scott Talbert (swt-techie)]

This issue still exists (for me) on Ubuntu 8.10 Alpha 5, using the Live CD.

[Bryce Harrington (bryce)]

[This is an automated message]

Hi swt-techie,

Please attach the output of `lspci -vvnn` too.

[Scott Talbert (swt-techie)]

Here's my lspci output.

[Attila (comer352l)]

Created an attachment (id=21978)
xorg.conf

The monitor (Samsung SyncMaster 22353BW) complains about wrong frequency: 59.8kHz/55 Hz => should be 60Hz

=> Screen is totally corrupted.

Hardware: Geforce 6100/6150SE / nForce 430, Asus M2N-VM DH
Software: openSUSE 11.1, Xorg 7.4, X-server 1.5.2

The NVIDIA-binary driver works without problems (60Hz).
I also had no problems on openSUSE 11.0 with Xorg 7.3 / X-server 1.4.

I've already reported this bug at Novells bugzilla, and the configuration files are OK:
https://bugzilla.novell.com/show_bug.cgi?id=465190

Bugs 151180 and 12002 (at bugs.freedesktop.org) seem to be very similar.

[Attila (comer352l)]

Created an attachment (id=21979)
Xorg.0.log

[Attila (comer352l)]

Created an attachment (id=21980)
Xorg.99.log

[Attila (comer352l)]

Correction:
I've set up another openSUSE 11.0-system yesterday, and this time I got the same problem (for the first time).
So it seems to occur on Xorg 7.3/X-server 1.4 sometimes, too.

[Marc Kaplan (marc-kaplan)]

Please retest with upgrading to latest Jaunty version. If it X fails to load, please upload copy of latest Xorg.0.log file. If log shows that card is not supported, please refer to Bug 333040 for further instruction.

[Scott Talbert (swt-techie)]

I tested this with the Jaunty Alpha 6 live CD. The flashing issue still exists for me. Attached is my X.org log file, if that will shed any light on the issue.

[Scott Talbert (swt-techie)]

Actually, this bug appears to be caused by X picking a vertical refresh rate that is outside the range of my monitor (NEC LCD 1700V). I tried using a different monitor and the issue goes away.

[Scott Talbert (swt-techie)]

I'm seeing this same bug as well with a GeForce 6150SE nForce 430 using the nv driver on Ubuntu Intrepid w/ X server 1.5.2. X reports that it is using a Modeline which should result in 64.0 kHz/60.0 Hz; in reality the monitor reports that it is being driven at 59.2 kHz/55.5 Hz. When I use the nVidia binary driver, X reports using the same exact Modeline but the monitor is driven at the correct rate (64.0 kHz/60.0 Hz).

[Scott Talbert (swt-techie)]

X is using a Modeline which should result in a 64.0 kHz / 60.0 Hz refresh rate. However, the monitor reports that the refresh rate is actually 59.2 kHz / 55.5 Hz. When I use the nvidia proprietary driver, X uses the same Modeline; however, the monitor is actually driven at 64.0 kHz / 60.0 Hz.

I found that this bug has been reported upstream already. I'll add a link to it.

[Scott Talbert (swt-techie)]

The patch provided in bug 12002 resolved this issue for me.

[Scott Talbert (swt-techie)]

This issue does not occur for me when using the nouveau driver in Karmic (it does, however, still occur when using the nv driver in Karmic).

[Bryce Harrington (bryce)]

We'll be moving to the -nouveau driver in Lucid. In the upstream bug you indicated that there was a patch that solved it; presumably we need to pull that in.

https://bugs.freedesktop.org/show_bug.cgi?id=12002

[Scott Talbert (swt-techie)]

Yes, the patch would resolve the issue for the -nv driver. Not sure it is worth the effort though, since you're moving to -nouveau in Lucid.

[Bryce Harrington (bryce)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.

[Corbin Simpson (mostawesomedude)]

Nobody is supporting xf86-video-nv and it will be going away at some point in the future. If your problem persists with nouveau or the proprietary driver provided by nVidia, please re-file accordingly. We apologize for the inconvenience.

This is part of an automated bulk action; if you believe that this bug was closed in error, then change the targeted component and reopen it.