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 19:06:19 +0100 [thread overview]
Message-ID: <8454413.yhxcbTWUVq@localhost> (raw)
In-Reply-To: <ZK3SOP73.6YO66WMV.YNJMSMQX@WSQODLVE.QGFFK3PZ.DREWN4SR>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On Saturday, 13 July 2019 18:42:27 BST Jack wrote:
>
> If linux-firmware is emerged with the savedconfig use flag, then only
> the firmware not deleted from the config file is left.
Yes. I used to do this, but gave up after a while.
> I did find a
> few extras based on the "failed to load..." messages after my initial
> overzealous trimming of that config file. My current concern is indeed
> with the microcode, about which no complaint. Looking at the link
> below shows me I am missing the files for my 17h family Ryzen CPU. It
> will be a bit before I can reboot to see if it does load them once I
> re-emerge linux-firmware to get them.
Make sure the corresponding AMDGPU driver settings are built in the kernel,
not as modules.
Ryzen CPUs are new(ish) and the MoBo OEMs should still be releasing UEFI/BIOS
firmware updates, which will contain any needed microcode patches. You'll
obtain these next time you flash your BIOS with the latest release, if/when
there is one available. Your 'dmesg | grep micro' patch number will change as
a result, but there will be no 'early microcode update ...' message since the
OS will not be applying any microcode patches itself.
It is older CPUs which need the patches, since OEMs usually abandon any
intention to support their hardware beyond the nominal warranty period.
> I'll update again once I've done that.
>
> Jack
Cool, thanks for your input.
--
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 18:06 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 [this message]
2019-07-13 18:16 ` Corbin
2019-07-13 19:23 ` Mick
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=8454413.yhxcbTWUVq@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