Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Debian Bullseye (11): Kernel update upset Nvidia with linux-image-5.10.0-29-amd64 (5.10.216-1)

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
Theuthr
Posts: 10
Joined: 2017-08-26 00:14
Been thanked: 1 time

Debian Bullseye (11): Kernel update upset Nvidia with linux-image-5.10.0-29-amd64 (5.10.216-1)

#1 Post by Theuthr »

F.Y.I
Just downloaded the the latest Bullseye update and it reverted the graphics to 640x480 from 2650x1440 :o

Code: Select all

Commandline: packagekit role='update-packages'
Install: 
linux-image-5.10.0-29-amd64:amd64 (5.10.216-1),
 linux-headers-5.10.0-29-common:amd64 (5.10.216-1),
 linux-headers-5.10.0-29-amd64:amd64 (5.10.216-1)
Upgrade: 
linux-kbuild-5.10:amd64 (5.10.209-2, 5.10.216-1),
Had to revert back to;-

Code: Select all

linux-image-5.10.0-28-amd64          5.10.209-2   amd64
To restore graphics.

Machine.

Code: Select all

Debian GNU/Linux 11 (bullseye) x86_64
Graphics:
  Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 470.223.02 
  Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~75Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.223.02 
CPU:
  Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP L2 cache: 3 MiB
Edit: B.T.W Nvidia driver loaded via APT when installing Bullseye.

hope this is useful

Aki
Global Moderator
Global Moderator
Posts: 3110
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 78 times
Been thanked: 419 times

Re: Kernel update upset Nvidia

#2 Post by Aki »

Hello,

Thanks for reporting.

The package is from:

Code: Select all

$ rmadison linux-image-5.10.0-29-amd64
linux-image-5.10.0-29-amd64 | 5.10.216-1    | oldstable-new | amd64
Subject modified from:
  • "Kernel update upset Nvidia"
to:
  • "Debian Bullseye (11): Kernel update upset Nvidia with linux-image-5.10.0-29-amd64 (5.10.216-1)"
The discussion is moved from:
  • "System and Network configuration" sub-forum
to:
  • "General Questions" sub-forum
Please, use code tags to include commands and/or their logs in the body of a message. I'll do it for you in previous message.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

linuxsat
Posts: 51
Joined: 2017-10-20 14:28
Has thanked: 1 time

Re: Debian Bullseye (11): Kernel update upset Nvidia with linux-image-5.10.0-29-amd64 (5.10.216-1)

#3 Post by linuxsat »

Hello,

I experienced the same kind of problem with the last kernel update (5.10.0-29) : the discrete Nvidia card of my laptop (DEll Precision 3561), seems
no longer taken into account (the nvidia-settings no longer starts, and the fan runs almost continuously), the problem disappears when booting on the
previous kernel 5.10.0-28).

Is anything to remedy that issue, other than booting on kernel 5.10.0-28 and wait for an update ?

Cheers

talwrii
Posts: 1
Joined: 2024-05-15 14:36

Re: Debian Bullseye (11): Kernel update upset Nvidia with linux-image-5.10.0-29-amd64 (5.10.216-1)

#4 Post by talwrii »

I got this error with google cloud platform's custom image `linux-image-5.10.0-29-cloud-amd64` which is probably a similar fork based on 5.10.216-1.

Based on the errors when trying to rebuild the nvidia errors, I suspect this is the same as issue as raised in this nvidia thread against 6.7.3 probably because of a backport.[1]
(base) jupyter@******:~$ sudo cat /var/log/nvidia-installer.log | grep FATAL
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
The issue seems to be that something about the build processes stops people from running proprietary code that is tained by GPL code. Strangely the kernel module still seems to be loaded.

[1] https://forums.developer.nvidia.com/t/l ... /280908/25

Post Reply