-
Notifications
You must be signed in to change notification settings - Fork 470
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] Incorrect report of CPU frequency on Windows. #800
Comments
Seems that SMBIOS reports some invalid data. Can you please try this program and upload its output? Note: The binary was compiled from https://github.com/KunYi/DumpSMBIOS. If not sure, you may compile it yourself. |
|
Big thanks for your kind help! But you don't need to do that. I have made a work around ( assume that @KunYi and I implemented SMBIOS detection code correctly ). Please test if the latest dev build work for you If you'd like to help more, you may try this command in native Linux and paste the output here ( live image should be enough, but not in WSL or a VM )
Example output for my laptop ( see
|
maybe check https://devblogs.microsoft.com/scripting/use-powershell-and-wmi-to-get-processor-information/ first and use script to check SMBIOS information first |
@KunYi WMI won't report max / boost CPU frequency in newer system (Win10 or newer), only base frequency.
There are only two known methods to acquire max CPU frequency without admin privileges: fetching SMBIOS data or using x86 instruction |
Yes, the SMBIOS (System Management BIOS) Table is filled by the BIOS code. So, if the BIOS provides an error related to the SMBIOS, the WMI (Windows Management Instrumentation) code merely reports the SMBIOS information to check the status reported by the BIOS. Perhaps you can ask the motherboard or computer vendor to fix these issues. The WMI is for vendors to identify and address duplication issues. |
No. Microsoft said WMI uses data from SMBIOS, but it doesnt. WMI reports everything as base freq (2700), while SMBIOS reports correct data (4700) in my laptop. |
okay, maybe to try RWEverything for check SMBIOS |
|
|
dmidecode output:
|
Thanks for your information. So that SMBIOS does report 8300 MHz Let's close this issue for now. If more people report the same issue, I will remove the method of SMBIOS detection code |
Note that the default information displayed by fastfetch was designed for linux and may not be useful for Windows. Fastfetch supports a lot more features than neofetch and winfetch. You can find information you interests in with |
General description of bug:
Fastfetch returns incorrect CPU frequency on Windows. No configuration used, installed from scoop, also happens on dev branch. The correct CPU frequency should be 3.5Ghz.
![image](https://private-user-images.githubusercontent.com/47502554/324145382-7debdb3f-acf1-4c9a-a768-915537bc6017.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MDkxMDEsIm5iZiI6MTczOTYwODgwMSwicGF0aCI6Ii80NzUwMjU1NC8zMjQxNDUzODItN2RlYmRiM2YtYWNmMS00YzlhLWE3NjgtOTE1NTM3YmM2MDE3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE1VDA4NDAwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQzY2QxZmFhMGVjZDUzZWVjOWQyZDZlMDZhNGU2MDgzODliNTI1NDcyYWNmYjEzNTEzODFhZWZhNDlmMTdjNDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.pLeu-ih9vS7D8AGyKJfP1Wy6KlQY3LJ-p-aoKCvkuYo)
Often helpful information:
Screenshot:
Output of
fastfetch -c ci.jsonc --format json
:Click to expand
Output of
fastfetch --list-features
:The text was updated successfully, but these errors were encountered: