-
Notifications
You must be signed in to change notification settings - Fork 67
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
"Failed to check for processor microcode upgrades" on Arch Linux #106
Comments
This is only for the kernel image check (which seems to work for you), so this is not a problem. needrestart relies on the output of Since not all microcode patches are applicable for all processor types or hw revisions the microcode field in |
Update: you might need to add
|
Plainly running
Which seems to be the same output as the command from the wiki. (This .img file is not built on my machine as part of an initrd generation process, but just extracted from the repo package - you might want to download it for code testing.) |
I've changed the lib/iucode-scan-versions wrapper to handle Arch's early boot initrd file. Could you please give it a try? |
I modified the PKGBUILD to build the current git revision, which right now is 3281733.
After one more reboot, the journal and
|
The microcode detection using But theres is another (severe) issue: Needrestart currently uses the signature value to detect a difference between running and available microcode revisions which is wrong. I've opened #108 for this new issue. |
Could you give |
ee6042a seems to work now. I downgraded the microcode on disk without rebooting yet, and it detects the change:
|
I'm using needrestart on an Arch machine, packaged using this PKGBUILD (bash, essentially
. ./PKGBUILD && prepare && build && package
). Especially with how frequent updates roll out on Arch, this is a really handy tool to have so I do not need to reboot the whole machine twice a day. ;)Since the update to v3.0 however I'm getting the error message
every time I run the command from the shell (among the usual expected messages), and an "UNKNOWN" status for the Nagios plugin mode with the following line:
Full log file of
sudo LC_ALL=C needrestart -rl -v
Line 17 says
[Kernel/Linux] Got garbage from linux image header (/boot/intel-ucode.img)
- I suspect that this is what it's ultimately choking on.On Arch, Intel microcode updates reside inside
/boot/intel-ucode.img
, which actually is an initrd image which must be prepended to the "regular" one by e.g.Some bootloaders allow to simply list multiple initrd images, like systemd-boot (which I use) - my bootloader entry file is as follows:
Paths in lines 2-4 are relative to the EFI system partition, which is mounted during runtime at
/boot
.The official method to check for new microcode, according to the Arch wiki, is comparing
/proc/cpuinfo
to the output ofexample output from my machine:
grep microcode /proc/cpuinfo
gives me 8x the lineThe text was updated successfully, but these errors were encountered: