Kernel configuration is not preserved when upgrading kernel.

[Budoka]

OK. I have done enough kernel upgrades now that I can state unequivocally that my kernel config is not being saved between upgrades. I always have to go back into the new kernel and manually configure it...again, and again, and again.

I understand that it may totally be due to some mistake on my part so in another attempt to solve this problem will outline my process and hopefully someone can tell me where I am going wrong. The problem was also addressed briefly in a previous thread but was never resolved. https://forums.gentoo.org/viewtopic-t-953956-start-25-postdays-0-postorder-asc-highlight-.html

I am using https://wiki.gentoo.org/wiki/Kernel/Upgrade and https://wiki.gentoo.org/wiki/Kernel/Configuration.

So I can emerge the new kernel successfully. In most cases I am using Gentoo-Sources but in the future would like to use the hardened kernel.

I can successfully set the symlink using

[Navar]

Disclaimer: I have not used genkernel since 2010.

http://wiki.gentoo.org/wiki/Genkernel#Using_previous_kernel_configuration_while_changing_the_sources

I'd start checking from that aspect (genkernel). In particular, if doing the old school method of cp path/priorconfig newpath/, make oldconfig, etc. seems to be working fine--especially if a simple diff of the priorconfig and newly revised shows only some changes you'd expect. But remember, genkernel does its own way (/etc/kernels /etc/genkernel.conf, etc.) That wiki will explain further details.

I make use of the /proc/config.gz kernel feature, so a simple cd /usr/src/linux && pwd -P && uname -r followed by zcat /proc/config.gz >.config does the job for me with the usual make oldconfig. The former is done just to ensure where the link is actually set as most of my setups have immediately auto eselected the newly installed kernel source on a world update while some don't. I usually forget to look into what would resolve the cause to this inconsistency. Which later borks update requirements on other package updates from that without being prior prepared or re-eselecting active compiled kernel source . Almost seems one of the main uses for --keep-going).

[eccerr0r]

"works for me" ... though between different versions of the kernel, technically speaking, all bets are off. You will still have to look through your config whether it be menuconfig or not, to make sure the options haven't changed in the new version.

Hence yes, I hate upgrading kernels. It _is_ a PITA. Even if I didn't have to reboot...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[NeddySeagoon]

Budoka,

[russK]

In my experience, genkernel will save a successful .config under /etc/kernels.

[Budoka]

[creaker]

From my experience "make oldconfig" leads to unpredictable results.
If I want to build new kernel with old .config I just copying it to new sources directory, navigating to this directory and starting "make && make modules_install" without any .config changes. If new kernel has some new options that missed in old .config - you will be asked for these options during compilation and your answers will be saved into .config automatically.

[kick6]

[N8Fear]