[EN] Nvidia card not recognized after updating to kernel 6.12.2-1-siduction-amd64

[DrJuanNadie]

I have 2 screens connected to an integrated Intel GPU and a 3rd one to an additional Nvidia card. After updating my system to kernel 6.12.2-1-siduction-amd64, the 3rd screen is not recognized, nor does the Nvidia card seem to be. My Nvidia driver version is 535. I rolled back the installation so I can keep working with my system, so that's all I can report.

[n4ai9i522]

Confirming this, gdm3 did not start and I was left with a blinking cursor on top left corner.
Tried configuring sddm from another shell, and a similar thing happened.
Finally could start by booting with previous kernel version. If I receive and install yet another new kernel, and I don't autoremove the current one which is working, I can still have siduction boot off it from grub, that will show 3 available kernels, right?

[michaa7]

...My Nvidia driver version is 535...

There is

Installationskandidat: 550.135-0~siduction.1
  Versionstabelle:
     550.135-0~siduction.1 500
        500 http://packages.siduction.org/fixes unstable/non-free

in the siductioon fixes repo. Don't know whether or not it makes a difference for your system, though.

[DrJuanNadie]

Info about my current well-working driver (without updating):

Code: [Select]

nvidia-smi
Fri Dec  6 10:07:41 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.216.03             Driver Version: 535.216.03   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1050        Off | 00000000:01:00.0  On |                  N/A |
|  0%   45C    P0              N/A /  65W |     49MiB /  2048MiB |     15%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1815      G   /usr/lib/xorg/Xorg                           47MiB |
+---------------------------------------------------------------------------------------+


[n4ai9i522]

Issue still standing with 6.12.3

[DrJuanNadie]

Seems there needs to be an update to nvidia drivers so that they can work on 6.12 kernels. For now I locked my system at 6.11 so that there be no further updates to kernel till this is resolved.

[n4ai9i522]

Seems there needs to be an update to nvidia drivers so that they can work on 6.12 kernels. For now I locked my system at 6.11 so that there be no further updates to kernel till this is resolved.

I hope you can pardon my newbness, how does one lock a specific kernel? I have searched online and found "pinning", or removing the metapackage so that it will not interfere with 6.11, plus other suggestions I wasn't really comfortable with as they seemed to need some invasive changes that required invasive procedures to revert.

I hope there is a way to just flag 6.11 as the version you want to keep, until a new nvidia driver is released at which point you can unflag 6.11?

[DrJuanNadie]

I hope you can pardon my newbness, how does one lock a specific kernel?

To "block" (hold):

Code: [Select]

sudo apt-mark hold linux-image-siduction-amd64 linux-headers-siduction-amd64 linux-doc linux-cpupower linux-libc-dev

To "unblock" (unhold):

Code: [Select]

sudo apt-mark unhold linux-image-siduction-amd64 linux-headers-siduction-amd64 linux-doc linux-cpupower linux-libc-dev

To consult what is being held:

Code: [Select]

apt-mark showhold

That's what I do.

[n4ai9i522]

Thanks, going straight to my personal notes! By holding the meta package though, I will still notice via apt output that there is a new version, even if it won't be installed, right?

[DrJuanNadie]

Thanks, going straight to my personal notes! By holding the meta package though, I will still notice via apt output that there is a new version, even if it won't be installed, right?

I don't know.

[der_bud]

..., I will still notice via apt output that there is a new version, even if it won't be installed, right?

Yes, not after 'apt update' but 'apt full-upgrade' will tell you

Code: [Select]

Calculating upgrade... Done
The following packages have been kept back:
  foo-packageonhold bar-dependingonfoo
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.It won't tell you why they are kept back, so remember your holds