-
Notifications
You must be signed in to change notification settings - Fork 479
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
[BUG] Reported processor speeds are incorrect on some machines. #815
Comments
SMBIOS sometimes reports incorrect max CPU freq, especially in some old platforms. Please try this: #800 (comment) |
Here are the processor values (in the same order as above), I also added comments for the speeds:
|
Can you try this ( assume Hyper-V / WSL2 is not enabled in your laptop ): Oops. Try this please: https://github.com/fastfetch-cli/fastfetch/actions/runs/8860844348/artifacts/1453449229 @Null-Ping @lostdusty Can you also test it? |
With new one (first is the CPU line from
Apparently the only change is 2.712 being rounded to 2.7 for i5-7300U? |
You didnt have WSL2 / virtual machine platform enabled right? |
According to https://stackoverflow.com/a/39620056, the method is only supported in Skylake (6th gen) and later. Its expected no change for old cpus What strange is 7700HQ |
The laptop with i7-7700HQ is not a VM (nor are the others), but I had virtualization enabled in its BIOS; after I disabled it, Fastfetch now shows:
So it now works correctly, but why does it depend on disabling virtualization in BIOS? |
Sure!
"frequency": {
"base": 1.2,
"max": 3.7,
"min": null
} Everything is correct, but I also had to disable virtualization like AcatXIo did, apparently my laptop had it on by default. "frequency": {
"base": 1.19,
"max": null,
"min": null
} |
Nope, sorry (I'll be away from my pc/home for about ~2 weeks, or maybe even more). But I have both virtualization and VT-x enabled. Also my processor is from the 7th gen, just like the i7-7700HQ. I guess virtualization features makes the smbios report the wrong frequency, even if it shows the right one in bios. |
I tested, and the SMBIOS for i7-7700HQ with virtualization off is still the same:
So the virtualization setting likely doesn't affect the SMBIOS data. |
You don't need to disable VT-x / AMD-v in BIOS, and it's recommanded to enable it to get better VM performance. You need to disable Virtual Machine Platform in Windows Features ( note WSL2 and WSA use that ) This feature has negative impact on performance. Microsoft suggests disabling it. |
I think this is the best result that fastfetch can get as for now. SMBIOS still seems ok for people uses WSL2 on newer CPUs ( like me ) so I want to keep it. |
General description of the bug:
I noticed that Fastfetch shows either the turbo or the regular processor speed depending on which machine I run it on; in one case, the reported speed was totally incorrect.
Tested machines (first 3 run Windows 11, and number 4 runs Windows 10):
Fastfetch should tell the user which processor speed it is showing: the regular one or the turbo, and the speed should be correct.
Often helpful information:
Screenshots:
The content of the configuration file you use (if any): Not used.
Outputs of
fastfetch -c ci.jsonc --format json
(I only included the processors; feel free to ask for the rest if needed.):Output of
fastfetch --list-features
(for all machines):The text was updated successfully, but these errors were encountered: