Manjaro randomly goes to black screen

Hi, I am having problems because my screen goes to black at random moments, is not always but when it happens I have to reset the computer. I also noticed is only a screen issue since the computer stays on even after this happens. Also the screen says that it is recieving signal from the DP.

Thanks in advance if someone can help
Tomás

hello mytorojas,
can you please provide the output of inxi -v 8 so that we can know a bit about your system config?
Welcome to the community!
Julius

1 Like

thanks! and sure here it is!

System:
  Kernel: 5.8.16-2-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=8b3593a8-6e11-41ac-b649-df598b2ee883 rw quiet apparmor=1 
  security=apparmor resume=UUID=b98b9f66-1812-45ea-9c50-af0e3a25d8ff 
  udev.log_priority=3 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> 
  Mobo: ASUSTeK model: TUF GAMING Z490-PLUS (WI-FI) v: Rev 1.xx 
  serial: <filter> UEFI: American Megatrends v: 1410 date: 09/04/2020 
CPU:
  Topology: 10-Core model: Intel Core i9-10850K bits: 64 type: MT MCP 
  arch: N/A family: 6 model-id: A5 (165) stepping: 5 microcode: C8 
  L2 cache: 20.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 144040 
  Speed: 800 MHz min/max: 800/5200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 
  4: 800 5: 800 6: 800 7: 801 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 
  14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:9bc5 
  Display: x11 server: X.Org 1.20.9 driver: intel unloaded: modesetting 
  alternate: fbdev,vesa display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: DP1 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") 
  diag: 551mm (21.7") 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CML GT2) v: 4.6 Mesa 20.1.8 
  direct render: Yes 
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3 
  chip ID: 8086:06c8 
  Sound Server: ALSA v: k5.8.16-2-MANJARO 
Network:
  Device-1: Intel Wireless-AC 9462/9560 driver: iwlwifi v: kernel port: 3000 
  bus ID: 00:14.3 chip ID: 8086:06f0 
  IF: wlo1 state: up mac: <filter> 
  Device-2: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:0d4d 
  IF: eno2 state: down mac: <filter> 
Drives:
  Local Storage: total: 931.51 GiB used: 14.96 GiB (1.6%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 
  size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: 111110WD scheme: GPT 
Partition:
  ID-1: / raw size: 585.94 GiB size: 575.74 GiB (98.26%) 
  used: 14.96 GiB (2.6%) fs: ext4 dev: /dev/nvme0n1p3 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 5.86 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 368 Uptime: 2h 20m Memory: 15.46 GiB used: 1.88 GiB (12.2%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: 1108 pacman: 1100 
  lib: 340 flatpak: 0 snap: 8 Shell: Bash v: 5.0.18 running in: xfce4-terminal 
  inxi: 3.1.05

Maybe as more background, this issue started when I installed xournal++ maybe it has to do with it but I am not sure. I don’t think so

Thanks for the reply, sorry for not getting back to you sooner.
Unfortunately I don’t see anything that could be causing the issue in there.
Maybe there is something useful in dmesg.
if you could please provide the output of dmesg | grep DP and dmesg | grep display
a look at journalctl | grep display may help, too.

If you don’t mind, a look at
cat /var/log/pacman.log may also be revealing to see what packages have been installed since then, be prepared for a wall of text however :wink:

Best Regards, Julius

Hi,
I have a similar problem with my NUC 7PJYH, but only with Kernel 5.9 and 5.10, 5.8 still works.
With one Monitor, the Screen goes black after some idling, so at first I suspectet a energy setting but could not find anything so far.
When the Screen is on and the second Monitor switched on (both HDMI), both Screens go black immediatly, but the Monitors are still on, so some Signal seems to be there.
After that I have to do a hard reset to get it going.

This started after the last big Update, when switching to 5.9

Seems we are both using the i915 Drivers:

System: Host: ManjaKDE Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=21fe2847-5885-41f9-b5c0-33cf88517521 rw quiet apparmor=1
security=apparmor resume=UUID=14b7c901-b446-4c70-a1bb-121db54f117f udev.log_priority=3
Desktop: KDE Plasma 5.20.2 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Mini-pc System: Intel product: NUC7PJYH v: J67992-400 serial: <superuser/root required> Chassis: type: 35
v: 2.0 serial: <superuser/root required>
Mobo: Intel model: NUC7JYB v: J67969-400 serial: <superuser/root required> UEFI: Intel
v: JYGLKCPX.86A.0057.2020.1020.1637 date: 10/20/2020
Battery: Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse serial: 405e-8b-04-16-8d
charge: 55% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech K780 Multi-Device Wireless Keyboard serial: 405b-a1-eb-7f-9e
charge: 100% (should be ignored) rechargeable: yes status: Discharging
Memory: RAM: total: 7.31 GiB used: 2.89 GiB (39.6%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: Quad Core model: Intel Pentium Silver J5005 bits: 64 type: MCP arch: Goldmont Plus family: 6
model-id: 7A (122) stepping: 1 microcode: 34 L2 cache: 4096 KiB bogomips: 11984
Speed: 1716 MHz min/max: 800/2800 MHz Core speeds (MHz): 1: 1716 2: 1773 3: 1572 4: 1668
Flags: 3dnowprefetch acpi aes aperfmperf apic arat arch_capabilities arch_perfmon art bts cat_l2 cdp_l2 clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts ept ept_ad erms est
flexpriority fpu fsgsbase fxsr ht ibpb ibrs ibrs_enhanced ida intel_pt lahf_lm lm mca mce md_clear mmx monitor
movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts
rdpid rdrand rdseed rdt_a rdtscp rep_good sdbg sep sha_ni smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip vme vmx vnmi vpid x2apic xgetbv1
xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel UHD Graphics 605 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3184
Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: intel unloaded: modesetting alternate: fbdev,vesa
display ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") s-diag: 777mm (30.6")
Monitor-1: HDMI1 res: 2560x1440 hz: 60 dpi: 108 size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
OpenGL: renderer: Mesa Intel UHD Graphics 605 (GLK 3) v: 4.6 Mesa 20.2.1 direct render: Yes
Audio: Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci bus ID: 00:0e.0 chip ID: 8086:3198
Device-2: Texas Instruments PCM2704 16-bit stereo audio DAC type: USB driver: hid-generic,snd-usb-audio,usbhid
bus ID: 1-4.2:5 chip ID: 08bb:2704
Sound Server: ALSA v: k5.8.18-1-MANJARO
Network: Device-1: Intel driver: iwlwifi v: kernel port: f000 bus ID: 00:0c.0 chip ID: 8086:31dc
IF: wlo2 state: down mac: 96:17:ff:61:d3:9f
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169 v: kernel port: e000
bus ID: 02:00.0 chip ID: 10ec:8168
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 94:c6:91:1d:35:41
IP v4: 192.168.178.33/24 type: dynamic noprefixroute scope: global broadcast: 192.168.178.255
IP v6: 2a00:6020:4002:8000:d5bd:4a8:b855:5ed4/64 type: dynamic noprefixroute scope: global
IP v6: fe80::8635:76fa:241a:77d5/64 type: noprefixroute scope: link
WAN IP: 94.31.80.120
Drives: Local Storage: total: 476.94 GiB used: 198.49 GiB (41.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda vendor: SanDisk model: SDSSDH3 512G size: 476.94 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s serial: 195253801934 rev: 1000 scheme: GPT
Message: No Optical or Floppy data was found.
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 100.59 GiB size: 98.01 GiB (97.44%) used: 46.67 GiB (47.6%) fs: ext4 dev: /dev/sda2 label: System
uuid: 21fe2847-5885-41f9-b5c0-33cf88517521
ID-2: /boot/efi raw size: 300.0 MiB size: 299.4 MiB (99.80%) used: 280 KiB (0.1%) fs: vfat dev: /dev/sda1
label: N/A uuid: DF85-B1A8
ID-3: /mnt/Daten raw size: 152.35 GiB size: 148.96 GiB (97.77%) used: 105.14 GiB (70.6%) fs: ext4 dev: /dev/sda6
label: Datengrab uuid: 7957eacf-543a-4041-b895-36e9748667fc
ID-4: /run/timeshift/backup raw size: 117.25 GiB size: 114.91 GiB (98.00%) used: 46.68 GiB (40.6%) fs: ext4
dev: /dev/sda5 label: Back uuid: 3655a0fe-e3bc-4c34-ae85-e9cb680ab6cc
Swap: Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 label: N/A
uuid: 14b7c901-b446-4c70-a1bb-121db54f117f
Unmounted: ID-1: /dev/sda4 size: 97.66 GiB fs: ext4 label: N/A uuid: 7af3a6ca-880d-4add-8713-421eaef3eb32
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 9 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 1-3:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip ID: 0bda:5411
Hub: 1-4:3 info: Belkin ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 050d:0233
Device-1: 1-4.2:5 info: Texas Instruments PCM2704 16-bit stereo audio DAC type: Audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s chip ID: 08bb:2704
Device-2: 1-4.3:6 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid
interfaces: 3 rev: 2.0 speed: 12 Mb/s chip ID: 046d:c52b
Device-3: 1-4.4:7 info: MosArt Wireless Keyboard/Mouse type: Keyboard,Mouse driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s chip ID: 062a:4101
Device-4: 1-9:4 info: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s chip ID: 8087:0aaa
Hub: 2-0:1 info: Full speed (or root) Hub ports: 7 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003
Hub: 2-3:2 info: Realtek Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip ID: 0bda:0411

Hello SvenB and mytorojas,

This is just an idea, could the issue be connected to the backlight, perhaps?

Here is a way to check whether this is the case:

  1. create a file in your home directory called brightness.txt
  2. put the following script in a file called brightness_log.py somewhere on your computer
import os
import time as t

path = "/sys/class/backlight/edp-backlight/brightness"
out = open("/home/julius/brightness.txt","a")

current = ""
last = ""

while True:
    
    f = open(path, "r")
    current = f.read()
    f.close()
    if current != last:
        out.write(current)
    last = current
    
    t.sleep(1)
  1. replace julius in the line out = open("/home/julius/brightness.txt","a") of the script with your account name. You can find out what it is by doing whoami in the terminal
  2. replace edp-backlight in the line path = "/sys/class/backlight/edp-backlight/brightness" with the name of your display. You can find out what it is by typing
    ls /sys/class/backlight/ in the terminal
  3. do python brightness_log.py in the folder where you saved brightness_log.py and leave it running.

When the issue comes up, do kate ~/brightness.txt in a terminal and see whether the last line displays a 0.
If so, the computer must have turned off the backlight of your display.

This is just an idea, but I would be thankful if one of you could try this out.
best Regards, Julius

The same here…I’ve got a Beelink Gemini x55 with a Intel UHD Graphics 605 and this bug only started when using the linux kernel 5.9.

Graphics: Device-1: Intel UHD Graphics 605 driver: i915 v: kernel Display: x11 server: X.org 1.20.9 driver: intel unloaded: modesetting resolution: <xdpyinfo missing> OpenGL: renderer: Mesa Intel UHD Graphics 605 (GLK 3) v: 4.6 Mesa 20.2.2

I’ve turneb back to kernel 5.8 and it works fine. Hope that Manjaro team could fix this in the next update.

Just to report that with this last update of the drivers, at the first time it works again with the latest kernel 5.9 but after a few reboots the error still exists…so I’m back to 5.8 kernel.

Hello dear community,
I had the same issue here on my MSI GF75 9RCX (with i915 too) with kernel 5.7. Fixed in 5.8 but back again in 5.9.
Cheers.

EDIT: Happened to me 3 times in a row with 5.8. Any suggestions to track this anomaly ?

Hello, I removed the non-free nvidia drivers and everything is fine now. No more occurrence. Cheers

This kernel is EOL, better change to 5.9 (be prepared for the next shift soon as 5.10 LTS will be available soon).

I’m not saying this fixes your problem, anyway.

After the recent update to kernel 5.10 the problem still persists. Unfortunelly now I can’t go back to 5.8 anymore and I’ve realized that when I have Lollypop playing music in the background despite of the system goes to suspend mode after wake up it show the login screen as it always should be.
Does anyone know how to solve this?

This are the drives that are installed:

Installed PCI configs:

              NAME               VERSION          FREEDRIVER           TYPE

       video-linux            2018.05.04                true            PCI

Hi everybody, I’m facing this problem since a few months and I came up with a brutal but working workaround.

Just connect with SSH and send this command:

DISPLAY=:0 xrandr --output DP-0 --auto

Obviously change the output depending on yours, just check it out with xrandr command.
You can also create a script with a shortcut with this command.
The screen will wake up soon after.

Hi chavo11,

Thanks for posting a solution but I’m kind of a newbie and would be great if you can help me what is the command line for connect first with SSH?
Sorry for this dumb question.

Hi Lastbreak, np :slight_smile:

The easiest thing you can do is to create a file somewhere with this inside:

#!/bin/bash
uxterm -e xrandr --output DP-0 --auto

then make it executable by changing the permissions with your file manager or by using:
chmod x /path/to/file

Then you can create a keyboard shortcut to that file, and each time your screen goes black you have just to press the shortcut.

If you want to try with SSH it’s quite easy too:

Install openssh on your pc.
Then you can connect from another pc by using:
ssh -p port user@server-address

The default port is 22, you can find the address on your pc by typing “ifconfig”, or from another pc with “arp -a”. You can also connect from a smartphone by installing an SSH client (I’m using JuiceSSH but it will not matter).

Tell me if got any more problems. Bye :slight_smile:

Hi chavo11,
thanks for the effort explaning this…I manage to do everthing right with the file creation option but when I send the computer to suspend mode it still have the black screen after hit any key to recover from suspend mode.

You did everything that I told you? Creating the shortcut and everything? If you press the shortcut while using the pc a terminal will show up for a split second, so you can check that it’s working.
Also check that your screen is DP-0, you can see it by typing xrandr in a terminal.
If this is not working then probably you’ve got a lockscreen after suspend and maybe shortcuts are not working there, which can be possible. In that case you have to use the SSH workaround.

I think that my screen is DP-0, check the xrandr output:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 59.90
1280x960 60.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1280x800 59.81 +
1920x1080 60.00* 60.00 50.00 59.94 30.00 24.00 29.97 23.98
1920x1080i 60.00 50.00 50.00 59.94
1600x1200 60.00
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 59.90
1366x768 59.79
1152x864 75.00
1280x720 60.00 50.00 59.94 49.83
1024x768 119.99 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x576i 50.00
720x480 60.00 59.94
720x480i 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

As far as SSH workaround I can’t go that way because I have in return this output after trying to ssh:
ssh: connect to host XXX.XXX.X.XX port 500: Connection refused

It’s there anything that I’m doing wrong?

Sorry I just checked the default port is 22, try with that. Probably that’s why you’re getting connection refused.

From your randr output it seems you’ve got 2 screens, the HDMI1 is the primary (DP stands for “Display Port” not display :smiley:.)

Anyway the command for the shortcut has to be:
uxterm -e xrandr --output HDM1 --auto
For SSH:
DISPLAY=:0 xrandr --output HDM1 --auto