search for: iucode_tool

Displaying 5 results from an estimated 5 matches for "iucode_tool".

2019 May 16
2
centos-virt CPU microcode updates?
Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel
2019 May 16
1
centos-virt CPU microcode updates?
...ode updates on CentOS6, Xen 4.10, kernel 4.9 ? > > I'm not sure off the top of my head. > > You can add ucode=scan to the xen command line, add a file /path/to/microcode_file as the last item in your boot list, and generate that microcode > file using something like: > > iucode_tool --write-earlyfw "${OUT_BLOB_FILE}" \ > "${TEMP_DIR_NAME}/intel-ucode" \ > "${TEMP_DIR_NAME}/intel-ucode-with-caveats" > > Where the last two items have been extracted from the intel microcode tarball. > > --Sarah > _________...
2015 May 13
3
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure
2015 May 15
2
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
...14-05/msg00053.html says > that I have to use ?cpio -H newc? not ?cpio -o c?, but I don?t know how > the Debian tools create the initrd. The intel-microcode package contains: /usr/share/initramfs-tools/hooks/intel_microcode which will be called during initamfs generation. It seems to call iucode_tool, from the iucode-tool package. That's a binary tool which seems to include its own cpio writer implementation, I've no idea if that is like a 'newc' or not. However: ijc at dagon:tmp$ find iucode-tool/ | cpio -o > normal.cpio 828 blocks ijc at dagon:tmp$ find iucode-tool/ | cpio...
2019 May 16
0
centos-virt CPU microcode updates?
...; is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? I'm not sure off the top of my head. You can add ucode=scan to the xen command line, add a file /path/to/microcode_file as the last item in your boot list, and generate that microcode file using something like: iucode_tool --write-earlyfw "${OUT_BLOB_FILE}" \ "${TEMP_DIR_NAME}/intel-ucode" \ "${TEMP_DIR_NAME}/intel-ucode-with-caveats" Where the last two items have been extracted from the intel microcode tarball. --Sarah