I have a FW laptop 13 AMD running Fedora Workstation Linux 41 (KDE, Wayland). I just did a system update, which apparently upped the kernel from 6.12.9 to 6.12.11. Now, after booting and successfully logging in, the laptop screen goes black after a few seconds. The external display (HDMI) remains fully functional. Sleeping/waking and fiddling with display controls doesn’t help. I can reboot into the previous kernel (6.12.9) by pressing esc during boot and selecting the previous kernel from the grub menu and the displays work as expected, but fingerprint unlock is not available after display sleep. I did see there was a UEFI update after I did the system update, but installing it did not help. Disconnecting the external monitor doesn’t improve things.
Edit: the rest of my post got cut off ?! Basically, does anyone have thoughts about what to try next?
Could be KDE-specific somehow, ran 6.12.11 on F41 workstation GNOME Wayland here on a FW13 7840U without issues (internal screen plus external via TB dock).
In case this is fixed in the kernel, 6.12.13 is now on testing (seems to be running fine here too) so you could try it before it hits stable:
sudo dnf --refresh --enablerepo updates-testing up kernel*
Also, FWIW, 6.13.x is probably going to reach stable later this week.
Edit: Maybe important: I have the older (matte 2256x1504) internal display.
Thanks. It was a good idea but no joy 
.
I forgot about the display now being a variable. I also have the old display. I’ll switch to Gnome and see if that makes a difference.
Edit 20250210@14:46: Tried using Gnome and it seemed to work fine. Certainly ran for far longer than I ever got with KDE/Plasma. When I did a restart, though, the main screen went dark and the external continued to display, but things seemed crashed. So I’m not sure I’d call it “success,” but Gnome certainly worked better than Plasma.
Any obvious (ish) journal entries, especially from amdgpu, when this happens? Anything interesting in terms of workload (maybe exposing a graphics driver bug)?
I had a couple of applications set to autostart, so I removed them and still have the same problem. I don’t think there are any workload issues, as it’s pretty much a plain vanilla start and the screen loss occurs seconds after login. No journal entries referencing amdgpu around the failure except
Feb 10 17:49:15 framis.sacdoc.org gnome-shell[2145]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
I don’t have a lot of experience with desktop environments, but nothing jumps out at me from the journal at the time that the screen dies.
Thanks for the ideas. I’m still probing.
While testing, the problem occurred once while I was still entering my password, so before I actually got to the login process.
Some log entries that I didn’t expect but don’t understand:
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: unknown error 0
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: unknown error 256
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: unknown error 256
Feb 10 18:06:18 framis.sacdoc.org kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
The problem persists with the latest kernel 6.12.15-200.fc41.x86_64 (64-bit). I tried disabling powerdevil for the display (as it seems the display is just turned off; everything else works fine and the display comes back, at least briefly, after a sleep/wake cycle). As this is a fairly vanilla Fedora with KDE (installed 39 then updated to 40 and 41), I’m surprised I don’t see other reports of it.
If anyone reading this is successfully running Fedora 41 with KDE/Plasma on a FW-13 Ryzen and a kernel > 6.12.9, let me know because I think the next step is then a system re-install.
addendum 20250223@20:40
Turning the display off with kscreen-doctor --dpms off and back on again (with a keypress or kscreen-doctor --dpms on) will bring the black display back, at least for a while (seconds to minutes) so it seems to definitely be a power management problem.