[opensuse] Black display on media server
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have an sporadic problem with my media server, currently running Leap 42.3. Typically it is running kodi full screen (on XFCE desktop). I leave it running on the night (it is also server for other things full time), so I just power off the display. Well, sometimes when I power back on the display it remains "dark grey", ie, black with backlight on; there is some signal, but it is black. No response to keyboard at all, that I can see. Most times I can not switch to console text mode. I can do ssh from another machine, tasks are running. I kill kodi if it still there, kill the screen saver, "chvt 1", "init 3"... nothing works, the display does not respond. I have no resource but reboot the server. I suspect that Kodi has crashed but not fully exited, not restored the display it grabs (full screen mode). There is a kodi_crashlog-20180602_042251.log The machine was halted 2018-06-02 12:22:19+02:00, then rebooted 2018-06-02 12:25:10+02:00, so it matches with the kodi crashlog stamp above. These are the message log entries: <10.6> 2018-06-02T04:20:03.895923+02:00 Isengard CRON 11695 - - pam_unix(crond:session): session closed for user root <3.6> 2018-06-02T04:20:03.910927+02:00 Isengard systemd 1 - - Stopping User Manager for UID 0... <3.6> 2018-06-02T04:20:03.912456+02:00 Isengard systemd 11696 - - Stopped target Default. <3.6> 2018-06-02T04:20:03.913310+02:00 Isengard systemd 11696 - - Reached target Shutdown. <3.6> 2018-06-02T04:20:03.947854+02:00 Isengard systemd 11696 - - Starting Exit the Session... <3.6> 2018-06-02T04:20:03.948525+02:00 Isengard systemd 11696 - - Stopped target Basic System. <3.6> 2018-06-02T04:20:03.949085+02:00 Isengard systemd 11696 - - Stopped target Paths. <3.6> 2018-06-02T04:20:03.950964+02:00 Isengard systemd 11696 - - Stopped target Sockets. <3.6> 2018-06-02T04:20:03.952677+02:00 Isengard systemd 11696 - - Stopped target Timers. <3.6> 2018-06-02T04:20:03.976307+02:00 Isengard systemd 11696 - - Received SIGRTMIN+24 from PID 11724 (kill). <10.6> 2018-06-02T04:20:03.981000+02:00 Isengard systemd - - - pam_unix(systemd-user:session): session closed for user root <3.6> 2018-06-02T04:20:03.987756+02:00 Isengard systemd 1 - - Stopped User Manager for UID 0. <3.6> 2018-06-02T04:20:03.989619+02:00 Isengard systemd 1 - - Removed slice User Slice of root. <16.6> 2018-06-02T04:22:31.384900+02:00 Isengard WatchDog - - - WatchDog MARK! Status: Router 1 (F/T 0/52) Google 1 (F/T 0/9) Rebooting 0 Reboots 0 <0.2> 2018-06-02T04:22:51.616991+02:00 Isengard systemd-coredump 11774 - - Process 12610 (kodi.bin) of user 1000 dumped core. <======================= <10.6> 2018-06-02T04:25:01.915324+02:00 Isengard cron 11863 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.6> 2018-06-02T04:25:01.930260+02:00 Isengard systemd 1 - - Created slice User Slice of root. <3.6> 2018-06-02T04:25:01.951911+02:00 Isengard systemd 1 - - Starting User Manager for UID 0... <3.6> 2018-06-02T04:25:01.957613+02:00 Isengard systemd 1 - - Started Session 3628 of user root. <10.6> 2018-06-02T04:25:01.966595+02:00 Isengard systemd - - - pam_unix(systemd-user:session): session opened for user root by (uid=0) Then there are only routine cron or timer related entries till I try to use the machine next morning. These is the coredump: Sat 2018-06-02 04:22:51 CEST 12610 1000 100 6 * /usr/lib64/kodi/kodi.bin Sat 2018-06-02 12:21:11 CEST 3690 1000 100 11 * /usr/lib64/libexec/kdeconnectd Sat 2018-06-02 12:21:14 CEST 24530 1000 100 11 * /usr/lib64/firefox/firefox Sat 2018-06-02 12:21:15 CEST 23478 1000 100 11 * /usr/lib64/firefox/firefox Sat 2018-06-02 12:21:18 CEST 23526 1000 100 11 * /usr/lib64/firefox/firefox Sat 2018-06-02 12:21:29 CEST 23553 1000 100 11 * /usr/lib64/firefox/firefox Oh, I see some more coredumps that day, but as the machine was halted at 12:22:19+02:00, they are not relevant. Why kdeconnectd was running, I do not know, the desktop is XFCE. It is running this instant, too. I don't know what it does. Ah, it connects to android phones... WTF is it running on XFCE? Ideas to investigate next time the display crash happens? - it is not even every week. Some information on the hardware: Isengard:~ # hwinfo --bios --chipcard --dvb --framebuffer --gfxcard --monitor --vbe 01: None 00.0: 10105 BIOS [Created at bios.186] Unique ID: rdCR.lZF+r4EgHp4 Hardware Class: bios BIOS Keyboard LED Status: Scroll Lock: off Num Lock: off Caps Lock: off SMBIOS Version: 2.8 BIOS Info: #0 Vendor: "American Megatrends Inc." Version: "EB120IMS.820" Date: "03/03/2016" Start Address: 0xf0000 ROM Size: 6656 kB Features: 0x0d03000000013f8b9880 PCI supported BIOS flashable BIOS shadowing allowed CD boot supported Selectable boot supported BIOS ROM socketed EDD spec supported 1.2MB Floppy supported 720kB Floppy supported 2.88MB Floppy supported Print Screen supported 8042 Keyboard Services supported Serial Services supported Printer Services supported ACPI supported USB Legacy supported BIOS Boot Spec supported System Info: #1 Manufacturer: "Micro-Star International Co., Ltd." Product: "MS-B120" Version: "1.0" Serial: "MSB120G7S0105312" UUID: undefined, but settable Wake-up: 0x06 (Power Switch) Board Info: #2 Manufacturer: "Micro-Star International Co., Ltd." Product: "MS-B120" Version: "1.0" Serial: "To be filled by O.E.M." Asset Tag: "To be filled by O.E.M." Type: 0x0a (Motherboard) Features: 0x09 Hosting Board Replaceable Location: "To be filled by O.E.M." Chassis: #3 Chassis Info: #3 Manufacturer: "Micro-Star International Co., Ltd." Version: "To Be Filled By O.E.M." Serial: "To Be Filled By O.E.M." Asset Tag: "To Be Filled By O.E.M." Type: 0x0d (All in One) Bootup State: 0x03 (Safe) Power Supply State: 0x03 (Safe) Thermal State: 0x03 (Safe) Security Status: 0x03 (None) Port Connector: #8 Type: 0x0e (Mouse Port) Internal Designator: "J1A1" External Designator: "PS2Mouse" External Connector: 0x0f (PS/2) Port Connector: #9 Type: 0x0d (Keyboard Port) Internal Designator: "J1A1" External Designator: "Keyboard" External Connector: 0x0f (PS/2) Port Connector: #10 Type: 0xff (Other) Internal Designator: "J2A1" External Designator: "TV Out" External Connector: 0x1d (Mini-Centronics Type-14) Port Connector: #11 Type: 0x09 (Serial Port 16550A Compatible) Internal Designator: "J2A2A" External Designator: "COM A" External Connector: 0x08 (DB-9 pin male) Port Connector: #12 Type: 0x1c (Video Port) Internal Designator: "J2A2B" External Designator: "Video" External Connector: 0x07 (DB-15 pin female) Port Connector: #13 Type: 0x10 (USB) Internal Designator: "J3A1" External Designator: "USB1" External Connector: 0x12 (Access Bus [USB]) Port Connector: #14 Type: 0x10 (USB) Internal Designator: "J3A1" External Designator: "USB2" External Connector: 0x12 (Access Bus [USB]) Port Connector: #15 Type: 0x10 (USB) Internal Designator: "J3A1" External Designator: "USB3" External Connector: 0x12 (Access Bus [USB]) Port Connector: #16 Type: 0xff (Other) Internal Designator: "J9A1 - TPM HDR" Internal Connector: 0xff (Other) Port Connector: #17 Type: 0xff (Other) Internal Designator: "J9C1 - PCIE DOCKING CONN" Internal Connector: 0xff (Other) Port Connector: #18 Type: 0xff (Other) Internal Designator: "J2B3 - CPU FAN" Internal Connector: 0xff (Other) Port Connector: #19 Type: 0xff (Other) Internal Designator: "J6C2 - EXT HDMI" Internal Connector: 0xff (Other) Port Connector: #20 Type: 0xff (Other) Internal Designator: "J3C1 - GMCH FAN" Internal Connector: 0xff (Other) Port Connector: #21 Type: 0xff (Other) Internal Designator: "J1D1 - ITP" Internal Connector: 0xff (Other) Port Connector: #22 Type: 0xff (Other) Internal Designator: "J9E2 - MDC INTPSR" Internal Connector: 0xff (Other) Port Connector: #23 Type: 0xff (Other) Internal Designator: "J9E4 - MDC INTPSR" Internal Connector: 0xff (Other) Port Connector: #24 Type: 0xff (Other) Internal Designator: "J9E3 - LPC HOT DOCKING" Internal Connector: 0xff (Other) Port Connector: #25 Type: 0xff (Other) Internal Designator: "J9E1 - SCAN MATRIX" Internal Connector: 0xff (Other) Port Connector: #26 Type: 0xff (Other) Internal Designator: "J9G1 - LPC SIDE BAND" Internal Connector: 0xff (Other) Port Connector: #27 Type: 0xff (Other) Internal Designator: "J8F1 - UNIFIED" Internal Connector: 0xff (Other) Port Connector: #28 Type: 0xff (Other) Internal Designator: "J6F1 - LVDS" Internal Connector: 0xff (Other) Port Connector: #29 Type: 0xff (Other) Internal Designator: "J2F1 - LAI FAN" Internal Connector: 0xff (Other) Port Connector: #30 Type: 0xff (Other) Internal Designator: "J2G1 - GFX VID" Internal Connector: 0xff (Other) Port Connector: #31 Type: 0xff (Other) Internal Designator: "J1G6 - AC JACK" Internal Connector: 0xff (Other) System Slot: #32 Designation: "J6B2" Type: 0xa5 (Other) Bus Width: 0x0d (Other) Status: 0x04 (In Use) Length: 0x04 (Long) Slot ID: 0 Characteristics: 0x010c (3.3 V, Shared, PME#) System Slot: #33 Designation: "J6B1" Type: 0xa5 (Other) Bus Width: 0x08 (Other) Status: 0x04 (In Use) Length: 0x03 (Short) Slot ID: 1 Characteristics: 0x010c (3.3 V, Shared, PME#) System Slot: #34 Designation: "J6D1" Type: 0xa5 (Other) Bus Width: 0x08 (Other) Status: 0x04 (In Use) Length: 0x03 (Short) Slot ID: 2 Characteristics: 0x010c (3.3 V, Shared, PME#) System Slot: #35 Designation: "J7B1" Type: 0xa5 (Other) Bus Width: 0x08 (Other) Status: 0x04 (In Use) Length: 0x03 (Short) Slot ID: 3 Characteristics: 0x010c (3.3 V, Shared, PME#) System Slot: #36 Designation: "J8B4" Type: 0xa5 (Other) Bus Width: 0x08 (Other) Status: 0x04 (In Use) Length: 0x03 (Short) Slot ID: 4 Characteristics: 0x010c (3.3 V, Shared, PME#) On Board Devices: #37 Video: "To Be Filled By O.E.M." OEM Strings: #38 To Be Filled By O.E.M. System Config Options (Jumpers & Switches) #39: To Be Filled By O.E.M. Physical Memory Array: #40 Use: 0x03 (System memory) Location: 0x03 (Motherboard) Slots: 2 Max. Size: 8 GB ECC: 0x03 (None) Memory Array Mapping: #41 Memory Array: #40 Partition Width: 2 Start Address: 0x0000000000000000 End Address: 0x0000000200000000 Memory Device: #42 Location: "A1_DIMM0" Bank: "A1_BANK0" Manufacturer: "Kingston" Serial: "0618FCE3" Asset Tag: "A1_AssetTagNum0" Part Number: "99U5469-041.A00LF" Memory Array: #40 Form Factor: 0x09 (DIMM) Type: 0x18 (Other) Type Detail: 0x0004 (Unknown) Data Width: 64 bits Size: 4 GB Speed: 1600 MHz Memory Device Mapping: #43 Memory Device: #42 Array Mapping: #41 Interleave Pos: 1 Interleaved Depth: 2 Start Address: 0x0000000000000000 End Address: 0x0000000100000000 Memory Device: #44 Location: "A1_DIMM1" Bank: "A1_BANK1" Manufacturer: "Kingston" Serial: "082FEA49" Asset Tag: "A1_AssetTagNum1" Part Number: "99U5469-041.A00LF" Memory Array: #40 Form Factor: 0x09 (DIMM) Type: 0x18 (Other) Type Detail: 0x0004 (Unknown) Data Width: 64 bits Size: 4 GB Speed: 1600 MHz Memory Device Mapping: #45 Memory Device: #44 Array Mapping: #41 Interleave Pos: 2 Interleaved Depth: 2 Start Address: 0x0000000100000000 End Address: 0x0000000200000000 Type 32 Record: #46 Data 00: 20 14 2e 00 00 00 00 00 00 00 00 00 00 00 00 00 Data 10: 00 00 00 00 Type 41 Record: #47 Data 00: 29 0b 2f 00 01 83 01 00 00 00 10 String 1: "Onboard IGD" Type 41 Record: #48 Data 00: 29 0b 30 00 01 85 01 00 00 00 c8 String 1: "Onboard LAN" Type 41 Record: #49 Data 00: 29 0b 31 00 01 81 01 00 00 03 e2 String 1: "Onboard 1394" Cache Info: #50 Designation: "CPU Internal L1" Level: L1 State: Enabled Mode: 0x01 (Write Back) Location: 0x00 (Internal, Not Socketed) ECC: 0x05 (Single-bit) Type: 0x01 (Other) Associativity: 0x01 (Other) Max. Size: 224 kB Current Size: 224 kB Supported SRAM Types: 0x0002 (Unknown) Current SRAM Type: 0x0002 (Unknown) Cache Info: #51 Designation: "CPU Internal L2" Level: L2 State: Enabled Mode: 0x01 (Write Back) Location: 0x00 (Internal, Not Socketed) ECC: 0x05 (Single-bit) Type: 0x05 (Unified) Associativity: 0x08 (16-way Set-Associative) Max. Size: 2048 kB Current Size: 2048 kB Supported SRAM Types: 0x0002 (Unknown) Current SRAM Type: 0x0002 (Unknown) Processor Info: #52 Socket: "SOCKET 0" Socket Type: 0x24 (Other) Socket Status: Populated Type: 0x03 (CPU) Family: 0x0b (Pentium) Manufacturer: "Intel" Version: "Intel(R) Pentium(R) CPU N3710 @ 1.60GHz" Asset Tag: "Fill By OEM" Part Number: "Fill By OEM" Processor ID: 0xbfebfbff000406c4 Status: 0x01 (Enabled) Voltage: 1.2 V External Clock: 80 MHz Max. Speed: 2400 MHz Current Speed: 1600 MHz L1 Cache: #50 L2 Cache: #51 Language Info: #53 Languages: en|US|iso8859-1 Current: en|US|iso8859-1 Type 143 Record: #54 Data 00: 8f 10 36 00 00 01 02 03 04 05 06 07 08 09 0a 0b String 1: "GOP1-[8.0.1035]" String 2: "RAID-13.1.0.2126" String 3: "PXEU1-v2.021" String 4: "AMI-AptioV" String 5: "N/A" String 6: "N/A" String 7: "N/A" String 8: "N/A" String 9: "N/A" String 10: "N/A" String 11: "N/A" String 12: "N/A" Type 144 Record: #55 Data 00: 90 05 37 00 01 String 1: "$INT15SWIDd0b1" Config Status: cfg=no, avail=yes, need=no, active=unknown 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: "i915" Memory Range: 0x80000000-0x80ffffff (rw,non-prefetchable) Memory Range: 0x90000000-0x9fffffff (ro,non-prefetchable) I/O Ports: 0xf000-0xf03f (rw) IRQ: 119 (15106350 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 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlsT81QACgkQtTMYHG2NR9Wj/wCfb7YGPrWrBiENuAS7kBgmqabJ TA8An1/RyKMlVwyrTcQEBuRV5tgoQYBG =swZP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-06-03 at 15:55 +0200, Carlos E. R. wrote:
Hi,
I have an sporadic problem with my media server, currently running Leap 42.3. Typically it is running kodi full screen (on XFCE desktop). I leave it running on the night (it is also server for other things full time), so I just power off the display.
Well, sometimes when I power back on the display it remains "dark grey", ie, black with backlight on; there is some signal, but it is black. No response to keyboard at all, that I can see. Most times I can not switch to console text mode. I can do ssh from another machine, tasks are running. I kill kodi if it still there, kill the screen saver, "chvt 1", "init 3"... nothing works, the display does not respond. I have no resource but reboot the server.
I suspect that Kodi has crashed but not fully exited, not restored the display it grabs (full screen mode).
Happened again and got more info; I was able to recover the display. kodi chrashed, yes. After sometime, the display wen black. Moving the mouse it restored. I had other things to do, so I left it be. After a while it went black, and longer afterwards the display itself powered off completely. Not "standby", but fully off. Eventually I used the remote control to power it back on. Black. Moved mouse, touched keys... no response. I knew the machine was responsive because I had been doing things on it for hours via ssh. Thinking that screensaver could be triggered, I carefully typed the password and enter. No response. Ctrl-alt-f1... no response. I removed the cable, which is connected to "HDMI1/DVI/PC" and connected it to HDMI2. No response, the remote control said there was no signal there. I connected it back to HDMI1, and this time I got signal: I could see the result of the Ctrl-alt-f1 I did before. Ctrl-alt-f7 got me back to the normal graphical display. I see my password typed as a command on the terminal, so the screensaver and lock was not active. Ideas? It is running Leap 42.3 and XFCE. The display is a Samsung. In settings, display power management is "off". Screensaver is disabled. Yet the display itself goes dark and later powers off, something which kodi impedes when it is running. I will try enabling power management of the display in XFCE, setting "switch off" to "never". - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlsm6PwACgkQtTMYHG2NR9VQ1QCgk6uXgexiTFcLMD3MBxsDuo14 SuwAn3J/yuxYPTkPaJ9giE/lKedg3wmo =3ObQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [06-17-18 19:07]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2018-06-03 at 15:55 +0200, Carlos E. R. wrote:
Hi,
I have an sporadic problem with my media server, currently running Leap 42.3. Typically it is running kodi full screen (on XFCE desktop). I leave it running on the night (it is also server for other things full time), so I just power off the display.
Well, sometimes when I power back on the display it remains "dark grey", ie, black with backlight on; there is some signal, but it is black. No response to keyboard at all, that I can see. Most times I can not switch to console text mode. I can do ssh from another machine, tasks are running. I kill kodi if it still there, kill the screen saver, "chvt 1", "init 3"... nothing works, the display does not respond. I have no resource but reboot the server.
I suspect that Kodi has crashed but not fully exited, not restored the display it grabs (full screen mode).
Happened again and got more info; I was able to recover the display.
kodi chrashed, yes. After sometime, the display wen black. Moving the mouse it restored. I had other things to do, so I left it be. After a while it went black, and longer afterwards the display itself powered off completely. Not "standby", but fully off.
Eventually I used the remote control to power it back on. Black. Moved mouse, touched keys... no response. I knew the machine was responsive because I had been doing things on it for hours via ssh. Thinking that screensaver could be triggered, I carefully typed the password and enter. No response. Ctrl-alt-f1... no response.
I removed the cable, which is connected to "HDMI1/DVI/PC" and connected it to HDMI2. No response, the remote control said there was no signal there. I connected it back to HDMI1, and this time I got signal: I could see the result of the Ctrl-alt-f1 I did before. Ctrl-alt-f7 got me back to the normal graphical display. I see my password typed as a command on the terminal, so the screensaver and lock was not active.
Ideas?
It is running Leap 42.3 and XFCE.
The display is a Samsung.
In settings, display power management is "off". Screensaver is disabled. Yet the display itself goes dark and later powers off, something which kodi impedes when it is running.
I will try enabling power management of the display in XFCE, setting "switch off" to "never".
is display/power management enabled in the bios? dpms ?? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-18 02:09, Patrick Shanahan wrote:
* Carlos E. R. <> [06-17-18 19:07]:
is display/power management enabled in the bios? dpms ??
AFAIK, no. It is a server, it is up24*7, not easy to reboot and check. It seems to be the display set own setting, 2 hours of non activity to switch off. The problem is convincing it to go "on" again. The computer apparently sends signal, but the display doesn't react. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. composed on 2018-06-18 02:34 (UTC+0200):
Patrick Shanahan wrote:
* Carlos E. R. composed:
is display/power management enabled in the bios? dpms ??
AFAIK, no. It is a server, it is up24*7, not easy to reboot and check.
It seems to be the display set own setting, 2 hours of non activity to switch off. The problem is convincing it to go "on" again. The computer apparently sends signal, but the display doesn't react.
Maybe /etc/X11/xorg.conf.d/50-monitor.conf containing: Section "Monitor" Identifier "DefaultMonitor" Option "DPMS" "off" EndSection would help? Does Xorg.0.log say anything useful about display power? Journal? Which gfxchip? Which Xorg driver? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-18 04:04, Felix Miata wrote:
Carlos E. R. composed on 2018-06-18 02:34 (UTC+0200):
Maybe /etc/X11/xorg.conf.d/50-monitor.conf containing:
Section "Monitor" Identifier "DefaultMonitor" Option "DPMS" "off" EndSection
would help?
I can try that.
Does Xorg.0.log say anything useful about display power? Journal? Which gfxchip? Which Xorg driver?
Detailed hardware info is in the first post of the thread. Xorg log: <http://susepaste.org/877831> -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. composed on 2018-06-18 04:21 (UTC+0200):
Felix Miata wrote:
Does Xorg.0.log say anything useful about display power? Journal? Which gfxchip? Which Xorg driver?
Detailed hardware info is in the first post of the thread.
Xorg log: <http://susepaste.org/877831>
You could try the other Xorg driver (modesetting, integral to the Xorg server, the usual default if xf86-video-intel is not installed, and preferable to it with some Intel gfx). I'm typing this on 42.3 on modesetting on Haswell, the generation before your Braswell. Nothing shows in the journal about display power around 1337508.841? Log says you're connected on HDMI3. You might try a different cable, or a HDMI to DVI cable. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-18 04:55, Felix Miata wrote:
Carlos E. R. composed on 2018-06-18 04:21 (UTC+0200):
Felix Miata wrote:
Does Xorg.0.log say anything useful about display power? Journal? Which gfxchip? Which Xorg driver?
Detailed hardware info is in the first post of the thread.
Xorg log: <http://susepaste.org/877831>
You could try the other Xorg driver (modesetting, integral to the Xorg server, the usual default if xf86-video-intel is not installed, and preferable to it with some Intel gfx). I'm typing this on 42.3 on modesetting on Haswell, the generation before your Braswell.
I'll leave that for a last resource :-) This morning the thing awoke just fine. I have meanwhile updated packages (including a kernel update) and will reboot shortly. I have applied changes to 50-monitor.conf.
Nothing shows in the journal about display power around 1337508.841?
And what time is that? Because it might be some relative time to when xorg was started weeks ago.
Log says you're connected on HDMI3. You might try a different cable, or a HDMI to DVI cable.
Yes, I saw that. Could be when I changed the cable on the monitor from HDMI1 to 2 and back. The computer itself only has one HDMI socket. So no HDMI3 anywhere. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-06-18 12:39, Carlos E. R. wrote:
On 2018-06-18 04:55, Felix Miata wrote:
Carlos E. R. composed on 2018-06-18 04:21 (UTC+0200):
...
This morning the thing awoke just fine. I have meanwhile updated packages (including a kernel update) and will reboot shortly. I have applied changes to 50-monitor.conf.
Just rebooted the machine. I see nothing in BIOS power menu regarding DPMS. There are only two entries: one that after power loss it will restore to last state, and the other that "Deep S5" is enabled. But the machine itself is running all the time, the daemons are doing their jobs non stop. It is only the display that goes funky the morning after kodi crashes - so it might be related to kodi leaving the display in some funky mode when it does not exit properly. A solution to this would be placing kodi in a script that restarts it automatically - but sometimes kodi crashes nonstop, so I hesitate. And worst, yesterday night it caused a related daemon to crash continuously, and this one is set to autorestart. So both would have been restarting and perhaps dumping cores ad infinitum last night had I kodi on autorestart, too. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-06-18 12:39 (UTC+0200):
Felix Miata wrote:
...>> Nothing shows in the journal about display power around 1337508.841?
And what time is that? Because it might be some relative time to when xorg was started weeks ago.
When you woke the display up from whatever mode constitutes sleep: [1337508.841] (II) AIGLX: Resuming AIGLX clients after VT switch [1337508.841] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI3 using pipe 2, position (0, 0), rotation normal, reflection none -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-18 19:45, Felix Miata wrote:
Carlos E. R. composed on 2018-06-18 12:39 (UTC+0200):
Felix Miata wrote:
...>> Nothing shows in the journal about display power around 1337508.841?
And what time is that? Because it might be some relative time to when xorg was started weeks ago.
When you woke the display up from whatever mode constitutes sleep: [1337508.841] (II) AIGLX: Resuming AIGLX clients after VT switch [1337508.841] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI3 using pipe 2, position (0, 0), rotation normal, reflection none
I don't see calendar time there. I see "1337508.841" which I can not read. The log starts: [ 432.065] X.Org X Server 1.18.3 Release Date: 2016-04-04 [ 432.065] X Protocol Version 11, Revision 0 So those are probably milliseconds since X started. It is impossible to correlate "1337508.841" to the date/time stamp in other logs. In that case it means 1337, less than one hour since start X, so not relevant at all then. It might be when I switched via keyboard without seeing the display to virtual terminal 1 (ctrl-alt-f1), or VT 1 Notice that the boot session started: Jun 02 12:47:09 Isengard systemd-journald[115]: Runtime journal (/run/log/journal/) is currently using 8.0M. till today: Jun 18 12:44:36 Isengard systemd-journald[381]: Journal stopped The problem was yesterday, sometime from 00 till the morning. No "hdmi" or "vt" or "aigl" in the journal (since Jun 17 00:00:01). No, I must be confused, it must has happened the night of Jun 17, because I posted Jun 18 01:04 hours. But any way, I looked in the entire log since Jun 17 00:00:01. Huh, the journal doesn't cover it all: Jun 17 09:06:51 Isengard kernel: SFW2-INext-DROP-DEFLT ...skipping... Jun 17 23:40:01 Isengard systemd[1]: Started Session 7476 of user root. that "skipping" is not mine. I'm using "journalctl --boot=-1". I'll go and see the /var/log/messages file instead. [...] This is the trigger: <0.2> 2018-06-17T19:24:55.009844+02:00 Isengard systemd-coredump 30726 - - Process 32623 (kodi.bin) of user 1000 dumped core. There is a corresponding kodi_crashlog-20180617_192455.log file, single crash that day. Then comes a lot of ssh activity, I was configuring publickey auth. And nothing of interest till: <0.2> 2018-06-18T00:36:53.031888+02:00 Isengard systemd-coredump 15982 - - Process 15939 (kodi.bin) of user 1000 dumped core. which means that sometime during those six hours I had restarted manually kodi, thus got the display failing and working in that interval. No idea of when exactly I called "kodi" manually. The current Xorg.0.log says: [ 39.058] (==) intel(0): DPMS enabled Despite /etc/X11/xorg.conf.d/50-monitor.conf: Section "Monitor" Identifier "DefaultMonitor" Option "DPMS" "off" EndSection The log says: [ 38.951] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 18 12:50:29 2018 [ 38.955] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 38.955] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 38.970] (==) No Layout section. Using the first Screen section. [ 38.970] (==) No screen section available. Using defaults. [ 38.970] (**) |-->Screen "Default Screen Section" (0) [ 38.970] (**) | |-->Monitor "<default monitor>" [ 38.970] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. It is ignoring the manual config. I'll try "Default Monitor" instead. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
So those are probably milliseconds since X started. It is impossible to correlate "1337508.841" to the date/time stamp in other logs. In that case it means 1337, less than one hour since start X, so not relevant at all then.
times in kernel are usually given in seconds, like [xxxx.yyyy] I can't see why 'X' would be different. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-19 07:50, L A Walsh wrote:
Carlos E. R. wrote:
So those are probably milliseconds since X started. It is impossible to correlate "1337508.841" to the date/time stamp in other logs. In that case it means 1337, less than one hour since start X, so not relevant at all then.
times in kernel are usually given in seconds, like [xxxx.yyyy]
I can't see why 'X' would be different.
Seconds counting from where? The epoch? Boot? The 3 first lines of the log are: [ 432.065] X.Org X Server 1.18.3 Release Date: 2016-04-04 So, does the log start 432 seconds after the epoch? Impossible. Seconds since start of X? Also impossible. 432 seconds, ie, 7.2 minutes after boot? Doubtful. X starts automatically. Boots stops to ask for the disk password, assume two minutes top to enter the password, and half a minute more to type the login password. Still, 4 more minutes to account for... So it has to be milliseconds since the start of X. When did it start? The log continues: [ 432.065] X Protocol Version 11, Revision 0 [ 432.065] Build Operating System: openSUSE SUSE LINUX [ 432.065] Current Operating System: Linux Isengard 4.4.132-53-default #1 SMP Wed May 23 06:57:07 UTC 2018 (036cd2f) x86_64 [ 432.065] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.132-53-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 ro showopts resume=/dev/disk/by-label/Swap splash=verbose [ 432.065] Build Date: 14 March 2018 10:01:54PM [ 432.065] [ 432.066] Current version of pixman: 0.34.0 [ 432.066] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 432.066] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 432.066] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jun 2 12:54:19 2018 Well, this may be it. 432.066 is Sat Jun 2 12:54:19 2018 Ok, the line of interest are: [1337273.371] (II) AIGLX: Suspending AIGLX clients for VT switch [1337508.841] (II) AIGLX: Resuming AIGLX clients after VT switch [1337508.841] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI3 using pipe 2, position (0, 0), rotation normal, reflection none Let's do some math using LO calc. How do I add seconds to a day date? I think it is =A3/(1000*60*60*24) where A5 is the cell containing the timestamp. The formulas are then (csv format): 432,066;"=A1/1000/60";02/06/2018 12:54;"=C1" ;;; 1337273,371;"=A3/(1000*60*60*24)";"=C$1+B3-B$1"; 1337508,841;"=A4/(1000*60*60*24)";"=C$1+B4-B$1"; 1337508,841;"=A5/(1000*60*60*24)";"=C$1+B5-B$1"; (the second column are days) And the results are: 432,066 0,0072011 02/06/2018 12:54 43253,5377199074 1337273,371 0,015477701053241 02/06/2018 13:06 1337508,841 0,015480426400463 02/06/2018 13:06 1337508,841 0,015480426400463 02/06/2018 13:06 (day/month/year) So those timestamps corresponds to the third column and are of no interest for whatever happened to my display, not in the day of interest. Now, if the timestamps were really seconds since *boot*, the results are different and plausible: 432,066 0,005000763888889 02/06/18 12:54 1337273,371 15,4777010532407 18/06/18 00:14 1337508,841 15,480426400463 18/06/18 00:18 1337508,841 15,480426400463 18/06/18 00:18 These are the messages log entries corresponding to those times: <10.6> 2018-06-18T00:05:03.661874+02:00 Isengard CRON 14995 - - pam_unix(crond:session): session closed for user root <10.6> 2018-06-18T00:10:01.673904+02:00 Isengard cron 15116 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.6> 2018-06-18T00:10:01.720686+02:00 Isengard systemd 1 - - Started Session 7486 of user root. <10.6> 2018-06-18T00:10:03.957215+02:00 Isengard CRON 15116 - - pam_unix(crond:session): session closed for user root <10.6> 2018-06-18T00:15:01.970598+02:00 Isengard cron 15253 - - pam_unix(crond:session): session opened for user root by (uid=0) <10.6> 2018-06-18T00:15:01.975040+02:00 Isengard cron 15251 - - pam_unix(crond:session): session opened for user root by (uid=0) <10.6> 2018-06-18T00:15:01.975715+02:00 Isengard cron 15252 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.6> 2018-06-18T00:15:02.036825+02:00 Isengard systemd 1 - - Started Session 7489 of user root. <3.6> 2018-06-18T00:15:02.042528+02:00 Isengard systemd 1 - - Started Session 7488 of user root. <3.6> 2018-06-18T00:15:02.052475+02:00 Isengard systemd 1 - - Started Session 7487 of user root. <10.6> 2018-06-18T00:15:02.185681+02:00 Isengard CRON 15251 - - pam_unix(crond:session): session closed for user root <1.5> 2018-06-18T00:15:02.383306+02:00 Isengard Sistema - - - Logging the current external IP= 83.... <10.6> 2018-06-18T00:15:02.388517+02:00 Isengard CRON 15252 - - pam_unix(crond:session): session closed for user root <10.6> 2018-06-18T00:15:04.313946+02:00 Isengard CRON 15253 - - pam_unix(crond:session): session closed for user root <3.6> 2018-06-18T00:18:45.295279+02:00 Isengard systemd 1 - - Received SIGWINCH. <3.3> 2018-06-18T00:18:45.300274+02:00 Isengard systemd 1 - - Failed to enqueue kbrequest.target job: Unit kbrequest.target failed to load: No such file or directory. <10.6> 2018-06-18T00:20:01.325297+02:00 Isengard cron 15451 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.6> 2018-06-18T00:20:01.348723+02:00 Isengard systemd 1 - - Started Session 7490 of user root. <10.6> 2018-06-18T00:20:03.620759+02:00 Isengard CRON 15451 - - pam_unix(crond:session): session closed for user root <3.6> 2018-06-18T00:24:13.747671+02:00 Isengard smartd 1185 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 52 to 56 <3.6> 2018-06-18T00:24:13.749185+02:00 Isengard smartd 1185 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 56 The only doubt there is the signal "Received SIGWINCH". It is not listed in "man signal.h" It appears here: cer@Telcontar:~> grep SIGWINCH /usr/src/linux-4.4.136-56/include/linux/signal.h * | SIGWINCH | ignore | rt_sigmask(SIGWINCH) | rt_sigmask(SIGURG) ) cer@Telcontar:~> No explanation. Wikipedia has one: SIGWINCH The SIGWINCH signal is sent to a process when its controlling terminal changes its size (a window change). Oh, well. But systemd getting that? It doesn't have a terminal. Go figure. Googling "systemd 1 - - Received SIGWINCH" says it is related to apache. So, nothing related to current problem, I think. What about "Isengard systemd 1 - - Failed to enqueue kbrequest.target job: Unit kbrequest.target failed to load: No such file or directory."? Isengard:~ # locate kbrequest.target Isengard:~ # There are some hits on google for "Failed to enqueue kbrequest.target job" but nothing that leaps to my eye. And anyway, it is the sole such entry in the messages file since January. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-06-19 12:09 (UTC+0200):
Seconds counting from where? The epoch? Boot?
The 3 first lines of the log are:
[ 432.065] X.Org X Server 1.18.3 Release Date: 2016-04-04
So, does the log start 432 seconds after the epoch? Impossible. Seconds since start of X? Also impossible. 432 seconds, ie, 7.2 minutes after boot? Doubtful. X starts automatically. Boots stops to ask for the disk password, assume two minutes top to enter the password, and half a minute more to type the login password. Still, 4 more minutes to account for...
So it has to be milliseconds since the start of X.
No it doesn't. It depends on what happens when a log out from X occurs. If the DM restarts on log out, 7.2 minutes since boot is totally within reason. I routinely see numbers of more than 100., 1000., 10000., or even 100000. on test installations, least of which since some settings changes require logging out and back in to take effect, e.g. an xorg.conf change. Only the first after boot would be around 40. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-19 13:35, Felix Miata wrote:
Carlos E. R. composed on 2018-06-19 12:09 (UTC+0200):
Seconds counting from where? The epoch? Boot?
The 3 first lines of the log are:
[ 432.065] X.Org X Server 1.18.3 Release Date: 2016-04-04
So, does the log start 432 seconds after the epoch? Impossible. Seconds since start of X? Also impossible. 432 seconds, ie, 7.2 minutes after boot? Doubtful. X starts automatically. Boots stops to ask for the disk password, assume two minutes top to enter the password, and half a minute more to type the login password. Still, 4 more minutes to account for...
So it has to be milliseconds since the start of X.
No it doesn't. It depends on what happens when a log out from X occurs. If the DM restarts on log out, 7.2 minutes since boot is totally within reason. I routinely see numbers of more than 100., 1000., 10000., or even 100000. on test installations, least of which since some settings changes require logging out and back in to take effect, e.g. an xorg.conf change. Only the first after boot would be around 40.
Read the rest of my post, the final calculation assumes seconds since boot. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/17/2018 07:04 PM, Carlos E. R. wrote:
On Sunday, 2018-06-03 at 15:55 +0200, Carlos E. R. wrote:
Hi,
I have an sporadic problem with my media server, currently running Leap 42.3. Typically it is running kodi full screen (on XFCE desktop). I leave it running on the night (it is also server for other things full time), so I just power off the display.
Well, sometimes when I power back on the display it remains "dark grey", ie, black with backlight on; there is some signal, but it is black. No response to keyboard at all, that I can see. Most times I can not switch to console text mode. I can do ssh from another machine, tasks are running. I kill kodi if it still there, kill the screen saver, "chvt 1", "init 3"... nothing works, the display does not respond. I have no resource but reboot the server.
On monitors I've had this sort of issue with, there has been a red/green LED generally close to the power button. When this LED is green, it means the computer still has a connection to the monitor. When the LED is red, it means that there is no connection between the monitor and the computer. Does your monitor have such an LED? If so, what does it "say"?
I suspect that Kodi has crashed but not fully exited, not restored the display it grabs (full screen mode).
Happened again and got more info; I was able to recover the display.
kodi chrashed, yes. After sometime, the display wen black. Moving the mouse it restored. I had other things to do, so I left it be. After a while it went black, and longer afterwards the display itself powered off completely. Not "standby", but fully off.
Eventually I used the remote control to power it back on. Black. Moved mouse, touched keys... no response. I knew the machine was responsive because I had been doing things on it for hours via ssh. Thinking that screensaver could be triggered, I carefully typed the password and enter. No response. Ctrl-alt-f1... no response.
I removed the cable, which is connected to "HDMI1/DVI/PC" and connected it to HDMI2. No response, the remote control said there was no signal there. I connected it back to HDMI1, and this time I got signal: I could see the result of the Ctrl-alt-f1 I did before. Ctrl-alt-f7 got me back to the normal graphical display. I see my password typed as a command on the terminal, so the screensaver and lock was not active.
Ideas?
It is running Leap 42.3 and XFCE.
The display is a Samsung.
In settings, display power management is "off". Screensaver is disabled. Yet the display itself goes dark and later powers off, something which kodi impedes when it is running.
I will try enabling power management of the display in XFCE, setting "switch off" to "never".
Carlos, I'd think you'd want power management to be on; yes, that would allow the monitor to go black after a specified amount of time, but it would also allow the monitor to come back on when the computer receives input from the mouse or keyboard. IIRC the "specified amount of time" can be set to forever. I also noticed in another post you had this:
The current Xorg.0.log says:
[ 39.058] (==) intel(0): DPMS enabled
Despite /etc/X11/xorg.conf.d/50-monitor.conf:
Section "Monitor" Identifier "DefaultMonitor" Option "DPMS" "off" EndSection
I have this: # grep DPMS Xorg.0.log [ 39.871] (II) modeset(0): No DPMS capabilities specified [ 40.054] (==) NOUVEAU(G0): DPMS enabled [ 40.118] (==) modeset(0): DPMS enabled which tells me that the X server gets instructions to change that setting from its original. Your logfile could possibly show such changes. The xset manpage shows several options for setting DPMS for X. Two other things: Try hitting Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus to get the monitor back from black. I'm trying to remember from having your same problems decades ago, but I did find a way to bring an unresponsive monitor back to life and those two commands force a reread of the monitor's capabilities, reconnecting to the monitor in the process. Those two key commands are explained in the Xorg manpage, if you want more info on them. To make it easier to find out what, if anything, crashed, I'd run "ps -ef --forest > ps.before" when my system is running properly, then the same command but with output redirected to a different file after the system horked. Afterwards I could compare the two files to see what possibly crashed. I'd also note if a PID changed; sometimes a server (e.g., X) will crash, but then nicely restart without a trace, except it has a new PID. Xorg and the stuff around it will be the most relevant. Hope something here helps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-19 11:42, ken wrote:
On 06/17/2018 07:04 PM, Carlos E. R. wrote:
On Sunday, 2018-06-03 at 15:55 +0200, Carlos E. R. wrote:
Hi,
I have an sporadic problem with my media server, currently running Leap 42.3. Typically it is running kodi full screen (on XFCE desktop). I leave it running on the night (it is also server for other things full time), so I just power off the display.
Well, sometimes when I power back on the display it remains "dark grey", ie, black with backlight on; there is some signal, but it is black. No response to keyboard at all, that I can see. Most times I can not switch to console text mode. I can do ssh from another machine, tasks are running. I kill kodi if it still there, kill the screen saver, "chvt 1", "init 3"... nothing works, the display does not respond. I have no resource but reboot the server.
On monitors I've had this sort of issue with, there has been a red/green LED generally close to the power button. When this LED is green, it means the computer still has a connection to the monitor. When the LED is red, it means that there is no connection between the monitor and the computer. Does your monitor have such an LED? If so, what does it "say"?
Nope, no such thing. There is a window that pops up saying "no signal" when moving the cable to another socket. But no such window before doing the cable move, so there was some sort of signal then.
I will try enabling power management of the display in XFCE, setting "switch off" to "never".
Carlos, I'd think you'd want power management to be on; yes, that would allow the monitor to go black after a specified amount of time, but it would also allow the monitor to come back on when the computer receives input from the mouse or keyboard. IIRC the "specified amount of time" can be set to forever.
But it doesn't come back, that is the problem. Normally yes, but not on a few occasions, which sometimes forced me to reboot. I normally power off the monitor when not using it, on the mains power strip.
Two other things:
Try hitting Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus to get the monitor back from black. I'm trying to remember from having your same problems decades ago, but I did find a way to bring an unresponsive monitor back to life and those two commands force a reread of the monitor's capabilities, reconnecting to the monitor in the process. Those two key commands are explained in the Xorg manpage, if you want more info on them.
Yes, those keys are for changing the display resolution, I know them. I have tried them, but not on this machine, sometimes with disastrous results because whatever machine is unable to cycle back to the original resolution.
To make it easier to find out what, if anything, crashed, I'd run "ps -ef --forest > ps.before" when my system is running properly, then the same command but with output redirected to a different file after the system horked. Afterwards I could compare the two files to see what possibly crashed. I'd also note if a PID changed; sometimes a server (e.g., X) will crash, but then nicely restart without a trace, except it has a new PID. Xorg and the stuff around it will be the most relevant.
Hope something here helps.
I can try that, but I know already that it happens when kodi crashes and it had the display. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (5)
-
Carlos E. R. -
Felix Miata -
ken -
L A Walsh -
Patrick Shanahan