NVIDIA Troubles with Endeavour OS Neo install

I have a HTPC desktop machine running NVIDIA RTX 3070. I have run Endeavour OS on this before but have been distrohopping in recent times trying Fedora, Mint among others. Eventually, decided that I like EndeavourOS the best especially the rolling release nature of staying up-to-date. So, I just re-formatted and installed eOS fresh on my desktop. Live media booted and installed fine. The trouble begins when I install the NVIDIA drivers. Everytime NVIDIA drivers are installed (using nvidia-inst), the system no longer boots graphical and I just never seem to be able to get systemd to put me into runlevel 3, so I just keep going back to reformatting and reinstalling and trying something slightly different to try to get the drivers to work. My trials so far:

  1. Online version of the install with GNOME DE - failed to boot after installing nvidia via nvidia-inst
  2. Offline version of the install with KDE - same failure
  3. Trying the online version of the install with KDE at the moment.

I am looking for some help in figuring out 2 main things:

  1. How to consistently install NVIDIA drivers?
  2. If that fails, how to get to non-graphical target in systemd so that I can actually look into further debugging/providing logs, uninstall what didn’t work, try something else without having to start over every time?

My apologies if the information here is insufficient or similar to other such posts. I was on Mint earlier and that did handle the NVIDIA install a whole lot better but that is probably the only positive I would state for Mint over eOS. Please help! Thanks.

1 Like

Welcome to the forum!

For starters, could you show some details about your graphics hardware (a terminal command):

inxi -Gza | eos-sendlog

Please show the returned address here.

If your install does not boot, use the USB installer to run the command.

https://0x0.st/Xhes.txt

I see the resolution is set to 4K (TV resolution), yet the log is showing 1920x1080. Not sure why or if it is relevant.

I assume you run nvidia-inst without any other flags?

Yes, no additional flags. In this latest install, I haven’t run it yet so that I have a “working” system to provide logs and such.

While starting to install, you can select the menu entry that provides Nvidia’s proprietary driver. But looks like you selected the open source driver instead?

Could you show the installed packages related to Nvidia:

pacman -Qs nvidia

Edit: by the way, if you install packages with nvidia-inst and get a boot problem after reboot, you can uninstall them quite easily by using the USB installer and
command arch-chroot to access your installed system. Then no reinstall is needed.
See more info about this in our discovery (wiki).

If I select the NVIDIA entry instead of the UEFI default, the live system doesn’t boot for me. That’s why I always start with the open source driver and then install NVIDIA once the system is installed and booted.

As for the command output:

pacman -Qs nvidia
local/libvdpau 1.5-3
Nvidia VDPAU library

Edit: I have used arch-chroot a couple of times but to be honest, I always try to search for the text mode way to get to a login where I can uninstall nvidia and fail! I have to remember to use the chroot the next time this happens. But I am hoping for a process where it doesn’t happen.

OK, currently the proprietary drivers are not installed, like you mentioned.
Is the inxi output above from the installed system, or from the USB installer?
Did you install in the offline mode?

This output is from the installed and booted system - not the live USB. All packages are up-to-date. This latest attempt was the online install with KDE.

So you are currently using the nouveau driver.

Please show the output of command

nvidia-inst --test

It does not change anything, but shows what it would do.

nvidia-inst --test
2024-12-09 11:06:58: Info: Running: nvidia-inst v24.10.2-2
2024-12-09 11:06:58: Info: Command line: nvidia-inst --test
2024-12-09 11:06:58: Info: Selected mode: nvidia
NVIDIA card id: 2484
Fetching driver data from nvidia.com …
2024-12-09 11:07:00: Info: Installing packages: dkms nvidia-dkms nvidia-utils nvidia-settings nvidia-hook

COMMANDS TO RUN:
    pacman -Syuq --noconfirm --noprogressbar --needed dkms nvidia-dkms nvidia-utils nvidia-settings nvidia-hook

I assume you are using wayland and not x11?
If so, please login with x11 instead.

Then try run one of the following commands that you haven’t tried so far:

nvidia-inst             # installs nvidia-dkms
nvidia-inst --no-dkms   # installs nvidia and nvidia-lts
nvidia-inst -o          # installs nvidia-open-dkms

After running a command, copy the output to a file, e.g. ~/nvidia.txt so that you are able to uninstall what the command installed.
Then reboot.
If boot fails, uninstall those packages (in TTY or with USB installer & arch-chroot), and try the next command.

Could you please elaborate on how to do this?

how to get to TTY? I tried an “s” at the end of the systemd-boot command line but that didn’t work. I also recall trying some other options for this but was never successful.

You should have used the nvidia option on install. It will install the latest nvidia drivers. If you use the default menu it installs with open source nouveau drivers.

Edit: You’re in good hands with @manuel

First: log out. On that login screen you’ll see (e.g. on some edge, that depends on the desktop) a selection of wayland or x11 session. Then select the x11 session and login again.

Simply press keys Ctrl-Alt-F3 at the same time (maybe first keep Ctrl and Alt pressed, then press F3). Note that F3 may not be the only key that works.
Then you should reach a big black command prompt screen where normal terminal commands can be run.
Basically to get back from TTY to desktop press Ctrl-Alt-F2 (or Ctrl-Alt-F1).
Or reboot.

Thanks @ricklinux. I would have liked to use the nvidia option on the live USB but that doesn’t work for me - same type of graphics failure as after the nvidia installation!

1 Like

Thanks for that. It sounds like whining but I have to say X11 change made it very difficult to do anything on the desktop. Since I am on a display that is a 4K TV that is about 10 feet away, font scaling on the system scaling is not working too well on X11 and making it extremely difficult to work with it.

I have tried the Ctrl-Alt-F3/F4, etc for TTY when the desktop doesn’t load but I was never even getting any display back (my display is directed through a AV receiver and it is clearly not getting any signal from my desktop once this failed nvidia load happens. So, unless something miraculous happens on this attempt, I am likely to revert to chroot method.

Either way, I will try to collect the info on the packages installed for options 2 and 3 suggested for nvidia-inst. Option 1 output would be the same as in the “–test” attempt.

I’m not familiar with the HTPC. Did you build it yourself or it’s purchased complete? Just wondering what the motherboard is and hardware besides the nvidia graphics.

For what’s it worth, I’m using a 4K TV too, with Nvidia 1030 GPU. It all works OK with x11, but wayland causes issues with some apps (e.g. kaffeine).

Just for reference, I have the following Nvidia related packages (not all are required):

$ pacman -Qs nvidia | grep ^local/
local/egl-gbm 1.1.2-1
local/egl-wayland 4:1.1.16-1
local/libva-nvidia-driver 0.0.13-1
local/libvdpau 1.5-3
local/libxnvctrl 565.57.01-1
local/nvidia 565.77-4
local/nvidia-hook 1.5.1-1
local/nvidia-inst 24.10.2-2
local/nvidia-lts 1:565.77-2
local/nvidia-settings 565.57.01-1
local/nvidia-utils 565.77-1
local/nvtop 3.1.0-1

Built it myself. It’s running an AMD Ryzen 9 5900X processor on an Asus X570 motherboard with the NVIDIA RTX 3070 GPU and 32 gigs of memory. It used to be a Windows dual boot but I messed up something during one of my distrohopping exercises and end up clearing out the EFI entries and then Windows installer kept failing to reinstall probably because of the TPM or the secure boot setting that I gave up and made this machine as linux workstation only. I was practically never using that windows anyway, so it made sense.