Discussion:
x11: Primary monitor goes black randomly
(too old to reply)
Rares Vernica
2016-07-14 16:28:36 UTC
Permalink
Hello,

I am using an HP Elitebook 2560p which has an integrated Intel video card.
I use two external monitors, one connected on the DisplayPort as primary
and one on the VGA port as secondary. I am not using the built-in display.

I use x11 with xfce and the Intel driver. It all works fine, except that
the the primary monitor (on the DisplayPort) goes black at random times.
Once black, the monitor reports no signal and goes on stand by. It does not
resume working if I move the mouse or type on the keyboard. One way I
managed to recover it is to turn the display off with xrandr and then back
on.

I reported a bug on FreeBSD but I wonder if there are other things I can
try or other workarounds less intrusive than the xrandr off/on one that I
am using. See here for the bug report, log output, and version info:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210929

Thanks!
Rares
Charles W. Ross
2016-07-14 18:54:27 UTC
Permalink
Try disabling the screen saver and/or DPMS (energy saver) via the xset
command.

To see what your current settings are, type 'xset q'

To disable DPMS, type 'xset -dpms'

To disable the screen saver, type 'xset s off'

Note: these settings will not persist after you quit your current
session or reboot the machine.

Hope this gives you a starting point.

Charlie
Post by Rares Vernica
Hello,
I am using an HP Elitebook 2560p which has an integrated Intel video
card.
I use two external monitors, one connected on the DisplayPort as primary
and one on the VGA port as secondary. I am not using the built-in
display.
I use x11 with xfce and the Intel driver. It all works fine, except that
the the primary monitor (on the DisplayPort) goes black at random times.
Once black, the monitor reports no signal and goes on stand by. It does
not
resume working if I move the mouse or type on the keyboard. One way I
managed to recover it is to turn the display off with xrandr and then
back
on.
I reported a bug on FreeBSD but I wonder if there are other things I can
try or other workarounds less intrusive than the xrandr off/on one that I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210929
Thanks!
Rares
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Rares Vernica
2016-07-14 19:49:55 UTC
Permalink
Thanks for the suggestions. I tried both, but they did not help. Here is
Post by Charles W. Ross
xset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Shift Lock: off 04: Group 2: off 05: Mouse Keys: off
auto repeat delay: 500 repeat rate: 20
auto repeating keys: 00feffffdffffbbf
fadfffffffdfe5ef
ffffffffffffffff
ffffffffffffffff
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: 0 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:

/usr/local/share/fonts/misc/,/usr/local/share/fonts/TTF/,/usr/local/share/fonts/OTF/,/usr/local/share/fonts/Type1/,/usr/local/share/fonts/100dpi/,/usr/local/share/fonts/75dpi/,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Disabled
Font cache:
Server does not have the FontCache Extension

Thanks!
Rares
Post by Charles W. Ross
Try disabling the screen saver and/or DPMS (energy saver) via the xset
command.
To see what your current settings are, type 'xset q'
To disable DPMS, type 'xset -dpms'
To disable the screen saver, type 'xset s off'
Note: these settings will not persist after you quit your current
session or reboot the machine.
Hope this gives you a starting point.
Charlie
Post by Rares Vernica
Hello,
I am using an HP Elitebook 2560p which has an integrated Intel video
card.
I use two external monitors, one connected on the DisplayPort as primary
and one on the VGA port as secondary. I am not using the built-in
display.
I use x11 with xfce and the Intel driver. It all works fine, except that
the the primary monitor (on the DisplayPort) goes black at random times.
Once black, the monitor reports no signal and goes on stand by. It does
not
resume working if I move the mouse or type on the keyboard. One way I
managed to recover it is to turn the display off with xrandr and then
back
on.
I reported a bug on FreeBSD but I wonder if there are other things I can
try or other workarounds less intrusive than the xrandr off/on one that I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210929
Thanks!
Rares
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Perry Hutchison
2016-07-15 08:10:49 UTC
Permalink
Post by Rares Vernica
I am using an HP Elitebook 2560p which has an integrated Intel video card.
I use two external monitors, one connected on the DisplayPort as primary
and one on the VGA port as secondary. I am not using the built-in display.
I use x11 with xfce and the Intel driver. It all works fine, except that
the the primary monitor (on the DisplayPort) goes black at random times.
Once black, the monitor reports no signal and goes on stand by. It does
not resume working if I move the mouse or type on the keyboard. One way I
managed to recover it is to turn the display off with xrandr and then back
on.
I suspect this is an x11 problem, not a FreeBSD problem.

I have been seeing something similar on a Dell laptop, using gnome,
with the built-in display as primary and an external 1920x1080
flatscreen on a DVI port (on the docking station) as secondary.
The primary occasionally goes blank just after logging in (via xdm),
about the time when xrandr would be setting up the dual screens,
and the only way I've found to bring it back is to tweak the screen
positions slightly in gnome-control-center (which then presumably
runs xrandr when I click Apply). I suspect a race condition since
it happens only occasionally.

So why do I think this is not a FreeBSD issue? Because it happens
on Fedora Linux (at $DAYJOB).

Loading...