On 10/29/2014 11:56 AM, Christian Hesse wrote:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com> on Wed, 2014/10/29 11:35:
On 10/29/2014 11:02 AM, list@eworm.de wrote:
From: Christian Hesse <mail@eworm.de>
https://www.kernel.org/doc/Documentation/x86/early-microcode.txt --- configs/releng/build.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 07ff911..8b6beee 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -90,7 +90,7 @@ make_customize_airootfs() { # Prepare kernel/initramfs ${install_dir}/boot/ make_boot() { mkdir -p ${work_dir}/iso/${install_dir}/boot/${arch} - cp ${work_dir}/${arch}/airootfs/boot/archiso.img ${work_dir}/iso/${install_dir}/boot/${arch}/archiso.img + cat ${work_dir}/${arch}/airootfs/boot/intel-ucode.img ${work_dir}/${arch}/airootfs/boot/archiso.img > ${work_dir}/iso/${install_dir}/boot/${arch}/archiso.img
This does not look good. archiso.img is compressed, while intel-ucode.img is uncompressed.
Both of these are cpio archives. So what's wrong?
# file initramfs-linux.img intel-ucode.img initramfs-linux.img: ASCII cpio archive (SVR4 with no CRC) intel-ucode.img: ASCII cpio archive (SVR4 with no CRC)
Looks like you are you working with uncompressed initcpio images (ie you made a change to the default mkinitcpio.conf provided by archiso.) If prefer this way: --- archiso_intel_ucode --- #!/bin/bash build() { cd /tmp bsdcpio -i -d < /boot/intel-ucode.bin add_file /tmp/kernel/x86/microcode/GenuineIntel.bin /kernel/x86/microcode/GenuineIntel.bin } help() { cat <<HELPEOF This hook adds intel microcode updates to the early boot stage. HELPEOF } # vim: set ft=sh ts=4 sw=4 et: ----------------------------
cp ${work_dir}/${arch}/airootfs/boot/vmlinuz-linux ${work_dir}/iso/${install_dir}/boot/${arch}/vmlinuz }