Screen goes black and freeze for minutes after opening from Suspend

I’ve used Manjaro more than a year. My laptop has a dedicated nVidia GPU along with integrated Intel HD GPU. I used optimus-switch for GPU management. But today I learnt about PRIME for GPU management. So I installed hybrid-intel-nvidia-prime driver from manjaro settings. and as prime-run was not working by default, so I added this fix also.
In my case /etc/X11/xorg.conf.d/10-prime.conf is:

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "iGPU"
    Option "AllowNVIDIAGPUScreens"

Section "Device"
    Identifier "iGPU"
    Driver "modesetting"
    BusID "PCI:0:2:0"

Section "Screen"
    Identifier "iGPU"
    Device "iGPU"

Section "Device"
    Identifier "dGPU"
    Driver "nvidia"
    BusID "PCI:4:0:0"

[I have no knowledge what this script do :sob:]

now prime-run is working fine but when I suspend my device and wake it up again after a period, rather than getting back logging screen, a blank screen is showing. After such a longer period(may be 2-3 min) the logging screen comes. But with optimus-switch I had no such issue…

Here is my system specification:

  Kernel: 5.4.64-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: root=UUID=299725f7-eb73-45b6-a9ff-ecbfd1cb4385 rw quiet 
  apparmor=1 security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.19.5 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
  RAM: total: 11.60 GiB used: 5.62 GiB (48.4%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
  Device-1: Intel HD Graphics 5500 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:1616 
  Device-2: NVIDIA GM108M [GeForce 930M] vendor: ASUSTeK driver: nvidia 
  v: 450.66 alternate: nouveau,nvidia_drm bus ID: 04:00.0 chip ID: 10de:1346 
  Device-3: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo 
  bus ID: 1-5:9 chip ID: 04f2:b483 
  Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 
  driver: modesetting,nvidia display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
  s-diag: 414mm (16.3") 
  Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6") 
  diag: 395mm (15.5") 
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.1.7 
  direct render: Yes 

:+1: Welcome to Manjaro! :+1:

  1. The 450 series is known to have a few bugs, so try the 440 series first especially with a 930M

  2. If that wouldn’t help, please read this:

    How to provide good information in your posts - Tutorials - Manjaro Linux Forum

    and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…

    An inxi --admin --verbosity=7 --filter --no-host would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)


I don’t know if it’s just in this post, but it should be “PCI:1:0:0”.

Does it happen after reboot? What happens if you switch to a TTY and switch back when this happens?

That’s why I asked OP to provide the inxi output: it could be PCI:4but that depends on his/her hardware…


User reported this happened only once and then got fixed. Closing this topic.

1 Like