Hello everyone!
I recently installed EOS on a Lenovo V14 with an AMD Ryzen 5 7430 w/ AMD graphics.
Everything is going pretty well except for one thing. When I undock my laptop from my thunderbolt dock the on screen display completely locks up, and does not respond to keypress.
I generally have to hard reset to machine to get the display to respond again. I am able to drop to tty in these scenarios but it seems like Wayland or Mesa is not handling the change in screen resolution well.
When I boot the same machine into Windows it handles being disconnected without issue the expected behavior occurs (screen remains responsive after dock disconnect).
Any ideas on where I might want to look or perhaps something to enable?
Thanks!
Welcome to the forum 
In able to help you a bit better it would be nice if we have some more information about your system please post the output of
sudo inxi -SMCGDmsxx --za
Meanwhile have you tried an X11 session ?
1 Like
Welcome to the community @Tach86 
Are able to test with an X11 session to try and confirm if this is the case?
Edit: Just saw @keescase already asked about X11 
I blame the tiny screen on my phone.
Thanks for the greeting . I tested X11 and it handled the handoff without issue. here’s the output:
System:
Kernel: 6.14.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 83FG v: Lenovo V14 G4 ABP
serial: Chassis: type: 10 v: Lenovo V14 G4 ABP serial:
Mobo: LENOVO model: LNVNB161216 v: SDK0T76530WIN serial:
part-nu: LENOVO_MT_83FG_BU_idea_FM_V14 G4 ABP UEFI: LENOVO v: MSCN20WW
date: 01/09/2025
Memory:
System RAM: total: 16 GiB available: 13.48 GiB used: 3.93 GiB (29.2%)
Array-1: capacity: 16 GiB note: est. slots: 2 modules: 2 EC: None
max-module-size: 8 GiB note: est.
Device-1: Channel-A DIMM 0 type: DDR4 size: 8 GiB speed: 2667 MT/s
volts: 1.2 manufacturer: Samsung part-no: M471A1K43DB1-CTD
Device-2: Channel-B DIMM 0 type: DDR4 size: 8 GiB speed: spec: 3200 MT/s
actual: 2667 MT/s volts: 1.2 manufacturer: Micron Technology
part-no: MT40A1G16TB-062E:F
CPU:
Info: 6-core model: AMD Ryzen 5 7430U with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
Speed (MHz): avg: 3207 min/max: 400/4390 boost: enabled cores: 1: 3207
2: 3207 3: 3207 4: 3207 5: 3207 6: 3207 7: 3207 8: 3207 9: 3207 10: 3207
11: 3207 12: 3207 bogomips: 55095
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Barcelo vendor: Lenovo
driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports:
active: DP-2 off: eDP-1 empty: DP-1, DP-3, DP-4, HDMI-A-1 bus-ID: 04:00.0
chip-ID: 1002:15e7 temp: 45.0 C
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-3:3 chip-ID: 5986:2160
Display: unspecified server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96
Monitor-1: DP-2 res: 2560x1440 hz: 144 dpi: 93 diag: 801mm (31.54")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
gbm: drv: radeonsi surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
renoir ACO DRM 3.61 6.14.1-arch1-1) device-ID: 1002:15e7
API: Vulkan v: 1.4.309 surfaces: xcb,xlib device: 0 type: integrated-gpu
driver: N/A device-ID: 1002:15e7
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Drives:
Local Storage: total: 2.07 TiB used: 963.08 GiB (45.3%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD Blue SN580 1TB
size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 36.9 C
ID-2: /dev/sda vendor: TeamGroup model: T-FORCE 1TB size: 953.87 GiB
speed: 6.0 Gb/s serial:
ID-3: /dev/sdb vendor: Western Digital model: WD PC SN740
SDDPMQD-256G-1101 size: 238.47 GiB type: USB rev: 3.2 spd: 5 Gb/s lanes: 1
serial:
Sensors:
System Temperatures: cpu: 69.1 C mobo: N/A gpu: amdgpu temp: 45.0 C
Fan Speeds (rpm): N/A
One option is to stick with X11, for now. Generally speaking, there are still things Wayland is ironing out.
But, if you’d like to persist and try to get Wayland behaving, some more details might help guide us. I have some ideas, but they’re largely a shot in the dark at the moment, so maybe we’ll try to gather details.
What might help is log data, collected specifically after the issue has occurred. Both of the below commands will generate a link (eos-sendlog) you can then share here, so we can look at the output.
If the issue occurs, and you’re able to access the terminal without needing to reset (not a hard lock), run this to retrieve the log from the current session:
journalctl -k -b -0 | eos-sendlog
If you have to restart to recover, this will retrieve the log from the previous session:
journalctl -b -1 | eos-sendlog
Here today to report that the issue seemingly resolved itself after kernel update. No special actions were taken beyond running yay
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.