0x206c2 is missing *from the Debian and Ubuntu packages* on purpose, but we could ship it if Intel explicitly tells us it is not going to permanently disable a box that has a very old BIOS with the blacklisted SINIT ACM for Intel TXT AND which happens to have Intel-TXT-based secure boot enabled in BIOS.
For 0x106e5, 0x306e4:
They are present in the intel-microcode packages in Debian, so I will leave the answer to the Ubuntu maintainer. Are you sure they are really missing from /lib/firmware/intel-ucode?
This will check if the microcodes are in the package (run it with the package installed and no extra manually-added microcodes in /lib/firmware/intel-ucode or /usr/share/misc/intel-microcode*)
For 0x206c2: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 907402
Refer to https:/
0x206c2 is missing *from the Debian and Ubuntu packages* on purpose, but we could ship it if Intel explicitly tells us it is not going to permanently disable a box that has a very old BIOS with the blacklisted SINIT ACM for Intel TXT AND which happens to have Intel-TXT-based secure boot enabled in BIOS.
For 0x106e5, 0x306e4: intel-ucode?
They are present in the intel-microcode packages in Debian, so I will leave the answer to the Ubuntu maintainer. Are you sure they are really missing from /lib/firmware/
This will check if the microcodes are in the package (run it with the package installed and no extra manually-added microcodes in /lib/firmware/ intel-ucode or /usr/share/ misc/intel- microcode* )
iucode_tool -q -l -s 0x106e5 -s 0x306e4 /lib/firmware/ intel-ucode
" reports they exist, then your issue is that they're not being installed to the initramfs.