Bug 389775 – sys-kernel/gentoo-sources: install fails with FIRMWARE_IN_KERNEL = y

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Aljosha Papsch 2011-11-07 00:17:47 UTC]

When trying to go through the compilation and install process of the Linux kernel (genkernel and manual method), install will fail when FIRMWARE_IN_KERNEL is enabled.


Reproducible: Always

Steps to Reproduce:
1. Try to do a standard kernel install
Actual Results:  
The error message will look like this:

make[1]: *** No rule to make target `/lib/firmware/./', needed by `/lib/firmware/ti_3410.fw'.  Stop.
make: *** [_modinst_post] Error 2

Expected Results:  
The kernel should install fine.

The problematic option FIRMWARE_IN_KERNEL seems to be enabled by default.
I'm not the only one affected:
http://archives.gentoo.org/gentoo-user/msg_b5974fc88d508412612d0fc1546cf6fc.xml

How to solve: Set FIRMWARE_IN_KERNEL = n
FIRMWARE_IN_KERNEL is located in:
Symbol: FIRMWARE_IN_KERNEL [=n]
 |  Type  : boolean
 │ Prompt: Include in-kernel firmware blobs in kernel binary
 │   Defined at drivers/base/Kconfig:80
 │   Depends on: FW_LOADER [=y]
 │   Location:
 │     -> Device Drivers
 │       -> Generic Driver Options
 │         -> Userspace firmware loading support (FW_LOADER [=y])

emerge --info: http://codepad.org/V4miMz3T

[Comment 1 Jeroen Roovers (RETIRED) 2011-11-08 16:02:05 UTC]

(In reply to comment #0)
> emerge --info: http://codepad.org/V4miMz3T

Please attach that or paste it in a comment.

[Comment 2 Aljosha Papsch 2011-11-08 16:12:39 UTC]

Created attachment 291975 [details]
emerge --info

[Comment 3 Mike Pagano 2011-12-11 19:52:23 UTC]

This bug pertains to a genkernel config default. Reassigning to proper team.

[Comment 4 Alessandro Capogna 2012-10-27 18:39:39 UTC]

i experimented this issue in every first installation of the kernel (when i install my system from scratch). To easy solve this issue just do: 

# mkdir /lib/firmware

from root, because that dir seems to be not present by default

PS This bug is not related to genkernel, because i don't use it at all

[Comment 5 Tom Wijsman (TomWij) (RETIRED) 2013-11-16 16:01:36 UTC]

Ugh, seems an exception when there is no firmware built that he directory isn't made; we've got two option here:

 1. File it upstream that the build system creates the directory.
 2. keepdir /lib/firmware/

We might be able to temporarily do (2) while waiting for upstream to resolve (1).

mpagano: What do you think about this?

[Comment 6 Mike Pagano 2013-12-22 01:50:09 UTC]

I ran make firmware_install on a chroot without the /lib/firmware directory and it was created. 

How can I reproduce this?