Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
selfhosting.couchsurfing
selfhosting.couchsurfing
@surfhosting@mastodon.pirateparty.be  ·  activity timestamp 3 weeks ago

okay, I found where past me got stumped last time with this box:

`echo 0 > /sys/devices/system/cpu/intel_pstate/no_turbo`

this fails when run as root in Debian 13, even with Secure Boot disabled, Kernel Lockdown disabled, etc.

in dmesg there's a message

intel_pstate: Turbo disabled by BIOS or unavailable on processor

this is because the #Dell BIOS is disabling turbo due to running on a "non-genuine" power adapter. I was able to work around this in Debian 12 but so far the same tricks aren't sufficient in Debian 13.

  • Copy link
  • Flag this post
  • Block
selfhosting.couchsurfing
selfhosting.couchsurfing
@surfhosting@mastodon.pirateparty.be replied  ·  activity timestamp 3 weeks ago

I finally got the CPU clock unlocked last night, it required setting `intel_pstate=disable` along with some other kernel params and a write to the MSR.

as best I can recall, disabling the intel_pstate driver wasn't required on Debian 12, some changes to the driver since then have prevented overwriting the no_turbo flag in certain cases even with root privileges.

I ran probably a couple dozen web searches related to this, and found some forum posts and kernel bug reports and mailing list posts which lead me to believe that this may in fact be a bug, and thus likely to be fixed in future kernels, but I can't wait around for that, so falling back to the old ACPI frequency scaling driver will have to suffice.

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1-alpha.40 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct