| from small one page howto to huge articles all in one place
Last additions:
May, 25th 2007:
April, 26th 2007:
Apr, 10th. 2007:
| 
. 
Details of sys-firmware/intel-microcode:
Description: Intel IA32/IA64 microcode update data
Homepage: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files https://github.com/platomav/CPUMicrocodes http://inertiawar.com/microcode/
available versions:
| releases | alpha | amd64 | arm | hppa | ia64 | mips | ppc | ppc64 | ppc macos | s390 | sh | sparc | x86 | USE-Flags | dependencies | ebuild warnings |
|---|
| intel-microcode-20250812_p20250813 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | dist-kernel
hostonly
+initramfs
+split-ucode
vanilla
| show | MICROCODE_BLACKLIST is set to \
Package was created using advanced options:
MICROCODE_SIGNATURES is set to \
Looks like iucode_tool was unable to detect any processor!
WARNING:
No ucode was installed! Because you have created this package
using MICROCODE_SIGNATURES variable please double check if you
have an invalid select.
It's rare but it is also possible that just no ucode update
is available for your processor(s). In this case it is safe
to ignore this warning.
No ucode was installed! It's rare but it is also possible
that just no ucode update is available for your processor(s).
In this case it is safe to ignore this warning.
Unset \
${P} contains microcode updates which require
additional kernel patches which aren't yet included in kernel <4.14.34.
Loading such a microcode through kernel interface from an unpatched kernel
can crash your system!
Those microcodes are blacklisted per default. However, if you have altered
MICROCODE_BLACKLIST or MICROCODE_SIGNATURES, you maybe have unintentionally
re-enabled those microcodes...!
Check \
requires additional kernel patches or not.
| | intel-microcode-20250512_p20250513 |
- | + | - | - | - | - | - | - | - | - | - | - | + | dist-kernel
hostonly
+initramfs
+split-ucode
vanilla
| show | MICROCODE_BLACKLIST is set to \
Package was created using advanced options:
MICROCODE_SIGNATURES is set to \
Looks like iucode_tool was unable to detect any processor!
WARNING:
No ucode was installed! Because you have created this package
using MICROCODE_SIGNATURES variable please double check if you
have an invalid select.
It's rare but it is also possible that just no ucode update
is available for your processor(s). In this case it is safe
to ignore this warning.
No ucode was installed! It's rare but it is also possible
that just no ucode update is available for your processor(s).
In this case it is safe to ignore this warning.
Unset \
${P} contains microcode updates which require
additional kernel patches which aren't yet included in kernel <4.14.34.
Loading such a microcode through kernel interface from an unpatched kernel
can crash your system!
Those microcodes are blacklisted per default. However, if you have altered
MICROCODE_BLACKLIST or MICROCODE_SIGNATURES, you maybe have unintentionally
re-enabled those microcodes...!
Check \
requires additional kernel patches or not.
| | intel-microcode-20250211_p20250211 |
- | + | - | - | - | - | - | - | - | - | - | - | + | dist-kernel
hostonly
+initramfs
+split-ucode
vanilla
| show | MICROCODE_BLACKLIST is set to \
Package was created using advanced options:
MICROCODE_SIGNATURES is set to \
Looks like iucode_tool was unable to detect any processor!
WARNING:
No ucode was installed! Because you have created this package
using MICROCODE_SIGNATURES variable please double check if you
have an invalid select.
It's rare but it is also possible that just no ucode update
is available for your processor(s). In this case it is safe
to ignore this warning.
No ucode was installed! It's rare but it is also possible
that just no ucode update is available for your processor(s).
In this case it is safe to ignore this warning.
Unset \
${P} contains microcode updates which require
additional kernel patches which aren't yet included in kernel <4.14.34.
Loading such a microcode through kernel interface from an unpatched kernel
can crash your system!
Those microcodes are blacklisted per default. However, if you have altered
MICROCODE_BLACKLIST or MICROCODE_SIGNATURES, you maybe have unintentionally
re-enabled those microcodes...!
Check \
requires additional kernel patches or not.
|
Legend: + stable~ testing- not availablesome ebuild warning depend on specific use-flags or architectures, all ebuild-warnings are shown.
| 
| 
| 
- Running on 
-
:
: 