Arch Linux

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,535

Re: nvidia-390xx AUR package discussion thread

With my Mac that has a GT 750M

According to https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/ that card should use the 470 driver , not the 390 .

Please post the output of lspci -knn -d ::03xx so the exact type/model of your card can be verified.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

4194304

Member

Registered: 2023-09-08

Posts: 14

Re: nvidia-390xx AUR package discussion thread

With my Mac that has a GT 750M

According to https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/ that card should use the 470 driver , not the 390 .

Please post the output of lspci -knn -d ::03xx so the exact type/model of your card can be verified.

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1)
    Subsystem: Apple Inc. Device [106b:0130]
    Kernel driver in use: nvidia
    Kernel modules: nouveau

nvidia_drm is missing as I'm trying to test the 470xx drivers to see if they work, but they likely will not

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,274

Re: nvidia-390xx AUR package discussion thread

They should, it's a Kepler card (GK107M is the relevant identification bit).

Nevertheless nvidia_drm would not show up on that output anyway.

ZelzalGD

Member

Registered: 2025-04-17

Posts: 2

Re: nvidia-390xx AUR package discussion thread

i did an update that led to my system to not boot probably
pacman.log
https://0x0.st/8Ofl.txt
the day that i update and it broke the system:
14th Apr 2025 - 15th apr 2025
Journalctl
https://0x0.st/8OZq.txt
i have already tried to rebuild the aur packages with nvidia in the name
and did `nvidia-drm.modeset=1` in grub commandline
i have downgraded for now but its not visible in the logs

Last edited by ZelzalGD (Yesterday 12:13:23)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,535

Re: nvidia-390xx AUR package discussion thread

Apr 17 15:11:23 Zelzal kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Apr 17 15:11:23 Zelzal kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Apr 17 15:11:23 Zelzal kernel: fbcon: Deferring console take-over
Apr 17 15:11:23 Zelzal kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Apr 17 15:11:23 Zelzal kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Apr 17 15:11:23 Zelzal kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
Apr 17 15:11:23 Zelzal kernel: Failed to initialize the nv-hotplug-helper DRM client (ensure DRM kernel mode setting is enabled via nvidia-drm.modeset=1).
Apr 17 15:11:23 Zelzal kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Unloading driver

Nvidia driver doesn't cooperate well with simpledrm device .

Try adding nvidia-drm.modeset=1 to your boot command line .
(How to do that depends on your chosen bootloader.)

NOTE: do not add it to a file in /etc/modprobe.d , that is processed to late for this to work.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

seth

Member

Registered: 2012-09-03

Posts: 62,824

Re: nvidia-390xx AUR package discussion thread

If that's not it (though you want to enable kms regardless of simpledrm and crash)

Apr 17 15:11:40 Zelzal systemd-coredump[611]: Process 601 (Xorg) of user 0 dumped core.

Stack trace of thread 601:
#0  0x000071c1dde2a5e7 abort (libc.so.6 + 0x255e7)
#1  0x00005d9e2fbb4b3e OsAbort (/usr/lib/Xorg + 0x153b3e)
#2  0x00005d9e2fbb6037 FatalError (/usr/lib/Xorg + 0x155037)
#3  0x00005d9e2fbbcfd8 n/a (/usr/lib/Xorg + 0x15bfd8)
#4  0x000071c1dde42cd0 n/a (libc.so.6 + 0x3dcd0)
#5  0x000071c1dde9c624 n/a (libc.so.6 + 0x97624)
#6  0x000071c1dde42ba0 raise (libc.so.6 + 0x3dba0)
#7  0x000071c1dde2a582 abort (libc.so.6 + 0x25582)
#8  0x000071c1dde2b3bf n/a (libc.so.6 + 0x263bf)
#9  0x000071c1ddea6765 n/a (libc.so.6 + 0xa1765)
#10 0x000071c1ddea67f3 n/a (libc.so.6 + 0xa17f3)
#11 0x000071c1ddeabaaf __libc_free (libc.so.6 + 0xa6aaf)
#12 0x00005d9e2fbd038c n/a (/usr/lib/Xorg + 0x16f38c)
#13 0x00005d9e2fbdb0fa InitOutput (/usr/lib/Xorg + 0x17a0fa)
#14 0x00005d9e2fa93c69 n/a (/usr/lib/Xorg + 0x32c69)
#15 0x000071c1dde2c488 n/a (libc.so.6 + 0x27488)
#16 0x000071c1dde2c54c __libc_start_main (libc.so.6 + 0x2754c)
#17 0x00005d9e2fa952b5 _start (/usr/lib/Xorg + 0x342b5)
ELF object binary architecture: AMD x86-64

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ZelzalGD

Member

Registered: 2025-04-17

Posts: 2

Re: nvidia-390xx AUR package discussion thread

Xorg.0.log
http://0x0.st/8OEP.txt

seth

Member

Registered: 2012-09-03

Posts: 62,824

Re: nvidia-390xx AUR package discussion thread

[    30.520] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 20 13:40:01 2025
[    30.520] (==) Using config file: "/etc/X11/xorg.conf"
[    30.520] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    30.520] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    30.520] (EE) 
[    30.520] (EE) Backtrace:
[    30.520] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.520] (EE) 0: /usr/lib/Xorg (?+0x0) [0x5ab77348df7c]
[    30.521] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.521] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d19cd0]
[    30.521] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.521] (EE) 2: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d73624]
[    30.521] (EE) 3: /usr/lib/libc.so.6 (gsignal+0x20) [0x7579e1d19ba0]
[    30.521] (EE) 4: /usr/lib/libc.so.6 (abort+0x26) [0x7579e1d01582]
[    30.521] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.522] (EE) 5: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d023bf]
[    30.522] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.522] (EE) 6: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d7d765]
[    30.522] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.522] (EE) 7: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d7d7f3]
[    30.522] (EE) 8: /usr/lib/libc.so.6 (__libc_free+0x1ff) [0x7579e1d82aaf]
[    30.522] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.522] (EE) 9: /usr/lib/Xorg (?+0x0) [0x5ab7734a138c]
[    30.523] (EE) 10: /usr/lib/Xorg (InitOutput+0x135a) [0x5ab7734ac0fa]
[    30.523] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.523] (EE) 11: /usr/lib/Xorg (?+0x0) [0x5ab773364c69]
[    30.523] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    30.523] (EE) 12: /usr/lib/libc.so.6 (?+0x0) [0x7579e1d03488]
[    30.523] (EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0x8c) [0x7579e1d0354c]
[    30.523] (EE) 14: /usr/lib/Xorg (_start+0x25) [0x5ab7733662b5]
[    30.523] (EE) 
[    30.523] (EE) 

It seems to crash right away with a corrupted stack…

[    30.520] Current Operating System: Linux Zelzal 6.13.5-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 27 Feb 2025 18:09:44 +0000 x86_64

You're booting some dated kernel?

and did `nvidia-drm.modeset=1` in grub commandline

And that's not reflected by the log at all, did you forget to run grub-mkconfig?

pacman -Qikk linux xorg-server nvidia-390xx-utils mesa glibc libx11

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc