** Description changed: [ Impact ] - * Providing nvidia-fs-dkms as an additional package requires + * Providing nvidia-fs-dkms as an additional package requires additional care and maintenance, it also has introduced package conflicts with the nvidia-fs-dkms in the cuda repo. This is a proof of concept of adding the nvidia-fs driver as a kernel module that is compiled with the Linux kernel. When using the Ubuntu packaging the nvidia-fs.ko is added as part of linux-modules-extra, which simplifies the build process. - *The nvidia-fs module does have a dependency on the nvidia driver + *The nvidia-fs module does have a dependency on the nvidia driver headers(nv_p2p.h). Since this makes the nvidia driver a kernel build dependency, it also requires the use of the 'KBUILD_MODPOST_WARN=1' flag. Without this flag, kbuild will error out when it identifies an external dependency. - [ Test Plan ] - *Make sure linux-modules-extra is installed and modinfo/modprobe + *Make sure linux-modules-extra is installed and modinfo/modprobe nvidia-fs - [ Where problems could occur ] - *As mentioned above this does add an nvidia driver dependency on a + *As mentioned above this does add an nvidia driver dependency on a kernel build, the linux-main debian/control file already addresses this with a build-depends on the nvidia driver, but if a user is just running a 'make modules' they would need to have the nvidia driver/headers installed for the build to be successful. - *There is an issue with trying to add to linux-modules instead of + *Another caveat with the nvidia driver dependency is that nvidia-fs + has to be a module and not a built-in ie CONFIG_NVIDIA_FS=m instead of + CONFIG_NVIDIA_FS=y + + *There is an issue with trying to add to linux-modules instead of -extra. The linux-modules package will a do a depmod on the included modules, this fails in a chroot environment because the nvidia driver does not successfully install in a chroot. Below is a snippet of the error when installing nvidia-dkms-570-server-open in a chroot Setting up kmod (31+20240202-2ubuntu7.1) ... sed: can't read /etc/modules: No such file or directory Setting up dkms (3.0.11-1ubuntu13) ... Setting up nvidia-kernel-source-570-server-open (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-firmware-570-server-570.158.01 (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-kernel-common-570-server (570.158.01-0ubuntu0.24.04.1) ... Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service → /usr/lib/systemd/system/nvidia-hibernate.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service → /usr/lib/systemd/system/nvidia-suspend.service. Setting up nvidia-dkms-570-server-open (570.158.01-0ubuntu0.24.04.1) ... WARNING: unsupported arch: arm64 Loading new nvidia-570.158.01 DKMS files... It is likely that 6.14.0-1008-nvidia belongs to a chroot's host - Building for + Building for Building for architecture arm64 Processing triggers for libc-bin (2.39-0ubuntu8) ... In order to add nvidia-fs to linux-modules we would need to either fix the nvidia driver dkms building in a chroot or ignore/skip the depmod check on the nvidia-fs.ko.
** Description changed: [ Impact ] * Providing nvidia-fs-dkms as an additional package requires additional care and maintenance, it also has introduced package conflicts with the nvidia-fs-dkms in the cuda repo. This is a proof of concept of adding the nvidia-fs driver as a kernel module that is compiled with the Linux kernel. When using the Ubuntu packaging the nvidia-fs.ko is added as part of linux-modules-extra, which simplifies the build process. - *The nvidia-fs module does have a dependency on the nvidia driver + * The nvidia-fs module does have a dependency on the nvidia driver headers(nv_p2p.h). Since this makes the nvidia driver a kernel build dependency, it also requires the use of the 'KBUILD_MODPOST_WARN=1' flag. Without this flag, kbuild will error out when it identifies an external dependency. [ Test Plan ] - *Make sure linux-modules-extra is installed and modinfo/modprobe + * Make sure linux-modules-extra is installed and modinfo/modprobe nvidia-fs [ Where problems could occur ] - *As mentioned above this does add an nvidia driver dependency on a + * As mentioned above this does add an nvidia driver dependency on a kernel build, the linux-main debian/control file already addresses this with a build-depends on the nvidia driver, but if a user is just running a 'make modules' they would need to have the nvidia driver/headers installed for the build to be successful. - *Another caveat with the nvidia driver dependency is that nvidia-fs + * Another caveat with the nvidia driver dependency is that nvidia-fs has to be a module and not a built-in ie CONFIG_NVIDIA_FS=m instead of CONFIG_NVIDIA_FS=y - *There is an issue with trying to add to linux-modules instead of + * There is an issue with trying to add to linux-modules instead of -extra. The linux-modules package will a do a depmod on the included modules, this fails in a chroot environment because the nvidia driver does not successfully install in a chroot. Below is a snippet of the error when installing nvidia-dkms-570-server-open in a chroot Setting up kmod (31+20240202-2ubuntu7.1) ... sed: can't read /etc/modules: No such file or directory Setting up dkms (3.0.11-1ubuntu13) ... Setting up nvidia-kernel-source-570-server-open (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-firmware-570-server-570.158.01 (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-kernel-common-570-server (570.158.01-0ubuntu0.24.04.1) ... Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service → /usr/lib/systemd/system/nvidia-hibernate.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service → /usr/lib/systemd/system/nvidia-suspend.service. Setting up nvidia-dkms-570-server-open (570.158.01-0ubuntu0.24.04.1) ... WARNING: unsupported arch: arm64 Loading new nvidia-570.158.01 DKMS files... It is likely that 6.14.0-1008-nvidia belongs to a chroot's host Building for Building for architecture arm64 Processing triggers for libc-bin (2.39-0ubuntu8) ... In order to add nvidia-fs to linux-modules we would need to either fix the nvidia driver dkms building in a chroot or ignore/skip the depmod check on the nvidia-fs.ko. + + [ Other Info ] + + * https://github.com/NVIDIA/gds-nvidia-fs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.14 in Ubuntu. https://bugs.launchpad.net/bugs/2119679 Title: Add nvidia-fs as an in tree module Status in linux-nvidia-6.14 package in Ubuntu: New Bug description: [ Impact ] * Providing nvidia-fs-dkms as an additional package requires additional care and maintenance, it also has introduced package conflicts with the nvidia-fs-dkms in the cuda repo. This is a proof of concept of adding the nvidia-fs driver as a kernel module that is compiled with the Linux kernel. When using the Ubuntu packaging the nvidia-fs.ko is added as part of linux-modules-extra, which simplifies the build process. * The nvidia-fs module does have a dependency on the nvidia driver headers(nv_p2p.h). Since this makes the nvidia driver a kernel build dependency, it also requires the use of the 'KBUILD_MODPOST_WARN=1' flag. Without this flag, kbuild will error out when it identifies an external dependency. [ Test Plan ] * Make sure linux-modules-extra is installed and modinfo/modprobe nvidia-fs [ Where problems could occur ] * As mentioned above this does add an nvidia driver dependency on a kernel build, the linux-main debian/control file already addresses this with a build-depends on the nvidia driver, but if a user is just running a 'make modules' they would need to have the nvidia driver/headers installed for the build to be successful. * Another caveat with the nvidia driver dependency is that nvidia-fs has to be a module and not a built-in ie CONFIG_NVIDIA_FS=m instead of CONFIG_NVIDIA_FS=y * There is an issue with trying to add to linux-modules instead of -extra. The linux-modules package will a do a depmod on the included modules, this fails in a chroot environment because the nvidia driver does not successfully install in a chroot. Below is a snippet of the error when installing nvidia-dkms-570-server-open in a chroot Setting up kmod (31+20240202-2ubuntu7.1) ... sed: can't read /etc/modules: No such file or directory Setting up dkms (3.0.11-1ubuntu13) ... Setting up nvidia-kernel-source-570-server-open (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-firmware-570-server-570.158.01 (570.158.01-0ubuntu0.24.04.1) ... Setting up nvidia-kernel-common-570-server (570.158.01-0ubuntu0.24.04.1) ... Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service → /usr/lib/systemd/system/nvidia-hibernate.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service. Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service → /usr/lib/systemd/system/nvidia-suspend.service. Setting up nvidia-dkms-570-server-open (570.158.01-0ubuntu0.24.04.1) ... WARNING: unsupported arch: arm64 Loading new nvidia-570.158.01 DKMS files... It is likely that 6.14.0-1008-nvidia belongs to a chroot's host Building for Building for architecture arm64 Processing triggers for libc-bin (2.39-0ubuntu8) ... In order to add nvidia-fs to linux-modules we would need to either fix the nvidia driver dkms building in a chroot or ignore/skip the depmod check on the nvidia-fs.ko. [ Other Info ] * https://github.com/NVIDIA/gds-nvidia-fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.14/+bug/2119679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
