Some issues as of late

Which Linux distro are you using?
Fedora Plasma KDE 42

Which release version? 42 with all updates
(if rolling release without a release version, skip this question)

Which kernel are you using? 6.15.6-200.fc42.x86_64

Which BIOS version are you using? 3.03

Which Framework Laptop 13 model are you using?AMD Ryzen™ AI 370 Series

I have 2 main issues since 2-3 week or so. I have not done anything beside updating using the Discover.

  1. One is this window i get when i try to go to sleep and the laptop wakes up right after and then i see this. Why?
  2. And the other issue i can’t figure out is the sleep don’t usually work the first time. I select sleep from the menu or even tried from shell using systemctl suspend and laptop tries to go to sleep and after 3-4 second wakes up again. I have to click sleep 2-3 times before it actually goes to sleep. I have tried to figure out why but have not been able to pinpoint it.

For now i have disabled XHC1 XHC0 XHC3 XHC4 NHI0 NHI1 which seems to have helped. Maybe there is some other tweaks i could do?

$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP0 S4 *enabled pci:0000:00:01.1
SWUS S4 *disabled
GPP1 S4 *enabled pci:0000:00:01.2
SWUS S4 *enabled pci:0000:60:00.0
GPP3 S4 *enabled pci:0000:00:02.1
GPP5 S4 *enabled pci:0000:00:02.3
XHC1 S3 *enabled pci:0000:c1:00.4
XHC0 S3 *enabled pci:0000:c3:00.0
XHC3 S3 *enabled pci:0000:c3:00.3
XHC4 S3 *enabled pci:0000:c3:00.4
NHI0 S4 *enabled pci:0000:c3:00.5
NHI1 S4 *enabled pci:0000:c3:00.6

1 Like

Hey @Reza, this was an issue caused by QT6 version 6.9.1-2, which came in an update a couple of weeks ago. A temporary workaround was to revert QT6 to 6.9.1-1, but since then they released 6.9.1-3 which fixes the issue. So updating again should fix it (it did for me – I had the exact same problem).

Here’s more info: KDE Plasma users - beware of new qt6-qtwayland version 6.9.1-2 (breaks lockscreen, may cause app crashes) - Fedora Discussion

(don’t know about problem number 2)

1 Like

Issue 2: on archwiki I found this command:
dmidecode -t system | grep -P '\tWake-up Type\: ' Which could give you the source of the last wakeup (or not, might always be power switch… First check the output changes before making conclusions based on it.)

Check that there aren’t any systemd timers with the WakeSystem directive set that keep triggering (for instance because the triggered unit fails)

Another possibility is powerdevil, the KDE powermanagement daemon, which has the capability to set an RTC wakealarm, but I’ve never seen that feature in use…

2 Likes

Cool, thanks for the info and link.
I check my version and it just shows Qt version 6.9.1 so not sure if i’m on the right one. I updated every 1-2 day so hopefully its the latest. Will wait and see if it happens. Hopefully now :slight_smile:
Also did the sudo dnf upgrade --refresh

1 Like

yes shows Wake-up Type: Power Switch
Wakes it by clicking the keyboard on the laptop+ trackpad.

Although since i disabled XHC1 XHC0 XHC3 XHC4 NHI0 NHI1 it feels like its not doing the same problem. Need some more time to make sure :slight_smile:

Sorry i’m noob linux user so not sure what the other suggestions are really. I use chatgpt allot for changing settings hehe
So i figure you mean: systemctl list-timers --all

And these did not result in anything so maybe i’m good. But please do let me know if there’s other things to check.
grep -r WakeSystem= /etc/systemd/system /usr/lib/systemd/system
grep -r ‘WakeSystem=true’ /etc/systemd/system /usr/lib/systemd/system

Be careful, often it suggests crap.
I assumed you kind of knew what you were doing, disabling USB and Thunderbolt wakeup sources. (Don’t know what the rest is)
Although your cat output notes all those as enabled…

But that grep is essentially what I would’ve done.

Try using various other sources, like the RTC wakealarm and the lid open switch.
I tried a few, and on the ryzen AI it seems to always report Power Switch…

This sounds like possibly a misbehaving USB/thunderbolt device. Try disabling the XHC/NHC sources one by one, trying to isolate the device causing the wakeups.

Update: GPP{0,1} is the bridge to the NVME device. Advice above still stands: isolate the device, and continue from there.

Thanks for the head’s up. I don’t do the changes blindly and always write how to revert.
I know chatgpt and AI in general are not bulletproof :slight_smile:
And yes the cat was from before i changed :wink:

For now i have not had the same issue. I use the powerbutton to go to sleep and it don’t wake up. Have worked for some days now. When i have time as you say i could try each and see which one is the blame :smiley: for now everything works so me happy hehe

1 Like

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.