Stuck at blinking cursor, Nvidia drivers

iFlxy · 2023-01-29 11:43:01

Hi,

I'm having issues with a blinking cursor after boot. I tried installing an older version of Nvidia drivers and I forgot to run mkinitcpio -P (I created a hook later), so I chrooted into the system and executed the command. I got stuck at "Starting systemd-udevd version 252.4-2-arch". I tried to install the latest drivers, and instead of a login GUI, I saw two white flashes, and then a blinking cursor. Please let me know if more information is required.

journalctl: http://0x0.st/oFWQ.txt

I found this in the journal:

kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel

and this

Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     configuration option may not be set correctly.  When the
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0):     Config Options in the README.
Jan 28 16:39:09 iflxypc /usr/lib/gdm-x-session[557]: (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
Jan 28 16:39:10 iflxypc /usr/lib/gdm-x-session[557]: (==) NVIDIA(0): Disabling shared memory pixmaps
Jan 28 16:39:10 iflxypc /usr/lib/gdm-x-session[557]: (==) NVIDIA(0): Backing store enabled
Jan 28 16:39:10 iflxypc /usr/lib/gdm-x-session[557]: (==) NVIDIA(0): Silken mouse enabled
Jan 28 16:39:10 iflxypc /usr/lib/gdm-x-session[557]: (==) NVIDIA(0): DPMS enabled

Do these lines mean something?

Thanks in advance.

Update: I tried using multi user target and executing gnome-shell --wayland, I was able to log in with Nvidia proprietary drivers, but there are some graphical glitches.

Last edited by iFlxy (2023-01-29 12:58:03)

seth · 2023-01-29 15:14:01

The problem is

Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) Backtrace:
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 0: /usr/lib/Xorg (WriteToClient+0x3ed) [0x55e37d75f53d]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7f331d8ac9e0]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 2: /usr/lib/libc.so.6 (memcpy+0x23) [0x7f331d914d53]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) unw_get_proc_name failed: no unwind info found [-10]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 3: /usr/lib/libnvidia-glcore.so.525.85.05 (?+0x0) [0x7f331b06d7a4]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) unw_get_proc_name failed: no unwind info found [-10]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 4: /usr/lib/libnvidia-glcore.so.525.85.05 (?+0x0) [0x7f331b392be8]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) unw_get_proc_name failed: no unwind info found [-10]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 5: /usr/lib/libnvidia-glcore.so.525.85.05 (?+0x0) [0x7f331b392cf8]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) unw_get_proc_name failed: no unwind info found [-10]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 6: /usr/lib/libnvidia-glcore.so.525.85.05 (?+0x0) [0x7f331b0c13e9]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) unw_get_proc_name failed: no unwind info found [-10]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) 7: /usr/lib/nvidia/xorg/libglxserver_nvidia.so (?+0x0) [0x7f3318cca02e]
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE)
Jan 28 17:14:39 iflxypc /usr/lib/gdm-x-session[520]: (EE) Segmentation fault at address 0x7f3318d8f000

This smells like some GL library mixup, but I can't really see why it would happen

ls -R /{etc,usr/share}/X11/xorg.conf*
pacman -Qkk nvidia nvidia-utils libglvnd

iFlxy · 2023-01-29 16:13:01

This is the output of these commands:

[iflxy@iflxypc ~]$ ls -R /{etc,usr/share}/X11/xorg.conf*
pacman -Qkk nvidia nvidia-utils libglvnd
/etc/X11/xorg.conf.d:

/usr/share/X11/xorg.conf.d:
10-nvidia-drm-outputclass.conf  10-quirks.conf  40-libinput.conf
nvidia-dkms: 419 total files, 0 altered files
nvidia-utils: 220 total files, 0 altered files
libglvnd: 58 total files, 0 altered files

Thanks for replying!

seth · 2023-01-29 16:17:59

Looks innocent enough - unfortunately

printenv
ldd /usr/lib/libnvidia-glcore.so.525.85.05
ldd /usr/lib/nvidia/xorg/libglxserver_nvidia.so

iFlxy · 2023-01-29 16:38:03

hmmm... Again, here's the output: (logged in, gnome wayland session)

[iflxy@iflxypc ~]$ printenv
ldd /usr/lib/libnvidia-glcore.so.525.85.05
ldd /usr/lib/nvidia/xorg/libglxserver_nvidia.so
SHELL=/bin/bash
COLORTERM=truecolor
DOTNET_ROOT=/usr/share/dotnet
XDG_SEAT=seat0
PWD=/home/iflxy
LOGNAME=iflxy
XDG_SESSION_TYPE=tty
SYSTEMD_EXEC_PID=488
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.TRWHZ1
MOTD_SHOWN=pam
HOME=/home/iflxy
LANG=en_US.UTF-8
VTE_VERSION=7002
WAYLAND_DISPLAY=wayland-0
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/1686de20_69c7_4ed8_8af2_4d1d1cce395f
DOTNET_BUNDLE_EXTRACT_BASE_DIR=/home/iflxy/.cache/dotnet_bundle_extract
GNOME_SETUP_DISPLAY=:1
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=iflxy
GNOME_TERMINAL_SERVICE=:1.128
KWIN_X11_FORCE_SOFTWARE_VSYNC=1
DISPLAY=:0
SHLVL=1
KWIN_X11_REFRESH_RATE=165000
XDG_VTNR=1
XDG_SESSION_ID=1
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_COLLATE=C
XDG_DATA_DIRS=/home/iflxy/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
PATH=/home/iflxy/.local/bin/:/home/iflxy/.local/bin/:/home/iflxy/.local/bin/:/home/iflxy/.local/bin/:/home/iflxy/.local/bin/:/home/iflxy/.local/bin/:/usr/local/sbin:/usr/local/bin:/usr/bin:/home/iflxy/.dotnet/tools:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin
__GLX_VENDOR_LIBRARY_NAME=nvidia
KWIN_X11_NO_SYNC_TO_VBLANK=1
GBM_BACKEND=nvidia-drm
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/iflxy
_=/usr/bin/printenv
	linux-vdso.so.1 (0x00007ffc4f7ad000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f17bc4e6000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f17b9819000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f17bc4e1000)
	libnvidia-tls.so.525.85.05 => /usr/lib/libnvidia-tls.so.525.85.05 (0x00007f17bc4db000)
	/usr/lib64/ld-linux-x86-64.so.2 (0x00007f17bc5fa000)
	linux-vdso.so.1 (0x00007fff5a6cf000)
	libnvidia-tls.so.525.85.05 => /usr/lib/libnvidia-tls.so.525.85.05 (0x00007f245eac6000)
	libnvidia-glcore.so.525.85.05 => /usr/lib/libnvidia-glcore.so.525.85.05 (0x00007f245b200000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f245b019000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f245dd18000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f245eac1000)
	/usr/lib64/ld-linux-x86-64.so.2 (0x00007f245eaf8000)

Last edited by iFlxy (2023-01-29 16:39:31)

seth · 2023-01-29 16:52:03

__GLX_VENDOR_LIBRARY_NAME=nvidia

Why is that there? You don't seem to have a hybrid graphics system?

Edit:

Update: I tried using multi user target and executing gnome-shell --wayland

Running xorg on gnome from the multi-user.target (no GDM) does also not work?
What about eg. openbox?

Last edited by seth (2023-01-29 16:54:12)

iFlxy · 2023-01-29 22:02:21

Yes that’s true, I don’t have a hybrid graphics system, I don’t know why is that there, maybe something I changed while following this (top comment) tutorial (I ended up switching to wayland), and also I think i didn’t word it correctly, sorry, english is not my first language, running gnome on wayland from multi user target works, but I didn’t try xorg. I’ll update this post when I get back home and try running it on xorg.

Edit:

Last edited by iFlxy (2023-01-29 22:39:18)

iFlxy · 2023-02-03 18:16:38

bump

seth · 2023-02-03 22:17:46

Yeah, there're no notifications for edits, sorry.

On topic:
Please post the Xorg log after such failure (~/.local/share/xorg/Xorg.0.log)
In general please avoid posting images of text (see the 1st link below on how to paste text from the console) and if you're sending them, it would be nice if they were not rotated

iFlxy · 2023-02-07 13:46:02

Alright, I'll remember not to post images with text.

Here's my Xorg.0.log

seth · 2023-02-07 14:33:03

Still same as https://bbs.archlinux.org/viewtopic.php … 2#p2081902

pacman -Qs nvidia

iFlxy · 2023-02-07 20:02:07

Here's the output: https://pastebin.com/4R2G4NSx

seth · 2023-02-07 23:07:44

Nope. (I had hoped nvidia-open would show up)
Since you're booting the regular kernel, you could try nvidia instead of nvidia-dkms - and make sure to remove the __GLX_VENDOR_LIBRARY_NAME export.

iFlxy · 2023-02-13 07:08:16

The problem magically fixed itself, I have no clue what I did. Now I'm having another issue, I can't use Wayland when booting into graphical target. There isn't an option to use Wayland under the settings button on the login screen, but "gnome-shell --wayland" works just fine.
Edit: I fixed the problem by editing the 61-gdm.rules file, but sometimes Wayland sessions crash for no reason.

Last edited by iFlxy (2023-02-13 12:32:19)

seth · 2023-02-13 08:37:28

https://bbs.archlinux.org/viewtopic.php … 9#p2083239

Arch Linux

#1 2023-01-29 11:43:01

Stuck at blinking cursor, Nvidia drivers

#2 2023-01-29 15:14:01

Re: Stuck at blinking cursor, Nvidia drivers

#3 2023-01-29 16:13:01

Re: Stuck at blinking cursor, Nvidia drivers

#4 2023-01-29 16:17:59

Re: Stuck at blinking cursor, Nvidia drivers

#5 2023-01-29 16:38:03

Re: Stuck at blinking cursor, Nvidia drivers

#6 2023-01-29 16:52:03

Re: Stuck at blinking cursor, Nvidia drivers

#7 2023-01-29 22:02:21

Re: Stuck at blinking cursor, Nvidia drivers

#8 2023-02-03 18:16:38

Re: Stuck at blinking cursor, Nvidia drivers

#9 2023-02-03 22:17:46

Re: Stuck at blinking cursor, Nvidia drivers

#10 2023-02-07 13:46:02

Re: Stuck at blinking cursor, Nvidia drivers

#11 2023-02-07 14:33:03

Re: Stuck at blinking cursor, Nvidia drivers

#12 2023-02-07 20:02:07

Re: Stuck at blinking cursor, Nvidia drivers

#13 2023-02-07 23:07:44

Re: Stuck at blinking cursor, Nvidia drivers

#14 2023-02-13 07:08:16

Re: Stuck at blinking cursor, Nvidia drivers

#15 2023-02-13 08:37:28

Re: Stuck at blinking cursor, Nvidia drivers

Board footer