On Thursday, 11 January 2018 05:08:01 GMT Adam Carter wrote:
> Looks like there was an issue with intel-microcode-20180108.
>
> 50/94 files are different from intel-microcode-20171117_p20171215-r1 to
> intel-microcode-20180108-r1, they are;
--->8
Thanks for the info. My 03-06-f2 isn't in the li
> 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/fi
On Wed, Jan 10, 2018 at 10:01 PM, Peter Humphrey
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
On Wednesday, 10 January 2018 17:06:46 GMT Peter Humphrey wrote:
> On Wednesday, 10 January 2018 15:47:25 GMT Wolfgang Mueller wrote:
> > > It looks as though my CPU hasn't been fixed yet. Is that right?
> >
> > It seems that patches are being pushed out as they are being received,
> > so back whe
On Wednesday, 10 January 2018 15:47:25 GMT Wolfgang Mueller wrote:
> > It looks as though my CPU hasn't been fixed yet. Is that right?
>
> It seems that patches are being pushed out as they are being received,
> so back when that one was released, no other updates were available.
>
> See https://
I've got this in my boot directory:
-rwxr-xr-x 1 root root 67584 Jan 10 15:12 /boot/microcode.bin
-rwxr-xr-x 1 root root 33792 Jan 7 23:56 /boot/microcode.bin.prev
These are the split ucode file for my cpu, specifically a copy of
/lib/firmware/intel-ucode/06-3f-02.
I'm running xen, an xl dme
> It looks as though my CPU hasn't been fixed yet. Is that right?
It seems that patches are being pushed out as they are being received,
so back when that one was released, no other updates were available.
See https://bugs.gentoo.org/643430#c10
We should get the full range of updates in the next
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: 0x6
8 matches
Mail list logo
