Skip to content

Nvidia driver and linux 6.12 phantom monitor

Description:

A continuation of #80 (closed)

What are nVidia users to do to have a functional TTY with kernel 6.12, now that the simpledrm-skipping patch has been dropped?

Options I see currently:

  1. Carry the patch and build locally
  2. Modify the config (CONFIG_SYSFB_SIMPLEFB=n) and build locally.

EDIT: I went with option #2 as a workaround for now.

Additional info:

  • linux 6.12.1.arch1-1
  • nvidia-dkms 565.57.01-2
  • nvidia-utils 565.57.01-2

Steps to reproduce:

  • nvidia_drm.modeset=1 nvidia_drm.fbdev=0 results in "phantom monitor" simpledrm device active. TTY is available.

  • nvidia_drm.modeset=1 nvidia_drm.fbdev=1 results in early boot text visible, blind-entering LUKS pwd, graphical session without TTY. Attempting to switch to TTY results in session freeze when attempting to switch to a TTY. REing (of the REISUB) returns to the GDM login screen where I can then log back in and continue a session or restart gracefully.

  • nvidia_drm.modeset=1 nvidia_drm.fbdev=1 initcall_blacklist=simpledrm_platform_driver_init results in black screen at boot, blind-entering LUKS pwd, graphical session without TTY. Attempting to switch to TTY freezes system results in session freeze when attempting to switch to a TTY. REing (of the REISUB) returns to the GDM login screen where I can then log back in and continue a session or restart gracefully.

  • nvidia_drm.modeset=1 nvidia_drm.fbdev=0 initcall_blacklist=simpledrm_platform_driver_init results in black screen at boot, blind-entering LUKS pwd, graphical session without TTY. Attempting to switch to TTY freezes system results in session freeze when attempting to switch to a TTY. REing (of the REISUB) returns to the GDM login screen where I can then log back in and continue a session or restart gracefully.

Edited by tekstryder
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information