-
Notifications
You must be signed in to change notification settings - Fork 52
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
Display aarch64 CPU info #293
Comments
I'm surprised to see such an edge case. I suspect this issue is due to manufacturer negligence. I wonder what else |
similar issue was resolved in FastFetch here: |
I don't think this is a good solution. There are many instances where we shell out to some command-line tool, but I'd like to see that number decrease, not the other way around. If you have the free time to study the other workarounds that |
if lscpu implementation is discussed but no code is shown here - https://www.cnx-software.com/2018/02/14/human-readable-decoding-of-proc-cpuinfo-for-arm-processors/ original lscpu implementer (sic) discussion - https://suihkulokki.blogspot.com/2018/02/making-sense-of-proccpuinfo-on-arm.html A totally different implementation is found here - https://github.com/chemag/cpuinfo/tree/master the table for which is here - https://github.com/chemag/cpuinfo/blob/master/cpuid.database.pbtxt |
The aarch64 CPU cannot be queried with
/proc/cpuinfo
as the CPU name is not in there. Version6.1.8
is not getting the CPU name correctly on my host.You can see there is a space pushing the core count (2) out.
lscpu has more info:
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
macchina --doctor
outputAdd a screenshot or copy and paste the output of
--doctor
if an element you're supposed to be seeing isn't showing up.System Information
You don't have to provide this information if you're not comfortable doing so, but it'll help us solve the issue a lot faster.
The text was updated successfully, but these errors were encountered: