Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu 22.04.3 x64 Kernel 6.5.0-14-generic Causes Missing Frequency and Turbo Options #225

Open
Munk3y opened this issue Jan 10, 2024 · 3 comments

Comments

@Munk3y
Copy link

Munk3y commented Jan 10, 2024

After installing the latest updates today for Ubuntu 22.04, I was upgraded to Kernel 6.5. When booting, CPUFreq starts up and seemingly operates like normal but with missing Min/Max Frequency and Turbo options. I took a look for any errors using Gnome Looking Glass but there don't appear to be any. Unfortunately, I'm not fully familiar how to troubleshoot this issue but I'm happy to help, if someone can point me in the right direction. Any thoughts?

OS: Ubuntu 22.04.3 x64
Kernel: Linux Monkey 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

CPUFreq

@Munk3y
Copy link
Author

Munk3y commented Jan 10, 2024

Ok, so I've done a large amount of reading and it looks like kernel 6.5 comes with the new amd-pstate-epp driver enabled by default. CPUFreq uses cpufreqctl to interface with the system, which no longer works, since the old acpi-cpufreq driver is no longer in use. I can only guess that parts of CPUFreq will need to be re-written to interface with the amd-pstate-epp driver at some point. In the meantime, you can revert to the old acpi-cpufreq driver in Ubuntu 22.04.3 by following these instructions:

$ sudo nano /etc/default/grub

  • Change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  • To this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_pstate=disable"
  • Ctrl+O to Save, Ctrl+X to Exit

$ sudo update-grub
$ sudo reboot

NOTE: I do not know the repercussions of reverting this driver. There may be performance or power differences that I'm unaware of.

@Munk3y
Copy link
Author

Munk3y commented Jan 10, 2024

After following the instructions above, CPUFreq appears to be back to normal.

CPUFreq-Fixed

@peter-lyons-kehl
Copy link

peter-lyons-kehl commented Jan 12, 2024

(Please ignore any email from the comment that I've removed. It applied to cpupower-gui app, but not necessarily to cpufreq.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants