| View previous topic :: View next topic |
| Author |
Message |
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 263
Location: Zedelgem Belgium
|
 Posted: Thu Feb 20, 2025 10:39 am Post subject: emerge gentoo-kernel installkernel not rebuilding nvidia-dri |
 |
|
First time using installkernel to build new kernel.
/etc/portage/make.conf:
| Code: | ....
....
USE="cups perl_features_ithreads dist-kernel"
...
... |
/etc/portage/package.use:
| Code: | | sys-kernel/installkernel grub dracut -systemd |
x11-drivers/nvidia-drivers are not rebuild |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23123
|
| Posted: Thu Feb 20, 2025 2:33 pm Post subject: |
|
|
| 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? |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 263
Location: Zedelgem Belgium
|
| Posted: Thu Feb 20, 2025 3:13 pm Post subject: |
|
|
| Hu wrote: | | 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:
| Quote: | * 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. |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2898
|
| Posted: Fri Feb 21, 2025 10:02 am Post subject: |
|
|
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. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 263
Location: Zedelgem Belgium
|
| Posted: Fri Feb 21, 2025 1:49 pm Post subject: |
|
|
| Ionen wrote: | 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 |
|
| Back to top |
|
|
|
Kernel & Hardware
