Intel microcodes only exist for very specific family/model/stepping CPUs. If no microcode gets added, there is no need to create an empty (only directories) cpio later that gets glued to the initrd.
This also fixes: *** Constructing GenuineIntel.bin **** cat: /lib/firmware/intel-ucode/06-3c-03: No such file or directory in hostonly mode if there is no suitable microcode for the CPU. Reviewed-by: Konrad Rzeszutek Wilk <[email protected]> Signed-off-by: Thomas Renninger <[email protected]> --- dracut.sh | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/dracut.sh b/dracut.sh index 0383c7e..618c301 100755 --- a/dracut.sh +++ b/dracut.sh @@ -1294,12 +1294,15 @@ if [[ $early_microcode = yes ]]; then dinfo "*** Constructing ${ucode_dest[$idx]} ****" if [[ $hostonly ]]; then _src=$(get_ucode_file) + if ! [[ -r $_fwdir/$_fw/$_src ]];then + break; + fi fi cat $_fwdir/$_fw/$_src > $_dest_dir/${ucode_dest[$idx]} + create_early_cpio="yes" fi done done - create_early_cpio="yes" fi rm -f -- "$outfile" -- 1.7.6.1 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
