| 1 |
On Wed, Jan 10, 2018 at 10:01 PM, Peter Humphrey <peter@××××××××××××.uk> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> I've just gone through the procedure to update the microcode on this |
| 5 |
> haswell |
| 6 |
> i7 box, but the version is the same now as before today's portage update. |
| 7 |
> On |
| 8 |
> looking again at the output of 'emerge intel-microcode' I see the date |
| 9 |
> hasn't changed: |
| 10 |
> |
| 11 |
> intel-ucode/06-3f-02 |
| 12 |
> signature: 0x306f2 |
| 13 |
> flags: 0x6f |
| 14 |
> revision: 0x3b |
| 15 |
> date: 2017-11-17 |
| 16 |
> size: 33792 |
| 17 |
> |
| 18 |
> It looks as though my CPU hasn't been fixed yet. Is that right? |
| 19 |
> |
| 20 |
|
| 21 |
That's odd - i wonder why the checksum of the file changed; |
| 22 |
|
| 23 |
# grep 06-3f-02 intel-firmware-md5s-9jan2018.txt |
| 24 |
intel-firmware-md5s-10jan2018.txt |
| 25 |
intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749 |
| 26 |
/lib/firmware/intel-ucode/06-3f-02 |
| 27 |
intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93 |
| 28 |
/lib/firmware/intel-ucode/06-3f-02 |
Archives