Siduction Forum > Scripting & Kernelhacking
[EN] early intel microcode
(1/1)
ralul:
I managed to create a valid initr.img holding:
--- Code: ---# lsinitrd icoreduo.img
Image: icoreduo.img: 25K
========================================================================
Version:
Arguments:
dracut modules:
========================================================================
drwxr-xr-x 2 root root 0 Oct 29 19:00 kernel
drwxr-xr-x 2 root root 0 Oct 29 19:00 kernel/x86
drwxr-xr-x 2 root root 0 Oct 29 19:00 kernel/x86/microcode
-rw-r--r-- 1 root root 24576 Oct 29 19:00 kernel/x86/microcode/GenuineIntel.bin
========================================================================
--- End code ---
Now dmesg shows
--- Code: ---# dmesg |grep microcode
[ 0.000000] CPU0 microcode updated early to revision 0xa0b, date = 2010-09-28
[ 0.006666] CPU1 microcode updated early to revision 0xa0b, date = 2010-09-28
[ 0.567774] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa0b
[ 0.567784] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa0b
[ 0.567869] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
--- End code ---
The 5 seconds later occurence of "Microcode Update Driver: v2.00"
I dont know where this comes from : I have removed all of /lib/firmware/microcode.dat,iucode-intel files
. . . I am just about to reboot using a newly created dracut initrd file . . .
[edit]
not better with a new initrd, the depreciated update driver was not called by the initrd:
--- Code: ---# dmesg |grep microcode
[ 0.000000] CPU0 microcode updated early to revision 0xa0b, date = 2010-09-28
[ 0.006666] CPU1 microcode updated early to revision 0xa0b, date = 2010-09-28
[ 0.458514] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa0b
[ 0.458524] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa0b
[ 0.458623] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
--- End code ---
I will try again to get rid of the traditional "Microcode Update Driver" by deinstalling the
package intel-microcode
[edit] I am not getting rid of ... but I am pretty sure the old Update Driver has nothing left to use to update from.
Navigation
[0] Message Index
Go to full version