New to EndeavourOS and linux admin in general. I’m on a fresh install, no issues just wiping and starting over but this seems like a good learning experience.
The only other programs installed are Discord and Steam. Those were installed first, and everything was running fine. I then installed nvidia-inst and ran it with no options. After rebooting, Cinnamon started in recovery mode. From here there are two things I wish I knew how to do:
- Find information on the nature of the error. There were a few promising leads in
xsession-errors and journalctl, but nothing I could personally make sense of.
- Cleanly revert whatever
nvidia-inst did to my machine. I don’t know how to figure out the sum total of what it did, but I tried to run pacman -R on the same packages it would have when I called nvidia-inst --nouveau. Doing this caused my DE not to boot at all, which I’m at a loss on how to investigate. No clue what side effects I would have to unwind to get things back to how they were on the fresh install.
So I’m kind of stuck at square one. Disappointed that this happened on a very fresh installation on older but supported hardware. Would love a few pointers. I can wipe this install, but ultimately I will need those drivers to play games (or alternatives, if there are any.)
first thing that let ring alarm bell is to firstinstall steam and after this the needed nvidia drivers… also installing steam needs to make the right choice while installing… it ask for choice where you need to select the right part for nvidia…
But running nvidia-inst -n should revert what itself does before on installing propritary drivers. so leads to the question if there is something from installing steam that is in the way…
inxi -Gaz will show info on GPU and used drivers… and you can check boot journal for related errors:
journalctl -b -0 | grep nvidia
journalctl -b -0 | grep nouveau
These could show some hint on what went wrong while booting.
And check installed packages:
pacman -Qs nvidia
But as long as you do not have access to X .-. better go the save route and remove steam:
sudo pacman -Rc steam
nvidia-inst -n
And welcome here we will get your system back i bet 
2 Likes
I definitely chose the nvidia dependencies when installing Steam. Uninstalling Steam has had no effect on the system.
relevant looking lines from journalctl -b -0 | grep cinnamon:
May 30 11:18:26 PC kernel: cinnamon[952]: segfault at 0 ip 00007fa2f6807118 sp 00007fff3a6a7a80 error 4 in libmuffin.so.0.0.0[7fa2f67fb000+ad000] likely on CPU 1 (core 1, socket 0)
May 30 11:18:26 PC systemd-coredump[963]: Process 952 (cinnamon) of user 1000 dumped core.`
relevant looking lines from journalctl -b -0 | grep nvidia
May 30 03:33:57 PC systemd-modules-load[306]: Failed to find module 'nvidia-uvm'
May 30 03:33:58 PC (udev-worker)[338]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \ -f 1) 255'' failed with exit code 1.
Here’s that coredump:
Process 900 (cinnamon) of user 1000 dumped core.
Stack trace of thread 900:
#0 0x00007fbd09834118 meta_monitor_spec_free (libmuffin.so.0 + 0x40118)
#1 0x00007fbd09834191 meta_monitor_config_free (libmuffin.so.0 + 0x401>
#2 0x00007fbd098422c7 n/a (libmuffin.so.0 + 0x4e2c7)
#3 0x00007fbd0984407c n/a (libmuffin.so.0 + 0x5007c)
#4 0x00007fbd09d21e63 n/a (libgobject-2.0.so.0 + 0x24e63)
#5 0x00007fbd09d23f0b g_object_new_valist (libgobject-2.0.so.0 + 0x26f>
#6 0x00007fbd09d2429e g_object_new (libgobject-2.0.so.0 + 0x2729e)
#7 0x00007fbd0983f07a meta_monitor_config_manager_new (libmuffin.so.0 >
#8 0x00007fbd098329e0 n/a (libmuffin.so.0 + 0x3e9e0)
#9 0x00007fbd09850aa4 n/a (libmuffin.so.0 + 0x5caa4)
#10 0x00007fbd0984cc67 n/a (libmuffin.so.0 + 0x58c67)
#11 0x00007fbd09832ffd n/a (libmuffin.so.0 + 0x3effd)
#12 0x00007fbd0988584f meta_init (libmuffin.so.0 + 0x9184f)
#13 0x0000560b9b92015e n/a (cinnamon + 0x215e)
#14 0x00007fbd0962d850 n/a (libc.so.6 + 0x23850)
#15 0x00007fbd0962d90a __libc_start_main (libc.so.6 + 0x2390a)
#16 0x0000560b9b920635 n/a (cinnamon + 0x2635)
Stack trace of thread 905:
#0 0x00007fbd09707c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbd09c6aa9f n/a (libglib-2.0.so.0 + 0xb7a9f)
#2 0x00007fbd09c0b032 g_main_context_iteration (libglib-2.0.so.0 + 0x5>
#3 0x00007fbd09c0b082 n/a (libglib-2.0.so.0 + 0x58082)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 909:
#0 0x00007fbd09707c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbd09c6aa9f n/a (libglib-2.0.so.0 + 0xb7a9f)
#2 0x00007fbd09c0b032 g_main_context_iteration (libglib-2.0.so.0 + 0x5>
#3 0x00007fbd09f81fde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 908:
#0 0x00007fbd09707c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbd09c6aa9f n/a (libglib-2.0.so.0 + 0xb7a9f)
#2 0x00007fbd09c0cf3f g_main_loop_run (libglib-2.0.so.0 + 0x59f3f)
#3 0x00007fbd09e6f28c n/a (libgio-2.0.so.0 + 0x11028c)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 906:
#0 0x00007fbd0970d2ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007fbd09c62b85 g_cond_wait (libglib-2.0.so.0 + 0xafb85)
#2 0x00007fbd09bd8094 n/a (libglib-2.0.so.0 + 0x25094)
#3 0x00007fbd09c4224e n/a (libglib-2.0.so.0 + 0x8f24e)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 907:
#0 0x00007fbd0970d2ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007fbd09c633a3 g_cond_wait_until (libglib-2.0.so.0 + 0xb03a3)
#2 0x00007fbd09bd8065 n/a (libglib-2.0.so.0 + 0x25065)
#3 0x00007fbd09c42cfb n/a (libglib-2.0.so.0 + 0x8fcfb)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 910:
#0 0x00007fbd0970d2ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007fbd09c633a3 g_cond_wait_until (libglib-2.0.so.0 + 0xb03a3)
#2 0x00007fbd09bd8065 n/a (libglib-2.0.so.0 + 0x25065)
#3 0x00007fbd09c42cfb n/a (libglib-2.0.so.0 + 0x8fcfb)
#4 0x00007fbd09c3fcc5 n/a (libglib-2.0.so.0 + 0x8ccc5)
#5 0x00007fbd0969144b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbd09714e40 n/a (libc.so.6 + 0x10ae40)
ELF object binary architecture: AMD x86-64
I tried uninstalling all the nvidia drivers, but this causes X to just not start at all (I think). I’m wondering if there’s some config settings that need to be rolled back manually. I’m just trying to get the system back to whatever the stock video settings were, which worked alright for general use but not for gaming.
Are you able to get into a tty?
inxi -Ga
Also if you could post the url
inxi -Faz | eos-sendlog
I can drop into a tty, but I can also open a terminal window on the desktop, the behavior is just a bit weird in rescue mode.
inxi -Ga output:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte driver: nvidia v: 530.41.03
alternate: nouveau,nvidia_drm non-free: 530.xx+ status: current (as of 2023-05) arch: Pascal
code: GP10x process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max:
gen: 3 speed: 8 GT/s ports: active: none off: DP-1,HDMI-A-1 empty: DVI-D-1,DVI-D-2
bus-ID: 01:00.0 chip-ID: 10de:1c03 class-ID: 0300
Device-2: Focusrite-Novation Scarlett 2i2 Camera driver: snd-usb-audio type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.3:4 chip-ID: 1235:8210 class-ID: 0102
serial: P5GX64299812F1
Device-3: Logitech Webcam C310 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.5:6 chip-ID: 046d:081b class-ID: 0102
serial: BDB66BC0
Display: x11 server: X.org v: 1.21.1.8 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch tty: 128x48
Monitor-1: DP-1 model: PX276h&PX277h built: 2019 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x335mm (23.5x13.19") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-1 model: PX276h&PX277h built: 2019 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x335mm (23.5x13.19") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 640x480
API: OpenGL Message: GL data unavailable in console. Try -G --display
inxi -Faz output:
http://ix.io/4xij
There are newer Bios versions for your motherboard. I would make sure you update it. Your current version is F1 dated 10/31/2016. There are 10 newer Bios versions so i would update to the latest.
Your output shows you have the nvidia drivers installed. So i would first updated the Bios and make sure you also run an update on EndeavourOS. You could do that first to see that it’s updated.
@Mystagogue
If need be you can revert to nouveau open source drivers as @joekamprad mentioned by running
nvidia-inst -n
if so it could be some conf under /etc/X11/xorg.conf.d/ check this with ls /etc/X11/xorg.conf.d/ But as title say it segfaults after installing Nvidia drivers… using nvidia-inst -n should have brought X back … but from what you wrote it is not clear if you cleanly removed Nvidia with nvidi-inst or try to do that manually… so running it again will be the first try nvidia-inst -n
looks like it still try to load nvidia driver…
I ran nvidia-inst -n and it looked like everything uninstalled cleanly, but the issue persisted.
Thanks to the “post-install” dialog, I was able to switch from lightdm to gdm, I would have no idea how to do that manually. That seems to have fixed the problem - I now have a full desktop environment, no fallback mode popup. Makes me wonder if the issue was something with lightdm, though I didn’t see any errors in the logs as far as I can tell.
EDIT : gdm actually has its own issues. Things seemed fine at first. But I can’t access display or general settings - they do not show up in the program search and the context menu options from the desktop fail.
There is only one file under /etc/X11/xorg.conf. It’s 00-keyboard.conf. Should there be more?
it could be an issue if you would have some there 
Basically you need to check if there is still nvidia modules and stuff installed … and revert to nouveau
fully… may you set something up for nvidia in addition ?
ls /etc/modules-load.d/
ls /etc/modprobe.d/
?
Check if it is using nouveau open source drivers.
inxi -Ga
inxi -Ga output:
Graphics:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte driver: nouveau v: kernel
non-free: 530.xx+ status: current (as of 2023-05) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: DP-1,HDMI-A-1 empty: DVI-D-1,DVI-D-2 bus-ID: 01:00.0 chip-ID: 10de:1c03 class-ID: 0300
temp: 36.0 C
Device-2: Focusrite-Novation Scarlett 2i2 Camera driver: snd-usb-audio type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.3:4 chip-ID: 1235:8210 class-ID: 0102
serial: P5GX64299812F1
Device-3: Logitech Webcam C310 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.5:6 chip-ID: 046d:081b class-ID: 0102
serial: BDB66BC0
Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 driver: X: loaded: nouveau
unloaded: modesetting alternate: fbdev,nv,vesa dri: nouveau gpu: nouveau tty: 160x45
Monitor-1: DP-1 model: PX276h&PX277h built: 2019 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x335mm (23.5x13.19") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-1 model: PX276h&PX277h built: 2019 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x335mm (23.5x13.19") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL Message: GL data unavailable in console. Try -G --display
ls /etc/modules-load.d/ : no output
ls /etc/modprobe.d/: only firewalld-sysctls.conf
I want to take this opportunity to say thanks to everyone who has helped so far. This has been a really valuable learning experience.
@Mystagogue
I would suggest you update the Bios. There are a number of newer updates. Should update to the latest version.
I did that after the last post mentioned it. I should be on the newest version now.
Last post or another topic? Should be version F9d dated 2018
You mentioned updating my bios in another reply, I updated to F9d after that.
1 Like
So are you still having issues? You originally said after installing Nvidia drivers. Now you are on nouveau open source drivers.
Yes, the issues persist even with nouveau installed instead.