View Single Post
Old 03-25-12, 05:38 PM   #7
alan242
Registered User
 
Join Date: Sep 2006
Posts: 20
Default Re: Random video hangs after upgrading from 290.10 to 295.9 and 295.17

Well, in your original post, your bug report shows there's problems with your X setup. Specifically,

[3235440.663] (WW) Warning, couldn't open module dri
[3235440.663] (II) UnloadModule: "dri"
[3235440.663] (II) Unloading dri
[3235440.663] (EE) Failed to load module "dri" (module does not exist, 0)
[3235440.663] (II) LoadModule: "dri2"
[3235440.663] (WW) Warning, couldn't open module dri2
[3235440.663] (II) UnloadModule: "dri2"
[3235440.663] (II) Unloading dri2
[3235440.663] (EE) Failed to load module "dri2" (module does not exist, 0)


[3235442.928] (WW) NVIDIA(0): The EDID for Mitsubishi MEUSPTV10 (DFP-0) contradicts itself:
[3235442.928] (WW) NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the
[3235442.928] (WW) NVIDIA(0): EDID's valid VertRefresh range (59.000-61.000 Hz) would
[3235442.928] (WW) NVIDIA(0): exclude this mode's VertRefresh (30.0 Hz); ignoring
[3235442.928] (WW) NVIDIA(0): VertRefresh check for mode "1920x1080".


[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[3235443.093] (WW) NVIDIA(0): such display device could be found, or all display devices
[3235443.093] (WW) NVIDIA(0): by that name are currently unavailable.
[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[3235443.093] (WW) NVIDIA(0): display device could be found, or all display devices by
[3235443.093] (WW) NVIDIA(0): that name are currently unavailable.

and lastly

[3235443.094] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0)
[3235443.094] (II) NVIDIA(0): The X server will not be able to send the VDPAU driver name to
[3235443.094] (II) NVIDIA(0): libvdpau.

So you need to figure out what's causing those issues.

Once your X setup is cleaned up and there are no more warnings or errors in the log, if you still have the problem, you may need to disable MSI interrupts. Either the motherboard or the video card might be having problems with using that interrupt mechanism. To disable MSI, you'll need to pass the parm NVreg_EnableMSI=0 to the nvidia kernel driver.
alan242 is offline   Reply With Quote