Skip to content
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

differ if microcode can not be checked due to missing components or unsupported plattform (i.e. ARM) #220

Closed
Wiggum127 opened this issue Oct 6, 2021 · 4 comments · Fixed by #290
Labels

Comments

@Wiggum127
Copy link

I always get "Failed to check for processor microcode upgrades" at the end of every apt-get upgrade on my Raspbian (Debian Buster) on a RPI 2B. Currently running 5.10.63-v7+ armv7l.

Is there anything I can add to help find the root cause of this?

Thanks.

@mmitch
Copy link
Contributor

mmitch commented Nov 11, 2021

I'm no developer here, but just have looked over exactly that part of the code:

Microcode updates can currently only be detected for Intel and AMD cpus (see README.uCode.md).
The Raspberry 2B runs on a Broadcom ARM chip, which currently is not supported.

@liske liske added the question label Jan 27, 2022
@liske
Copy link
Owner

liske commented Jan 27, 2022

Yes there is no implementation for ARM.

@liske liske closed this as completed Jan 27, 2022
@Wiggum127
Copy link
Author

If that's the case, just tell the user there is no implementation for his CPU, instead of the misleading "Failed to check for processor microcode upgrades". This makes the user think he's done something wrong or there is a configuration error on his system/network. Just state "This CPU is not supported"

@liske liske reopened this Jan 28, 2022
@liske liske added wishlist and removed question labels Jan 28, 2022
@liske liske changed the title Failed to check for processor microcode upgrades on Raspbian (Buster) RPI 2B differ if microcode can not be checked due to missing components or unsupported plattform (i.e. ARM) Jan 28, 2022
@liske
Copy link
Owner

liske commented Jan 28, 2022

I'll keep this as a wishlist issue. The current implementation lacks the ability to differ why microcode checks are not possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants