Red Hat Bugzilla – Bug 511321
nouveau driver causing monitor oddness
Last modified: 2014-06-29 19:01:28 EDT
Description of problem:
Upgraded to F11 last night and decided to dump the nvidia driver since nouveau supports dual-head configurations. I moved my previously-working F10 xorg.conf out of /etc/X11/, rmmoded the nvidia driver, and started X.
Everything seemed to be working well and the display configuration allowed me to setup my dual-monitor perfectly. I was quite pleased this was working.
After a short while, I started to notice what I first thought were some dead or stuck pixels on my primary LCD (Dell 2001FP) but realized if I moved a window over to those pixels, they were not a problem with the LCD, but with X or the driver. This was only happening on the primary display device (the left one in this case). The right display showed no strange 'stuck' pixels (but it could be that I just didn't notice them.
I've also found that I could not consistently wake up the left monitor when the screens went black when the screensaver (which is set to just a blank screen) would run. I would have to switch inputs (this model has 4 selectable ones) or turn the monitor on and off to get the screen to come back.
Version-Release number of selected component (if applicable):
The display that could not be restored without messing with the monitor happened 4 times this morning, so I can probably reproduce it on demand.
Steps to Reproduce:
1. Boot system and login to X.
2. Wait until screensaver (blank) runs.
Left display does not show an image without messing with the settings or power-cycling it.
Left display powers up and shows information just like the right display does.
$ lspci -vs 05:00.0
05:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro PCI-E Series] (rev a2) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 0215
Flags: bus master, fast devsel, latency 0, IRQ 20
Memory at a2000000 (32-bit, non-prefetchable) [size=16M]
Memory at b0000000 (32-bit, prefetchable) [size=256M]
Memory at a1000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nvidia, nouveau
$ uname -a
Linux quad 184.108.40.206-191.fc11.x86_64 #1 SMP Tue Jun 16 23:23:21 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
I was really hoping this wasn't my monitor dying, so I restored xorg.conf, modprobed the nvidia driver, and restarted X. So far I do not notice the odd stuck pixels or problems coming back when the system was locked, running screen-saver. I'll monitor that and post back if that changes.
Can we get your X logs? Thanks.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Fedora Bugzappers volunteer triage team
I'll try and provide this info when I can reboot and try the latest kernel. It apprears my Xorg.0.log only shows what's running right now, not the old config....
yes, Xorg.0.log is rewritten every time X starts. Thanks.
Fedora Bugzappers volunteer triage team
Created attachment 356943 [details]
Created attachment 356944 [details]
When I restarted my system today I noticed that the nvidia driver had not been built for the newly installed kernel (220.127.116.11-217.2.3.fc11), so I went ahead and tested nouveau for a while this morning.
It generally seemed to work well, but I got up to do something and when I came back it would not come back from a blank screen (I also use the blank-screen as my screensaver).
The Xorg.0.log.frozenx file will probably contain a few restarts because I didn't wipe my xorg.conf file before using the nouveau driver, so I had to delete it and restart X.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
So I just rebooted to use the nouveau driver included with 18.104.22.168-96.fc11.x86_64 and I'll report back any problems I find.
More lockups using nouveau from 22.214.171.124-96.fc11.x86_64, but I'll try a live usb image sometime soon (I'll have to schedule a reboot) and see what it looks like.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.