Bug#1099016: nvidia-legacy-340xx-driver: Unpatched return thunk in use. This should not happen!

[Fab Stz]

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" ?

So now in that dir I have these symlinks

nv_drv.so -> nvidia_drv.so
nvidia_drv.so -> /etc/alternatives/glx--nvidia_drv.so

However it is still failing. Please find full Xorg.0.log attached

Snippet below:

[    23.691] (EE) LoadModule: Module nv does not have a nvModuleData 
data object.
[    23.691] (EE) Failed to load module "nv" (invalid module, 0)
[    24.331] (EE) [drm] Failed to open DRM device for pci:0000:03:00.0: -19
[    24.331] (EE) open /dev/dri/card0: Invalid argument
[    24.331] (EE) open /dev/dri/card0: Invalid argument
[    24.334] (EE) Unable to find a valid framebuffer device
[    24.335] (EE) Screen 0 deleted because of no matching config section.
[    24.335] (EE) Screen 0 deleted because of no matching config section.
[    24.380] (II) Initializing extension MIT-SCREEN-SAVER
[    24.386] (EE) Failed to initialize GLX extension (Compatible NVIDIA 
X driver not found)

Maybe there is something problematic with the "nv" vs "nvidia" module name?

Do you have any idea on how to debug further?

Regards
Fab



On Wed, 16 Apr 2025 11:47:32 +0200 Fab Stz <fabstz-it at yahoo.fr> wrote:
> Last time I tried I thought it failed because of this log, but I would have to check again to be sure. It will take some time until I can access this computer.
> 
> Fab
> 
> Le 16 avril 2025 10:58:07 GMT+02:00, Andreas Beckmann <anbe at debian.org> a écrit :
> >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
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: text/x-log
Size: 24281 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20250523/ffdbe549/attachment-0001.bin>