On Tue, Jan 9, 2018 at 8:33 PM, Corbin Bird wrote:
>
> On 01/09/2018 01:56 AM, Mick wrote:
>
> At this point, the only sure bet, is a non x86, x86_64, ARM, ARM64 CPU.
>
> Don't know enough to make a recommendation on a particular CPU arch at this
> point.
>
Good luck with that...
If you aren't h
On 01/09/2018 01:56 AM, Mick wrote:
> On Monday, 8 January 2018 17:47:03 GMT Corbin Bird wrote:
>> On 01/07/2018 02:46 PM, taii...@gmx.com wrote:
>>> I have several sandy/ivybridge CPU's and I was wondering if anyone
>>> knows as to if intel is releasing microcode updates for them.
>>>
>>> It sur
Walter Dnes wrote:
> Question: does PIE imply pic/PIC?
The code is somewhat different, but in principle yes.
> I.e does a PIE build also require USE="pic"
Assembler code which breaks pic will also break pie,
so better do not use that code.
> and CFLAGS/CXXFLAGS="-fpic -fPIC"?
These are usua
On Tue, Jan 9, 2018 at 2:47 PM, Holger Hoffstätte
wrote:
>
> Desaster Warning Time!
>
> Unless you enjoy restoring from backups in the most creative ways,
> DO NOT casually install today's update of sys-apps/attr-2.4.48, or
> your box WILL be hosed.
>
> If you are on ~arch pmask that thing _right
Desaster Warning Time!
Unless you enjoy restoring from backups in the most creative ways,
DO NOT casually install today's update of sys-apps/attr-2.4.48, or
your box WILL be hosed.
If you are on ~arch pmask that thing _right now_:
$echo "=sys-apps/attr-2.4.48" >> /etc/portage/package.mask
See
On Tue, 9 Jan 2018 10:14:50 -0700, Grant Taylor wrote:
> > Putting the patch in /etc/portage/patches/x11-xterms/xterm should do
> > it.
>
> Okay.
>
> I suppose that it will need to be some sort of diff that will
> automatically get applied?
>
> Do you know what directory the diff needs to be
Hi Grant,
I believe this wiki page is what you're looking for:
https://wiki.gentoo.org/wiki//etc/portage/patches
--
Andrew
On 01/09/2018 01:52 AM, Neil Bothwick wrote:
You can usually add extra configure items by creating, in your case
/etc/portage/env/x11-terms/xterm containing
EXTRA_ECONF="--enable-blah..."
That seems simple enough.
Putting the patch in /etc/portage/patches/x11-xterms/xterm should do it.
Ok
On Tue, 09 Jan 2018 14:21:10 +, Holger Hoffstätte wrote:
> On Mon, 08 Jan 2018 11:53:58 +, Mick wrote:
>
>> On Monday, 8 January 2018 09:05:02 GMT Max Zettlmeißl wrote:
>>> It seems like there are no microcode updates for your specific CPU
>>> bundled in linux-firmware.
>>
>> Only two ou
On Mon, 08 Jan 2018 11:53:58 +, Mick wrote:
> On Monday, 8 January 2018 09:05:02 GMT Max Zettlmeißl wrote:
>> It seems like there are no microcode updates for your specific CPU
>> bundled in linux-firmware.
>
> Only two out of three Intel boxen here report an early update of microcode in
> d
On Tue, Jan 9, 2018 at 4:26 AM, Wols Lists wrote:
> On 08/01/18 13:52, Rich Freeman wrote:
>> There is also a lot of discussion on lkml about the right fix. We
>> might very well end up seeing both AMD- and Intel-specific fixes with
>> conditional logic. The two vendors don't really seem to be
>
On Tuesday, 9 January 2018 11:50:56 GMT Peter Humphrey wrote:
> On Tuesday, 9 January 2018 11:34:24 GMT Mick wrote:
> > I just noticed I am not able to override FF's protestations about the
> > domain name of the loaded TLS certificate not matching the visited
> > domain. When I click on Advance/"
On Tuesday, 9 January 2018 11:34:24 GMT Mick wrote:
> I just noticed I am not able to override FF's protestations about the
> domain name of the loaded TLS certificate not matching the visited
> domain. When I click on Advance/"Confirm Security Exception" to
> permanently store this exception noth
I just noticed I am not able to override FF's protestations about the domain
name of the loaded TLS certificate not matching the visited domain. When I
click on Advance/"Confirm Security Exception" to permanently store this
exception nothing happens. All I can do thereafter is cancel this pop
>
> Hopefully there's an equivalent for AMD.
>
Here's what I came up with. This is very hacky and unreliable, but get the
CPUID with;
cpuid -r | grep "0x0001 0x00" | awk '{ print $3}' | uniq | cut -d x -f 3
then grab MCE (thanks Max for the suggestion) from
https://github.com/platomav/MCExtr
On Tuesday, 9 January 2018 07:31:35 GMT Mick wrote:
> On Tuesday, 9 January 2018 00:15:03 GMT Peter Humphrey wrote:
> > On Monday, 8 January 2018 10:29:41 GMT Max Zettlmeißl wrote:
> > > > How do you build the microcode into the kernel? The only
> > > > place I can see to do that in menuconfig is u
On 08/01/18 13:52, Rich Freeman wrote:
> There is also a lot of discussion on lkml about the right fix. We
> might very well end up seeing both AMD- and Intel-specific fixes with
> conditional logic. The two vendors don't really seem to be
> coordinating on this. Intel is pushing patches that ap
On Tue, Jan 9, 2018 at 12:15 AM, Peter Humphrey wrote:
> On Monday, 8 January 2018 10:29:41 GMT Max Zettlmeißl wrote:
>> > How do you build the microcode into the kernel? The only
>> > place I can see to do that in menuconfig is under Device Drivers;
>> > there's no such field under Firmware.
>>
>
>
> > The Device Drivers section is exactly where the microcode is included.
> > CONFIG_EXTRA_FIRMWARE is the relevant symbol.
>
> Right. So which of the 95 files under /lib/firmware/intel-ucode do I
> specify? That's in addition to the 14 files I have for my amdgpu.
>
>
For intel;
iucode_tool -L
On Mon, 8 Jan 2018 22:57:30 -0700, Grant Taylor wrote:
> I have been playing with a customized version of Xterm outside of
> portage and I'd like to migrate my customizations to the copy of Xterm
> that is emerged as part of the system.
>
> So far my customizations consist of a modified ./confi
On Tue, 09 Jan 2018 00:15:03 +, Peter Humphrey wrote:
> > > How do you build the microcode into the kernel? The only
> > > place I can see to do that in menuconfig is under Device Drivers;
> > > there's no such field under Firmware.
> >
> > The Device Drivers section is exactly where the mi
I have a less-two-old N3700 CPU on a Asrock N3700-ITX board that (was)is
perfect for my NAS, but without pcid instruction that mitigates the last
pti patches slowdown.
Asrock said nothing about the microcode/bios update and I asked for
warranty return because I consider a factory defect but I think
22 matches
Mail list logo
