Re: Processor microcode update packages
On Sat, 29 Sep 2012, Eric Valette wrote:
> On 29/09/2012 12:32, Henrique de Moraes Holschuh wrote:
> >If you want to use non-modular, built-in microcode, the documentation of
> >iucode-tool does explain how to trigger the microcode reload after boot. You
> >will have to add it to your system yourself.
>
> Fair enough. Already done. However, during the stable->wheezy
> migration, all users building their own kernel may be affected as
> microcode.ctl package did had an initscript...
And it was properly documented on NEWS.Debian. I expect that, out of the
1400 or so users of Squeeze intel-microcode/microcode.ctl, no more than 1%
have custom, no-initramfs kernels with microcode built-in instead of as a
module.
If you want an initscript, you're welcome to write one and submit it as a
patch. I will add it as an example to the package, so that others can
easily use it if they want. For this class of user, it will be irrelevant
soon enough when a proper way to load microcode updates during initial
processor setup lands on v3.7, and we switch to initramfs-piggyback-cpio-
assisted microcode updates.
--
"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
Reply to: