cpupower VS extension-manager

Okay, after much tinkering around, I managed to find a tool that does exactly what I needed it to with literally no extra tinkering, which I found here: https://github.com/deinstapel/cpupower but to be honest it just raised more questions. If I leave the CPU on boost mode in the bios, it gives me pretty much full range of minimum clock speed and maximum clock speed (Except minimum can only go as low as 16% for some reason, which is odd, but I'm sure there's a reason for that somewhere.) But here's where it gets weird. If I leave the maximum at 100%, it seems the lower I put the minimum allowed clock speed, the more likely audio issues are to occur. (Mind you, all these tests were done with the maximum allowed speed set to 100%) For instance, in my limited testing I did, if I leave the minimum at 16%, audio issues happen INCREDIBLY quickly, but if I raise the minimum to 50%, no REAL audio issues seem to occur except maybe a pop every once in a while. I really would like to know the cause of this.

- changing minimum frequency to 100% using CPU Power Manager

You can check cpupower

thanks. i wonder if this extension uses that system.

If you install this extension and limit your cpu, you might.

To get some more detailed control, at some point I installed a gnome gui applet called CPU Power Manager. I set it to high performance mode here, and enable turbo.

On top of the GNOME power profiles, I use the CPU power extension (https://github.com/deinstapel/cpupower)

Whoops, sorry, I’m half asleep and posted the outdated extensions link. I’ve updated the link to point to their GitHub which also lists installation instructions — there’s a Fedora copr available to install the extension and it’s fully compatible with GNOME 42 too (I’ve been using it on both Fedora 35 and now 36, it’s working great :)). Sorry for posting the wrong link just before!

Take a look at CPU Power Manager but keep in mind that you will never reach the energy efficiency of Windows.

Extension Manager [0] allows for installing Gnome extensions through an libadwaita app.

This replaces the Gnome Extensions app and the browser extension.

[0]: https://github.com/mjakeman/extension-manager

If I remember correctly you need gnome-shell-extensions for the auto update to work in extension manager. https://github.com/mjakeman/extension-manager

You can use https://github.com/mjakeman/extension-manager to check whether your extensions have support for a particular gnome version from the upgrade assistant.

FWIW, the GNOME Extensions addon broke on Firefox 110.1 (installed natively) on Arch Linux for me too at least a week ago. I've tried troubleshooting why, but came up with little. I've concluded it's just dead for some reason, on my system at least. I have since uninstalled it and have been using Extension Manager instead to manage my shell extensions for the time being. No complaints here.

My suggestion would be to start using https://github.com/mjakeman/extension-manager instead. I think it's much better than the browser-based way of installing them.

Bonus tip: Extension Manager is an app to manage your extensions.

https://github.com/mjakeman/extension-manager can show you a list of compatible extensions before you upgrade, and it also allows you to search and install extensions without the browser extension.

Finally, you might want to check out the Extension Manager app, this makes managing extension easier in my opinion.