> Since I dont know where look up firmware version numbers i'm in the dark.
You can use MC Extractor to extract the metadata associated with the
AMD microcode updates.
The microcode_amd.bin which is part of
sys-kernel/linux-firmware-20180103-r1 contains the following microcode
updates:
CPUID
On Monday, 8 January 2018 04:55:58 GMT Max Zettlmeißl wrote:
> You can either use an initrd or build the microcode into your kernel
> image. I prefer the latter.
I'm confused now. How do you build the microcode into the kernel? The only
place I can see to do that in menuconfig is under Device Dr
> 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.
On Mon, Jan 8, 2018 at 9:14 PM, Peter Humphrey
wrote:
> On Monday, 8 January 2018 04:55:58 GMT Max Zettlmeißl wrote:
>
> > You can either use an initrd or build the microcode into your kernel
> > image. I prefer the latter.
>
> I'm confused now. How do you build the microcode into the kernel? The
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
dmesg. Even when they do, it is not certain the latest firm
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
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 sure would be funny if intel wanted you to buy a new CPU to fix a
> problem that was their fault to begin with
On 01/07/2018 09:24 PM, Adam Carter wrote:
> Does the absence of a "microcode updated" message in dmesg imply that
> the microcode was not updated?
>
> I believe my fam10/barcelona AMD CPU will use
> amd-ucode/microcode_amd.bin but there's no update message.
>
> I've checked the config against an
Alan McKinnon wrote:
> I have one of those under my desk at home. Finally switched it off for
> the last time about 2 months ago.
>
> So yes, you can run 64 bit Gentoo on it just fine. Make the
> appropriate changes in make.conf and away you go.
>
> Just because distro X does not support cpu Y in m
On Mon, Jan 08, 2018 at 04:15:57AM +0100, mad.scientist.at.la...@tutanota.com
wrote
> Does any body know if it's possible to set up gentoo on a single core
> 64 bit athlon, old socket 754? I tried another distro and it said
> it didn't support non-smp 64 bit. If not i'll have to put some 32
> bi
On Mon, Jan 8, 2018 at 4:43 PM, Walter Dnes wrote:
> There are "athlons" and then there are "athlons". Check the gcc page
> https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/x86-Options.html#x86-Options
> for an idea of what's what. You need at least the "k8" version. The
> ultimate way to find ou
On Sun, Jan 7, 2018 at 11:42 PM, wrote:
> You really can't fix it completely in
> software on either brand, at best you are counting on code to protect code
> from a hardware on intel, and more mild but still dangerous design issues
> on both.
As far as I can tell from the various emails/postin
On 2017-12-05, Grant Edwards wrote:
> On 2017-12-05, Ian Zimmerman wrote:
>> On 2017-12-05 00:05, Holger Hoffstätte wrote:
>>
>>> > There are a number of third-party binary executables that I use
>>> > regularly on my Gentoo systems.
>>> > [...]
>>> > Is switching to the new 17.0 profile likely t
On 2018-01-08,
wrote:
> Does any body know if it's possible to set up gentoo on a single core
> 64 bit athlon, old socket 754?
Yes, it's possible.
Here's an recent writeup on installing Gentoo on a IBM PS/1 133MHz 486
with 64MB of RAM:
https://github.com/yeokm1/gentoo-on-486
--
Grant
On Mon, Jan 08, 2018 at 08:44:04PM -0600, R0b0t1 wrote
> I was under the impression that disabling SMP on single core systems
> could lead to a performance increase, but wasn't necessary.
Quote from the "Help" in "make menuconfig" from the CONFIG_SMP item:
=
If you execute...
grep ":pic " /usr/portage/profiles/use.local.desc
...you'll get multiple listings that mention...
- disable optimized assembly code that is not PIC friendly
- Force shared libraries to be built as PIC (this is slower)
Question: does PIE imply pic/PIC? I.e does a PIE build
How do I customize the features that are compiled into x11-terms/xterm?
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 modifie
I am curious to know has anyone moved their ppc or ppc64 over to profile
17? If so what were hurdles if any?
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 under Device Drivers;
> > > there's no such field under Firmw
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 sure would be funny if intel wanted you to
20 matches
Mail list logo
