emerge gentoo-kernel installkernel not rebuilding nvidia-dri

[linux_os2]

First time using installkernel to build new kernel.

/etc/portage/make.conf:

Code: Select all

....
....
USE="cups perl_features_ithreads dist-kernel"
...
...

/etc/portage/package.use:

Code: Select all

sys-kernel/installkernel grub dracut -systemd

x11-drivers/nvidia-drivers are not rebuild

[Hu]

Are you saying that you expected emerge would rebuild x11-drivers/nvidia-drivers, but that it did not schedule that for rebuild? Or are you trying to say that emerge scheduled them for a build, and the build failed?

[linux_os2]

Are you saying that you expected emerge would rebuild x11-drivers/nvidia-drivers, but that it did not schedule that for rebuild?

Yes I expected.
Also:

* Your configuration for sys-kernel/gentoo-kernel-6.13.3 has been saved in
* "/etc/portage/savedconfig/sys-kernel/gentoo-kernel-6.13.3" for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* /usr/src/linux points at another kernel, leaving it as-is.
* Please use 'eselect kernel' to update it when desired.

I would expect that the eselect kernel would be done.

[Ionen]

Unfortunately automated rebuilds for modules with USE=dist-kernel only work when the kernel is being updated to a new version (aka works for normal @world updates), if you rebuild the *same* kernel (by manually doing e.g. emerge -1 gentoo-kernel) then the rebuild won't happen.

Or at least, I assume that this is what happened for you.

You still need to rebuild nvidia-drivers in that situation, but portage (or the package manager spec) has no mechanism to make it happen at the moment and it cannot be fixed by the dist-kernel maintainers alone. It could potentially happen in a future EAPI but well.

[linux_os2]

Unfortunately automated rebuilds for modules with USE=dist-kernel only work when the kernel is being updated to a new version (aka works for normal @world updates), if you rebuild the *same* kernel (by manually doing e.g. emerge -1 gentoo-kernel) then the rebuild won't happen.

Or at least, I assume that this is what happened for you.

You still need to rebuild nvidia-drivers in that situation, but portage (or the package manager spec) has no mechanism to make it happen at the moment and it cannot be fixed by the dist-kernel maintainers alone. It could potentially happen in a future EAPI but well.

You are right it was a re-emerge.

Now there is a problem with ugrd se other topic