There are some rumblings about this when doing a web search, but nothing substantive jumps out.
I need to switch to linux-image-rt/oldstable and it seems nvidia-current-dkms is incompatible. Any elegant path forward?
I'd hate to have to jump to manual driver build from the nvidia vendor website.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
SOLVED: nvidia-current-dkms and "RT" kernel
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
SOLVED: nvidia-current-dkms and "RT" kernel
Last edited by kent_dorfman766 on 2024-02-27 17:41, edited 1 time in total.
- sunrat
- Administrator
- Posts: 6511
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 119 times
- Been thanked: 489 times
Re: nvidia-current-dkms and "RT" kernel
Nvidia has never built on RT kernels afaik. There's a check in the build script which blocks it. You can override it with:
before installing a kernel or nvidia driver.
I'm interested to hear why you want to install an RT kernel. They may be useful in an industrial engineering setting but can be a problem for general purpose use. I tried several for audio production a while back but got better results with a Liquorix kernel which is default configured for low latency. Even stock kernels since 5.19 have been capable of full pre-emption by adding the kernel boot option preempt=full.
Code: Select all
export IGNORE_PREEMPT_RT_PRESENCE=1
I'm interested to hear why you want to install an RT kernel. They may be useful in an industrial engineering setting but can be a problem for general purpose use. I tried several for audio production a while back but got better results with a Liquorix kernel which is default configured for low latency. Even stock kernels since 5.19 have been capable of full pre-emption by adding the kernel boot option preempt=full.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: nvidia-current-dkms and "RT" kernel
IMHO, the linux kernel has never handled IO channel bottlenecks well, and it seems to have gotten worse the more they try to genericise a kernel "for general use" by playing with newer more complicated schedulers. RT is an experiment to see if the occasional "mouse freeze" or system lag during disk IO goes away or gets better.
Also, my simulation projects are easier to metric if I can measure and mimimize kernel latency in a more deterministic way.
Back when I genned my own kernels 4.x and usually build nvidia drivers from vendor source, I did use rt patches with nvidia drivers but yes, there seems to be some online discussion about nvidia not playing well in that environment.
Will try to hack the dkms build using the env var you mention and see what happens.
Thanks!
Also, my simulation projects are easier to metric if I can measure and mimimize kernel latency in a more deterministic way.
Back when I genned my own kernels 4.x and usually build nvidia drivers from vendor source, I did use rt patches with nvidia drivers but yes, there seems to be some online discussion about nvidia not playing well in that environment.
Will try to hack the dkms build using the env var you mention and see what happens.
Thanks!
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: nvidia-current-dkms and "RT" kernel
FWIW, the symbol export previously suggested just changed the error message to:
and I'm not inclined to start hacking the dkms module build scripts, so I guess it's a dead issue unless I get really bored.
An interesting anomoly is that the referenced /var/lib/dkms/... directory doesn't even exist. I wonder if the debian installation script was "lacking by design" since they don't want to install under RT anyways.
Thx!
Code: Select all
root@files:/usr/src# export IGNORE_PREEMPT_RT_PRESENCE=1
root@files:/usr/src# dkms build nvidia-current/470.223.02 -k 5.10.0-28-rt-amd64/x86_64 --kernelsourcedir /usr/src/linux-headers-5.10.0-28-rt-amd64
Error! The /var/lib/dkms/nvidia-current/470.223.02/5.10.0-28-rt-amd64/x86_64/dkms.conf for module nvidia-current includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
An interesting anomoly is that the referenced /var/lib/dkms/... directory doesn't even exist. I wonder if the debian installation script was "lacking by design" since they don't want to install under RT anyways.
Thx!
- stevepusser
- Posts: 12930
- Joined: 2009-10-06 05:53
- Has thanked: 41 times
- Been thanked: 72 times
Re: SOLVED: nvidia-current-dkms and "RT" kernel
Liquorix is fine for low latency I/O for demanding audio/video work; have you at least tried it?
The latest Liquorix kernels are not being built for Bullseye/oldstable since the developer switched to using zstd kernel and module compression, but I continue to do so for MX Linux by reverting to xz for that.
The latest Liquorix kernels are not being built for Bullseye/oldstable since the developer switched to using zstd kernel and module compression, but I continue to do so for MX Linux by reverting to xz for that.
MX Linux packager and developer
- sunrat
- Administrator
- Posts: 6511
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 119 times
- Been thanked: 489 times
Re: nvidia-current-dkms and "RT" kernel
I never tried building it from source. It worked last time (which was when Bullseye was Testing) just by setting the environment variable and apt install nvidia-driver. nvidia-tesla-470-driver is in Debian repo so no need to build from source. I read somewhere they plan to drop the "tesla" moniker soon which is good as it's confusing.kent_dorfman766 wrote: ↑2024-02-27 17:40 FWIW, the symbol export previously suggested just changed the error message to:
Code: Select all
root@files:/usr/src# export IGNORE_PREEMPT_RT_PRESENCE=1 root@files:/usr/src# dkms build nvidia-current/470.223.02 -k 5.10.0-28-rt-amd64/x86_64 --kernelsourcedir /usr/src/linux-headers-5.10.0-28-rt-amd64 Error! The /var/lib/dkms/nvidia-current/470.223.02/5.10.0-28-rt-amd64/x86_64/dkms.conf for module nvidia-current includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built.
Also +1 what Stevo said about Liquorix, they are well worth trying for improved latency and some other performance tweaks. Only kernel I have used for years.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: SOLVED: nvidia-current-dkms and "RT" kernel
I've not played with it, but intend to review it now that I'm aware.stevepusser wrote: ↑2024-02-27 22:52 Liquorix is fine for low latency I/O for demanding audio/video work; have you at least tried it?