-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Improving MacOS M1 CPU/GPU prints #2038
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For what it's worth, this works for me! I see Apple M1 Max (10)
now.
(Although… for "GPU", I just see |
Hmm... Interesting, it works for me to highlight the core count. You should be able to run this simple command and see what your machine returns:
For me, this returns Once this (pretty heavy) command gets run the first time, it gets cached into |
Re-tested just now and this works great. Seems like the cache ought to be invalidated automatically in some cases (the neofetch script timestamp is greater than the cached value, so bugfixes actually take effect?) but I do in fact have 32 GPU cores: |
…1 CPU/GPU prints Upstream PR: dylanaraps/neofetch#2038 Thanks to @GustavoSilvera Co-authored-by: Gustavo Silvera <grs5382@gmail.com>
Thank you for your contribution! This PR is merged into hyfetch since this repo (dylanaraps/neofetch) seems no longer maintained. HyFetch is a fork of neofetch with LGBTQ pride flags, but the repo also maintains an updated version of the original neofetch, addressing many pull requests that are not merged in the original repo. Read the "Running Updated Original Neofetch" section for more info! |
Description
Adding better support for Apple Silicon (M1) CPU and GPU prints
OLD:
NEW:
This is accurate for me as I have the 10c CPU and 24c GPU model
Features
Issues
TODO