[opensuse] Can not wake up the display
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm testing my new "server". I got an MSI Cubi N-020BEU. It's got an Intel Braswell N 3710, 1.66GHz CPU, connected to a Samsung TV via HDMI cable. Leap 42.2 running XFCE. Left running all night to check, but display powered off. This morning it would not respond to the keyboard.The TV said there was no signal in the cable. Via ssh did not see load on CPU nor messages. I killed xscreensaver. [...] Oops. Wrong. ssh was on the wrong computer :-/ I disconnected the video cable, then connected again. ctrl-alt-f1 and back. Nothing. Then ctrl-alt-backspace. Got login prompt. Not nice. I have disabled for now screen power saving features. Ideas? I suspect xscreensaver. I have to try again with it on remote. Isengard:~ # hwinfo --monitor --gfxcard --framebuffer 08: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.378] Unique ID: _Znp.qslZ+SExVcE SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Device Name: "Onboard IGD" Model: "Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x22b1 "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0xb120 Revision: 0x35 Driver: "i915" Driver Modules: "drm" Memory Range: 0x80000000-0x80ffffff (rw,non-prefetchable) Memory Range: 0x90000000-0x9fffffff (ro,non-prefetchable) I/O Ports: 0xf000-0xf03f (rw) IRQ: 123 (6257765 events) Module Alias: "pci:v00008086d000022B1sv00001462sd0000B120bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=no, avail=yes, need=no, active=unknown 21: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.RysAyeVxkx7 Parent ID: _Znp.qslZ+SExVcE Hardware Class: monitor Model: "SAMSUNG T22C350" Vendor: SAM "SAMSUNG" Device: eisa 0x0ab9 "T22C350" Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@67Hz Resolution: 640x480@72Hz Resolution: 640x480@75Hz Resolution: 800x600@60Hz Resolution: 800x600@72Hz Resolution: 800x600@75Hz Resolution: 832x624@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@70Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@75Hz Resolution: 1152x864@75Hz Resolution: 1280x720@60Hz Resolution: 1280x1024@60Hz Resolution: 1366x768@60Hz Resolution: 1920x1080@60Hz Size: 477x268 mm Year of Manufacture: 2012 Week of Manufacture: 52 Detailed Timings #0: Resolution: 1920x1080 Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz Year of Manufacture: 2012 Week of Manufacture: 52 Detailed Timings #1: Resolution: 1366x768 Horizontal: 1366 1436 1579 1792 (+70 +213 +426) +hsync Vertical: 768 771 774 798 (+3 +6 +30) +vsync Frequencies: 85.50 MHz, 47.71 kHz, 59.79 Hz Driver Info #0: Max. Resolution: 1920x1080 Vert. Sync Range: 24-75 Hz Hor. Sync Range: 15-81 kHz Bandwidth: 148 MHz Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #8 (VGA compatible controller) Isengard:~ # - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlg6zWEACgkQtTMYHG2NR9UALgCfRoNPd+FdtsdXQ/hUItXJgBOk 5rAAn3NKS1Cfu3yaMihFasR52/JC6B1Z =Nz8e -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/11/16 13:11, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I'm testing my new "server". I got an MSI Cubi N-020BEU.
It's got an Intel Braswell N 3710, 1.66GHz CPU, connected to a Samsung TV via HDMI cable. Leap 42.2 running XFCE. Left running all night to check, but display powered off.
This morning it would not respond to the keyboard.The TV said there was no signal in the cable.
Via ssh did not see load on CPU nor messages. I killed xscreensaver. [...] Oops. Wrong. ssh was on the wrong computer :-/
I disconnected the video cable, then connected again. ctrl-alt-f1 and back. Nothing. Then ctrl-alt-backspace. Got login prompt. Not nice.
I have disabled for now screen power saving features.
Ideas?
I suspect xscreensaver. I have to try again with it on remote.
Isengard:~ # hwinfo --monitor --gfxcard --framebuffer 08: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.378] Unique ID: _Znp.qslZ+SExVcE SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Device Name: "Onboard IGD" Model: "Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x22b1 "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0xb120 Revision: 0x35 Driver: "i915" Driver Modules: "drm" Memory Range: 0x80000000-0x80ffffff (rw,non-prefetchable) Memory Range: 0x90000000-0x9fffffff (ro,non-prefetchable) I/O Ports: 0xf000-0xf03f (rw) IRQ: 123 (6257765 events) Module Alias: "pci:v00008086d000022B1sv00001462sd0000B120bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=no, avail=yes, need=no, active=unknown
21: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.RysAyeVxkx7 Parent ID: _Znp.qslZ+SExVcE Hardware Class: monitor Model: "SAMSUNG T22C350" Vendor: SAM "SAMSUNG" Device: eisa 0x0ab9 "T22C350" Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@67Hz Resolution: 640x480@72Hz Resolution: 640x480@75Hz Resolution: 800x600@60Hz Resolution: 800x600@72Hz Resolution: 800x600@75Hz Resolution: 832x624@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@70Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@75Hz Resolution: 1152x864@75Hz Resolution: 1280x720@60Hz Resolution: 1280x1024@60Hz Resolution: 1366x768@60Hz Resolution: 1920x1080@60Hz Size: 477x268 mm Year of Manufacture: 2012 Week of Manufacture: 52 Detailed Timings #0: Resolution: 1920x1080 Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz Year of Manufacture: 2012 Week of Manufacture: 52 Detailed Timings #1: Resolution: 1366x768 Horizontal: 1366 1436 1579 1792 (+70 +213 +426) +hsync Vertical: 768 771 774 798 (+3 +6 +30) +vsync Frequencies: 85.50 MHz, 47.71 kHz, 59.79 Hz Driver Info #0: Max. Resolution: 1920x1080 Vert. Sync Range: 24-75 Hz Hor. Sync Range: 15-81 kHz Bandwidth: 148 MHz Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #8 (VGA compatible controller) Isengard:~ #
I have the Samsung T22C300, but it's hooked up to my laptop dock via VGA and I'm running KDE on oS 13.1. Have you gone through the power saving options on the TV? I just looked at the Menu -> System -> Eco Solution, and I note Auto Power Off is set to Off (default is on, goes off after 4 hours of no activity). It's more than two years since I bought the TV and set it up, but seeing that I now recall that I had to set it to Off because I found the display dead if left overnight. Had no problems since. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-27 13:22, gumb wrote:
I have the Samsung T22C300, but it's hooked up to my laptop dock via VGA and I'm running KDE on oS 13.1.
Have you gone through the power saving options on the TV? I just looked at the Menu -> System -> Eco Solution, and I note Auto Power Off is set to Off (default is on, goes off after 4 hours of no activity). It's more than two years since I bought the TV and set it up, but seeing that I now recall that I had to set it to Off because I found the display dead if left overnight. Had no problems since.
I don't think it affects in this case. The TV was switched off manually. On the morning I switched it on and the TV program came up. Then I told it to use the HDMI input instead, coming from the miniPC, and this one was dead, no display. I have now been reading the log, and nothing wrong there. Nov 27 12:30:36 Isengard unix2_chkpwd[21086]: gkr-pam: the password for the login keyring was invalid. Nov 27 12:30:36 Isengard unix2_chkpwd[21086]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser= rhost= user=cer Nov 27 12:30:38 Isengard unix2_chkpwd[21086]: pam_authenticate(xscreensaver, cer): Authentication failure Nov 27 12:30:41 Isengard unix2_chkpwd[21090]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control Nov 27 12:30:41 Isengard unix2_chkpwd[21090]: gkr-pam: couldn't unlock the login keyring. Nov 27 12:30:41 Isengard unix2_chkpwd[21090]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser= rhost= user=root Nov 27 12:30:43 Isengard unix2_chkpwd[21090]: pam_authenticate(xscreensaver, root): Authentication failure Nov 27 12:31:06 Isengard unix2_chkpwd[21096]: gkr-pam: the password for the login keyring was invalid. Nov 27 12:31:06 Isengard unix2_chkpwd[21096]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser= rhost= user=cer These entries come from when I tried to press keys, like repeatedly the "Enter" key, trying to wake it up. The keyboard was working, it attempted to interpret as password to xscreensaver. On /var/log/Xorg.0.log.old I see: [ 7012.221] (II) SYN_DROPPED event from "USB OPTICAL MOUSE " - some input events have been lost. [ 7014.368] (II) SYN_DROPPED event from "USB OPTICAL MOUSE " - some input events have been lost. [ 7025.088] (II) SYN_DROPPED event from "USB OPTICAL MOUSE " - some input events have been lost. [ 7027.760] (II) SYN_DROPPED event from "USB OPTICAL MOUSE " - some input events have been lost. [ 7148.806] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 8672.586] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40765.885] (II) intel(0): EDID vendor "SAM", prod id 2745 [ 40765.885] (II) intel(0): Using EDID range info for horizontal sync [ 40765.885] (II) intel(0): Using EDID range info for vertical refresh [ 40765.885] (II) intel(0): Printing DDC gathered Modelines: [ 40765.885] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 40765.885] (II) intel(0): Modeline "1366x768"x0.0 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync (47.7 kHz e) [ 40765.885] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 40765.885] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) That may be when I tried reconnecting the display, or when I powered it up this morning. a bit later: [ 40765.886] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz e) [ 40765.886] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40765.889] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40765.889] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40765.890] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40765.923] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40947.872] (II) AIGLX: Suspending AIGLX clients for VT switch [ 40951.856] (II) AIGLX: Resuming AIGLX clients after VT switch [ 40951.856] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 2, disabling CRTC:31 [ 40952.394] (--) intel(0): HDMI max TMDS frequency 225000KHz [ 40952.397] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard [ 40952.397] (II) input device 'Power Button', /dev/input/event5 is a keyboard [ 40952.399] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard [ 40952.399] (II) input device 'Video Bus', /dev/input/event8 is a keyboard [ 40952.400] (II) input device 'Sleep Button', /dev/input/event4 is tagged by udev as: Keyboard [ 40952.400] (II) input device 'Sleep Button', /dev/input/event4 is a keyboard [ 40952.401] (II) input device 'USB Gaming Keyboard', /dev/input/event0 is tagged by udev as: Keyboard [ 40952.401] (II) input device 'USB Gaming Keyboard', /dev/input/event0 is a keyboard -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-27 13:11, Carlos E. R. wrote:
Hi,
I'm testing my new "server". I got an MSI Cubi N-020BEU.
It's got an Intel Braswell N 3710, 1.66GHz CPU, connected to a Samsung TV via HDMI cable. Leap 42.2 running XFCE. Left running all night to check, but display powered off.
This morning it would not respond to the keyboard.The TV said there was no signal in the cable.
Via ssh did not see load on CPU nor messages. I killed xscreensaver. [...] Oops. Wrong. ssh was on the wrong computer :-/
I disconnected the video cable, then connected again. ctrl-alt-f1 and back. Nothing. Then ctrl-alt-backspace. Got login prompt. Not nice.
I have disabled for now screen power saving features.
Ideas?
I got a private response in Spanish, I'll write here the gist. It may be related to xfce ≥ 4.12, and a problem with xfsettingsd. Once the display is switched off, it disconnects the output and the process needs to be restarted. https://bugs.gentoo.org/show_bug.cgi?id=593960 But here restarting the process doesn't seem to work. I'll have to try after tonight. Ah, this time ctrl-alt-f1 did work and I could see the console. xscreensaver was deactivated. I want to try with LXDE, but I'm unable to switch. Wrote another email about that problem. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Mon, 28 Nov 2016, Carlos E. R. wrote:
On 2016-11-27 13:11, Carlos E. R. wrote:
It's got an Intel Braswell N 3710, 1.66GHz CPU, connected to a Samsung TV via HDMI cable. Leap 42.2 running XFCE. Left running all night to check, but display powered off.
This morning it would not respond to the keyboard.The TV said there was no signal in the cable.
Via ssh did not see load on CPU nor messages. I killed xscreensaver. [...] Oops. Wrong. ssh was on the wrong computer :-/
I disconnected the video cable, then connected again. ctrl-alt-f1 and back. Nothing. Then ctrl-alt-backspace. Got login prompt. Not nice.
I have disabled for now screen power saving features. Ideas?
I got a private response in Spanish, I'll write here the gist. It may be related to xfce ≥ 4.12, and a problem with xfsettingsd. Once the display is switched off, it disconnects the output and the process needs to be restarted.
I have found the power management of Xfce+nouveau is unstable with an nVidia Quadro 4000 card and two iiyama Prolite 2783QSU monitors. I was planning to file a bug report but I got held up by a neighbour's tree falling into my place. One or other monitor just goes blank although power on (blue light, not power saving). Reboot to recover. Roger
On 2016-11-28 16:47, Roger Price wrote:
On Mon, 28 Nov 2016, Carlos E. R. wrote:
I have found the power management of Xfce+nouveau is unstable with an nVidia Quadro 4000 card and two iiyama Prolite 2783QSU monitors. I was planning to file a bug report but I got held up by a neighbour's tree falling into my place.
One or other monitor just goes blank although power on (blue light, not power saving). Reboot to recover.
Well, this minipc has Intel graphics: "GPU: Mesa DRI Intel(R) HD Graphics (Cherryview)". I have switched to the LXDE desktop, and apparently the problem is not present. I'll confirm tomorrow morning, after the monitor gets powered off for several hours. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-28 21:19, Carlos E. R. wrote:
On 2016-11-28 16:47, Roger Price wrote:
On Mon, 28 Nov 2016, Carlos E. R. wrote:
I have found the power management of Xfce+nouveau is unstable with an nVidia Quadro 4000 card and two iiyama Prolite 2783QSU monitors. I was planning to file a bug report but I got held up by a neighbour's tree falling into my place.
One or other monitor just goes blank although power on (blue light, not power saving). Reboot to recover.
Well, this minipc has Intel graphics: "GPU: Mesa DRI Intel(R) HD Graphics (Cherryview)".
I have switched to the LXDE desktop, and apparently the problem is not present. I'll confirm tomorrow morning, after the monitor gets powered off for several hours.
Confirmed. With LXDE the display waked up perfectly. Initially the monitor had no signal, but touch the mouse and it came instantly. Thus it must be a bug in XFCE. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (3)
-
Carlos E. R.
-
gumb
-
Roger Price