Laptop (Dell XPS-M1210) monitor flickers using nvidia-180.xx drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-180 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 8.10-amd64
~/ lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation G72M [GeForce Go 7400] (rev a1)
Using ubuntu nvidia-glx-180.11 or PPA driver nvidia-
I do not have any problems with drivers 173 or 177, Only 180's. Have tried 180.11 and 180.29
I have a laptop with an external monitor that I use in twinview. When I upgraded to 180.11 and rebooted the laptop screen flickers like when interlacing is enabled on CRT monitors. Only once X starts, and only on the laptop screen. The external screen is crystal clear. It's like the lines have all been shifted up half a line, and they are slightly fuzzy but still readable. It's just hard on the eyes. Not sure how else to describe it.
The laptop screen also appears like it is limited in the number of colours it displays compared to the external monitor as the gradient background image appears to have bands through it instead of being sooth like on the other monitor.
It happens with both of the 180 series drivers I tried. It also happens when the external monitor is disconnected.
I have tried deleting /etc/X11/xorg.conf and running nvidia-xconfig but it still produces the same problem.
It will go away if I go into nvidia-settings and change any setting related to the laptop screen. Ie, set refresh rate to auto instead of 60hz or vice versa and hit apply. The screen will flash black for a second the become crystal clear again. Until I restart X again.
Anything else I can try?
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelMo
Package: nvidia-glx-180 180.29-
ProcEnviron:
SHELL=/bin/bash
PATH=/
LANG=en_AU.UTF-8
SourcePackage: nvidia-
Uname: Linux 2.6.27-11-generic x86_64
UnreportableReason: This is not a genuine Ubuntu package
Hi karlbowden,
Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]