On 4/16/25 10:47, Fab Stz via pkg-nvidia-devel wrote:

Maybe not as grave as I thought
Apparently it's only a warning.

I could be a consequence of this commit which appeard in kernel 6.9

There is nothing we can do about that since we cannot recompile the blob
parts with newer hardening options ...

Does the module still work? I'm trying to backport patches to keep the
module buildable for newer kernels, but I have no way to test it at all ;-)


Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 5/23/25 09:47, Fab Stz wrote:

Hello Andreas,

At last I could have a check on that computer.

Actually the driver seems to load fine despite the kernel warning but
the nvidia logo is not displayed and nothing is displayed on screen. But
the computer responds. I can reboot by doing Ctrl+Alt+F1 and then Ctrl+Alt+Del.

I additionally created a symlink in /usr/lib/xorg/modules/drivers/
nv_drv.so -> nvidia_drv.so because this seems required. Maybe X is now searching for "nv" instead of "nvidia" ?

There is/was a 'nv' driver in Xorg, but it is no longer packaged in
Debian. It was likely superseded by 'nouveau'.

If xorg.conf does not specify a driver, Xorg will try all possibly
fitting driver names for the detected hardware, thus you see the failure
to load nv, but that does not matter.

But you shouldn't rename/symlink the drivers, as that's a source for
major confusion. Please revert.

You might try a minimal xorg.conf (or xorg.conf.d/*.conf snippet)
containing only

Section "Device"
Identifier "My GPU"
Driver "nvidia"
EndSection

to specifically select the proprietary driver and skip autoprobing.
Should help to avoid irrelevant error messages from autoprobed drivers.

But it may well be that the driver is no longer compatible with current
Xorg versions.


Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)