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
signature.asc
Description: This is a digitally signed message part.
