Skip to content

Conversation

@pmenzel
Copy link
Contributor

@pmenzel Paul Menzel (pmenzel) commented Oct 14, 2026 •

AI disclaimer: This merge/pull request was generated by claude-opus-5.5 and reviewed by Paul Menzel (@pmenzel).

On hosts tagged desktop (hostconfig --list desktop), load nvidia-drm with modeset=1. (All installed driver versions (535.104.05, 570.144, 580.178.04) default to modeset=0.):

$ modinfo -p /usr/share/nvidia/kernel/6.18.51.mx64.498/nvidia-drm.ko
modeset:Enable atomic kernel modesetting (1 = enable, 0 = disable (default)) (bool)
fbdev:Create a framebuffer device (1 = enable (default), 0 = disable) (bool)

The parameter is passed to insmod directly, because nvidiactl loads the modules from /usr/share/nvidia/kernel/, not via modprobe.

Note: Since 570, fbdev=1 is the default, so with modeset=1 nvidia-drm also takes over the console framebuffer.

Tested on sigusr2.

On hosts tagged *desktop*, load nvidia-drm with `modeset=1`.  All
installed driver versions (535.104.05, 570.144, 580.178.04) still
default to `modeset=0`:

    $ modinfo -p /usr/share/nvidia/kernel/6.18.51.mx64.498/nvidia-drm.ko
    modeset:Enable atomic kernel modesetting (1 = enable, 0 = disable (default)) (bool)
    fbdev:Create a framebuffer device (1 = enable (default), 0 = disable) (bool)

Without kernel modesetting, the DRM device registered by nvidia-drm
offers no KMS, so Wayland compositors cannot drive the display on the
proprietary driver.

The parameter is passed to insmod directly, since nvidiactl loads the
modules from /usr/share/nvidia/kernel/ and not via modprobe, so a
modprobe.d snippet would have no effect.

Assisted-by: claude-opus-5.5 (Claude Code)
Sign in to join this conversation on GitHub.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant