Date: Sun, 30 Nov 2025 01:45:30 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: FreeBSD User <freebsd@walstatt-de.de> Cc: Tomek CEDRO <tomek@cedro.info>, freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: CURRENT: working alternative nVidia GPU driver for x11/nvidia-kmod? Message-ID: <20251130014530.3f8d7fa8efeca2ce99f6a434@dec.sakura.ne.jp> In-Reply-To: <20251129142412.1746f00c@hermann> References: <20251129131506.41ceec97@hermann> <CAFYkXj=M6-AB77vn_n_1yPmWpX%2Bhq_y8743mWrRBqiN9wPmELA@mail.gmail.com> <20251129142412.1746f00c@hermann>
index | next in thread | previous in thread | raw e-mail
On Sat, 29 Nov 2025 14:25:00 +0100 FreeBSD User <freebsd@walstatt-de.de> wrote: > On Sat, 29 Nov 2025 13:18:12 +0100 > Tomek CEDRO <tomek@cedro.info> wrote: > > > On Sat, Nov 29, 2025 at 1:15 PM FreeBSD User <freebsd@walstatt-de.de> wrote: > > > Since some recent changes to the CURRENT kernel, x11/nividia-kmod/driver is > > > no longer working. Either kernel module nvidia-modeset.ko/nvidia.ko reject > > > to load with a failure when both the following OIDs are set to ZERO: > > > > Do you have this set in /boot/loader.conf for the new nvidia gpu? > > > > Loading the GPU driver module via /etc/rc.conf.local saves me from > crashes/kernel hung in case of a problem, so setting those OIDs in loader.conf > is ineffective here because the module isn't already loaded. > > > hw.nvidiadrm.modeset=1 > > hw.nvidia.registry.EnableGpuFirmware=1 > > I've set hw.nvidia.registry.EnableGpuFirmware=1 in /etc/sysctl.conf.local, the > first one not. > > Loading "kldload nvidia-modeset" after a successful boot of CURRENT. > > Issuing > sysctl hw.nvidia.registry.EnableGpuFirmware=1 > hw.nvidia.registry.EnableGpuFirmware: 0 -> 1 > > but for > # sysctl hw.nvidiadrm.modeset=1 > sysctl: unknown oid 'hw.nvidiadrm.modeset' > > > > > Or this is another problem? > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info Please try patch at Bug291212 [1] or review D53987 [2]. Both are actually the same patch. But if this is the case, the offending commit is temporarily reverted now at commit fad4c92b78a123f87195173ac118655fa8e325cd as of "Stabilization Week". So upgrading to it would help, but once the offending commit 9562994a7aacee2baae6ddee1a7b558b48ae39ef is reapplied, the issue would be surely revive without actual fix. And maybe commit e00a781c216cb12603a0a71c9ca293dde3e06250 or later would be wanted if you don't explicitly disabled LINUX option for x11/nvidia-kmod[-devel]. (This is just my prediction, as my main branch environment is too outdated to test. stable/15 and main are installed in different SSDs of exactly the same computer, thus, hard to take time to switch to main and upgrade to test.) [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291212 [2] https://reviews.freebsd.org/D53987 -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20251130014530.3f8d7fa8efeca2ce99f6a434>