Re: [gentoo-user] microcode applied?

> 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.

Re: [gentoo-user] microcode applied?

> 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

Re: [gentoo-user] microcode applied?

> The contents of cpuinfo is the same as the messages in dmesg. What does that > imply? Your BIOS or EFI might already install the same version or a later version than what the microcode package provides. Although the second case is highly unlikely. The update might also just not get applied

Re: [gentoo-user] microcode applied?

> Does the absence of a "microcode updated" message in dmesg imply that the > microcode was not updated? Not necessarily. > Is there a way to turn on debugging? The easiest way to check whether the microcode update was applied correctly would be to check the microcode version in /proc/cpuinfo

Re: [gentoo-user] Q: pp requires --uesr option t hat doesn't exist?

$ pip install --user awscli or $ pip2.7 install --user awscli works. Merry Christmas. On 24 December 2017 at 21:54, Steven Lembark wrote: > > This should have been simple: Install AWS client command line tools. > Catch: Installing it with AWS' example tells me to use the