You are not logged in.
After inactivity, my monitor would power off via DPMS. Now the screen just turns black, but the backlight stays on. I'm currently running the latest nvidia-355.11-3, but the problem has existed since 352.41-1.
Last known working version was nvidia-352.30-3. It works if I roll back to that driver version.
$ xset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 660 repeat rate: 25
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/OTF/,/usr/share/fonts/Type1/,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is OnEDIT: I should also mention that running "xset dpms force off" does not power down the screen either.
Last edited by heystove (2015-10-08 05:42:25)
Offline
Same here. Interistingly
vbetool dpms force offworks
Offline
I've been having the same issue with these drivers, except when I run "xset dpms force off", my monitors shut off for a few seconds, and then they come right back on. Funnily enough, this issue only occurs with monitors attached via DisplayPort, and not HDMI, or rather HDMI via passive DisplayPort adapters. Ugh, times like this, make me wish I had waited to buy an AMD card, rather than jumping onto the Maxwell bandwagon
.
Edit: I noticed this appear in my Xorg log after I ran "xset dpms force off".
[ 9033.366] (--) NVIDIA(GPU-0): CRT-0: disconnected
[ 9033.366] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 9033.366] (--) NVIDIA(GPU-0):
[ 9033.369] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 9033.369] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 9033.369] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 9033.369] (--) NVIDIA(GPU-0):
[ 9033.369] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 9033.369] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 9033.369] (--) NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
[ 9033.369] (--) NVIDIA(GPU-0):
[ 9033.369] (--) NVIDIA(GPU-0): DELL U2414H (DFP-2): connected
[ 9033.369] (--) NVIDIA(GPU-0): DELL U2414H (DFP-2): Internal DisplayPort
[ 9033.369] (--) NVIDIA(GPU-0): DELL U2414H (DFP-2): 960.0 MHz maximum pixel clock
[ 9033.369] (--) NVIDIA(GPU-0):
[ 9033.370] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 9033.370] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 9033.370] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 9033.370] (--) NVIDIA(GPU-0):
[ 9033.370] (--) NVIDIA(GPU-0): DELL U2414H (DFP-4): connected
[ 9033.370] (--) NVIDIA(GPU-0): DELL U2414H (DFP-4): Internal DisplayPort
[ 9033.370] (--) NVIDIA(GPU-0): DELL U2414H (DFP-4): 960.0 MHz maximum pixel clock
[ 9033.370] (--) NVIDIA(GPU-0):
[ 9033.370] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 9033.370] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[ 9033.370] (--) NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
[ 9033.370] (--) NVIDIA(GPU-0):
[ 9033.371] (--) NVIDIA(GPU-0): DELL U2414H (DFP-6): connected
[ 9033.371] (--) NVIDIA(GPU-0): DELL U2414H (DFP-6): Internal DisplayPort
[ 9033.371] (--) NVIDIA(GPU-0): DELL U2414H (DFP-6): 960.0 MHz maximum pixel clock
[ 9033.371] (--) NVIDIA(GPU-0):
[ 9033.371] (--) NVIDIA(GPU-0): DFP-7: disconnected
[ 9033.371] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[ 9033.371] (--) NVIDIA(GPU-0): DFP-7: 330.0 MHz maximum pixel clockLast edited by sapphirus (2015-10-09 07:01:08)
Offline
Same issue here. I have two monitors one connected via DVI and one via DisplayPort. Monitor connected via DVI switches off just fine, but the one connected via DisplayPort does not. I have GTX 960 card.
Offline
OP, here. I'm connected via DisplayPort, too.
Offline
Guys, good news! I've discovered a simple workaround to this whole conundrum
! Just downgrade your driver from 352-355.xx to 346.87. First, you'll need to remove the drivers installed from Arch's repositories. Then just download the appropriate driver off of Nvidia's website here, run the binary as root, and just follow the onscreen instructions to install. Unfortunately, GTX 950 users will have to wait until Nvidia resolves this issue with versions 352.xx or later.
Last edited by sapphirus (2015-10-10 05:57:44)
Offline
on nvidia forum, nvidia is of course blaming the monitor. I have 3 monitors from 3 different manufacturers and all behave the same.
Offline
OT, but.......
@sapphirus. Please do not recommend installing software outside of pacman. You are setting yourself up for trouble down the road. If you can't find the driver version you want from the AUR, and for some reason you can't downgrade to an earlier pacman package from your cache, create your own PKGBUILD for the driver version you want. You and anyone following your advice on installing from nVidia's site will almost assuredly have issues when pacman tries to upgrade the nVidia drivers or the Linux Kernel built against a newer nVidia driver later on, and the upgrade will fail. I know you're new here, but you need to read up on package management with Arch using pacman before you tell someone to almost definitely cause themselves problems for future upgrades.
Matt
"It is very difficult to educate the educated."
Offline
disabling Displayport v1.2 (falling back to 1.1a) on my monitors gives back the monitor sleep
Offline
nvidia 358.16 should have solved this issue.
Offline
nvidia 358.16 should have solved this issue.
358.16 didn't fix this problem for me, neither did switching from displayport 1.2. Could it be because I'm using a ck version of the nvidia driver?
Anyone else still having this after 358.16?
Offline
Matt3o wrote:nvidia 358.16 should have solved this issue.
358.16 didn't fix this problem for me, neither did switching from displayport 1.2. Could it be because I'm using a ck version of the nvidia driver?
Anyone else still having this after 358.16?
These issues were resolved for me after upgrading to 358.16.
Last edited by sapphirus (2015-12-16 00:54:39)
Offline