Groups | Search | Server Info | Login | Register
Groups > linux.debian.security > #5613
| From | Lou Poppler <LouPoppler@cableone.net> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: Intel Microcode updates |
| Date | 2019-06-24 02:20 +0200 |
| Message-ID | <yckSd-4UK-1@gated-at.bofh.it> (permalink) |
| References | <y7jN8-18n-3@gated-at.bofh.it> <y7Eyd-52j-1@gated-at.bofh.it> <yc5zP-43y-3@gated-at.bofh.it> |
| Organization | Train 102 |
I am only guessing, but I think a possible explanation which resolves this conundrum might be this: The latest release page is saying that the latest microcode package contains the latest microcode for this Core2 processor, which is the version last updated on 2010-09-28. Not changed, but still made available in the 20190312 standard microcodes blob. Maybe, only guessing. On Sun, 2019-06-23 at 09:55 +0200, Davide Prina wrote: > On 11/06/19 04:19, Henrique de Moraes Holschuh wrote: > > On Mon, 10 Jun 2019, Russell Coker wrote: > > > model name : Intel(R) Core(TM)2 Quad CPU Q9505 @ 2.83GHz > > Intel upstream decided to not distribute it, for whatever reason. The > > Core2 will not get any fixes for MDS either (nor will Nehalem and > > Westmere). > > ok, I have read that also, but in the latest release page[¹] > it tell you that Intel® Core™2 Quad Processor is supported by the latest > microcode (Version: 20190312 (Latest)). > > But if I do a > # dmesg | grep microcode > [ 0.000000] microcode: microcode updated early to revision 0xa0b, > date = 2010-09-28 > > $ dpkg -l intel-microcode > ii intel-microcode 3.20190618.1~deb9u1 > > So Intel tell you, in the "press", that your CPU is not supported; in > the microcode official page, it tell you that your CPU is supported... > and the microcode is installed on my PC, but not loaded... something is > wrong, or I don't have understand. > > > It is easy enough to source that microcode update if you look for it, > > and you can just drop it on /usr/share/misc/intel-microcode.bin with > > intel-microcode installed, and update the initramfs. It will pick the > > extra microcode up. > > in the page [¹] there is not a download link, but a .txt file that tell > you do download from github[²] and here there is exactly what I have in: > $ dpkg -L intel-microcode > > and not the intel-microcode.bin you talk about > > Am I missing something? > > Ciao > Davide > > [¹] > https://downloadcenter.intel.com/download/28727/Linux-Processor-Microcode-Data-File?product=35428 > > [²] > https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files >
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar
Intel Microcode updates Russell Coker <russell@coker.com.au> - 2019-06-10 06:10 +0200
Re: Intel Microcode updates Michael Stone <mstone@debian.org> - 2019-06-10 13:20 +0200
Re: Intel Microcode updates Davide Prina <davide.prina@gmail.com> - 2019-06-10 19:50 +0200
Re: Intel Microcode updates Michael Stone <mstone@debian.org> - 2019-06-10 20:40 +0200
Re: Intel Microcode updates Davide Prina <davide.prina@gmail.com> - 2019-06-11 20:10 +0200
Re: Intel Microcode updates Michael Stone <mstone@debian.org> - 2019-06-11 22:00 +0200
Re: Intel Microcode updates Russell Coker <russell@coker.com.au> - 2019-06-11 14:00 +0200
Re: Intel Microcode updates Henrique de Moraes Holschuh <hmh@debian.org> - 2019-06-11 04:20 +0200
Re: Intel Microcode updates Russell Coker <russell@coker.com.au> - 2019-06-11 14:00 +0200
Re: Intel Microcode updates Moritz Mühlenhoff <jmm@inutil.org> - 2019-06-11 14:30 +0200
Re: Intel Microcode updates Henrique de Moraes Holschuh <hmh@debian.org> - 2019-06-12 17:00 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-18 13:00 +0200
Re: Intel Microcode updates Henrique de Moraes Holschuh <hmh@debian.org> - 2019-06-23 22:30 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-23 22:40 +0200
Re: Intel Microcode updates Henrique de Moraes Holschuh <hmh@debian.org> - 2019-06-24 04:10 +0200
Re: Intel Microcode updates Davide Prina <davide.prina@gmail.com> - 2019-06-24 19:40 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-18 22:10 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-22 14:30 +0200
Re: Intel Microcode updates Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-11 19:10 +0200
Re: Intel Microcode updates Holger Levsen <holger@layer-acht.org> - 2019-06-11 19:20 +0200
Re: Intel Microcode updates Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-11 21:10 +0200
Re: Intel Microcode updates Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-11 21:20 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-18 11:20 +0200
Re: Intel Microcode updates Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-18 20:30 +0200
Re: Intel Microcode updates Rob van der Putten <rob@sput.nl> - 2019-06-20 14:40 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-18 22:10 +0200
Re: Intel Microcode updates Elmar Stellnberger <estellnb@gmail.com> - 2019-06-22 14:30 +0200
Re: Intel Microcode updates Davide Prina <davide.prina@gmail.com> - 2019-06-23 10:00 +0200
Re: Intel Microcode updates Lou Poppler <LouPoppler@cableone.net> - 2019-06-24 02:20 +0200
Re: Intel Microcode updates Davide Prina <davide.prina@gmail.com> - 2019-06-24 20:00 +0200
csiph-web