I have AMDGPU and until kernel 4.14 all kernels compiled just fine. With kernel 4.14 I see this failure: * Linux Kernel 4.14.0-gentoo for x86_64... * .. with config file /etc/kernels/kernel-config-x86_64-4.14.0-gentoo * kernel: Using config from /etc/kernels/kernel-config-x86_64-4.14.0-gentoo * Previous config backed up to .config--2017-11-16--19-00-31.bak * kernel: >> Running mrproper... * >> Running oldconfig... * kernel: >> Cleaning... * >> Compiling 4.14.0-gentoo bzImage... * >> Installing firmware ('make firmware_install') due to CONFIG_FIRMWARE_IN_KERNEL != y... * ERROR: Failed to compile the "firmware_install" target... * * -- Grepping log... -- * * CC arch/x86/boot/compressed/misc.o * MKPIGGY arch/x86/boot/compressed/piggy.S * AS arch/x86/boot/compressed/piggy.o * DATAREL arch/x86/boot/compressed/vmlinux * LD arch/x86/boot/compressed/vmlinux *ld: arch/x86/boot/compressed/head_64.o: warning: relocation in readonly section `.head.text' *ld: warning: creating a DT_TEXTREL in a shared object. *-- * Running with options: all * Using genkernel.conf from /etc/genkernel.conf * Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh .. * Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load .. * * ERROR: Failed to compile the "firmware_install" target... * * -- End log... -- * * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively. * * Please do *not* report compilation failures as genkernel bugs! * Reproducible: Always /var/log/genkernel.log: HOSTCC arch/x86/boot/compressed/mkpiggy CC arch/x86/boot/compressed/cpuflags.o CC arch/x86/boot/compressed/early_serial_console.o LZ4 arch/x86/boot/compressed/vmlinux.bin.lz4 CC arch/x86/boot/compressed/misc.o MKPIGGY arch/x86/boot/compressed/piggy.S AS arch/x86/boot/compressed/piggy.o DATAREL arch/x86/boot/compressed/vmlinux LD arch/x86/boot/compressed/vmlinux ld: arch/x86/boot/compressed/head_64.o: warning: relocation in readonly section `.head.text' ld: warning: creating a DT_TEXTREL in a shared object. ZOFFSET arch/x86/boot/zoffset.h OBJCOPY arch/x86/boot/vmlinux.bin AS arch/x86/boot/header.o LD arch/x86/boot/setup.elf OBJCOPY arch/x86/boot/setup.bin BUILD arch/x86/boot/bzImage Setup is 16028 bytes (padded to 16384 bytes). System is 8545 kB CRC c2eebaa6 Kernel: arch/x86/boot/bzImage is ready (#1) * >> Installing firmware ('make firmware_install') due to CONFIG_FIRMWARE_IN_KERNEL != y... COMMAND: make -j12 -j1 CC="gcc" LD="ld" AS="as" ARCH="x86" make: *** No rule to make target „firmware_install“. Exit. * Gentoo Linux Genkernel; Version 65 * Running with options: all * Using genkernel.conf from /etc/genkernel.conf * Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh .. * Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load .. * ERROR: Failed to compile the "firmware_install" target... * * -- Grepping log... -- * * * -- End log... -- * * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively. * * Please do *not* report compilation failures as genkernel bugs! *
4.14 no longer supports in-kernel firmware at all. I'll amend the check to forcibly bail out, but you need to migrate yourself as previously noted by genkernel.
For the moment, disable FIRMWARE_INSTALL in your config.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba0de310141c3f0863688e7eae78bc8f591efce8 commit ba0de310141c3f0863688e7eae78bc8f591efce8 Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2017-11-16 23:41:11 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2017-11-16 23:44:12 +0000 sys-kernel/genkernel: bump. Fixes: https://bugs.gentoo.org/637698 Fixes: https://bugs.gentoo.org/637446 Package-Manager: Portage-2.3.8, Repoman-2.3.3 sys-kernel/genkernel/Manifest | 1 + sys-kernel/genkernel/genkernel-3.5.2.4.ebuild | 165 ++++++++++++++++++++++++++ 2 files changed, 166 insertions(+)
*** Bug 638018 has been marked as a duplicate of this bug. ***
FIRMWARE="no" in /etc/genkernel.conf does NOT solve the problem. Upgrading to genkernel 3.5.2.4 solves the problem. (and thanks to the devs for the quick action)
FIRMWARE_INSTALL=no is the workaround.
Hello. Just a question, why was this bug changed from genkernel-next to genkernel? If genkernel-next no longer supported or was the summary where I forgot to explicitly mention genkernel-next misleading?
(In reply to Vit Pelcak from comment #8) > Hello. > > Just a question, why was this bug changed from genkernel-next to genkernel? > > If genkernel-next no longer supported or was the summary where I forgot to > explicitly mention genkernel-next misleading? It was unclear and really affects both. genkernel-next should import this patch as well in a new release. CC'ing back the genkernel-next maintainer
Nothing in the original report other than the component said genkernel-next. muddler: can you throw a small patch onto gk-next that changes the log destinations and bug reporting details?
Just got bit by this bug when gentoo-sources 4.14.7 was marked stable...had to pull in genkernel 3.5.2.4 (still keyworded) to get it to build.
*** Bug 641824 has been marked as a duplicate of this bug. ***
Same here, with genkernel-next-66. Happens on compiling both 4.14.7 and 4.14.8-r1 kernels. Also hoping for a patch on genkernel-next.
*** Bug 642022 has been marked as a duplicate of this bug. ***
it would be nice if someone with proper permissions could change the subject to "sys-kernel/genkernel" instead of just "genkernel" so this will pop up on a search like this: https://bugs.gentoo.org/buglist.cgi?quicksearch=ALL%20sys-kernel%2Fgenkernel
maybe is better to mask affected genkernels for the moment
alicef: please don't reopen like this. This is fixed in ~arch versions already, and I'm trying to get a stable out the door.
*** Bug 642438 has been marked as a duplicate of this bug. ***
