Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

[Floyd Anderson]

On Wed, 20 Dec 2017 16:51:04 +0000
Mick <michaelkintzios@×××××.com> wrote:
>On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote:
>> On Wed, Dec 20, 2017 at 9:26 AM, Mick <michaelkintzios@×××××.com> wrote:
>
>> > You are quite right, there is no firmware_install in the 4.14.7 release.
>> > What does this mean?  How are we meant to install firmware now?
>>
>> I believe all firmware has been removed from the kernel sources.
>>
>> You should install sys-kernel/linux-firmware, or grab just the files
>> you need from the git repo.
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>
>Thank you all, but I see to have a mental disconnect here:
>
>I already have sys-kernel/linux-firmware-20170314 installed.
>
>I have specified in the kernel which blobs I need and /lib/firmware/ as the
>path for the kernel to find any firmware it may need.
>
>I used to run make firmware_install and the kernel was able to load whatever
>firmware I had specified so that CPU/GPU can function properly at boot time.
>
>With 4.14.7 I (can) no longer do this;

Since I fully encrypt my drives and therefore using an EFI-stub kernel 
with an embedded initramfs, I use genkernel-next and different scripts 
to build my kernels. It can be tricky and feels like a tool-chain but 
also works for me.

>
>AND
>
>the newly compiled kernel does not load at boot time any of the needed
>firmware.
>
>What step am I missing to arrive at a bootable kernel with all necessary
>firmware?

Assuming your specified blobs are all available and required kernel 
options like CONFIG_MICROCODE and CONFIG_MICROCODE_INTEL [1] are proper 
set, I’m not sure it makes any difference but the default is:

    CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

without the appended forward slash.


[1] <https://wiki.gentoo.org/wiki/Intel_microcode>


-- 
Regards,
floyd