https://bugs.kde.org/show_bug.cgi?id=496772
John Kizer <john.ki...@proton.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |UPSTREAM
--- Comment #5 from John Kizer <john.ki...@proton.me> ---
(In reply to redford from comment #4)
> Yup, the issue still reproduces after doing that. I didn't know that the
> firmware could change the profile preset I chose in the OS, I thought this
> is a feature of the OS, not the firmware? Is this actually an ACPI feature?
> If so, then I guess I need to contact Lenovo support...
Ah - yep, the catch there is the number of layers, starting from hardware,
through firmware and down to userspace software, that all have to work in sync
(the rest of that Arch Wiki article on CPU frequency scaling has a lot of good
links and info if you want to dig really deeply on it!). The visible interface
you see in a desktop environment like KDE (or Windows, for that matter) is the
very surface layer, but if that surface layer tries to pass along a command
that isn't functioning properly at a lower layer, it just won't work.
(In an analogous way, our family purchased a laptop once - ironically, also
Lenovo - on which the pre-configured Windows installation couldn't put the
laptop to sleep. We came to find out that the Windows equivalent of
power-profiles-daemon was calling for the firmware to use a sleep state that it
didn't outright reject, but couldn't successfully set, so the machine just
hard-froze - we had to do some work in the Windows Terminal to force it to only
attempt certain sleep states)
In this case, it might be helpful to check around with your device's model
number to see if there are any generally known power-state issues with the
device. You could also try booting from a live USB for another distribution,
like Ubuntu or Fedora, to see if they exhibit the same behavior - if not, then
it may be something that is funky in how your specific Arch setup has come
together, or in how power-profiles-daemon is interacting with it. Fedora 41
(which comes in a very well-maintained KDE Spin), for example, uses tuned
instead of power-profiles-daemon, which might produce different results.
Best of luck!
--
You are receiving this mail because:
You are watching all bug changes.
