This almost always happens to me when I change the EXTRAVERSION in the kernel makefile of the same kernel version. I was installing a new machine with an Ubuntu liveCD, and I just got this. I've received this trivial error on other machine's before, but it's always cured with a quick ^C. Second attempt gets the name right, and I move on. Terminal output: ubuntu linux # genkernel all * Gentoo Linux Genkernel; Version 3.4.10 * Running with options: all * Linux Kernel 2.6.27-gentoo-r8-experimental_usb-no_pata2.6.27-gentoo-r8 for x86... * >> Running oldconfig... * config: --no-clean is enabled; leaving the .config alone. * >> Compiling 2.6.27-gentoo-r8-experimental_usb-no_pata bzImage... ^Cubuntu linux # genkernel all * Gentoo Linux Genkernel; Version 3.4.10 * Running with options: all * Linux Kernel 2.6.27-gentoo-r8-experimental_usb-no_pata for x86... * >> Running oldconfig... * config: --no-clean is enabled; leaving the .config alone. * >> Compiling 2.6.27-gentoo-r8-experimental_usb-no_pata bzImage... * >> Compiling 2.6.27-gentoo-r8-experimental_usb-no_pata modules... * Copying config for successful build to /etc/kernels/kernel-config-x86-2.6.27-gentoo-r8-experimental_usb-no_pata * busybox: >> Using cache * initramfs: >> Initializing... * >> Appending base_layout cpio data... * >> Appending auxilary cpio data... * >> Appending busybox cpio data... * >> Appending lvm cpio data... * LVM: Adding support (using local static binaries)... * >> Appending modules cpio data... * * Kernel compiled successfully! * * Required Kernel Parameters: * real_root=/dev/$ROOT * * Where $ROOT is the device node for your root partition as the * one specified in /etc/fstab * * If you require Genkernel's hardware detection features; you MUST * tell your bootloader to use the provided INITRAMFS file. Otherwise; * substitute the root argument for the real_root argument if you are * not planning to use the initrd... * WARNING... WARNING... WARNING... * Additional kernel cmdline arguments that *may* be required to boot properly... * add "dolvm" for lvm support * Do NOT report kernel bugs as genkernel bugs unless your bug * is about the default genkernel configuration... * * Make sure you have the latest genkernel before reporting bugs. Reproducible: Always Steps to Reproduce: 1. open /usr/src/linux/Makefile in your favorite text editor 2. add a little snippet to the end of EXTRAVERSION to test this with. 3. # genkernel all 4. Watch it go. 5. Files and everything land in the correct place, but the output text being wrong is just annoying.
It seems the problem was, that generated file include/config/kernel.release even when it is out of sync. I think I was able to fix it. Please try genkernel-99999 (five nines) to get and test the fix. If needed, please re-open this bug. http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=48ca00ec29afdec6cb168fbaae87a7b07ea65988
I had to revert the patch above, as it introduced a regression of more importance (bug #352787). Re-opening.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=3abb33bf0e12e38f453e262392572b0c6d47ea7c commit 3abb33bf0e12e38f453e262392572b0c6d47ea7c Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-03-28 20:37:17 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-03-28 20:37:17 +0000 genkernel: tell user that shown kernel version is subject to change When you start with fresh (unused) kernel sources, we will get Kernel Version from KERNEL_DIR. If you already have compiled that KV, genkernel maybe use your existing configuration from /etc/kernels (depends on other settings like --mrproper). Once your new kernel was built and you are saving configs (--save-config), we will save the used configuration in /etc/kernels/kernel-config-${ARCH}-${KV}. If you used --menuconfig during genkernel run to change kernel options like CONFIG_LOCALVERSION or CONFIG_LOCALVERSION_AUTO or have modified kernel's Makefile manually to change version, KV is subject to change once genkernel has called 'make prepare'. With this change we will tell user when KV has changed to end confusion like shown in bug 521778. Closes: https://bugs.gentoo.org/521778 Closes: https://bugs.gentoo.org/352787 Closes: https://bugs.gentoo.org/263927 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> genkernel | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=58a57b303efb9fb5ce60c0dc40c806e7d7b46db0 commit 58a57b303efb9fb5ce60c0dc40c806e7d7b46db0 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-03-28 20:04:21 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-03-28 20:04:21 +0000 get_KV(): refactoring how we determine KV - Fix handling O= builds (--kernel-outputdir): Patch (commit 8de731164496d09384d8be81a3f22316230deb65) from bug 238707 has probably never worked: There's no MAKEARGS in $KERNEL_DIR/Makefile... It is enough to read include/linux/version.h or include/linux/utsrelease.h from $KERNEL_OUTPUTDIR which is either set to $KERNEL_DIR or is a separate directory in which case there will be no files created in $KERNEL_DIR. - Set marker if KV will change to allow for user notification to avoid confusion. Bug: https://bugs.gentoo.org/521778 Bug: https://bugs.gentoo.org/352787 Bug: https://bugs.gentoo.org/263927 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> gen_determineargs.sh | 50 +++++++++++++++++++++++++++++--------------------- 1 file changed, 29 insertions(+), 21 deletions(-)
