I have Arch Linux installed rolling with current kernel version 6.18.7-arch1-1 on AMD Ryzen AI 300 Framework 16 laptop. The BIOS is 03.04 and the output of journalctl -b can be seen at this link journalctl -b output
Objective would be fore KDE Plasma SDDM install that supports Wayland and X11 session login. As of now either session freezes immediately after login. Dropping to terminal ALT+Fn does not work thus I appear to need a hard reboot. I do get the SDDM login screen on boot and can drop to terminal as long as I do it before attempting to login.
I did switch themes from Breeze and I did add the amd/nvidia kernel arguments. It was working at one point. Appears to have broke either from pacman -Syu update or from installing the xsession support for SDDM. Have not yet pinned it down.
When closing the laptop lid and allowing it to suspend/sleep and then opening it back the login screen almost lets me in again but then freezes.
I started a post about this yesterday with the same problem, happened after an update a couple days ago and during the troubleshooting I even tried removing the GPU and going with just the iGPU and that didn’t help. I reinstalled arch on a different SSD and it experiences the same bug of freezing shortly after you login. I don’t have my dGPU in right now cause I’ve been troubleshooting, but suspending the laptop and resuming seems to fix it if you’re running on the iGPU, it lets you log back into your session and seems fine after that.
Edit: Can confirm if you have the Nvidia dGPU installed the resuming from sleep still causes it to freeze a couple seconds after it starts drawing to the display on SDDM. Guess we are stuck waiting for a fix. But I haven’t a clue which package update broke it.
Edit2: Someone suggested adding POWERDEVIL_NO_DDCUTIL=1 to the /etc/environment file and it seems to have resolved the issue for me freezing with the dGPU in and the sleep then wake fixing it like on the iGPU, also doesn’t freeze shortly after login.
Thanks @turbo5546 - for experimental reasons I just installed from arch ground zero but installed gdm/gnome instead. Working flawlessly for the last few hours so far. I will give the POWERDEVIL_NO_DDCUTIL=1 a go if I end up back in KDE/Plasma.
Thanks @ava1ar I will check it out. I will add that parameter and reinstall KDE/Plasma. I am now wondering why GDB/Gnome works since these are kernel parameters and hardware related compared to environment/Wayland/X11 related i.e. theoretically switching from KDE/Plasma to GDB/Gnome should yielded equivalent behavior I suppose.
New Frame.Work user here, also recent convert to Arch KDE. I have the AMD GPU and had the same symptoms, freezing right after login. Determined to be graphical issue because I could still Ctrl+Alt+F3, and despite frozen screen do a blind login and sudo reboot. Was trying to trouble shoot vulkan because I couldn’t get a desktop without nomodeset. Can confirm, not only does the ddcutil fix work, vulkan works as expected.
Can confirm this issue too on my Framework 16 Laptop on Arch Linux.
Logging in through the graphical interface did not work anymore with X11 and Wayland.
So I simply accessed my user through TTY and downgraded (AUR (en) - downgrade love this tool btw.) the package to the earlier release 2.2.3-1.
this issue also affects the 7040 series Framework 16 laptops.
Encountered inability to boot KDE this morning,
Adding nomodeset to kernel parameters allowed me to get into the system at the cost of disabling all GPU acceleration. (press e on the boot menu for systemd-boot or grub to edit the entry temproarily to add the option)
Downgrading ddcutil from 2.2.5 to 2.2.3 and rebooting with default boot options restored functionality. and it looks like the ddcutil team is aware of the issue so hopefully they’ll get it fixed real soon.
They pushed out an update for ddcutil for arch a few hours ago. 2.2.5-2 which has a fix for the screen freezing issue, and I went ahead and commented out the environment variable and rebooted with this fix and it works for me.
@turbo5546 I uninstalled gdm/gnome and reinstalled plasma/kde (core only) and the freezes are gone. Thanks for the notice on the ddcutil update. I still have a blind SDDM issue but I can log in and use KDE/plasma. I did change the theme. Shooting for Wayland and Xsession login optoins but your help is a leap forward. Much appreciated.
For the SDDM issue you might try this, I can’t confirm if this 100% fixed the issue for me or if something else I did while troubleshooting the freezing issue fixed it. I had SDDM mostly working normally with occasional blank screens before and since this I haven’t had an issue with a blank SDDM screen yet.
@turbo5546 I can confirm this works. I am amazed how you can track or keep up with all these changes. I really appreciate your contributions. It works and creates different problems for me. I am also running the Nvidia GPU in my setup. If I apply the fix I get a SDDM login screen but then my applications that depend on the Nvidia GPU break. I am running Isaac ROS which is married to the Nvidia GPU. So I guess I have to figure out how to manage or switch between the two.
Edit: Found this which also seems to help bring up the SDDM login screen but still seems to ditch the Nvidia. Looks like you were already on that issue too.
Well I think I have the nvidia-prime tool installed on mine so if the application isn’t aware of more than one gpu, you can launch it with prime-run to get it to run on the nvidia dGPU. I’m sure there are other work arounds, this is just the one I found while I’m trying to figure this whole linux thing out.
Looking at the fedora packages and it looks like none of the supported fedora versions have version 2.2.3
So it’s unlikely that you’re experiencing the package issue, unless i’m missing something.
either way you should be able to use that link to find a valid package to downgrade ddcutil to which would presumably resolve the issue until the newest version lands in stable.
