> 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
>
Is anyone else having a sys-libs/glibc emerge compile failure?
> checking for python3... python3
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the
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
Corbin Bird wrote:
> Is anyone else having a sys-libs/glibc emerge compile failure?
>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>> *** building glibc. Please change the environment variable
>> *** and run configure again.
> Same error regardless of the version of glibc I
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:
On 10/01/18 20:12, Mick wrote:
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
On 10/01/18 19:55, Corbin Bird wrote:
Is anyone else having a sys-libs/glibc emerge compile failure?
checking for python3... python3
checking LD_LIBRARY_PATH variable... contains current directory
configure: error:
*** LD_LIBRARY_PATH shouldn't contain the current directory when
*** building
Le 10/01/18 à 21:49, Nikos Chantziaras a tapoté :
> Intel has a page somewhere
source, please.
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
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
I used to think that when I close the lid the system goes to sleep. But
it's not. I did not use that functionality for quite a long time so I
can't say when it was broken. Meantime I would like to get that feature
back but I'm more a scientist than an IT specialist, so I need help with
that. To
> 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
I've found the manuals, sorry for the noise.
Hi Melleus,
Please share some details of the solution (e.g. reference the manuals)
you've found so other people with similar problems that would stumble
upon you email can use it too.
---
Andrew
On Wednesday, 10 January 2018 19:49:25 GMT Nikos Chantziaras wrote:
> On 10/01/18 20:12, Mick wrote:
> > 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.
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
On ~amd64 sys-firmware/intel-microcode-20180108 just came through. The
checksum on every file in /lib/firmware/intel-ucode/ has changed with this
update. My skylake system went from;
microcode: sig=0x406e3, pf=0x80, revision=0xba
to
microcode: sig=0x406e3, pf=0x80, revision=0xc2
17 matches
Mail list logo