[Bug 291232] x11/nvidia-kmod: On recent CURRENT black screen, problem rebooting

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291232

            Bug ID: 291232
           Summary: x11/nvidia-kmod: On recent CURRENT black screen,
                    problem rebooting
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])

On recent CURRENT (FreeBSD 16.0-CURRENT #14 master-n282165-718acd74657f: Wed
Nov 26 08:26:23 CET 2025 amd64) with a recent nvidia 5060Ti GPU, port 
x11/nvidia-kmod (nvidia-kmod-580.105.08.1600004) fails to present xdm/GUI. The
x11/nvidia-kmod, x11/nvidia-driver ports are recompiled every time world/kernel
is build.

xdm is setup via /etc/ttys (ttyv9   "/usr/local/bin/xdm -nodaemon"  xterm  
onifexists      insecure).

Since a couple of days for now, it seems that with recent nvidia kernel module
loaded, a reboot (either reboot or shutdown -r now) takes a long time until an
error occurs ("... some processes would not die, ... adviced"). It is not
possible to interrupt or watch which process rejects to perish, but I guess it
is xdm.

Without nvidia kernel module loaded, FreeBSD behaves in most cases as expected
and performs a clean reboot or even working without GUI is possible so far.

I use a custom kernel! Custom kernel worked before, I guess, commit
9562994a7aacee2baae6ddee1a7b558b48ae39ef - this commit is a marker to me, I
rebuilt kernel yesterday before this commit has been made and it worked so far
even with GUI. After that commit, I had to follow now vanished UPDATING remarks
about setting some sysctl flags (see my PR 291212 on that).

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.