-
Notifications
You must be signed in to change notification settings - Fork 116
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
incorrect CPU count #374
Comments
I just realized neowofetch is showing the number of threads per socket. so maybe that's intended? it's still confusing that all three show different numbers. |
I would say that both "96" and "4x 24" are accurate, but "4x 48" isn't... so maybe open an issue in the fastfetch repo instead? Also ping @CarterLi Yea it is kind of confusing |
It's expected to report You may paste the content of Better post this issue to fastfetch repo. |
here's the content of /proc/cpuinfo: cpuinfo.txt |
running on a server with 4x Intel Xeon E5-4657L v2 (12c24t each, 48c96t total):
original neofetch shows:
Intel Xeon E5-4657L v2 (96) @ 2.9GHz
fastfetch shows:
4 x Intel(R) Xeon(R) E5-4657L v2 (48) @ 2.90 GHz
hyfetch's neowofetch shows:
4x Intel Xeon E5-4657L v2 (24) @ 2.9GHz
I'm not sure if the intention is to show cores or threads, but in either case neowofetch is wrong.
The text was updated successfully, but these errors were encountered: