Summary: | sys-kernel/genkernel-4.1.2-r3: option --module-rebuild doesn’t call "emerge […] @module-rebuild" (--install required?) | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Thibaud CANALE <thican> |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | genkernel.log (gzip) |
Description
Thibaud CANALE
2020-09-25 13:34:34 UTC
Genkernel output is pretty clear, not? > * >> --no-install set; Skipping 'emerge --ignore-default-opts --buildpkg=n --usepkg=n --quiet-build=y @module-rebuild' ... Also from quoted man page: > --[no-]module-rebuild > Runs, or does not run "emerge --ignore-default-opts --buildpkg=n --usepkg=n --quiet-build=y @module-rebuild" > to build out-of-tree modules when possible, i.e. when non-static kernel and modules will be build, installed, > ^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^ > --kernel-modules-prefix is not set, /var/lib/module-rebuild/moduledb exists and is not empty. Problem is that emerge cannot build for non-installed kernels. > Also, the option "--[no-]install" talks about "install[ing] the kernel to /boot after building." > but nothing about the modules, which I do on my own "make modules_install" after genkernel’s success. Don't do that. You are getting it wrong. Installing kernel also includes doing /lib/modules... If you use genkernel to create kernel, you shouldn't touch kernel manually and doing anything manually will cause trouble. (In reply to Thomas Deutschmann from comment #1) > Genkernel output is pretty clear, not? > > > * >> --no-install set; Skipping 'emerge --ignore-default-opts --buildpkg=n --usepkg=n --quiet-build=y @module-rebuild' ... My bad, I didn’t see it. It could be displayed on stdin too. It’s just a game of puzzle and threads to understand the genkernel options and some of its implications. I think some options should have explicit messages in its man page about "requires --X option" or "will be skipped if option --Y". > Problem is that emerge cannot build for non-installed kernels. I always managed to build modules (emerge @module-rebuild) for non-installed kernels, because I execute it before rebooting to avoid loosing service and then time. > > Also, the option "--[no-]install" talks about "install[ing] the kernel to /boot after building." > > but nothing about the modules, which I do on my own "make modules_install" after genkernel’s success. > > Don't do that. You are getting it wrong. Installing kernel also includes > doing /lib/modules... I really don’t understand what means "installing kernel", because its path depends on too many ways to boot it from different bootloaders. > If you use genkernel to create kernel, you shouldn't touch kernel manually > and doing anything manually will cause trouble. At least 7 years I move it manually (was recently still using extlinux before moving to systemd-boot for UEFI support), never had trouble. Still have no idea where genkernel wants to "install" the kernel and its initramfs. |