public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AMD microcode updates - where are they?!
Date: Sat, 13 Jul 2019 13:42:27 -0400	[thread overview]
Message-ID: <ZK3SOP73.6YO66WMV.YNJMSMQX@WSQODLVE.QGFFK3PZ.DREWN4SR> (raw)
In-Reply-To: <5413979.80MaF9lyBd@localhost> (from michaelkintzios@gmail.com on Sat Jul 13 13:18:35 2019)

On 2019.07.13 13:18, Mick wrote:
> On Saturday, 13 July 2019 17:21:40 BST Jack wrote:
> > On 2019.07.12 08:18, Mick wrote:
[snip....]
>> And, one question - if I have linux-firmware emerged with  
>> savedconfig use flag set, what's the best/easiest way to hunt  
>> through the actually available firmware, to check if I might have  
>> missed something relevant.  So far, I've just searched the git  
>> repository for the package.  I suppose I could have kept a copy of  
>> the manifest from the initial emerge (without savedconfig)  but I  
>> didn't think of it at the time.
> 
> Look under your /lib/firmware/ directory for the file you want to  
> use, or the file dmesg complains is missing.  For microcode there  
> will be no complaining, but for other hardware there usually is  
> something along the lines:  "failed to load blah-blah.bin, file not  
> found."
If linux-firmware is emerged with the savedconfig use flag, then only  
the firmware not deleted from the config file is left.  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.

I'll update again once I've done that.

Jack

  parent reply	other threads:[~2019-07-13 17:42 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 [this message]
2019-07-13 18:06       ` Mick
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=ZK3SOP73.6YO66WMV.YNJMSMQX@WSQODLVE.QGFFK3PZ.DREWN4SR \
    --to=ostroffjh@users.sourceforge.net \
    --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