Nvidia on Ubuntu: Difference between revisions

(20 intermediate revisions by 2 users not shown)

Line 1:

Because I wanted to run a local [[Artificial Intelligence]] platform called [[Ollama]], I wanted to ensure that my GPU was fully utilized in the system since GPUs are the particular type of hardware best suited for these [[Vector database|Vector]] calculations. And, I have a 'decent' GPU - [[PC Build 2024#Video Card (GPU)|Nvidia GeForce RTX 4060]] (the best you could get at the ~~time~~). In trying to install the latest Nvidia driver, I set off on a week's long journey of learning, frustration and perseverance discovering the inner workings of Ubuntu 24.04, Xorg, the Linux kernel and kernel modules, DRM, Secure Boot, initramfs and more.

Because I wanted to run a local [[Artificial Intelligence]] platform called [[Ollama]], I wanted to ensure that my GPU was fully utilized in the system since GPUs are the particular type of hardware best suited for these [[Vector database|Vector]] calculations<ref>https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#the-benefits-of-using-gpus</ref>. And, I have a 'decent' GPU - [[PC Build 2024#Video Card (GPU)|Nvidia GeForce RTX 4060]] (the best you could get when I built the system in 2024). In trying to install the latest Nvidia driver, I set off on a week-long journey of learning, frustration and perseverance discovering the inner workings of Ubuntu 24.04, Xorg, the Linux kernel and kernel modules, DRM, Secure Boot, initramfs and more.

I still do not have the Nvidia driver loaded - even after 40+ reboots and attempts. Instead I'm using the Nouveau driver but at least I have a working system and I believe now that I've finally figured out what needs to be done to disable Nouveau and install Nvidia - a project that I ~~might tackle shortly~~. I'm ~~just~~ documenting the things that I ~~encountered~~ in this journey so that I ~~can pick~~ it ~~back up at~~ the right ~~time~~.

I still do not have the Nvidia driver loaded - even after 40+ reboots and attempts. Instead I'm using the Nouveau driver but at least I have a working system and I believe now that I've finally figured out what needs to be done to disable Nouveau and install Nvidia - a project that I am approaching with greater scrutiny now. I'm documenting the things that I encounter in this journey.

Why not just continue to use [https://nouveau.freedesktop.org/index.html Nouveau], a project of the [https://www.freedesktop.org/wiki/ freedesktop] community? I mean "if it ain't broke, don't fix it" - right? In principle, I'd very much like to use nouveau. I'm not even sure that any alternative is "better" in any way - especially since ''I am not a gamer''<ref>I'm not opposed in any way, I just don't have the time to add another hobby. This is a clarifying statement for my use-case, and therefore, requirements.</ref>. My use case is to get the best performance from local LLMs. As I become familiar with the methods to switch video drivers reliably, I intend to run benchmarks and explore the benefits of one configuration vs another.

== Status ==

As of 2025-07-03, I'm still not running with an NVIDIA driver. According to [https://www.reddit.com/r/Ubuntu/comments/1li7wg7/how_do_i_install_nvidiadriver575_correctly/ a Reddit thread] just days ago, it's always been rather messy getting the right system together. I should "upgrade your system either to Ubuntu 25.04 for Wayland experience and no working suspend to RAM, or to 24.04 if you need suspend to RAM, but are Ok with using X11 instead of Wayland."

Since I'm on 24.04, and I've tried using X11 instead of Wayland without success, I plan to ensure my home directory is on its own partition and reinstall the OS to 25.04

== Opposite ==

To go the opposite route, purging all proprietary drivers and installing the open source Nouveau driver, ~~there~~'s a ~~good albeit older tutorial~~ at https://~~linuxconfig~~.org/~~how~~-to-~~uninstall~~-the-nvidia-drivers-on-~~ubuntu~~-20-04-~~focal~~-~~fossa~~-~~linux~~

To go the opposite route, purging all proprietary drivers and installing the open source Nouveau driver, you pretty much just <code>sudo apt install xserver-xorg-video-nouveau</code> You might find seemingly good content/tutorials by linuxconfig, but I'm intentionally not linking to their site or YouTube videos because their content is plausible, but sketchy - IOW, it is Artificial Intelligence '''[[wp:AI slop|slop]]'''. <ref>linuxconfig.org/how-to-install-nvidia-drivers-on-ubuntu-24-04 describes how to get Nvidia drivers working on Ubuntu 24, but curiously refers to deprecated commands like 'ubuntu drivers autoinstall'. They have a whole section where they talk about downloading 'drivers' from Nvidia - but the '.run' files are '''not''' drivers at all, they are installers. And they instruct you to use 'telinit' to switch runlevels when the concept of SysV runlevels is obsolete (and thus so is the command). Granted the telinit command will be transparently translated into systemd unit activation requests, but old, deprecated "howto" is "how '''NOT''' to".</ref>

== About this System ==

In your desktop environment, you can access 'System Settings' -> '[[About this System]]' ([https://docs.kde.org/stable5/en/kinfocenter/kinfocenter/index.html KInfoCenter]) to display basic info about your Software and Hardware environment including the 'graphics processor'. Mine says '''NV197''' - which is the codename given to the card by the Nouveau project<ref>https://nouveau.freedesktop.org/CodeNames.html</ref>. You can click on 'Show More Information' which reveals a multi-tab dialog for OpenCL, OpenGL, Vulkan, Window Manager and X-Server with extensive Graphics info.

Or, you can also get details from a variety of CLI commands like glxinfo, lspci etc.

<code>glxinfo | grep -E "OpenGL version|OpenGL renderer"</code>

'''OpenGL renderer''' string: NV197

'''OpenGL version''' string: 4.3 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1

If you are on a TTY (without a display), <code>lspci</code> shows the same info

<code>lspci | grep VGA</code>

01:00.0 '''VGA''' compatible controller: NVIDIA Corporation AD107 [GeForce RTX 4060] (rev a1)

After the installation of Nvidia drivers fails, you won't have a functioning GPU, since you will no longer have the nouveau driver available either, and so the output of the same glxinfo command will show that "llvmpipe" is the renderer.

'''OpenGL renderer''' string: llvmpipe (LLVM 19.1.1, 256 bits)

'''OpenGL version''' string: 4.5 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1

[https://docs.mesa3d.org/drivers/llvmpipe.html LLVMpipe] is a software rasterizer within the Mesa 3D graphics library that utilizes the LLVM compiler infrastructure to perform rendering entirely on the CPU. It acts as a software fallback when a dedicated GPU or its drivers are unavailable or malfunctioning, allowing OpenGL applications to run without hardware acceleration. Essentially, LLVMpipe takes over the rendering process when the GPU can't or shouldn't be used.

If dpkg shows xserver-xorg-video-'''nouveau is installed''', then you can switch to it from e.g. "Driver Manager" in Settings.

Synaptic will allow you to view drivers, but you won't be able to switch from that interface (you'll get an error message about a lock file).

Although switching drivers from the system settings interface appears to complete without error, I'm not sure how well it works - if at all.

I was getting a broken desktop (single monitor, no good results from things like nvidia-smi) after installing Nvidia drivers, and so I tried switching to nouveau - and it somehow eventually worked. <pre>

apt-get remove -y --purge '^libnvidia-.*' && apt-get remove -y --purge '^nvidia-*' && apt-get remove -y --purge '*575*' && apt -y autoremove

apt -y autoclean

shutdown -r now

(recovery mode)

vim /etc/default/grub

update-grub

</pre>After doing a couple of reboots changing the boot 'modeline' and 'nosplash' options from a recovery console or the TTY, I didn't seem to get anywhere. But when I issued a 'startX' command, and the system booted into the GNOME desktop instead of KDE (?!!??), then I had dual monitors again. Amazingly nvidia-smi returned results, but glxinfo says now that I'm using onboard graphics from the CPU (not the GPU) but it doesn't say LLVMpipe

'''OpenGL renderer''' string: Mesa Intel(R) Graphics ('''RPL-S''')

'''OpenGL version''' string: 4.6 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1<pre>

sudo lsmod|grep -i nvidia

nvidia_uvm 2158592 4

nvidia_drm 139264 5

nvidia_modeset 1736704 6 nvidia_drm

nvidia 11550720 81 nvidia_uvm,nvidia_modeset

ecc 45056 2 ecdh_generic,nvidia

video 77824 3 xe,i915,nvidia_modeset

</pre>Grub right now is 'normal' <pre>

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

</pre>The NVIDIA persistence daemon is running <pre>

systemctl list-units --type service --all | grep nvidia

nvidia-persistenced.service loaded active running NVIDIA Persistence Daemon

</pre>[[DKMS|dkms]] shows that kernel modules are installed for two kernels<pre>

dkms status

nvidia/575.57.08, 6.8.0-60-generic, x86_64: installed (Original modules exist)

nvidia/575.57.08, 6.8.0-62-generic, x86_64: installed (Original modules exist)

</pre>

== GUI is stuck ==

[[File:Proprietary Drivers selection in Software Sources GUI.png|thumb|Unable to select a proprietary driver in "Software Sources"]]If you go into the Graphical User Interface (GUI) for "System Settings" and then "Hardware -> Driver Manager" ~~where~~ it would appear to allow you to simply choose to use a proprietary driver from Nvidia~~, and you find that~~ the choices are ~~all~~ disabled (grayed out)~~, that is because no other driver is found on the system~~. ~~You would need to download a driver through your package manager first. However, the major caveat is that every~~ attempt I made to "install an Nvidia driver" - whether through a graphical package manager like Synaptic, or the CLI using apt or dpkg, would just result in a "non-working" graphics system where I didn't even have dual monitor support. In theory, if you have multiple drivers, the GUI allows you to effortlessly choose and switch between them. In practice, installing a second driver is not possible from a Graphical desktop environment.

[[File:Proprietary Drivers selection in Software Sources GUI.png|thumb|Unable to select a proprietary driver in "Software Sources"]]

In theory, the GUI (see image) allows you to effortlessly choose and switch between multiple drivers. There are even YouTube videos that show how it's supposed to work<ref>I do not want to link to AI-generated content that creates a worse Internet, but this is what I'm refering to www.youtube.com/watch?v=pmGfi1ldBqc The bot doesn't respond to questions, so is my experience different because I have Secure Boot enabled? Is my experience different because something changed in the OS between Ubuntu 20 and Ubuntu 24?</ref>. In practice, at least on my system, installing a second driver is not possible from a Graphical desktop environment.

If you go into the Graphical User Interface (GUI) for "System Settings" and then "Hardware -> Driver Manager" it would appear to allow you to simply choose to use a proprietary driver from Nvidia. But all the choices are disabled (grayed out). Every attempt I made to "install an Nvidia driver" - whether through a graphical package manager like Synaptic, or the CLI using apt or dpkg, would just result in a "non-working" graphics system where I didn't even have dual monitor support.

== X.org ==

Line 82:

Line 154:

== NVidia ==

The installation guide (46 chapters) is at https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/

Documentation for installing NVidia drivers is at https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/

The installation guide for the v570 of the driver (46 chapters) is at https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/

I've read the whole thing.

Line 95:

Line 169:

We explore these in more detail below.

Over at StackExchange, a user asked [https://unix.stackexchange.com/questions/352828/how-to-switch-nvidia-driver-from-nouveau-to-nvidia-proprietary how to switch ~~nvidia~~ driver from nouveau to nvidia ~~proprietary~~] and succeeded in part by '''modifying the boot parameters in grub''' to deny nouveau.

Over at StackExchange, a user asked [https://unix.stackexchange.com/questions/352828/how-to-switch-nvidia-driver-from-nouveau-to-nvidia-proprietary how to switch graphics driver from nouveau to nvidia] and succeeded in part by '''modifying the boot parameters in grub''' to deny nouveau. Note that the boot parameters were used only during the process to stop using one driver and install the other driver. It is not a configuration that would allow you to have two different boot menu entries in GRUB in order to use two graphics modes.

Over in the Manjaro Linux forums, a user asked a similar question: [https://forum.manjaro.org/t/how-do-i-switch-between-nvidia-and-nouveau-drivers-on-boot/92044 How do I switch between Nvidia and Nouveau drivers on boot?] They tried using

<code>modprobe.blacklist=nvidia systemd.setenv=GPUMOD=nouveau rd.driver.blacklist=nvidia nouveau.modeset=1 nvidia.modeset=0</code>

But ultimately had to install the OS twice on different disk partitions in order to choose to boot one system or the other depending on what graphics driver they needed to use.

=== Denylist ===

Line 148:

Line 228:

On systems with Secure Boot enabled (mine), you most likely need to sign the module. See [https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/installdriver.html#modulesigning Signing NVIDIA Kernel Module]. However, I didn't get an explicit message that signing was a problem; and I did see that the installation process signs the module with a generated key. I assume that the MOK process hooks into the trust system somehow.

When troubleshooting keeps turning up mysteries, you have to check your assumptions.<syntaxhighlight lang="text">

sudo modprobe nvidia

modprobe: ERROR: could not insert 'nvidia': Key was rejected by service

</syntaxhighlight>See [[Nvidia on Ubuntu/Kernel modules|Kernel modules]]

== Tools and Troubleshooting ==

Ubuntu wants you to use the '[[Nvidia on Ubuntu/ubuntu-drivers|ubuntu-drivers]]' tool<ref>https://documentation.ubuntu.com/server/how-to/graphics/install-nvidia-drivers/</ref>.

NVIDIA seems to just settled on a new mechanism<ref>https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/</ref> rather than downloading the (former?) .run installers: <code>wget <nowiki>https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/x86_64/cuda-keyring_1.1-1_all.deb</nowiki> dpkg -i cuda-keyring_1.1-1_all.deb apt update</code> <code>apt install nvidia-open</code>

NVIDIA distributes a script called <code>nvidia-bug-report.sh</code> that you can and should run<ref>https://forums.developer.nvidia.com/t/if-you-have-a-problem-please-read-this-first/27131

</ref> to collect detailed information about any problems.

== Interesting Notes ==

Usually, when you have 'sudo' or root privileges you can do '''more'''. One exception is the X-Server. Root access to the server may be restricted. In that case,

<code>glxinfo</code>

will give

Error: unable to open display

A regular user will have no problem running <code>glxinfo</code>.

=== Different Desktop Environments ===

As a regular user, my DE is KDE Plasma (using Kubuntu) rather than the GNOME default of Ubuntu

~~=== See Also ===~~

* [[{{~~PAGENAMEE~~}}~~/ubuntu-drivers|ubuntu-drivers (command)]]~~

@@ Line 1: / Line 1: @@
-Because I wanted to run a local [[Artificial Intelligence]] platform called [[Ollama]], I wanted to ensure that my GPU was fully utilized in the system since GPUs are the particular type of hardware best suited for these [[Vector database|Vector]] calculations. And, I have a 'decent' GPU - [[PC Build 2024#Video Card (GPU)|Nvidia GeForce RTX 4060]] (the best you could get at the time). In trying to install the latest Nvidia driver, I set off on a week's long journey of learning, frustration and perseverance discovering the inner workings of Ubuntu 24.04, Xorg, the Linux kernel and kernel modules, DRM, Secure Boot, initramfs and more.
+Because I wanted to run a local [[Artificial Intelligence]] platform called [[Ollama]], I wanted to ensure that my GPU was fully utilized in the system since GPUs are the particular type of hardware best suited for these [[Vector database|Vector]] calculations<ref>https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#the-benefits-of-using-gpus</ref>. And, I have a 'decent' GPU - [[PC Build 2024#Video Card (GPU)|Nvidia GeForce RTX 4060]] (the best you could get when I built the system in 2024). In trying to install the latest Nvidia driver, I set off on a week-long journey of learning, frustration and perseverance discovering the inner workings of Ubuntu 24.04, Xorg, the Linux kernel and kernel modules, DRM, Secure Boot, initramfs and more.
-I still do not have the Nvidia driver loaded - even after 40+ reboots and attempts. Instead I'm using the Nouveau driver but at least I have a working system and I believe now that I've finally figured out what needs to be done to disable Nouveau and install Nvidia - a project that I might tackle shortly. I'm just documenting the things that I encountered in this journey so that I can pick it back up at the right time.
+I still do not have the Nvidia driver loaded - even after 40+ reboots and attempts. Instead I'm using the Nouveau driver but at least I have a working system and I believe now that I've finally figured out what needs to be done to disable Nouveau and install Nvidia - a project that I am approaching with greater scrutiny now. I'm documenting the things that I encounter in this journey.
+Why not just continue to use [https://nouveau.freedesktop.org/index.html Nouveau], a project of the [https://www.freedesktop.org/wiki/ freedesktop] community? I mean "if it ain't broke, don't fix it" - right? In principle, I'd very much like to use nouveau. I'm not even sure that any alternative is "better" in any way - especially since ''I am not a gamer''<ref>I'm not opposed in any way, I just don't have the time to add another hobby. This is a clarifying statement for my use-case, and therefore, requirements.</ref>. My use case is to get the best performance from local LLMs. As I become familiar with the methods to switch video drivers reliably, I intend to run benchmarks and explore the benefits of one configuration vs another.
+== Status ==
+As of 2025-07-03, I'm still not running with an NVIDIA driver. According to [https://www.reddit.com/r/Ubuntu/comments/1li7wg7/how_do_i_install_nvidiadriver575_correctly/ a Reddit thread] just days ago, it's always been rather messy getting the right system together. I should "upgrade your system either to Ubuntu 25.04 for Wayland experience and no working suspend to RAM, or to 24.04 if you need suspend to RAM, but are Ok with using X11 instead of Wayland."
+Since I'm on 24.04, and I've tried using X11 instead of Wayland without success, I plan to ensure my home directory is on its own partition and reinstall the OS to 25.04
 == Opposite ==
-To go the opposite route, purging all proprietary drivers and installing the open source Nouveau driver, there's a good albeit older tutorial at https://linuxconfig.org/how-to-uninstall-the-nvidia-drivers-on-ubuntu-20-04-focal-fossa-linux
+To go the opposite route, purging all proprietary drivers and installing the open source Nouveau driver, you pretty much just <code>sudo apt install xserver-xorg-video-nouveau</code> You might find seemingly good content/tutorials by linuxconfig, but I'm intentionally not linking to their site or YouTube videos because their content is plausible, but sketchy - IOW, it is Artificial Intelligence '''[[wp:AI slop|slop]]'''. <ref>linuxconfig.org/how-to-install-nvidia-drivers-on-ubuntu-24-04 describes how to get Nvidia drivers working on Ubuntu 24, but curiously refers to deprecated commands like 'ubuntu drivers autoinstall'. They have a whole section where they talk about downloading 'drivers' from Nvidia - but the '.run' files are '''not''' drivers at all, they are installers. And they instruct you to use 'telinit' to switch runlevels when the concept of SysV runlevels is obsolete (and thus so is the command). Granted the telinit command will be transparently translated into systemd unit activation requests, but old, deprecated "howto" is "how '''NOT''' to".</ref>
+== About this System ==
+In your desktop environment, you can access 'System Settings' -> '[[About this System]]' ([https://docs.kde.org/stable5/en/kinfocenter/kinfocenter/index.html KInfoCenter]) to display basic info about your Software and Hardware environment including the 'graphics processor'. Mine says '''NV197''' - which is the codename given to the card by the Nouveau project<ref>https://nouveau.freedesktop.org/CodeNames.html</ref>. You can click on 'Show More Information' which reveals a multi-tab dialog for OpenCL, OpenGL, Vulkan, Window Manager and X-Server with extensive Graphics info.
+Or, you can also get details from a variety of CLI commands like glxinfo, lspci etc.
+<code>glxinfo | grep -E "OpenGL version|OpenGL renderer"</code>
+'''OpenGL renderer''' string: NV197
+'''OpenGL version''' string: 4.3 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1
+If you are on a TTY (without a display), <code>lspci</code> shows the same info
+<code>lspci | grep VGA</code>
+:00.0 '''VGA''' compatible controller: NVIDIA Corporation AD107 [GeForce RTX 4060] (rev a1)
+After the installation of Nvidia drivers fails, you won't have a functioning GPU, since you will no longer have the nouveau driver available either, and so the output of the same glxinfo command will show that "llvmpipe" is the renderer.
+'''OpenGL renderer''' string: llvmpipe (LLVM 19.1.1, 256 bits)
+'''OpenGL version''' string: 4.5 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1
+[https://docs.mesa3d.org/drivers/llvmpipe.html LLVMpipe] is a software rasterizer within the Mesa 3D graphics library that utilizes the LLVM compiler infrastructure to perform rendering entirely on the CPU. It acts as a software fallback when a dedicated GPU or its drivers are unavailable or malfunctioning, allowing OpenGL applications to run without hardware acceleration. Essentially, LLVMpipe takes over the rendering process when the GPU can't or shouldn't be used.
+If dpkg shows xserver-xorg-video-'''nouveau is installed''', then you can switch to it from e.g. "Driver Manager" in Settings.
+Synaptic will allow you to view drivers, but you won't be able to switch from that interface (you'll get an error message about a lock file).
+Although switching drivers from the system settings interface appears to complete without error, I'm not sure how well it works - if at all.
+I was getting a broken desktop (single monitor, no good results from things like nvidia-smi) after installing Nvidia drivers, and so I tried switching to nouveau - and it somehow eventually worked.  <pre>
+apt-get remove -y --purge '^libnvidia-.*' && apt-get remove -y --purge '^nvidia-*' && apt-get remove -y --purge '*575*' && apt -y autoremove
+apt -y autoclean
+shutdown -r now
+(recovery mode)
+vim /etc/default/grub
+update-grub
+</pre>After doing a couple of reboots changing the boot 'modeline' and 'nosplash' options from a recovery console or the TTY, I didn't seem to get anywhere. But when I issued a 'startX' command, and the system booted into the GNOME desktop instead of KDE (?!!??), then I had dual monitors again. Amazingly nvidia-smi returned results, but glxinfo says now that I'm using onboard graphics from the CPU (not the GPU) but it doesn't say LLVMpipe
+'''OpenGL renderer''' string: Mesa Intel(R) Graphics ('''RPL-S''')
+'''OpenGL version''' string: 4.6 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1<pre>
+sudo lsmod|grep -i nvidia
+nvidia_uvm           2158592  4
+nvidia_drm            139264  5
+nvidia_modeset       1736704  6 nvidia_drm
+nvidia              11550720  81 nvidia_uvm,nvidia_modeset
+ecc                    45056  2 ecdh_generic,nvidia
+video                  77824  3 xe,i915,nvidia_modeset
+</pre>Grub right now is 'normal'  <pre>
+GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
+</pre>The NVIDIA persistence daemon is running <pre>
+systemctl list-units --type service --all | grep nvidia
+  nvidia-persistenced.service                           loaded    active     running      NVIDIA Persistence Daemon
+</pre>[[DKMS|dkms]] shows that kernel modules are installed for two kernels<pre>
+dkms status
+nvidia/575.57.08, 6.8.0-60-generic, x86_64: installed (Original modules exist)
+nvidia/575.57.08, 6.8.0-62-generic, x86_64: installed (Original modules exist)
+</pre>
 == GUI is stuck ==
-[[File:Proprietary Drivers selection in Software Sources GUI.png|thumb|Unable to select a proprietary driver in "Software Sources"]]If you go into the Graphical User Interface (GUI) for "System Settings" and then "Hardware -> Driver Manager" where it would appear to allow you to simply choose to use a proprietary driver from Nvidia, and you find that the choices are all disabled (grayed out), that is because no other driver is found on the system. You would need to download a driver through your package manager first. However, the major caveat is that every attempt I made to "install an Nvidia driver" - whether through a graphical package manager like Synaptic, or the CLI using apt or dpkg, would just result in a "non-working" graphics system where I didn't even have dual monitor support. In theory, if you have multiple drivers, the GUI allows you to effortlessly choose and switch between them. In practice, installing a second driver is not possible from a Graphical desktop environment.
+[[File:Proprietary Drivers selection in Software Sources GUI.png|thumb|Unable to select a proprietary driver in "Software Sources"]]
+In theory, the GUI (see image) allows you to effortlessly choose and switch between multiple drivers. There are even YouTube videos that show how it's supposed to work<ref>I do not want to link to AI-generated content that creates a worse Internet, but this is what I'm refering to www.youtube.com/watch?v=pmGfi1ldBqc The bot doesn't respond to questions, so is my experience different because I have Secure Boot enabled? Is my experience different because something changed in the OS between Ubuntu 20 and Ubuntu 24?</ref>. In practice, at least on my system, installing a second driver is not possible from a Graphical desktop environment.
+If you go into the Graphical User Interface (GUI) for "System Settings" and then "Hardware -> Driver Manager" it would appear to allow you to simply choose to use a proprietary driver from Nvidia. But all the choices are disabled (grayed out). Every attempt I made to "install an Nvidia driver" - whether through a graphical package manager like Synaptic, or the CLI using apt or dpkg, would just result in a "non-working" graphics system where I didn't even have dual monitor support.
 == X.org ==
@@ Line 82: / Line 154: @@
 == NVidia ==
-The installation guide (46 chapters) is at https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/
+Documentation for installing NVidia drivers is at https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/
+The installation guide for the v570 of the driver (46 chapters) is at https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/
 I've read the whole thing.
@@ Line 95: / Line 169: @@
 We explore these in more detail below.
-Over at StackExchange, a user asked [https://unix.stackexchange.com/questions/352828/how-to-switch-nvidia-driver-from-nouveau-to-nvidia-proprietary how to switch nvidia driver from nouveau to nvidia proprietary] and succeeded in part by '''modifying the boot parameters in grub''' to deny nouveau.
+Over at StackExchange, a user asked [https://unix.stackexchange.com/questions/352828/how-to-switch-nvidia-driver-from-nouveau-to-nvidia-proprietary how to switch graphics driver from nouveau to nvidia] and succeeded in part by '''modifying the boot parameters in grub''' to deny nouveau. Note that the boot parameters were used only during the process to stop using one driver and install the other driver. It is not a configuration that would allow you to have two different boot menu entries in GRUB in order to use two graphics modes.
+Over in the Manjaro Linux forums, a user asked a similar question: [https://forum.manjaro.org/t/how-do-i-switch-between-nvidia-and-nouveau-drivers-on-boot/92044 How do I switch between Nvidia and Nouveau drivers on boot?] They tried using
+<code>modprobe.blacklist=nvidia systemd.setenv=GPUMOD=nouveau rd.driver.blacklist=nvidia nouveau.modeset=1 nvidia.modeset=0</code>
+But ultimately had to install the OS twice on different disk partitions in order to choose to boot one system or the other depending on what graphics driver they needed to use.
 === Denylist ===
@@ Line 148: / Line 228: @@
 On systems with Secure Boot enabled (mine), you most likely need to sign the module. See [https://download.nvidia.com/XFree86/Linux-x86_64/570.153.02/README/installdriver.html#modulesigning Signing NVIDIA Kernel Module]. However, I didn't get an explicit message that signing was a problem; and I did see that the installation process signs the module with a generated key. I assume that the MOK process hooks into the trust system somehow.
+When troubleshooting keeps turning up mysteries, you have to check your assumptions.<syntaxhighlight lang="text">
+sudo modprobe nvidia
+modprobe: ERROR: could not insert 'nvidia': Key was rejected by service
+</syntaxhighlight>See [[Nvidia on Ubuntu/Kernel modules|Kernel modules]]
+== Tools and Troubleshooting ==
+Ubuntu wants you to use the '[[Nvidia on Ubuntu/ubuntu-drivers|ubuntu-drivers]]' tool<ref>https://documentation.ubuntu.com/server/how-to/graphics/install-nvidia-drivers/</ref>.
+NVIDIA seems to just settled on a new mechanism<ref>https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/</ref> rather than downloading the (former?) .run installers:  <code>wget <nowiki>https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/x86_64/cuda-keyring_1.1-1_all.deb</nowiki> dpkg -i cuda-keyring_1.1-1_all.deb apt update</code> <code>apt install nvidia-open</code>
+NVIDIA distributes a script called <code>nvidia-bug-report.sh</code> that you can and should run<ref>https://forums.developer.nvidia.com/t/if-you-have-a-problem-please-read-this-first/27131
+</ref> to collect detailed information about any problems.
+== Interesting Notes ==
+Usually, when you have 'sudo' or root privileges you can do '''more'''. One exception is the X-Server. Root access to the server may be restricted. In that case,
+<code>glxinfo</code>
+will give
+ Error: unable to open display
+A regular user will have no problem running <code>glxinfo</code>.
+=== Different Desktop Environments ===
+As a regular user, my DE is KDE Plasma (using Kubuntu) rather than the GNOME default of Ubuntu
+{{Subpages|}}
-=== See Also ===
+{{References}}
-* [[{{PAGENAMEE}}/ubuntu-drivers|ubuntu-drivers (command)]]