Sure but not as packages, and user maintained, every update on them could include new issues
I appreciate the efforts here, but despite installing various nvidia packages, I still have a blank screen with a blinking cursor. Following the directions here, I was able to get to a console screen. BTW, if the font is too small, I found that one can add fbcon=font:TER16x32 as a boot parameter in the GRUB edit. That font is too large, but it’s better than barely readable for some of us with older eyes.
I think my main problem is that I’m running EOS as a VM on an old laptop with a NVIDIA GeForce GT 525M GPU. A quick 'Net search says that that graphics card was launched on 5 January 2011, so rather ancient in computing years.
I found an AUR package, nvidia-470xx-dkms that was supposed to be compatible, but it turned out to be of no help, at least for me.
Looks like I’ll be using the console to make my final backups & say goodbye to EOS, at least until I can get a newer laptop.
I’ve very much appreciated the way EOS makes Arch easy to use. This forum is one of its best features. I hope to return, someday.
According to Nvidia series 470 is not compatible but 390 is with 525M. But maybe the nouveau driver works better?
The initial issue we talk about here is about supported Nvidia GPUs not old legacy Models, we do never had support on the ISO to boot legacy with legacy Nvidia drivers. I made some ISO before in cases users really needed this in the past but default is that on Nvidia legacy GPU you boot with default boot option on nouveau drivers. Also i do not klnow if the current issue also affects older legacy GPUs at all i can check that partly only as of no such hardware in use here.. may i can plug an old Nvidia in a PC somehow..
If I can figure out what to do, I might try nouveau. The Arch wiki page for Nouveau isn’t an easy read.
I’m not a kernel config guy, nor am I a heavy user of graphics on Linux. One of the things that appealed to me about EOS was that it was terminal-centric.
Hmm, maybe I can find a comfortable font for the console & just use virtual ttys. Not ideal, but …
EDIT: If I’m reading Der Doktor’s post correctly nouveau is the default. Default is what led me to my current situation. yay -Syu & then no GUI. Installing nouveau package(s) doesn’t sound hopeful.
Any advice would be welcomed. Using default is what got me to the current situation. Recently, I did the usual yay -Syu, but afterwards all I got was the blank screen with blinking cursor.
Roughly four years ago, I decided to try EOS. I don’t remember making any special graphics choices. Until this month, everything worked fine (other than an infrequent software glitch here or there that the forum always helped me resolve).
One of the appeals of EOS for me was getting the benefit of Arch rolling-release without having to be a config expert. The installer made the right choices.
Please show the output of commands
pacman -Q | grep -P 'nvidia|nouveau'
lspci -vnn | grep -A9 -P 'VGA|3D|Display'
lsmod | grep -P 'nvidia|nouveau'
first remove the nvidia-470xx package if its still installed make sure no other nvidia packages are installed too nvidia-utils per example..
check with pacman -Qs nvidia (search installed [local] packages)
Also make sure you do not have any config for nvidia under /etc/X11/xorg.conf.d
ls /etc/X11/xorg.conf.d will show what is there.
a lot of cards (particularly mobile 5000 series) are not working with the latest nvidia driver (575.57.08)
Since i’ts an nvidia thread and all figured i’d toss in the warning.
If people are getting the No devices were found error when running nvidia-smi, this is why: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/876#issue-3127364336
So if I want to install EOS on a desktop with AMD + RTX 5080, I simply need to add
nvidia-open
nvidia-utils
to the user_pkglist.txt and everything will be fine?
The only problem is that the installer fails to detect that it needs to install these packages?
I did reinstall day before yesterday and had no issues with RTX 4060, although ISO- image I had on my stick was not the latest. I have Ryzen 9 with integrated AMD graphics with it.
I also did not do any pkglist additions. 
yes this should do the trick!
If it is not the latest ISO it could work in case.. but also will include other issues we resolved with latest. Always recommended installing only with latest releases.
I usually do so, but I had no issues with it so dared to do re-install from it. Of course that may have been foolhardiness. 
I generally have been able to avoid (thus far) problems with drivers and such that have been lurking on some ISOs (knocks on the wood). 
it is only bad circumstances at the moment everything around Nvidia is totally messed up again.. we only need to adopt again ..
–
only wanted to make it clear that using older ISO is not the very best solution.
And in case not using Nvidia boot-option it would fail to load Desktop the same way on online installs with the older ISO.
Hi
Just followed the above for the installer for my Nvidia 3060ti
Installation failed and here is the error
Any idea what’s happening?
Ps I replaced my nvme drive with an old sata and it works now
Apparently my nvme drive went caput…no longer recognised in bios
2025-06-15 - 16:42:51 [6]: .. Running QList("/bin/sh", "-c", "mkdir -p /tmp/calamares-root-88tbmgld/etc/pacman.d/")
2025-06-15 - 16:42:54 [6]: Calamares::CommandList::run()::<lambda(QString)>
2025-06-15 - 16:42:54 [6]: "mkdir: cannot create directory '/tmp/calamares-root-88tbmgld/etc': Read-only file system\n"
2025-06-15 - 16:42:54 [6]: .. Target cmd: QList("/bin/sh", "-c", "mkdir -p /tmp/calamares-root-88tbmgld/etc/pacman.d/") Exit code: 1 (no output)
log does not say much you would have been able to see on journal but indicating something wrong with teh nvme a sof not able to write to it..
Does anyone know how to check if the nvidea drivers are present? im pretty sure i had them before but yesterday when running a game that normally uses my Nvidea gpu it used my onboard gpu instead.
@AllGeniusHost, in terminal, run pacman -Qs nvidia, it should provide what you have present on your system.
Here’s mine…
❯ pacman -Qs nvidia
local/egl-gbm 1.1.2.1-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.19-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.2-1
NVIDIA XLib and XCB EGL Platform Library
local/lib32-libvdpau 1.5-3
Nvidia VDPAU library
local/lib32-nvidia-utils 575.64-2
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-3
Nvidia VDPAU library
local/libxnvctrl 575.64-1
NVIDIA NV-CONTROL X extension
local/nvidia-hook 1.5.2-1
pacman hook for nvidia
local/nvidia-inst 25.6.5-1
Script to install/uninstall nvidia driver packages in EndeavourOS
local/nvidia-open-dkms 575.64-1
NVIDIA open kernel modules - module sources
local/nvidia-settings 575.64-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 575.64-1
NVIDIA drivers utilities
❯
Thank you for the quick response!
I think everything is in order
[aghn@aghn-rogstrixg513qrg513qr ~]$ pacman -Qs nvidia
local/egl-gbm 1.1.2.1-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.19-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.2-1
NVIDIA XLib and XCB EGL Platform Library
local/libnvidia-container 1.17.8-1
NVIDIA container runtime library
local/libvdpau 1.5-3
Nvidia VDPAU library
local/nvidia 575.57.08-5
NVIDIA kernel modules
local/nvidia-container-toolkit 1.17.8-1
NVIDIA container toolkit
local/nvidia-inst 25.6.5-1
Script to install/uninstall nvidia driver packages in EndeavourOS
local/nvidia-utils 575.57.08-3
NVIDIA drivers utilities