On Sat, 29 Sep 2012, Lionel Gamay wrote: > Meanwhile I tried something else: I kept the "intel-microde" and > "iucode-tool" packages installed but used the previous microcode-free > kernel instead of the one generated after installing the above > packages. However, I added "microcode" to "/etc/modules" in order to > force module loading. When I boot the machine in this config, > microcode gets read and updated as it should... and the machine runs > fine. > > dmesg|grep microcode > [ 17.458855] microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x212 > [ 19.014638] microcode: CPU0 updated to revision 0x218, date = 2009-04-10 > [ 19.015639] microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x212 > [ 19.034041] microcode: CPU1 updated to revision 0x218, date = 2009-04-10 > [ 19.036638] microcode: Microcode Update Driver: v2.00 > <tig...@aivazian.fsnet.co.uk>, Peter Oruba
That just means you didn't load it from the initramfs, but much later, when /etc/modules was processed. Since the problem is in the initramfs, it doesn't surprise me much that it worked that way :-) -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
