blank black screen after waking up from suspend

thetareefarz · 2025-02-28 12:35:05

Hello, users of the arch forum

I am using arch on a Lenovo ideapad D330-10IGL. (its a screen-keyboard deattachable laptop) (sort of like an iPad connecting to a attachable keyboard)

The problem: After I wake the laptop up from sleep or suspend, the display turns on but it is a complete black screen. Clicking on the mouse or the keyboard doesn't change anything and re-suspending it waking it up from sleep again doesn't do anything either.

My temporary solution: I have noticed that switching ttys via the (Ctrl+Alt+Num) keybinding fixes the problem only if one of the tty is running a xorg server.
If there isnt a xorg server running in the background and there is only ttys, changing between different ttys doesnt do anything.

I would really appreciate it if someone could help me with this problem. I am clipping some journals and dmesg output for more information.

Thank you in advance.

Journal log:- http://0x0.st/8m2g.txt
Dmesg log:- http://0x0.st/8m2E.txt

Last edited by thetareefarz (2025-02-28 12:51:59)

thetareefarz · 2025-02-28 12:41:29

Scenario of how the temporary solution works:

Before sleeping:
- i start startx on tty1
- display server startup (sometimes, if it doesnt, i just switch between ttys (Ctrl+Alt+F2 then Ctrl+Alt+F1) , ignore this for now)
- i go to sleep by closing the lid or by the power button

After sleeping:
- I open up the lid or open the lid and click the power button
- The display turns on but, , the display is a blank black screen which doesnt do anything (the display is still on the xorg tty1)
- I can get the display on by going (Ctrl+Alt+F2 -> Ctrl+Alt+F1) (switching between tty1 and tty2)

This temporary solution only works if there is a xorg server running.

seth · 2025-02-28 15:49:33

Does "setterm --blank poke" help?
Though you might require a modeswitch, https://man.archlinux.org/man/extra/fbset/fbset.8.en - ideally try (and inspect) this via ssh.

thetareefarz · 2025-03-02 07:14:13

seth wrote:

Does "setterm --blank poke" help?

Hello seth, thank you again for your reply.

Using the provided command merely returns with a error of

setterm: terminal xterm-256color does not support --blank

i figured that xterm-256color wasnt supported by this cmd so i changed the TERM env variable to nothing so it could work properly but then it just tells me that its a invalid terminal type.

seth wrote:

Though you might require a modeswitch, https://man.archlinux.org/man/extra/fbset/fbset.8.en - ideally try (and inspect) this via ssh.

i am not sure i follow by what you mean by this. I would really appreciate it if you could explain the steps to me.

Thank you.

thetareefarz · 2025-03-02 07:18:17

im using linux as my term value rn and ill add it to this post if i see anything that could be useful

thetareefarz · 2025-03-02 07:19:52

ok i used the setterm --blank poke command and i can confirm that this command cannot resolve the issue.

thetareefarz · 2025-03-02 07:25:10

doing the tty switching method with wayland works as well

thetareefarz · 2025-03-02 07:40:12

here is one of the post in the manjaro forum where this problem is depicted: https://forum.manjaro.org/t/black-scree … it/31976/8

the guy supposedly fixed the problem via using gdm. I tried these method but couldn't be successful with fixing the problem.

seth · 2025-03-02 08:45:03

Please don't bump, edit your prevous post to mend it if nobody has replied.

Why does your console set "xterm-256color" as TERM environment??
Alternatively, if you're entering that in a GUI terminal emulator (alacritty etc) that's certainly not gonna do anything.

The idea would have been to check "fbset -i" while the console is blank, attempt eg. "fbset -xres 1024 -yres 768" and then back to "fbset -match"

thetareefarz · 2025-03-07 14:27:26

sorry for the bumps.

the cmds doesn't fx the problem n queston.

here s the output anyway for more detals:

mode "800x1280"
    geometry 800 1280 800 1280 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : i915drmfb
    Address     : (nil)
    Size        : 4096000
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 3200
    Accelerator : No

seth · 2025-03-07 17:26:03

The output is pivoted?
Does this also happen in landscape mode?

thetareefarz · 2025-03-08 08:58:43

seth wrote:

Does this also happen in landscape mode?

Yes both of them.

seth · 2025-03-09 16:18:39

I assume switching between pivot and landscape likewise doesn't revive the output?

thetareefarz · 2025-03-11 07:55:55

seth wrote:

I assume switching between pivot and landscape likewise doesn't revive the output?

nope.

seth · 2025-03-17 16:59:44

Not sure whether this is a better workaround, but see https://raw.githubusercontent.com/torva … /fbcon.rst and try "fbcon=map:000001" what should get you a bogus console on VT6, so ctrl+alt+f6 should™ turn the output off (except it oc already is) and going back to VT1 (and device 0) will hopefully restore the output…

lucasgabmoreno · 2025-08-05 14:32:10

seth wrote:

Not sure whether this is a better workaround, but see https://raw.githubusercontent.com/torva … /fbcon.rst and try "fbcon=map:000001" what should get you a bogus console on VT6, so ctrl+alt+f6 should™ turn the output off (except it oc already is) and going back to VT1 (and device 0) will hopefully restore the output…

Hi! I've tried fbcon=map:000001 and doesn't work on Gnome Wayland on Lenovo ideapad D330-10IGL

seth · 2025-08-05 14:43:02

To address what issue? And as basis of what further action?
Does

switching ttys via the (Ctrl+Alt+Num) keybinding fixes the problem only if one of the tty is running a xorg server.

work in your situation as well?
The idea behind the fbcon=man is to provoke a modeswitch failure on tty6 and the hope that this (you'd go to black on TTY6) serves the same purpose (w/o an extra X11 server around)

thetareefarz · 2025-08-17 13:12:30

seth wrote:

"fbcon=map:000001" what should get you a bogus console on VT6, so ctrl+alt+f6 should™ turn the output off

Hello there seth,
Thank for continuing to shedding light on this matter.

Sadly, this kernel parameter doesn't do all that much. i tried appending fbcon=map:000001 in my boot entry for systemd-boot as well as grub with no luck, and I don't get a bogus console on tty6, i can switch to it just fine with no issues.
Could possibly doing something wrong but no, tty6 is still pretty much accessible and the display does not turn off.

seth · 2025-08-17 13:14:40

Check "cat /proc/cmdline" and make sure the parameter shows up there.
Same behavior w/ "fbcon=map:000002" ?

thetareefarz · 2025-08-17 13:35:14

Note: This blank issue occurs after going to screensaving mode as well

seth · 2025-08-17 14:00:30

You mean https://wiki.archlinux.org/title/Displa … ux_console or is there a display server running on the affected TTY as well?
Which one?

thetareefarz · 2025-08-18 11:41:20

seth wrote:

You mean https://wiki.archlinux.org/title/Displa … ux_console or is there a display server running on the affected TTY as well?
Which one?

Not really sure what you meant by "is there a display running on the affected TTY as well", but I am not referring to DPMS or anything but I am not sure if that has to do something with DPMS anyway

What I wanted to imply was the fact that after suspending and as well as after the screensaver popups (this could be DPMS, the screensaver is the default screensaver on xorg with dwm, i usually turn it off with xset -dpms and xset s off)

The common factor which i've found from this observation is that,

The issue occurs commonly after the display has turned off in some sort of way (be that suspending or going to power saving via dpms or the screensaver mechanism)

seth wrote:

Check "cat /proc/cmdline" and make sure the parameter shows up there.

$ cat /proc/cmdline
initrd=\initramfs-linux.img root=UUID=decbc62f-9b11-4610-a1e2-2475c0d0e707 rw fbcon=map:000001

Can confirm the kernel param is there and is not creating a bogus tty on tty6

seth wrote:

Same behavior w/ "fbcon=map:000002" ?

No luck with this solution either.

Last edited by thetareefarz (2025-08-18 11:54:09)

seth · 2025-08-18 14:20:22

Getting the console (the DOS like text only interface) to enter DPMS requires you to jump through some hoops and I think also a custom kernel config.
I was under the impression that you were running the multi-user.target (2nd link below) only and required a pointless X11 server on a different tty.

From X11, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General after such incident and also the output of "xrandr -q" before, during and after losing the output.

xset dpms force off; sleep 10; xset dpms force on; xrandr -q; printf '\a' # or anything else that produces an audible signal so you know xrandr had fired

should™ work for "during" part.

Arch Linux

#1 2025-02-28 12:35:05

blank black screen after waking up from suspend

#2 2025-02-28 12:41:29

Re: blank black screen after waking up from suspend

#3 2025-02-28 15:49:33

Re: blank black screen after waking up from suspend

#4 2025-03-02 07:14:13

Re: blank black screen after waking up from suspend

#5 2025-03-02 07:18:17

Re: blank black screen after waking up from suspend

#6 2025-03-02 07:19:52

Re: blank black screen after waking up from suspend

#7 2025-03-02 07:25:10

Re: blank black screen after waking up from suspend

#8 2025-03-02 07:40:12

Re: blank black screen after waking up from suspend

#9 2025-03-02 08:45:03

Re: blank black screen after waking up from suspend

#10 2025-03-07 14:27:26

Re: blank black screen after waking up from suspend

#11 2025-03-07 17:26:03

Re: blank black screen after waking up from suspend

#12 2025-03-08 08:58:43

Re: blank black screen after waking up from suspend

#13 2025-03-09 16:18:39

Re: blank black screen after waking up from suspend

#14 2025-03-11 07:55:55

Re: blank black screen after waking up from suspend

#15 2025-03-17 16:59:44

Re: blank black screen after waking up from suspend

#16 2025-08-05 14:32:10

Re: blank black screen after waking up from suspend

#17 2025-08-05 14:43:02

Re: blank black screen after waking up from suspend

#18 2025-08-17 13:12:30

Re: blank black screen after waking up from suspend

#19 2025-08-17 13:14:40

Re: blank black screen after waking up from suspend

#20 2025-08-17 13:35:14

Re: blank black screen after waking up from suspend

#21 2025-08-17 14:00:30

Re: blank black screen after waking up from suspend

#22 2025-08-18 11:41:20

Re: blank black screen after waking up from suspend

#23 2025-08-18 14:20:22

Re: blank black screen after waking up from suspend

Board footer