From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is sys-firmware/intel-microcode-20180108 complete?
Date: Thu, 11 Jan 2018 09:37:05 +1100 [thread overview]
Message-ID: <CAC=wYCFHJ1gK-+PhtBAP9wtTKMd_SKbq+sXMix0Xsg9stVTq9Q@mail.gmail.com> (raw)
In-Reply-To: <2128113.qSj3GTADmc@peak>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Wed, Jan 10, 2018 at 10:01 PM, Peter Humphrey <peter@prh.myzen.co.uk>
wrote:
> I've just gone through the procedure to update the microcode on this
> haswell
> i7 box, but the version is the same now as before today's portage update.
> On
> looking again at the output of 'emerge intel-microcode' I see the date
> hasn't changed:
>
> intel-ucode/06-3f-02
> signature: 0x306f2
> flags: 0x6f
> revision: 0x3b
> date: 2017-11-17
> size: 33792
>
> It looks as though my CPU hasn't been fixed yet. Is that right?
>
That's odd - i wonder why the checksum of the file changed;
# grep 06-3f-02 intel-firmware-md5s-9jan2018.txt
intel-firmware-md5s-10jan2018.txt
intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749
/lib/firmware/intel-ucode/06-3f-02
intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93
/lib/firmware/intel-ucode/06-3f-02
[-- Attachment #2: Type: text/html, Size: 1404 bytes --]
next prev parent reply other threads:[~2018-01-10 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 11:01 [gentoo-user] Is sys-firmware/intel-microcode-20180108 complete? Peter Humphrey
2018-01-10 15:47 ` Wolfgang Mueller
2018-01-10 16:33 ` Håkon Alstadheim
2018-01-10 17:06 ` Peter Humphrey
2018-01-10 18:12 ` Mick
2018-01-10 19:49 ` [gentoo-user] " Nikos Chantziaras
2018-01-10 19:52 ` netfab
2018-01-10 21:24 ` Mick
2018-01-10 22:37 ` Adam Carter [this message]
2018-01-11 5:08 ` [gentoo-user] " Adam Carter
2018-01-11 9:32 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=wYCFHJ1gK-+PhtBAP9wtTKMd_SKbq+sXMix0Xsg9stVTq9Q@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox