Scroll to installation guides.
I did notice that your ppa was in the guide today after I just installed it and it seemed familiar.
IDK if installing/uninstalling cpufreq messed it up or why my adaptive backlight management never worked with that (maybe I never actually installed it and only installed the OEM kernel from the guide…)
But now it seems to be working and for video playback, I’m getting 6.5w on 43% brightness instead of 6.5w on 10% brightness.
Are those good numbers ? Because I don’t think everything is in that guide, I noticed you talking about powertop auto managment or something and other things that I didn’t find in there…
For the matter of suspend, I can confirm that suspend has been working fine on 6.8 kernels as well. Currently on 6.8.2-300.fc40.x86_64
myself.
With a web browser and code editor open and nothing compiling, it looks like I’m sitting pretty much at 10w according to powertop, with --auto-tune
already run previously. Any suggestions for reducing? I’m on Fedora Gnome.
- Turn off fractional scaling if you’ve got it turned on. @Charlie_6 found that increased power consumption by ~40%.
- Double check the slots you have all your cards match Framework documentation (particularly USB-A cards).
Can you link to more reading on the fractional scaling power consumption? I just did a test on my own system and could not reproduce any meaningful difference in consumption between 1.0 and 1.5 scaling in Sway on Fedora 39.
Is this compositor independent? I.e. does it matter if I use Plasma, Gnome or Sway?
Yes, gnome uses mutter, kde uses plasma etc.
Which one is better at 150% zoom? Mutter or plasma?
Measure it and see. I have no idea.
Uh, sure, that was what I was aiming at.
My question was if the increase in power draw was independent of the compositor, in which case the generalisation would fit, or if it differs between compositors and we need to measure.
It will differ from compositor to compositor quite significantly I would imagine. Wayland compositors are basically like the X11 Server, bit of the Client and the Window Manager all wrapped up into one. How they implement things differs significantly. Weston is the reference wayland compositor ; wlroots is a minimalist implementation (of which sway makes use of ) and kwin_plasma differs significantly to gnomes mutter. Things like the X11 bridge in kwin_wayland are matched with the compositor vs mutter which traditionally has called a helper. Especially for legacy X11 apps - this bridge service is going to be likely the source of a lot potential optimization or not. kwin_waylands much better at dealing with it than mutter, although mutter is catching up.
FYI folks PPD 0.21 was just released.
This release should help with battery life on F13 and F16 AMD by more efficient tuning in battery mode.
Ping your distros to pull it in and try it out.
Seems it now automatically switches profiles on battery/mains use. More info in Phoronix too:
I got even lower battery wattage using TLP this time
-
Main: AMD 7840U - 61Wh battery
SSD: SK Hynix Platinum P41 2TB
RAM: Framework DDR5-5600 - 1 X 32GB(likely badge engineered ADATA DDR5-5600 SO-DIMM)
Expansion cards: 2 X USB-C, 2 X USB-A -
OS: Arch Linux 6.8.4
DE: LXQt 1.4.0
Power management: TLP 1.6.1 -
0% brightness, no keyboard backlight
Wifi connected, bluetooth off.
As there seems to be a lot to sort through here, we recommending to just use powertop --auto-tune
for now?
powertop --auto-tune
is a big hammer that has potentially negative implications especifically for USB devices. I’ve personally observed on F16 this makes the USB keyboard feel “laggy” when it goes into auto suspend.
Using PPD 0.21 on balanced you should get a very good experience.
Interesting, I haven’t had that issue on the 7840U FW13 running Fedora 40 gnome. I’ll keep that in mind, though.
Is it recommended to just use the in-distro PPD for that then?
Yes F40 has PPD 0.21 already.
If you see other MEASURABLE improvements from powertop --auto-tune
I would like to know.
It’s important to work out individual knobs that make a difference, not just ones that say they’re in a “bad” state to start.
I haven’t done any measurements myself for now, but I will keep that in mind, thank you.