From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AMD microcode updates - where are they?!
Date: Sat, 13 Jul 2019 20:23:07 +0100 [thread overview]
Message-ID: <3234975.s2AmX6VSSp@localhost> (raw)
In-Reply-To: <d31e7637-404b-8799-2431-47b90143b056@charter.net>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
On Saturday, 13 July 2019 19:16:18 BST Corbin wrote:
> For reference, the .config file for the kernel should have something
>
> along the lines of this:
> > #
> > # Firmware loader
> > #
> > CONFIG_FW_LOADER=y
> > CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin
> > amd-ucode/microcode_amd_fam15h.bin amdgpu/polaris10_ce.bin
> > amdgpu/polaris10_ce_2.bin amdgpu/polaris10_k_smc.bin
> > amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin
> > amdgpu/polaris10_me_2.bin amdgpu/polaris10_mec.bin
> > amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec2_2.bin
> > amdgpu/polaris10_pfp.bin amdgpu/polaris10_pfp_2.bin
> > amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma.bin
> > amdgpu/polaris10_sdma1.bin amdgpu/polaris10_smc.bin
> > amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin
> > amdgpu/polaris10_vce.bin"
> > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
> > CONFIG_FW_LOADER_USER_HELPER=y
As I understand it the CONFIG_FW_LOADER_USER_HELPER has some edge use cases,
but is not needed for our hardware/firmware.
> CPU is a AMD FX-9590 ( Fam15h )
>
> Video is a RX480 ( Polaris 10 )
>
> And, yes, both microcode updates ( Fam10h / Fam15h ) need to be builtin.
Are you sure about this?
I added 'amd-ucode/microcode_amd.bin' for Fam10h, rebooted and nothing changed
here as far as microcode patches is concerned. I am not using savedconfig on
this PC, so all amd-ucode binaries are available to be loaded from the
filesystem.
> Previous generation CPU updates will be builtin, even if you try to
> exclude them.
Fine, so following the wiki page and ONLY adding the microcode specific to the
CPU family should still work.
> Corbin
Thanks Corbin, I wonder if despite articles about microcode patch releases to
deal with spectre and what not, there are just no patches made available for
my aging AMD CPUs.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-13 19:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 12:18 [gentoo-user] AMD microcode updates - where are they?! Mick
2019-07-12 16:07 ` [gentoo-user] " Ian Zimmerman
2019-07-13 0:56 ` Adam Carter
2019-07-13 1:13 ` Adam Carter
2019-07-13 10:04 ` Mick
2019-07-13 10:01 ` Mick
2019-07-13 16:21 ` [gentoo-user] " Jack
2019-07-13 17:18 ` Mick
2019-07-13 17:23 ` Mick
2019-07-13 17:42 ` Jack
2019-07-13 18:06 ` Mick
2019-07-13 18:16 ` Corbin
2019-07-13 19:23 ` Mick [this message]
2019-07-13 20:16 ` Wols Lists
2019-07-13 21:01 ` Rich Freeman
2019-07-13 22:03 ` Mick
2019-07-14 13:26 ` Mick
2019-07-15 0:42 ` Adam Carter
2019-07-17 3:21 ` Corbin
2019-07-17 10:58 ` Mick
2019-07-17 12:46 ` Corbin
2019-07-17 20:51 ` [gentoo-user] " Ian Zimmerman
2019-07-18 12:33 ` Corbin
2019-07-18 18:23 ` Mick
2019-07-17 23:38 ` [gentoo-user] " Adam Carter
2019-07-15 4:30 ` [gentoo-user] " Ian Zimmerman
2019-07-15 21:18 ` Ian Zimmerman
2019-07-16 9:47 ` Mick
2019-07-15 5:15 ` [gentoo-user] " Adam Carter
2019-07-16 8:10 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3234975.s2AmX6VSSp@localhost \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox