[gentoo-user] genkernel's new configs not used?

[gentoo-user] genkernel's new configs not used?

[caveman رَجُلُ الْكَهْفِ 穴居人]

i thought to re-compile my kernel with some new
options.  so i did:

> sudo genkernel --menuconfig all

new kernel came, and was used normally as one
would expect across reboots.

then i periodically update the system by:

> sudo emerge -avDuNt --quiet-build=y --keep-going=y @world

problem is:  when the gentoo-source kernel gets
updated by emerge, it does not use my genkernel's
new configs.

questions:
  1. What's going on?
  2. How to fix it?

ty,
cm.

Re: [gentoo-user] genkernel's new configs not used?

[Jack]

On 12/31/21 11:28, caveman رَجُلُ الْكَهْفِ 穴居人 wrote:
> i thought to re-compile my kernel with some new options.  so i did:
>> sudo genkernel --menuconfig all
> new kernel came, and was used normally as one would expect across reboots.
I suspect you omit certain details, such as running grub-mkconfig or 
otherwise updating your grub (or other bootloader) configuration prior 
to the first reboot.
> then i periodically update the system by:
>> sudo emerge -avDuNt --quiet-build=y --keep-going=y @world
> problem is:  when the gentoo-source kernel gets updated by emerge, it does not use my genkernel's new configs.
>
> questions:
>    1. What's going on?
>    2. How to fix it?
Unless I'm missing something about what you are doing, simply emerging a 
new gentoo-kernel version does nothing except install the sources, it 
doesn't build the new kernel.  You would still need to run genkernel 
again for that new version.

Re: [gentoo-user] genkernel's new configs not used?

[caveman رَجُلُ الْكَهْفِ 穴居人]

On Friday, December 31st, 2021 at 6:52 PM, Jack <ostroffjh@users.sourceforge.net> wrote:

> .... You would still need to run genkernel
> again for that new version.

so, no auto-migration for configs?  i thought
configs used to migrate automatically.

basically i'm trying to avoid building some
modules.

Re: [gentoo-user] genkernel's new configs not used?

[thelma]

On 12/31/21 21:43, caveman رَجُلُ الْكَهْفِ 穴居人 wrote:
> On Friday, December 31st, 2021 at 6:52 PM, Jack <ostroffjh@users.sourceforge.net> wrote:
> 
>> .... You would still need to run genkernel
>> again for that new version.
> 
> so, no auto-migration for configs?  i thought
> configs used to migrate automatically.
> 
> basically i'm trying to avoid building some
> modules.

When it comes to kernel nothing is fully automatic.

Go though these commands:

cd /usr/src
rm linux

eselect kernel list
eselect kernel set #

or
ln -sfn linux-new_kernel-gentoo linux

cd linux
cp ../linux-old_kernel/.config .
make oldconfig
[just keep hitting enter]
make menuconfig

You are not done yet!

1.) At this point you must copy new kernel to your boot directory.
2.) emerge --ask -vq @module-rebuild rebuild
3.) must run to update grub menu entries eg.:
# grub-mkconfig -o /boot/grub/grub.cfg

4.) What else did I miss? (somebody correct me).

Re: [gentoo-user] genkernel's new configs not used?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]

On Fri, 31 Dec 2021 22:21:53 -0700, thelma@sys-concept.com wrote:

> On 12/31/21 21:43, caveman رَجُلُ الْكَهْفِ 穴居人 wrote:
> > On Friday, December 31st, 2021 at 6:52 PM, Jack
> > <ostroffjh@users.sourceforge.net> wrote: 
> >> .... You would still need to run genkernel
> >> again for that new version.  
> > 
> > so, no auto-migration for configs?  i thought
> > configs used to migrate automatically.
> > 
> > basically i'm trying to avoid building some
> > modules.  
> 
> When it comes to kernel nothing is fully automatic.
> 
> Go though these commands:
> 
> cd /usr/src
> rm linux
> 
> eselect kernel list
> eselect kernel set #
> 
> or
> ln -sfn linux-new_kernel-gentoo linux
> 
> cd linux
> cp ../linux-old_kernel/.config .
> make oldconfig
> [just keep hitting enter]

If you just want to accept the defaults for all new options, use "make
olddefconfig".

> make menuconfig
> 
> You are not done yet!
> 
> 1.) At this point you must copy new kernel to your boot directory.
> 2.) emerge --ask -vq @module-rebuild rebuild
> 3.) must run to update grub menu entries eg.:
> # grub-mkconfig -o /boot/grub/grub.cfg
> 
> 4.) What else did I miss? (somebody correct me).
> 

Compiling the kernel and modules? Replace 1 with

make all modules_install install

There's also the matter of the initramfs, one of the main reasons people
use genkernel, although I prefer dracut for this.


-- 
Neil Bothwick

"Be strict when sending and tolerant when receiving."
 RFC 1958 - Architectural Principles of the Internet - section 3.9

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] genkernel's new configs not used?

[Wols Lists]

On 01/01/2022 08:39, Neil Bothwick wrote:
> On Fri, 31 Dec 2021 22:21:53 -0700, thelma@sys-concept.com wrote:
> 
>> On 12/31/21 21:43, caveman رَجُلُ الْكَهْفِ 穴居人 wrote:
>>> On Friday, December 31st, 2021 at 6:52 PM, Jack
>>> <ostroffjh@users.sourceforge.net> wrote:
>>>> .... You would still need to run genkernel
>>>> again for that new version.
>>>
>>> so, no auto-migration for configs?  i thought
>>> configs used to migrate automatically.
>>>
>>> basically i'm trying to avoid building some
>>> modules.
>>
>> When it comes to kernel nothing is fully automatic.
>>
>> Go though these commands:
>>
>> cd /usr/src
>> rm linux

Does that work? Or do you need to use "unlink"? And anyway, the next few 
commands make it redundant.
>>
>> eselect kernel list
>> eselect kernel set #
>>
>> or
>> ln -sfn linux-new_kernel-gentoo linux
>>
>> cd linux
>> cp ../linux-old_kernel/.config .
>> make oldconfig
>> [just keep hitting enter]
> 
> If you just want to accept the defaults for all new options, use "make
> olddefconfig".
> 
>> make menuconfig
>>
>> You are not done yet!
>>
>> 1.) At this point you must copy new kernel to your boot directory.
>> 2.) emerge --ask -vq @module-rebuild rebuild
>> 3.) must run to update grub menu entries eg.:
>> # grub-mkconfig -o /boot/grub/grub.cfg
>>
>> 4.) What else did I miss? (somebody correct me).
>>
> 
> Compiling the kernel and modules? Replace 1 with
> 
> make all modules_install install
> 
> There's also the matter of the initramfs, one of the main reasons people
> use genkernel, although I prefer dracut for this.
> 
> 
until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT, 
which doesn't work, by design. Or NO_INSTALL, which does rather more 
than just not installing ...

I'm investigating source_mage, and ought to investigate dracut.

Cheers,
Wol

Re: [gentoo-user] genkernel's new configs not used?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:

> > Compiling the kernel and modules? Replace 1 with
> > 
> > make all modules_install install
> > 
> > There's also the matter of the initramfs, one of the main reasons
> > people use genkernel, although I prefer dracut for this.
> > 
> >   
> until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT, 
> which doesn't work, by design. Or NO_INSTALL, which does rather more 
> than just not installing ...
> 
> I'm investigating source_mage, and ought to investigate dracut.

Once you have a working kernel, there's very little to do on updates. A
script that runs

cd /usr/src/linux
zcate /proc/config.gz >.config
make oldconfig
make all modules_install install
dracut --kver=$(cat include/config/kernel.release) --xz
update the bootloader

mostly does it all, with a few frills thrown in to cover things like 
rebuilding modules.


-- 
Neil Bothwick

Windoze95 Quote: Why is the Pentium 166 so fast? - Its for booting
faster, if Windows crashed again.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] genkernel's new configs not used?

[Dale]

Neil Bothwick wrote:
> On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:
>
>>> Compiling the kernel and modules? Replace 1 with
>>>
>>> make all modules_install install
>>>
>>> There's also the matter of the initramfs, one of the main reasons
>>> people use genkernel, although I prefer dracut for this.
>>>
>>>   
>> until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT, 
>> which doesn't work, by design. Or NO_INSTALL, which does rather more 
>> than just not installing ...
>>
>> I'm investigating source_mage, and ought to investigate dracut.
> Once you have a working kernel, there's very little to do on updates. A
> script that runs
>
> cd /usr/src/linux
> zcate /proc/config.gz >.config
> make oldconfig
> make all modules_install install
> dracut --kver=$(cat include/config/kernel.release) --xz
> update the bootloader
>
> mostly does it all, with a few frills thrown in to cover things like 
> rebuilding modules.
>
>


Can you explain this part a bit?  How it knows what version for example
to build against?  Does it follow the link in /usr/src/linux, eselect
info or something else?


> dracut --kver=$(cat include/config/kernel.release) --xz


The one thing that stumps me is figuring out how to tell dracut what
version I want built.  I keep 2, 3 and sometimes 4 kernels of different
versions lurking about in /boot. 

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] genkernel's new configs not used?

[Dale]

Dale wrote:
> Neil Bothwick wrote:
>> On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:
>>
>>>> Compiling the kernel and modules? Replace 1 with
>>>>
>>>> make all modules_install install
>>>>
>>>> There's also the matter of the initramfs, one of the main reasons
>>>> people use genkernel, although I prefer dracut for this.
>>>>
>>>>   
>>> until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT, 
>>> which doesn't work, by design. Or NO_INSTALL, which does rather more 
>>> than just not installing ...
>>>
>>> I'm investigating source_mage, and ought to investigate dracut.
>> Once you have a working kernel, there's very little to do on updates. A
>> script that runs
>>
>> cd /usr/src/linux
>> zcate /proc/config.gz >.config
>> make oldconfig
>> make all modules_install install
>> dracut --kver=$(cat include/config/kernel.release) --xz
>> update the bootloader
>>
>> mostly does it all, with a few frills thrown in to cover things like 
>> rebuilding modules.
>>
>>
>
> Can you explain this part a bit?  How it knows what version for example
> to build against?  Does it follow the link in /usr/src/linux, eselect
> info or something else?
>
>
>> dracut --kver=$(cat include/config/kernel.release) --xz
>
> The one thing that stumps me is figuring out how to tell dracut what
> version I want built.  I keep 2, 3 and sometimes 4 kernels of different
> versions lurking about in /boot. 
>
> Thanks.
>
> Dale
>
> :-)  :-) 


I got it figured out.  That's a little like cheating.  LOL 

Dale

:-)  :-) 

Re: [gentoo-user] genkernel's new configs not used?

[William Kenworthy]

On 2/1/22 13:44, Dale wrote:
> Dale wrote:
>> Neil Bothwick wrote:
>>> On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:
>>>
>>>>> Compiling the kernel and modules? Replace 1 with
>>>>>
>>>>> make all modules_install install
>>>>>
>>>>> There's also the matter of the initramfs, one of the main reasons
>>>>> people use genkernel, although I prefer dracut for this.
>>>>>
>>>>>    
>>>> until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT,
>>>> which doesn't work, by design. Or NO_INSTALL, which does rather more
>>>> than just not installing ...
>>>>
>>>> I'm investigating source_mage, and ought to investigate dracut.
>>> Once you have a working kernel, there's very little to do on updates. A
>>> script that runs
>>>
>>> cd /usr/src/linux
>>> zcate /proc/config.gz >.config
>>> make oldconfig
>>> make all modules_install install
>>> dracut --kver=$(cat include/config/kernel.release) --xz
>>> update the bootloader
>>>
>>> mostly does it all, with a few frills thrown in to cover things like
>>> rebuilding modules.
>>>
>>>
>> Can you explain this part a bit?  How it knows what version for example
>> to build against?  Does it follow the link in /usr/src/linux, eselect
>> info or something else?
>>
>>
>>> dracut --kver=$(cat include/config/kernel.release) --xz
>> The one thing that stumps me is figuring out how to tell dracut what
>> version I want built.  I keep 2, 3 and sometimes 4 kernels of different
>> versions lurking about in /boot.
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-)
>
> I got it figured out.  That's a little like cheating.  LOL
>
> Dale
>
> :-)  :-)
rattus ~ # (cd /usr/src/linux && make kernelversion)
5.10.76-gentoo-r1
rattus ~ #

Re: [gentoo-user] genkernel's new configs not used?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

On Sat, 1 Jan 2022 23:44:55 -0600, Dale wrote:

> > Can you explain this part a bit?  How it knows what version for
> > example to build against?  Does it follow the link in /usr/src/linux,
> > eselect info or something else?
> >
> >  
> >> dracut --kver=$(cat include/config/kernel.release) --xz  

> I got it figured out.  That's a little like cheating.  LOL 

One man's cheating is another man's optimisation ;-)


-- 
Neil Bothwick

There are only two hard problems in distributed systems:
 2. Exactly-once delivery
 1. Guaranteed order of messages
 2. Exactly-once delivery

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] genkernel's new configs not used?

[caveman رَجُلُ الْكَهْفِ 穴居人]

On Saturday, January 1st, 2022 at 9:57 AM, Matthew Smith <matt@offtopica.uk> wrote:

> You can tell genkernel to run `make oldconfig` (see
>
> `/etc/genkernel.conf`), but I think if you only have a few config
>
> tweaks the best solution is to migrate to a distribution kernel.
>
> For example, you could create /etc/kernel/config.d/nogpu.config with
>
> the contents
>
> CONFIG_DRM_AMDGPU=n
>
> CONFIG_DRM_I915=n
>
> CONFIG_DRM_NOUVEAU=n
>
> CONFIG_DRM_RADEON=n
>
> And every time you build a dist kernel like sys-kernel/gentoo-kernel
>
> or sys-kernel/vanilla-kernel these options will be applied.


thanks!  config.d option fits me perfectly.

i didn't know of this feature of distribution
kernels, even though i'm using gentoo-sources
for years.  me even dumber than i thought.