Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: minixjr on 2021/05/28, 16:04:18
-
Hello all,
after updating the Nvidia driver to version 460.80 my system froze at next boot, sometimes kernel panics.
I found out that there are other poor people, like me, who have this problem, even with newer drivers like 465.31.
Please see: https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782 (https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782)
To me it looks like it is hardware dependent, monitor+port+resolution.
Take care
minixjr
-
And what do you think, we can do?
-
I don't think you can do anything, it's on Nvidia. Or, maybe you can provide the last 45x driver within the siduction repository?
As far I can see it's a problem with the monitor, from Dell and Benq, maybe others.
If someone already have this problem, a workaround could be:- use the nouveau driver
- if the nvidia card is supported by the tesla driver, use this one (like me, ask nvidia-detect)
:~$ nvidia-detect
Detected NVIDIA GPUs:
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1)
Checking card: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)
Your card is supported by the default drivers.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
It is recommended to install the
nvidia-driver
package.
To access the system you have to start with grub option "single" and than remove all the nvidia stuff.
apt purge *nvidia* and reboot.
For nouveau, I think, you need to install at least
apt install xserver-xorg-video-nouveauAnd for Teslaapt install nvidia-tesla-460-driverHope this helps
minixjr
-
You could grab 460.73.01 from testing.
-
Thank you for pointing this out. For some reason testing was not in my sources.list. ???
-
From that thread on the nvidia forum, this has something to do with 4k and DisplayPort.
-
Thank you for pointing this out. For some reason testing was not in my sources.list. ???
Testing should not be enabled permanently in your sources. If you add it to try that driver, disable it immediately after installing. nvidia-driver will be upgraded to the sid version next time you run upgrade anyway so you would need to pin all the nvidia packages, of which they are many, until the issue is fixed. Or just don't upgrade until it's fixed which could eventually bring its own problems.
Edited to reflect subsequent advice from towo.
-
Testing should not be enabled permanently in your sources.
Why not? enabling testing is not a problem.
-
Testing should not be enabled permanently in your sources.
Why not? enabling testing is not a problem.
I stand corrected. It's not included by default and seems rather pointless as packages from testing would overwritten by unstable packages in the normal course of upgrades.
-
packages from testing would overwritten by unstable packages in the normal course of upgrades.
That's exactly the point, why it doesn't matter if testing is activated. And sometimes testing is needed, if a version in sid has a bug, and the version in testing is running fine. So there is no problem wit testing in the sources.
-
Thanks for the clarification, towo. So if one were to install the nvidia-driver package from testing, I guess it should be held with apt-mark hold nvidia-driver until the issue is resolved in unstable.
-
For me the problem is solved with the new driver 470.42.01 from experimental
$ inxi -G
Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 470.42.01
Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution: 3840x2160~60Hz
OpenGL: renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 470.42.01