Works fine on my 3070 ti model.
As @Bink mentioned above, according to the Arch WIKI, open-source Nvidia drivers are from Turing (NV160/TUXXX) and newer. I used nvidia-inst for my GeForce RTX 3060 Ti and the open-source drivers were presented.
This broke sddm on virtualbox for me (it stopped at the line “Reached target graphical interface”). I got it fixed by switching to tty and changing sddm configuration to make it start under wayland instead of X11.
This affects my hybrid AMD/nVidia laptop. Downgrading mesa via chroot worked. When I get my system back up fully I can post my output.
Not sure if this is the right place to reply, but I wanted to share my experience in case it helps others.
On my machine with an AMD GPU, I didn’t run into any issues after recent updates — everything worked fine.
However, on another system with an NVIDIA GPU, I did face boot freezes and black screens…
Here’s what worked for me on the NVIDIA setup (running KDE Plasma on EndeavourOS):
-
Booted into a Live ISO (EndeavourOS):
Created a bootable USB and launched the live session. -
Mounted the root partition and chrooted into the system:
sudo mount /dev/sdXn /mnt sudo arch-chroot /mnt (Replace /dev/sdXn with the correct partition for your root filesystem.) -
Installed NVIDIA drivers:
sudo pacman -S nvidia nvidia-utils nvidia-settings -
Downgraded Mesa to a stable version that worked (25.0.5-1):
sudo pacman -S downgrade sudo downgrade mesa
If the console ask about disable mesa updates, set yes.
-
Reinstalled mkinitcpio and rebuilt the initramfs:
sudo pacman -S mkinitcpio sudo mkinitcpio -P -
Exit, umount and rebooted:
exit sudo umount -R /mnt reboot
[Optional] Force KDE to use X11 instead of Wayland:
This step wasn’t needed in my case, but it might help if Wayland is giving you trouble:
sudo nano /etc/sddm.conf.d/10-wayland.conf
Add:
[General]
DisplayServer=x11
I’m not sure this is the best solution, but it worked as a temporary fix for anyone who needs to get their system running again and doesn’t have a backup available.
1 Like
NOTE: It “looks” like a fix “may” be out…try with caution.
I just tried the most recent mesa update (1:25.1.1-2) and it is still broken. 
mesa-1:25.1.1-2 fixed the black screen issue for me. However, installing either mesa-utils 9.0.0-6 or xf86-video-vmware 13.4.0-4 or both both of them (they came out at the same time as the problematic mesa version) results in a black screen on boot.
I’m running EndeavourOS and KDE Plasma in a VMWare Workstation Pro virtual machine.
2 Likes
Good to know, will avoid updating mesa.
I wished I came across this post earlier… After an update yesterday I was stuck with this dumb black-screen-cursor thing. I tried the best I could to fix the issue with all the solutions I found on the web (none directly pointed to this thread strangely enough…) but gave up and did a full wipe and full new install of EOS today…
What was my stupefaction seeing the exact same issue after a full reinstall
What worked for me:
- Install the nvidia-open-lts
- Install KDE plasma (x11/wayland)
Now both XFCE and KDE work 
I dunno if it’s still relevant but here are the output asked from the first post:
0a:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce GTX 1650] (rev a1)
Graphics:
Device-1: NVIDIA TU106 [GeForce GTX 1650] driver: nvidia v: 570.153.02
Display: wayland server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.153.02
renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
Info: Tools: api: eglinfo,glxinfo
de: kscreen-doctor,xfce4-display-settings gpu: nvidia-smi
x11: xdpyinfo, xprop, xrandr
1 Like
Little update, with the last mesa compromised update which I was concerned by the black screen, using the nouveau driver as default one. (choice made by default du to nvidia problematics at the time of EOS installation, 3 years ago)
I’ve updated this situation by migrating to the nvidia driver via the helpful EOS Apps info (discovered in the same time… 
$ sudo pacman -S nvidia-inst
Then test and install as mentioned by the instructions given.
So now, here my new situation, up-to-date and working:
lspci | grep 'VGA'
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] (rev a1)
inxi -G
Graphics:
Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] driver: nvidia
v: 570.153.02
Device-3: Chicony HP Wide Vision HD Camera driver: N/A type: USB
Display: x11 server: X.Org v: 21.1.16 driver: X: loaded: intel,nvidia
unloaded: modesetting dri: i965 gpu: i915 resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: iris,nvidia,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.1.1-arch1.2
renderer: Mesa Intel UHD Graphics (TGL GT1)
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
pacman -Qs mesa
local/glu 9.0.3-2
Mesa OpenGL utility library
local/mesa 1:25.1.1-2
Open-source OpenGL drivers
local/mesa-utils 9.0.0-6
Essential Mesa utilities
Hope this return will be useful 
5080… i will may ask you to test some ISO in the future 
1 Like
Can more users please confirm the latest mesa update works ? Specially the ones with a rtx card and intel igpu.
As of today, June 1, 2025, all is well…
❯ lspci | grep 'VGA'
01:00.0 VGA compatible controller: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] (rev a1)
❯ inxi -G
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] driver: nvidia
v: 570.153.02
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: nvidia,nvidia-nvswitch resolution: 2560x1440~165Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.153.02
renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
API: Vulkan v: 1.4.313 drivers: nvidia surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
❯ pacman -Qs mesa
local/glu 9.0.3-2
Mesa OpenGL utility library
local/lib32-glu 9.0.3-2
Mesa OpenGL utility library (32 bits)
local/lib32-mesa 1:25.1.1-2
Open-source OpenGL drivers - 32-bit
local/mesa 1:25.1.1-2
Open-source OpenGL drivers
local/mesa-utils 9.0.0-6
Essential Mesa utilities
I’m not on my laptop right now however It is Nvidia GeForce 1060 and everything went fine with the update and the reboot booted straight to lightdm. Running XFCE on the Laptop.
Graphics:
Device-1: Intel Alder Lake-HX GT1 [UHD Graphics 770] driver: i915 v: kernel
Device-2: NVIDIA GA107GLM [RTX A1000 Laptop GPU] driver: nouveau v: kernel
Device-3: Luxvisions Innotech Integrated RGB Camera driver: uvcvideo
type: USB
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
loaded: modesetting dri: iris,nouveau gpu: i915,nouveau resolution:
1: 1920x1200~60Hz 2: 1920x1200~60Hz 3: 1920x1200~60Hz
API: EGL v: 1.5 drivers: iris,nouveau,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 25.0.5-arch1.1
renderer: Mesa Intel UHD Graphics (ADL-S GT1)
API: Vulkan v: 1.4.313 drivers: intel surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Affected. Downgrading mesa seems to fix it for now
To boot or install because I normally don’t reinstall unless I have to and am running Arch, but if it helps EndeavourOS I can do a reinstall for you?
Welcome for this forum!
For the record, can you show the output of
pacman -Q | grep -P 'nvidia|mesa'
Hello,
My vmware guest and my proxmox guests both had this issue.
Ref
Update
Today
- I installed EndeavourOS_Mercury-Neo-2025.03.19.iso, on my proxmox vm, took a snapshot, and upgraded everything. No more issues, maybe the bug has been fixed.
- I upgraded my vmware guest to latest, unpinning mesa, ssdm + x11 coredumps
Process 1629 (Xorg) of user 0 dumped core.
Stack trace of thread 1629:
#0 0x000071363dc2174c n/a (libc.so.6 + 0x9774c)
#1 0x000071363dbc7dc0 raise (libc.so.6 + 0x3ddc0)
#2 0x000071363dbaf57a abort (libc.so.6 + 0x2557a)
#3 0x00005c439cf9db3e OsAbort (/usr/lib/Xorg + 0x153b3e)
#4 0x00005c439cf9f037 FatalError (/usr/lib/Xorg + 0x155037)
#5 0x00005c439cfa5fd8 n/a (/usr/lib/Xorg + 0x15bfd8)
#6 0x000071363dbc7ef0 n/a (libc.so.6 + 0x3def0)
#7 0x000071363dcf69c9 n/a (libc.so.6 + 0x16c9c9)
#8 0x000071363e20f694 n/a (vmware_drv.so + 0xb694)
#9 0x00005c439cebec4b AddScreen (/usr/lib/Xorg + 0x74c4b)
#10 0x00005c439cfc315d InitOutput (/usr/lib/Xorg + 0x17915d)
#11 0x00005c439ce7cc69 n/a (/usr/lib/Xorg + 0x32c69)
#12 0x000071363dbb16b5 n/a (libc.so.6 + 0x276b5)
#13 0x000071363dbb1769 __libc_start_main (libc.so.6 + 0x27769)
#14 0x00005c439ce7e2b5 _start (/usr/lib/Xorg + 0x342b5)
ELF object binary architecture: AMD x86-64
Sure. Although im not using my graphics card 
mesa 1:25.0.5-1
mesa-utils 9.0.0-6
1 Like
OK just did a fresh install of BlueStar from their previous ISO and as I expected installed without issue, on reboot stopped just short of getting to the desktop.
1 Like