Blank screen after reopening screen

[Safenein]

It's on laptop with nvidia drivers used.

I currently use an Asus Zenbook Duo. It has a second screen integrated in the laptop and it is this screen that has an issue : When I close then reopen the laptop the main screen is waking up and display things correctly while the other one keep displaying black (it is actually powered).

There is no related line in log but here is the output of hyprctl monitors:

Monitor eDP-1 (ID 0):
    2880x1800@120.000999 at 0x0
    description: Samsung Display Corp. 0x416D (eDP-1)
    make: Samsung Display Corp.
    model: 0x416D
    serial: 
    active workspace: 2 (term)
    reserved: 0 25 0 0
    scale: 2.00
    transform: 0
    focused: yes
    dpmsStatus: 1
    vrr: 0

Monitor DP-1 (ID 3):
    2880x864@120.015999 at 0x900
    description: BOE 0x0A8D (DP-1)
    make: BOE
    model: 0x0A8D
    serial: 
    active workspace: 10 (10)
    reserved: 0 0 0 0
    scale: 2.00
    transform: 0
    focused: no
    dpmsStatus: 1
    vrr: 0

It doesn't change between the state with black screen and the working state. It is the screen on DP-1 btw.

Hope this is easy to fix, ask me if something is needed. Hyprland version: hyprland-nvidia-0.25.0-1, built with Arch AUR

[Safenein]

I switched to classic hyprland from official repos and it still have the same behavior.

I found a temporary solution, if I set the luminosity at 0 and bring it back up, it reactivate my screen.

Also, if I don't close my laptop and let hyprctl disable dpms, it work well when re-enabling dpms with swayidle. I don't know if it may help.

[A31Nesta]

Same issue here but with a desktop PC. Plasma wayland works perfectly with one monitor connected to AMD integrated graphics and the other connected to nvidia GPU.

But in Hyprland if I suspend the computer and wake up, the monitor connected to nvidia stays black but powered, there's no "no signal" message and the backlight stays on.

I don't know how to set the luminosity to 0 like you mentioned but I tried with brightness and it didn't do anything, I also tried disabling dpms and enabling it after suspension but it didn't work.

In using a fresh install of Arch Linux with Nvidia (proprietary) and AMD drivers and I'm using the normal hyprland package from the official repository (not hyprland nvidia from the AUR)

Edit: I forgot to update this but it turns out I just forgot to follow part of the wiki's nvidia-specific instructions

[ElDavoo]

I'm having the same issue with a laptop with hybrid graphics (which further complicates things as the gpu gets shut down dinamically).
In the last two years I had all sorts of issues with the nvidia card, but driver and hyprland updates progressively solved them. This is the only major one left for my setup.

I'm on gentoo linux, with hyprland 0.42.0 and nvidia open dkms 560.35.03 (my gpu is a rtx 3070.)
As OP said, after a little while (I didn't suspend my system) the external hdmi monitor (wired to the nvidia card) will be powered but without showing anything.
I've tried suspend/resuming (by callinghyprctl dispatch dpms).
Currently my only solution is to reboot the machine.

[Safenein]

Does it work once you set up nvidia vars and stuff?

Also, op, was it fixed for you?

I followed the guide on Hyprland's Wiki to set up my GPU.

It is not yet fixed on my side, this issue is common on the machine I'm using because it is quite rare to get 2 screen embedded in a laptop. I get the same black screen in other compositors as well (not it TTY though...). The screen doesn't even appear in the right folder in /sys, driver issue or something. I may close this is issue if its okay because my issue was not Hyprland related. I keep this open until ElDavoo get its issue resolved.

ElDavoo, are you running any power management tool ? Swayidle or anything of this kind ? You may try other alternatives for these to see if this is related.

[ElDavoo]

Yeah, but hypridle just callshyprctl dispatch dpms off

[ElDavoo]

I have https://forums.developer.nvidia.com/t/555-58-02-10-nvidia-open-driver-crash/302036 so let's wait for this issue to be solved first