EndeavourOS hangs on boot (display drvr)

General system Newbie
41

If I run arandr I get following errors:

Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Traceback (most recent call last):
  File "/usr/bin/arandr", line 42, in <module>
    main()
  File "/usr/lib/python3.9/site-packages/screenlayout/gui.py", line 344, in main
    app = Application(
  File "/usr/lib/python3.9/site-packages/screenlayout/gui.py", line 113, in __init__
    self.window = window = Gtk.Window()
  File "/usr/lib/python3.9/site-packages/gi/overrides/Gtk.py", line 519, in __init__
    raise RuntimeError(
RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to handle this case.
42

Ok, but I read from here that arandr is just GUI for xrandr. I’m having problems with xrandr. Can you assist with xrandr?

43

It is and is there to make things easier to set up with i3. There is something missing here. It could be any of several issues but with the current information it is almost impossible.

  1. You didn’t verify the ISO and it is a corrupted image.
  2. The USB stick you used is faulty.
  3. You changed something in the default installation process.
  4. That NVME has some left over data stuck on it and needs to be secure erased or DD’ed and start over.
44

I get this after running lightdm --test-mode --debug:

What is strange into my newbie-eyes is “acquired bus name org.freedesktop.displaymanager”. Should it really be that way?

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=4543
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG:   [Seat:*] contains unknown option logind-check-graphical
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating user session
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 2: Logging to /var/log/lightdm/x-2.log
[+0.01s] DEBUG: XServer 2: Writing X server authority to /run/lightdm/root/:2
[+0.01s] DEBUG: XServer 2: Launching X Server
[+0.01s] DEBUG: Launching process 4549: /usr/bin/X :2 -seat seat0 -auth /run/lightdm/root/:2 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 2: Waiting for ready signal from X server :2
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
45

I am fairly certain that does not belong there. Not sure why it is looking for plymouth.

It also seems to be there might be an issue with root user account and permissions. Did you enter a root password?

1 Like
46

Yap, it asked for sudo password. Here is my

systemctl status lightdm

ightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2021-05-31 21:06:04 EEST; 5s ago
       Docs: man:lightdm(1)
   Main PID: 38552 (lightdm)
      Tasks: 6 (limit: 18959)
     Memory: 18.6M
        CPU: 294ms
     CGroup: /system.slice/lightdm.service
             ├─38552 /usr/bin/lightdm
             ├─38558 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
             └─38614 lightdm --session-child 12 19

touko 31 21:06:04 presari5510 systemd[1]: Starting Light Display Manager...
touko 31 21:06:04 presari5510 systemd[1]: Started Light Display Manager.
touko 31 21:06:05 presari5510 lightdm[38562]: Could not find provider with name modesetting
touko 31 21:06:05 presari5510 lightdm[38565]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=969) >

and here is my bash script done according to wiki page:

  GNU nano 5.7                                   /etc/lightdm/display_setup.sh                                             
#!/bin/sh
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
47

I only have AMD hardware so I am limited here but it looks like this is wrong…

1 Like
48

Well, I removed lightdm with pacman -Rns lightdm. Reinstalled and started again - now my cursor is not halted but blinking again.

Out of curiosity I installed sddm. When I start it by systemctl I have cursor halted on top left of my screen.

49

Have you made sure it’s trying to load intel in the beginning with your setup?

1 Like
50

Ok this seems somewhat solved. I reinstalled nvidia-drivers with -b -option (previous installation was without). I have my DE back.

Whether all the other stuff I made any difference will remain mystery forever.

One big question remains - I have to check whether endeavouros is really using nvidia as display adapter. How do I do that?

51

So reinstalling the nvidia driver with -b gives bumblebee.

Edit Not sure how old the laptop is? Bumblebee isn’t used on newer stuff i don’t think. But hey if it works. :man_shrugging:

52

Just a reminder.
It’s an active bug, that’s why it works for bumblebee…

1 Like
53

This laptop is from 2015 or 2016. Nvidia website doesn’t list this M1000M-GPU any longer but according to this page it is Optimus compatible:

If I run xrandr still says “Can’t open display” if I run it. I thought everything that comes through display comes from xrandr, that is controlled by arandr in this case.

54

Maybe @keybreak can answer that. I’m not really up on Hybrid Graphics. I do run Nvidia and i have helped install a lot of Hybrid setups but things have seemed to change and stuff isn’t working as it was prior.

55

I saw that yes :slight_smile: ,however my system didn’t crash as I first thought.

1 Like
56

@keybreak I’m not sure about exact terms but I don’t think my kernel “crashed”. It just wouldn’t load desktop environment. It never froze etc.

57

Well, as i’ve heard about this bug (it’s all over the place and pretty random, meaning active only for some GPUs and with displayport) basically you don’t have display output at all after boot…

Which is insane :exploding_head:

1 Like
58

Aha - Nvidia-driver doesn’t seem to be in use. But…This probable isn’t good place to check it?

nvidia-settings
ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system
1 Like
59

Post inxi again.

60 
inxi -Ga
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell driver: N/A alternate: i915 bus-ID: 00:02.0 chip-ID: 8086:191b 
           class-ID: 0300 
           Device-2: NVIDIA GM107GLM [Quadro M1000M] driver: N/A alternate: nouveau, nvidia_drm, nvidia bus-ID: 01:00.0 
           chip-ID: 10de:13b1 class-ID: 0302 
           Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-12:3 chip-ID: 0c45:6713 
           class-ID: 0e02 
           Display: server: X.org 1.20.11 compositor: picom v: git-dac85 driver: loaded: intel,vesa 
           unloaded: fbdev,modesetting tty: 123x52 
           Message: Advanced graphics data unavailable in console. Try -G --display