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
