Re: Intel Microcode updates
On Tue, 18 Jun 2019, Elmar Stellnberger wrote:
> Perhaps you could add a bash script that does automatically download the
> microcode like f.i. winetricks does with windows code. That way one could be
> more sure to use the right url for it. I also still have quite a lot of Core
> 2 computers and would thus profit from such a provision.
I can add it as an example, sure, if someone writes one that is good
enough to share and sends it as a *whishlist* bug to the BTS with the
But I fear it will be pointless. The README already tells you how to do
it yourself, and people won't read it, why would them find about an
example downloader script?
I have been quite clear enough in my reply below about microcode updates
sourced from random places, so such a downloader would *HAVE* to
download from the official microcode updates distribution, anyway.
> Am 12.06.19 um 16:52 schrieb Henrique de Moraes Holschuh:
> > (BCC'd to #929073 to avoid dragging the BTS into this thread).
> > On Tue, 11 Jun 2019, Moritz Mühlenhoff wrote:
> > > Russell Coker <firstname.lastname@example.org> schrieb:
> > > > Should it be regarded as a bug in the intel-microcode package that it doesn't
> > > > have this update that is "easy enough to source"? Or do you mean "easy to get
> > > > but not licensed for distribution"?
> > > This is covered by #929073, which links to a PDF by Intel (which documents
> > > that Intel won't ship an update for your CPU).
> > I'd like to add that:
> > We do not, and will not, distribute in non-free's intel-microcode
> > anything we did not get from Intel (or from someone else who got it from
> > Intel with permission to redistribute). This ensures all microcode
> > updates we distribute in non-free are under a license that allows
> > redistribution.
> > Note that, as long as there are very good reasons to do so, I am willing
> > to distribute microcode updates that are no longer being distributed,
> > since we did receive it with an appropriate license that allows
> > redistribution in the first place.
> > Also, one can place whatever microcode updates they got from wherever to
> > /usr/share/misc/intel-microcode*.bin at their own risk and
> > responsibility, and the intel-microcode package will attempt to use it.
> >  as in: "they were being distributed by Intel on the Linux microcode
> > update package in the past, and for more than one release of Intel's
> > microcode update package".