You are not logged in.
LTS still has this issue.
It's like an update I did some time last week switched a hidden persistent bit on the BIOS, which I can't switch back on the BIOS because interface is childish.
To solve the problem, I have to make changes on what the CPU capabilities are before GRUB loads. That's how screwed up this problem is. This is NOT a solution. It's not even a patch. It's a pathetic hack.
@AidanDaOne, if your BIOS is also an overly simplistic one, I think we need a third person to confirm the same issue with mighty laptop i9's with a similar pathetic BIOS and we have confirmation on the combination of things that's causing this.
I've reached a point where I have to try and write my own BIOS using Coreboot. I don't know if I want to do that. You'd imagine somebody somewhere still believes in service, nowadays, and would actually help with this problem. I guess when AI arrived on the scene, people checked out completely, except for people in communities, such as this.
Anyway, I firmly believe that this is an issue with the BIOS that was somehow affected by an update, or just enough time with a buggy BIOS that just made some switches on its own behind the scenes. But, when the kernel reports that the CPU has no turbo because the BIOS turned it off, or the CPU doesn't support it, and you can't access pstate switches in sysfs no matter what, then there's an issue with the way your system is talking to your OS.
Offline
After weeks of trying all manner of things, my solution to the problem was to disable intel_pstate altogether. It turns out that on this line of CPUs, bu my estimation, it's geared far more towards Windows gaming, than serious workstation demands from a driver point of view. The problem is with the interaction between the BIOS, which is locked, and the intel_pstate driver in its current versions in kernels 6.14.6 onward (6.14.9, as of writing this post). I dissected the driver in the kernel, trying to find ways to patch it. The patch that worked was tantamount to disabling the pstate driver entirely.
Putting the driver into passive mode in kernel, as I used to, is now - for this CPU - completely useless. Passive mode doesn't not turn off HWP, as it once used to. And in the confusion, turbo is turned off by default. Those were on the good days. On the bad ones since this started, turbo isn't reported as being available at all.
Originally, the solution was to writing a DSDT that would inject itself after BIOS and before GRUB through UEFI. Which, in essence, makes the rEFInd bootloader more suited as the system bootloader and I'm not cool with that for my setup and needs. Besides, it's just waaaaay to much hacking before getting off the ground, for my taste.
So, the most practical things to do was to disable intel_pstate with the kernel parameter:
intel_pstate=disableAnd then write a bunch of new profiles for tuned, which is what I use for CPU frequency scaling management, but cpupower will do just as well, depending on your needs.
I've found that with realtime profiles, I can get each core going at max, which for the high-power cores is a whopping 5.6GHz, and the efficiency cores are 4.1GHz. With a modified throughput-performance profile, I can get very nice speed scaling on the mid 3.6GHz side, jumping to 5.6GHz range on a moment's notice. You can turn boost on, but turbo is useless, as it's a pstate driver exclusive switch. The other cool thing about this solution is, with the acpi_cpufreq driver that the CPU defaults to with pstate off, you have access to the schedutil governor. On profiles that you create in order to save power on low-demand operations, the latency between frequency jumps is much quicker then with the ondemand governor. Very handy for more workstation-oriented computing.
I have an open bug report at Intel on this, as well as a thread on one of their support forums, but I'm guessing that this will be a fix that will come way later than I'm willing to wait.
I hope this helps anyone else who is suffering from this very weird problem from a driver that works near-flawlessly on other machines I'm aware of. I'm marking this as SOLVED.
Offline
Hi, I think I had tried that already and it did not solve the issue for me. Had to switch over to windows 11 for now which fixed the problem as I can barely run 3 VMs at once with an i7 ?
Offline