Nvidia with toolbx

Ask Fedora
, , , , , ,
1

Okey

I saw this issue today when using toolbx fedora 41 with kde F41 where everything works as should, but not dGPU Nvidia…

I was spending some minutes to figure out where is the issue and not sure is there already automated nvidia-container-toolkit on host where it actually enables host Nvidia drivers to containers to be used.

The what I was doing I had to enable rpm-fusion repos and install Nvidia drivers, but on container I can’t install drivers with CUDA all CUDA drivers and packages failed.

Also I had to install nvidia-container-toolkit on container too to get dGPU actually working on graphics demanding apps DaVinci Resolve was on this test and VScode was another where I need to have dGPU for 3D development and rendering

Host system is F41 kinoite with optimus hybrid setup and all apps are flatpaks or inside toolbx as is development environments.

Inside toolbx terminal it still shows nvidia-smi etc when using system terminal, but if I use bscode terminal it is more containerized example is VScode is installed as flatpak and connected to toolbx container where I do all development creating directories and cloning repos shows only on container when using VScode terminal, but if I use system terminal inside toolbx and creating directories and cloning repos those actually shows on host

1 Like
2

Added container, kde-plasma, kinoite, nvidia, toolbx

3

Added atomic-desktops, podman

4

Today i ran into a similar issue, vulkaninfo shows only the llvmpipe GPU in a fresh created toolbx:
vulkaninfo --summary

(...)
Devices:
========
GPU0:
	apiVersion         = 1.3.296
	driverVersion      = 0.0.1
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 19.1.5, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 24.3.3 (LLVM 19.1.5)
	conformanceVersion = 1.3.1.1
	deviceUUID         = 6d657361-3234-2e33-2e33-000000000000
	driverUUID         = 6c6c766d-7069-7065-5555-494400000000

but i got it running by downloading the nvidia Drivers directly from nvidia and installed it inside the toolbx with this commands:
wget https://us.download.nvidia.com/XFree86/Linux-x86_64/565.57.01/NVIDIA-Linux-x86_64-565.57.01.run

sudo ./NVIDIA-Linux-x86_64-565.57.01.run -s --no-kernel-modules --no-x-check --no-check-for-alternate-installs --skip-module-load --skip-depmod --no-rebuild-initramfs --no-questions --no-systemd --no-kernel-module-source --no-dkms

this will throw lots of errors complaining files couldn’t be deleted. just ignore them all
After this, my GPU was found:

Devices:
========
GPU0:
	apiVersion         = 1.3.289
	driverVersion      = 565.77.0.0
	vendorID           = 0x10de
	deviceID           = 0x2420
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce RTX 3080 Ti Laptop GPU
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 565.77
	conformanceVersion = 1.3.8.2
	deviceUUID         = 7d778413-ae77-a694-2456-15d319fde8da
	driverUUID         = 5d948742-de2b-5e32-9692-c2a5621aed9a
GPU1:
	apiVersion         = 1.3.296
	driverVersion      = 0.0.1
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 19.1.5, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 24.3.3 (LLVM 19.1.5)
	conformanceVersion = 1.3.1.1
	deviceUUID         = 6d657361-3234-2e33-2e33-000000000000
	driverUUID         = 6c6c766d-7069-7065-5555-494400000000

now my wine app inside toolbx is running fine.

i hope this will help you.

Please note: the version downloaded must match the version of the driver installed on the host. if you update the drivers on the host, you must also update them in the Toolbx.

1 Like
5

Curious how this acts over time

6

We will see,

on older Fedora releases I only installed “akmod-nvidia” through rpmfusion inside the Toolbx and it works, iirc.

but i don’t care, if there something nasty going on inside the Toolbx, i would just throw them away and start over.