Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 03-31-12, 08:17 AM   #1
dinsdale2
Registered User
 
Join Date: Mar 2012
Posts: 5
Default 295.33 unreadable display after resume on external monitor via displayport 2560x1440

I run the 295.33 nvidia binary driver on Archlinux 64Bit (latest updates, X.Org X Server 1.12.0)
I use an attached second yamakasi monitor with the supported resolution of 2560x1440 on a Thinkpad T520 with the Nvidia NVS 4200m. The monitor is connected via the DisplayPort and an active DVI adapter (Bizlink, Dell)

Upon resume (monitor goes to sleep not resume from suspend) more often than not the external display has garbled and unreadable text and graphics. The resulting display error is best described as a 'really bad vertical interlacing error'
I tried to make a screenshot however the error doesn't show up on the screenshot and I currently don't have a digital camera. The native LCD monitor of the laptop is fine, only the external monitor is affected.

The only remedy is to actually reboot the computer which has to be hard reset. Once the error occures the shutdown hardlocks the system and vertical red lines appear on the external monitor while the native lcd monitor just displays blank. Also trying to 'unset' the monitor in nvidia-settings has the same effet of crash and red stripes.

I haven't been able to reproduce the error artifcially by suspending the monitor manually by running the command:
Code:
xset -display :0 dpms force off
My corresponding xorg file:
10-monitor.conf

Code:
Section "ServerLayout"      
    Identifier     "DualSreen"
    Screen       0 "Screen0"
    Screen       1 "Screen1"
    Option         "Xinerama" "0" #To move windows between screens
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    Option         "Enable" "true"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    Option         "Enable" "true"
        HorizSync       89.52
        VertRefresh     59.96
        Modeline "2560x1440_60.00"  311.83  2560 2744 3024 3488  1440 1441 1444 1490  -HSync +Vsync

EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    Screen         0
Option          "RegistryDwords" "EnableBrightnessControl=1"
Option         "CustomEDID" "DFP-4: /etc/X11/yamakasi_27inch.bin"
#Option "IgnoreEDID" "true" 
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    Screen         1
Option          "RegistryDwords" "EnableBrightnessControl=1"
#       Option "IgnoreEDID" "true" 
        Option         "CustomEDID" "DFP-4: /etc/X11/yamakasi_27inch.bin"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    SubSection "Display"
        Depth          24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth   24
    Option         "TwinView" "1"
    SubSection "Display"
        Depth          24
        #Modes          "2560x1440_60.00"
    EndSubSection
EndSection
Below is what I find in my Xorg.log file when the problem appears:


Code:
[    15.808] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 21964.128] (II) evdev: Power Button: Close
[ 21964.129] (II) UnloadModule: "evdev"
[ 21964.154] (II) evdev: Video Bus: Close
[ 21964.154] (II) UnloadModule: "evdev"
[ 21964.204] (II) evdev: Sleep Button: Close
[ 21964.204] (II) UnloadModule: "evdev"
[ 21964.257] (II) evdev: Chicony  PFU-65 USB Keyboard: Close
[ 21964.257] (II) UnloadModule: "evdev"
[ 21964.364] (II) evdev: Microsoft Microsoft(R) Compact Optical Mouse: Close
[ 21964.364] (II) UnloadModule: "evdev"
[ 21964.424] (II) evdev: Integrated Camera: Close
[ 21964.424] (II) UnloadModule: "evdev"
[ 21964.454] (II) evdev: AT Translated Set 2 keyboard: Close
[ 21964.454] (II) UnloadModule: "evdev"
[ 21964.667] (II) UnloadModule: "synaptics"
[ 21964.721] (II) evdev: ThinkPad Extra Buttons: Close
[ 21964.721] (II) UnloadModule: "evdev"
[ 21964.827] (II) evdev: TPPS/2 IBM TrackPoint: Close
[ 21964.828] (II) UnloadModule: "evdev"
[ 21975.881] (EE) NVIDIA(GPU-0): Failed to tear down EVO channel
dinsdale2 is offline   Reply With Quote
Old 03-31-12, 10:15 AM   #2
Plagman
NVIDIA Corporation
 
Plagman's Avatar
 
Join Date: Sep 2007
Posts: 254
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

Does the problem reproduce if you set Option "UseDPLib" "0" in xorg.conf?
Plagman is offline   Reply With Quote
Old 04-01-12, 04:55 PM   #3
dinsdale2
Registered User
 
Join Date: Mar 2012
Posts: 5
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

Quote:
Originally Posted by Plagman View Post
Does the problem reproduce if you set Option "UseDPLib" "0" in xorg.conf?
I will try the suggested option and have changed the corresponding screen section of my xorg file so it reads now:

Code:
Section "Screen"                                                                                                                                     
    Identifier     "Screen1"                                                                                                                         
    Device         "Device1"                                                                                                                         
    Monitor        "Monitor1"                                                                                                                        
    DefaultDepth   24                                                                                                                                
    Option         "TwinView" "1"
        Option "UseDPLib" "0"
    SubSection "Display"
        Depth          24
        #Modes          "2560x1440_60.00"
    EndSubSection
EndSection
dinsdale2 is offline   Reply With Quote
Old 04-02-12, 10:47 AM   #4
dinsdale2
Registered User
 
Join Date: Mar 2012
Posts: 5
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

Quote:
Originally Posted by Plagman View Post
Does the problem reproduce if you set Option "UseDPLib" "0" in xorg.conf?
Just happened again so above option does not solve the problem.
dinsdale2 is offline   Reply With Quote
Old 04-03-12, 02:51 PM   #5
dinsdale2
Registered User
 
Join Date: Mar 2012
Posts: 5
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

I tried disabling the energy saving options in KDE but it didn't help. I noticed though that it appears only the second time the monitor goes into standby the problem occurs. Currently I have to reboot my laptop at least twice per day which is very annoying.

Anything else I can do to help get to the bottom of this?
dinsdale2 is offline   Reply With Quote
Old 04-05-12, 03:57 AM   #6
dinsdale2
Registered User
 
Join Date: Mar 2012
Posts: 5
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

Is it possible the problem is related to the energy saving options of the gfx card? As mentioned below - relatively short periods of monitor suspend don't lead to a problem - also this morning when I woke up the monitor the picture was still clear - an hour later when the monitor went to sleep for 30 mins or so the picture was scrambled.

Is it possible that during longer suspend periods the gfx card goes into a deeper state of sleep and that the problem only happens after the card goes to sleep for a second time? Or does this point more to a physical hardware defect. I have a lenovo T520 which still has guarantee however it expires soon so I will have to make a decision whether to send it back or not rather soon than later.
dinsdale2 is offline   Reply With Quote
Old 04-18-12, 01:56 PM   #7
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: 295.33 unreadable display after resume on external monitor via displayport 2560x1

I debugged something that sounds similar, but it's not related to how long the display is asleep. Rather, it's random whether or not the problem will occur. Does the problem go away if you run "xset dpms force off" and then hit a key or move the mouse to wake it back up, repeating those steps a few times?

If so, then it should be fixed in a future release.
AaronP is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 10:16 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.