sudo genkernel --menuconfig all
sudo emerge -avDuNt --quiet-build=y --keep-going=y @world
i thought to re-compile my kernel with some new options. so i did:I suspect you omit certain details, such as running grub-mkconfig or
sudo genkernel --menuconfig allnew kernel came, and was used normally as one would expect across reboots.
then i periodically update the system by:Unless I'm missing something about what you are doing, simply emerging a
sudo emerge -avDuNt --quiet-build=y --keep-going=y @worldproblem 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?
.... You would still need to run genkernel
again for that new version.
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.
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).
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.
On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:
Once you have a working kernel, there's very little to do on updates. A script that runsCompiling the kernel and modules? Replace 1 withuntil you trip over genkernel's "features" ... like AUTOMOUNT_BOOT,
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.
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.
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.
dracut --kver=$(cat include/config/kernel.release) --xz
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.
Dale wrote:rattus ~ # (cd /usr/src/linux && make kernelversion)
Neil Bothwick wrote:
On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote:Can you explain this part a bit? How it knows what version for example
Once you have a working kernel, there's very little to do on updates. ACompiling the kernel and modules? Replace 1 withuntil you trip over genkernel's "features" ... like AUTOMOUNT_BOOT,
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.
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.
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.
to build against? Does it follow the link in /usr/src/linux, eselect
info or something else?
dracut --kver=$(cat include/config/kernel.release) --xzThe 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
:-) :-)
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
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 429 |
Nodes: | 16 (2 / 14) |
Uptime: | 113:30:31 |
Calls: | 9,055 |
Calls today: | 2 |
Files: | 13,395 |
Messages: | 6,016,252 |