I’ve had EndeavourOS installed on my AMD Framework 13 for about 3 months at this point, and while this issue has cropped up during that time, I never thought to make a post about it. So, here I am.
The issue I’m running into is that sometimes my desktop environment KDE (wayland) will, upon resuming from either suspend to RAM or hibernation, displays a blank white screen. My cursor is still visible, and I can interact with my system, but I can’t see what I’m doing. I’ve been able to make several journalctl logs when it happens, but most of them were made before the update to Plasma 6. However, even with the update, the issue still happens. I’ve tried switching to the LTS Linux kernel and the zen kernel, but the issue still happens. This makes me think it might be more of an issue with Framework firmware, as I saw a few posts on the Framework forums describing a similar issue. I am on the latest firmware for FW 13, v3.03 I believe.
Here is a pastebin of a log I took yesterday after encountering the issue after resuming from hibernation:
I had a similar issue, I do not know the root cause but switching to X11 from Wayland on KDE fixed it for me. My main monitor would go white after hibernate/sleep.
Just realized there was an update to the Framework firmware, the current version is now v3.05. I’ll update when I have the time and report back with results. However, since my last system update about 3 days ago the issue hasn’t come up again, but I also disabled scatter gather in my kernel parameters. That might have something to do with it, not entirely sure. I did switch to X11 and that fixed the issue, but I am not keen on using X11. I recently started using the foot terminal emulator which only works on Wayland.
Another issue I’ve noticed though is that there are some strange graphical artifacts that show up on the very bottom of my screen, they can’t be more than one or two pixels tall. To get rid of them I have to switch between virtual desktops, and they go away for a little bit then show up again a little later. Little annoying, but not as big an inconvenience as the issue I originally posted. I don’t know what exactly in logs would help diagnose the problem.
Yes, but I didn’t have to do any special configuring, they Just Worked™ out of the box on Wayland so sadly not much I can offer to help them out.
EDIT: I remember setting a kernel parameter to get hibernation to work correctly on my AMD Framework. Might be a stretch, but it has ‘acpi’ in the name so it can’t hurt to try it:
rtc_cmos.use_acpi_alarm=1
This disables the ACPI alarm so that the laptop can properly suspend-then-hibernate, which is the method I use when closing the lid.