my current system config can be found on gitlab
→ https://gitlab.com/zzkt/guix/-/blob/endless/config/framework13-system.org
I went for the overkill option and am using (firmware (list linux-firmware)) too. Later I want to just limit it to the firmware the Framework needs, but figuring out which ones those are is very low priority for me right now.
As for kernel arguments, nothing special, just this one I saw on Arch Wiki about setting the wireless regulatory domain:
(kernel-arguments
(append
(list
"cfg80211.ieee80211_regdom=US")
%default-kernel-arguments))
To be honest, I hadn’t even noticed that the Framework has a keyboard backlight until now, but it seems to be working for me without your kernel option.
I just upgraded to nonguix linux-6.7 (currently based on linux-libre-6.7.2) with the most recent linux-firmware and it looks like everything is working fine without any extra config options.
so the kernel options might be needed for earlier kernels but appear unnecessary now.
1 Like
It looks like this is caused by shepherd waiting indefinitely for a mt7921e kernel thread to end. It’s not very elegant, but you can shutdown or reboot with rmmod mt7921e && shutdown or some variation of that.
I just got my Framework 13 AMD and wrote up how I got Guix working, but it seems that as a new user I can’t post more than two links 
Anyway I posted it on my blog instead: guix on the framework 13 amd — wingolog
2 Likes
I’m not sure which of the two actually fixed it, but shutdown actions work for me now on kernel version 6.8.6 and a Guix pulled/reconfigured today.