Bug#995026: Update

2022-02-13 Thread Jeremy Hendricks
Correction to above: Option #1 is preferable as I don't know if installing updates down the road for Option #2 would cause libnvidia-cfg1 to be installed. I assume it will be fine but you know what they say about 'assume'.

Bug#995026: Update

2022-02-13 Thread Jeremy Hendricks
I was able to finally track down this issue. The issue is due to the 32bit packages being installed if you have 'sudo dpkg --add-architecture i386'. If you do, 'sudo apt install nvidia-legacy-390xx-driver' will install libnvidia-cfg1 (which is an nvidia 460 component) that causes the initial issue

Bug#995026: Update

2022-01-23 Thread Jeremy Hendricks
This is definitely a misconfiguration on my part. I’m trying to track down why it works for me in one case and not another (on the same hardware). Maybe that’ll save others some frustration if it’s just a missing package or similar.

Bug#995026: Update

2022-01-22 Thread Jeremy Hendricks
I take that back. It worked fine on a Debian 11 machine with a GTX 460. I tried today on my other machine with Debian 11 and a GT 630 and ran into this issue again. I’m going to try to determine the real cause on the same machine the GTX 460 works on. Please keep this open. My workaround in the

Bug#995026: Update

2021-09-25 Thread Jeremy Hendricks
I confirmed this also happens in Testing (bookworm) aside from it pulling in Nvidia 470 packages instead. I tested this on the same machine but in a bookworm chroot with: apt install nvidia-legacy-390xx-driver -s