nvidia 390.157-13 Failed to acquire modesetting permission

dakota · 2024-12-02 19:25:23

After upgrading nvidia-390xx-utils and nvidia-390xx-dkms from 12 ==> 13 (and executing mkinitcpio -P), xorg fails to start (via startx).

65:00.0 VGA compatible controller: NVIDIA Corporation GF119 [NVS 315] (rev a1)
	Subsystem: NVIDIA Corporation Device 102f
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia

xorg log
journal

I tried adding nvidia_drm.fbdev=0 to the kernel parameters, but this leads to

kernel: nvidia_drm: unknown parameter 'fbdev' ignored

Cheers,

Last edited by dakota (2024-12-02 19:27:25)

pvtvega · 2024-12-02 20:42:55

From your bootlogs, it looks like the kernel is using simpledrm which is not supported with the NVIDIA drivers when the nvidia_drm.fbdev parameter is set to 0. Does enabling this parameter allow the X server to start?

dakota · 2024-12-02 21:04:11

pvtvega wrote:

From your bootlogs, it looks like the kernel is using simpledrm...

That's odd. Shouldn't setting...

nvidia_drm.modeset=1

... as a kernel parameter enable DRM kernel mode setting? Or is that something different?

Note that later in the journal, it appears that drm is initialized

Dec 02 10:45:52 maria kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
...
Dec 02 10:45:52 maria kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 241
Dec 02 10:45:52 maria kernel: [drm] [nvidia-drm] [GPU ID 0x00006500] Loading driver
Dec 02 10:45:52 maria kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:65:00.0 on minor 1
Dec 02 10:45:52 maria kernel: Registered the nv-hotplug-helper DRM client.

# cat /sys/module/nvidia_drm/parameters/modeset
Y

pvtvega wrote:

Does enabling this (the nvidia_drm.fbdev parameter) allow the X server to start?

No.

It makes no difference if I omit the parameter, explicitly enable it, or explicitly disable it. In all cases, the journal reports

kernel: nvidia_drm: unknown parameter 'fbdev' ignored

Cheers,

Last edited by dakota (2024-12-02 21:05:05)

seth · 2024-12-02 21:05:15

The nvidia_drm.modeset=1 hack wa removed from the 6.12 kernels for "reasons", I guess.
Use the LTS kernel - for the 6.12 kernel you can try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

The nvidia_drm.fbdev is only supported since some 5xx.xx version (525 or 535 or so)

https://gitlab.archlinux.org/archlinux/ … /issues/94

dakota · 2024-12-02 21:27:34

seth wrote:

The nvidia_drm.modeset=1 hack wa removed from the 6.12 kernels for "reasons", I guess.

Humph.

seth wrote:

Use the LTS kernel.

The LTS kernel works fine, and I'm happy to use that as a short-term solution.

seth wrote:

...for the 6.12 kernel you can try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters.

Using this results in a black screen, but with the following entry in the journal

kernel: initcall simpledrm_platform_driver_init blacklisted

Cheers,

EDIT - Thanks for your feedback, Seth!

Last edited by dakota (2024-12-02 23:24:39)

seth · 2024-12-02 21:31:10

Using this results in a black screen, but with the following entry in the journal

By this time an expectable pattern

Stay tuned for developments on the gitlab bug. I hope.

pvtvega · 2024-12-02 21:33:34

seth wrote:

The nvidia_drm.modeset=1 hack wa removed from the 6.12 kernels for "reasons", I guess.

This is good to know, thanks. Can you clarify what "removed" means? And what would be the rationale for disabling this?

WorMzy · 2024-12-02 22:34:18

Mod note: moving to AUR Issues.

seth · 2024-12-02 22:38:22

pvtvega wrote:

Can you clarify what "removed" means? And what would be the rationale for disabling this?

It was a downstream patch that no longer gets applied.
No reason has been published.
The question is open on the gitlab bug - it could just be "let's see whether we still need this", but nvidia_drm.fbdev doesn't reliably work and blocking the simlpydumb initcall seems too late and older nvidia drivers cannot handle this at all. Unless there's a technical reason (patch no longer compiles etc.) I see no upside in removing it.

tekstryder · Yesterday 23:20:37

seth wrote:

Unless there's a technical reason (patch no longer compiles etc.)

The patch (as of 6.11.9 build) requires no rebase and applies cleanly to kernel 6.12.1.

Applying patch disable-simple-drm.patch...
patching file drivers/firmware/sysfb.c

Most recent commit to sysfb.c was on 2024-09-26.

Patched kernel 6.12.1 compiles without issue.

Arch Linux

#1 2024-12-02 19:25:23

nvidia 390.157-13 Failed to acquire modesetting permission

#2 2024-12-02 20:42:55

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#3 2024-12-02 21:04:11

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#4 2024-12-02 21:05:15

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#5 2024-12-02 21:27:34

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#6 2024-12-02 21:31:10

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#7 2024-12-02 21:33:34

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#8 2024-12-02 22:34:18

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#9 2024-12-02 22:38:22

Re: nvidia 390.157-13 Failed to acquire modesetting permission

#10 Yesterday 23:20:37

Re: nvidia 390.157-13 Failed to acquire modesetting permission

Board footer