We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Quack,
Running in verbose mode needrestart run the following command: iucode_tool -l -s 0x000106a5,0x1 -tb /lib/firmware/intel-ucode
iucode_tool -l -s 0x000106a5,0x1 -tb /lib/firmware/intel-ucode
This end-up failing:
microcode bundle 1: /lib/firmware/intel-ucode/0f-02-06 … microcode bundle 47: /lib/firmware/intel-ucode/06-0e-0c microcode bundle 48: /lib/firmware/intel-ucode/list iucode_tool: microcode bundle /lib/firmware/intel-ucode/list: unknown microcode format
and
Failed to check for processor microcode upgrades.
Similarly as what is done in #106 I tried using --ignore-broken and the result is much better:
--ignore-broken
microcode bundle 1: /lib/firmware/intel-ucode/0f-02-06 … microcode bundle 96: /lib/firmware/intel-ucode/0f-06-05 selected microcodes: 060/001: sig 0x000106a5, pf_mask 0x03, 2013-06-21, rev 0x0019, size 10240
The processor microcode seems to be up-to-date.
It is easy to add the option in /etc/default/intel-microcode but I wonder if this should not be the default mode of operation.
/etc/default/intel-microcode
\_o<
The text was updated successfully, but these errors were encountered:
eeda0a1
Thanks.
Sorry, something went wrong.
No branches or pull requests
Quack,
Running in verbose mode needrestart run the following command:
iucode_tool -l -s 0x000106a5,0x1 -tb /lib/firmware/intel-ucode
This end-up failing:
and
Similarly as what is done in #106 I tried using
--ignore-broken
and the result is much better:and
It is easy to add the option in
/etc/default/intel-microcode
but I wonder if this should not be the default mode of operation.\_o<
The text was updated successfully, but these errors were encountered: