Nvidia GTX1080 Nvidia Drivers on Umbrel 2.0

Hello,

I’ve installed the new Umbrel 2.0 and it’s working brilliantly. The only problem is that it apparently uses some new Nvidia drivers which don’t support the Nvidia GTX 1080 graphics card – it doesn’t appear as a detected GPU. Is there any way to use older drivers in Umbrel 2.0 so that I can make use of the graphics card?

Many thanks for your help.

hey, the GTX 1080 is part of NVIDIA’s Pascal generation, which has moved to security-only driver updates rather than ongoing feature support. So I wouldn’t count on Umbrel adding out-of-the-box support for it, though that doesn’t mean the card can’t still work with a compatible driver.

If you’re comfortable tinkering, you might wanna look into the pre-start hook. It lets you run custom setup commands before Umbrel starts, including loading drivers, since normal OS changes get reset on reboot. There’s an explanation here: 1.7 FS changes is being reset after reboot · Issue #2124 · getumbrel/umbrel · GitHub

You could experiment with a Pascal-compatible proprietary driver and, if you get it working, use the hook to reapply the setup on boot. I’d test it manually first though, rather than putting a driver installer straight into the hook. Definitely a DIY workaround rather than a guaranteed fix.

Hi everyone! First of all, thank you so much for the initial help and guidance. I’m updating my case because I managed to build the kernel modules with the Tesla 535 drivers, and the GTX 1080 works perfectly, as shown in the terminal output below:

Plaintext

root@umbrel:~# nvidia-smi
Thu Oct 30 14:39:53 2026         
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.274.02             Driver Version: 535.274.02     CUDA Version: 12.2     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf         Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |             MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1080        Off |   00000000:02:00.0 Off |                  N/A |
|  0%   47C    P5           18W /  250W |       0MiB /    8192MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

However, I wanted to share a critical blocker I’ve hit regarding persistence: upon rebooting, it is impossible to maintain the configuration using startup hooks or custom systemd services.

Due to the immutable architecture of umbrelOS (Debian Trixie-based), the root filesystem and module directories (/lib/modules/...) are reset or cleared on every reboot. Even when automating the DKMS rebuild process at boot, it conflicts with the OS lifecycle, stale legacy driver registrations (v550), and read-only system layers, which causes module loading to fail (Invalid argument / No such device).

Has anyone found a way to properly handle umbrelOS’s immutability so that kernel modules or startup scripts survive a reboot without manual intervention? Any insights would be greatly appreciated!

Nice work!

The pre-start script itself should survive if it’s saved at /home/umbrel/umbrel/custom-hooks/pre-start. What doesn’t survive is the driver installation under /usr, /lib/modules, etc. The hook runs again on each boot to recreate those changes, rather than making them permanent.

The catch is that it runs before Umbrel starts, not before the kernel loads drivers. So if the bundled NVIDIA modules are already loaded, installing 535 over them could leave you with conflicting versions. Those errors alone don’t confirm that’s what’s happening, though.

Could you share your hook script, the commands that got 535 working, and the output of these after a failed boot? Remove any passwords or tokens from the script first.

uname -r
cat /proc/driver/nvidia/version
modinfo -F version nvidia
sudo journalctl -u umbrel-custom-pre-start.service -b --no-pager
sudo journalctl -k -b --no-pager | grep -iE 'nvidia|NVRM|nouveau'

That should help distinguish the hook not running from it running and hitting a driver conflict. I’d hold off on rebuilding with DKMS every boot until that’s clearer.

I was able to install drivers for my Tesla P4 GPU and it persists a reboot. However, after updating from Umbrel 2.0.0 to 2.0.1, it did wipe the drivers I installed, so I had to rerun the commands to get the drivers installed again after the update. Future Umbrel updates will likely wipe that too. These are the commands I ran in this order to get it to persist reboots:

sudo rugix-ctrl state overlay force-persist true

sudo apt update (if I dont run this then the next command would fail)

sudo apt install nvidia-driver nvidia-kernel-dkms

sudo reboot

After the reboot, run nvidia-smi and it should work.

Hope this helps!

Hi bdubs96, I wanted to share my experience and thank you for the key tip. After experimenting with various startup scripts and custom hooks (which ultimately failed or proved unreliable for multiple users), I finally confirmed the definitive method to keep NVIDIA drivers fully persistent across reboots on umbrelOS.

The root cause in umbrelOS is its immutable overlay filesystem, which by default resets modifications made to core system directories upon rebooting.

To solve this cleanly and directly (tested and verified on a GTX 1080), here is the exact sequence of commands to execute:

  1. Force filesystem overlay persistence: Bypass the OS immutability so system-level changes are saved to disk:

    Bash

    sudo rugix-ctrl state overlay force-persist true
    
    
  2. Update the package index: (Required step, otherwise the driver installation command will fail):

    Bash

    sudo apt update
    
    
  3. Install the NVIDIA drivers and DKMS kernel modules: Install the official drivers, DKMS autocompilation tools, and system management interface:

    Bash

    sudo apt install -y nvidia-driver nvidia-kernel-dkms nvidia-smi
    
    
  4. Reboot the system:

    Bash

    sudo reboot
    
    

After the server reboots, logging back in via SSH and running nvidia-smi confirms that the GPU is detected properly and remains fully functional.

Important Note: As mentioned by other members, major umbrelOS system updates (such as updating from 2.0.0 to 2.0.1) will likely wipe the overlay layer. If you update your Umbrel version, you will simply need to re-run these four commands to restore your GPU drivers.

Hope this helps anyone looking to run NVIDIA GPUs on Umbrel!

Thank you so much for this. It got my old quadro p2000 working in 2.0. Legacy cards are still great for things like media transcoding so I’d love if they were just natively supported.

Had this working great until I reimaged the system and installed 2.1 Beta 1. :frowning:

In Beta 1 I try to install and get this error, might need to downgrade.

umbrel@umbrel:~$ sudo apt install -y nvidia-driver nvidia-kernel-dkms nvidia-smi

Solving dependencies… Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
nvidia-driver : Depends: nvidia-driver-libs (= 550.163.01-2) but 595.91.07-1 is to be installed
Depends: xserver-xorg-video-nvidia (= 550.163.01-2) but it is not going to be installed
Recommends: nvidia-settings (>= 550) but it is not going to be installed
Recommends: libnvidia-cfg1 (= 550.163.01-2) but 595.91.07-1 is to be installed
nvidia-kernel-dkms : Depends: firmware-nvidia-gsp (= 550.163.01) or
firmware-nvidia-gsp-550.163.01
nvidia-smi : Depends: libnvidia-ml1 (= 550.163.01-2) but 595.91.07-1 is to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:

  1. nvidia-driver:amd64=550.163.01-2 is selected for install
  2. nvidia-driver:amd64=550.163.01-2 Depends nvidia-driver-libs (= 550.163.01-2)
    but none of the choices are installable:
    • nvidia-driver-libs:amd64=550.163.01-2 is not selected for install

Hi,

The next update I plan to install will be 2.1 Final. When it’s available, I’ll try installing the drivers again. I’ll let you know how it goes.

Thanks! much appreciated.