[SOLVED] Black screen after login

Keyres · 2023-12-21 18:23:28

Hi all,

after the update of the kernel to version >= 6.6.5 my screen is black after login (looks like it is simply turned off). It works fine with previous version (6.6.4), works as expected with nomodeset kernel parameter (although this is not a solution, as I have an AMD integrated GPU which requires KMS — there is no backlight control nor HW decoding etc). Early KMS did not help either.
As far as I can tell there is nothing interesting happening in the system logs, nor in Sway logs (the only errors appear in the latter, but they don't look related; similar errors are reported when running on earlier version of the kernel where everything works.

My setup is the following : I use Sway as the window manager, my CPU is Ryzen 7 6860Z with integrated Radeon 680M GPU.
I have searched the web but found nothing helpful so far. If needed I will provide whatever info requested.

Cheers!

Last edited by Keyres (2023-12-24 13:47:02)

seth · 2023-12-21 20:34:08

What are you logging into from where?
Is this all on the multi-user.target (console) or are you logging from agetty intto a sway session or do you use a DM (which) to start sway?

Keyres · 2023-12-22 18:54:45

I simply have a line launching Sway after logging in to a shell session. specifically the following is a part of my zshrc

if [ -z $DISPLAY ] && [ "$(tty)" = "/dev/tty1" ]; then
    exec systemd-cat -t sway sway
fi

Head_on_a_Stick · 2023-12-22 18:57:06

That should be in ~/.zlogin or ~/.zprofile.

And you don't need to check for $DISPLAY because `tty` will only return /dev/tty1 in a console. You don't need to quote /dev/tty1 either.

EDIT: which is all irrelevant, sorry. Got carried away there. Happens a lot.

Please share the logs. You might have missed something.

Sounds like a kernel regression though.

Last edited by Head_on_a_Stick (2023-12-22 19:13:03)

seth · 2023-12-22 20:39:56

You actually do want to check for DISPLAY and probably WAYLAND_DISPLAY in case you're running a login shell from the graphical session, but this is indeed not relevant to the topic at hand.
So agetty works on a framebuffer console, but sway shuts down the output.

Do
a) weston
b) some X11 session (openbox, twm or just an xterm, doesn't matter)
cause the same?

Keyres · 2023-12-22 21:48:18

seth wrote:

Do
a) weston
b) some X11 session (openbox, twm or just an xterm, doesn't matter)
cause the same?

Weston does indeed produce graphical output, I am really confused now.

Here are logs from a boot (black screen after logging in), I have noticed that my keybindings still work and (blind typed) commands in the terminal are executed. I have no external monitor to check whether there would be output on one.
Logs from Sway.

Dec 22 22:30:31 archZ13 sway[1492]: 2023-12-22 22:30:31 - [swaybg-1.2.0/main.c:293] Found config * for output eDP-1 (Samsung Display Corp. 0x4167)
Dec 22 22:30:31 archZ13 sway[1538]: [2023-12-22 22:30:31.713] [info] Using configuration file /home/marcin/.config/waybar/config
Dec 22 22:30:31 archZ13 sway[1538]: [2023-12-22 22:30:31.955] [info] Unable to receive desktop appearance: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
Dec 22 22:30:31 archZ13 sway[1538]: [2023-12-22 22:30:31.955] [info] Using CSS file /home/marcin/.config/waybar/style.css
Dec 22 22:30:32 archZ13 sway[1544]: blueman-applet 22.30.32 WARNING  PluginManager:94 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
Dec 22 22:30:32 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._openssl.abi3.so'
Dec 22 22:30:32 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._padding.abi3.so'
Dec 22 22:30:32 archZ13 sway[1544]: blueman-applet 22.30.32 WARNING  PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Dec 22 22:30:32 archZ13 sway[1544]: blueman-applet 22.30.32 WARNING  PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Dec 22 22:30:32 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/apex._apex.abi3.so'
Dec 22 22:30:32 archZ13 sway[1538]: [2023-12-22 22:30:32.066] [info] Bar configured (width: 1440, height: 29) for output: eDP-1
Dec 22 22:30:32 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:32 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:32 archZ13 sway[2041]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86CameraAccessEnable
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86CameraAccessDisable
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86CameraAccessToggle
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86NextElement
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86PreviousElement
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86MarkWaypoint
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86Sos
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86NavChart
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86FishingChart
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86SingleRangeRadar
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86DualRangeRadar
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86RadarOverlay
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86TraditionalSonar
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86ClearvuSonar
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86SidevuSonar
Dec 22 22:30:32 archZ13 sway[2041]: > Warning:          Could not resolve keysym XF86NavInfo
Dec 22 22:30:32 archZ13 sway[2041]: Errors from xkbcomp are not fatal to the X server
Dec 22 22:30:32 archZ13 sway[2042]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Unsupported maximum keycode 708, clipping.
Dec 22 22:30:32 archZ13 sway[2042]: >                   X11 cannot support keycodes above 255.
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86CameraAccessEnable
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86CameraAccessDisable
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86CameraAccessToggle
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86NextElement
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86PreviousElement
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86MarkWaypoint
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86Sos
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86NavChart
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86FishingChart
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86SingleRangeRadar
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86DualRangeRadar
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86RadarOverlay
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86TraditionalSonar
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86ClearvuSonar
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86SidevuSonar
Dec 22 22:30:32 archZ13 sway[2042]: > Warning:          Could not resolve keysym XF86NavInfo
Dec 22 22:30:32 archZ13 sway[2042]: Errors from xkbcomp are not fatal to the X server
Dec 22 22:30:33 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:33 archZ13 sway[2076]: warn: wayland.c:1509: fractional scaling not available
Dec 22 22:30:33 archZ13 sway[2076]: warn: wayland.c:1512: no server-side cursors available, falling back to client-side cursors
Dec 22 22:30:34 archZ13 sway[1549]: dropbox: load fq extension '/opt/dropbox/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:34 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/cryptography.hazmat.bindings._openssl.abi3.so'
Dec 22 22:30:34 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/cryptography.hazmat.bindings._padding.abi3.so'
Dec 22 22:30:34 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/apex._apex.abi3.so'
Dec 22 22:30:35 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:35 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:35 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:36 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
Dec 22 22:30:37 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/PyQt5.QtCore.so'
Dec 22 22:30:37 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/PyQt5.sip.so'
Dec 22 22:30:37 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/PyQt5.QtGui.so'
Dec 22 22:30:37 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/PyQt5.QtWidgets.so'
Dec 22 22:30:37 archZ13 sway[2163]: dropbox: load fq extension '/home/marcin/.dropbox-dist/dropbox-lnx.x86_64-189.4.8395/PyQt5.QtDBus.so'
Dec 22 22:30:38 archZ13 sway[2076]:  err: wayland.c:1977: failed to roundtrip Wayland display: Connection reset by peer
Dec 22 22:30:38 archZ13 sway[2076]:  err: wayland.c:1977: failed to roundtrip Wayland display: Connection reset by peer
Dec 22 22:30:38 archZ13 sway[2076]:  err: wayland.c:1977: failed to roundtrip Wayland display: Connection reset by peer
Dec 22 22:30:38 archZ13 sway[2076]:  err: wayland.c:1942: failed to flush wayland socket: Connection reset by peer

I wasn't sure what to filter the system logs by though. I have included them on pastebin here.

seth · 2023-12-22 22:07:30

Dec 22 22:30:19 archZ13 kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0

ceterum censeo: add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

Can you switch to a different TTY while sway is running (ie. is this maybe a backlight issue) - and inspect the backlight condition from there (or via ssh)?
https://wiki.archlinux.org/title/Backlight#ACPI

Does sway work for a fresh user account (or after moving away ~/.config/sway/config )?

Keyres · 2023-12-22 22:37:13

Including "initcall_blacklist=simpledrm_platform_driver_init" as a kernel parameter made no noticeable difference, neither did running Sway with stock configuration.
Writing 100 to "/sys/class/backlight/amdgpu_bl1/brightness" did turn on the screen, so this does seem to be a backlight issue.

seth · 2023-12-23 07:08:52

so this does seem to be a backlight issue

https://bbs.archlinux.org/viewtopic.php … 1#p2138701

Keyres · 2023-12-24 13:37:56

I see, thank you for your assistance!

Indeed, the issue is gone after upgrading to 6.6.8.

Last edited by Keyres (2023-12-24 13:46:17)

Arch Linux

#1 2023-12-21 18:23:28

[SOLVED] Black screen after login

#2 2023-12-21 20:34:08

Re: [SOLVED] Black screen after login

#3 2023-12-22 18:54:45

Re: [SOLVED] Black screen after login

#4 2023-12-22 18:57:06

Re: [SOLVED] Black screen after login

#5 2023-12-22 20:39:56

Re: [SOLVED] Black screen after login

#6 2023-12-22 21:48:18

Re: [SOLVED] Black screen after login

#7 2023-12-22 22:07:30

Re: [SOLVED] Black screen after login

#8 2023-12-22 22:37:13

Re: [SOLVED] Black screen after login

#9 2023-12-23 07:08:52

Re: [SOLVED] Black screen after login

#10 2023-12-24 13:37:56

Re: [SOLVED] Black screen after login

Board footer