Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There's a bug in Nvidia proprietary drivers triggered by upgrading to 6.1.0-18 (Linux v6.1.76)
If this is that, a fix is (or soon will be) in the "proposed-updates" repo.
(This can be enabled by editing sources.list to duplicate your "deb ... bookworm main ..." line and change the copy to "deb ... bookworm-proposed-updates main ...")
It may be necessary to boot into the previous kernel 6.1.017 (Linux v6.1.69) to achieve this.
(If this is something different, apologies for the noise.)
No, "proposed-updates" is not the same as "updates", and it should only be "main" if the original "bookworm" line (which is probably the first uncommented "deb" line) is just main.
Based on this example:
Code:
deb http://deb.debian.org/debian bookworm main non-free-firmware
deb http://deb.debian.org/debian-security/ bookworm-security main non-free-firmware
deb http://deb.debian.org/debian bookworm-updates main non-free-firmware
One would add:
Code:
deb http://deb.debian.org/debian bookworm-proposed-updates main non-free-firmware
If one doesn't have non-free-firmware enabled, it should not be added - however, it's my understanding that this issue only affects proprietary nvidia drivers and thus the non-free-firmware section is required for the package(s) in question.
I am on Debian Bookworm, and am having a similar issue to OP, also getting the following after installing nvidia-driver package:
Errors were encountered while processing: nvidia-kernel-dkms nvidia-driver
I tried to add the stable-proposed-updates repository in /etc/apt/sources.list , but when updating apt , I get the following:
W: Skipping acquire of configured file 'stable-proposed-updates/binary-amd64/Packages' as repository 'http://deb.debian.org/debian bookworm-updates InRelease' doesn't have the component 'stable-proposed-updates' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'stable-proposed-updates/i18n/Translation-en_NZ' as repository 'http://deb.debian.org/debian bookworm-updates InRelease' doesn't have the component 'stable-proposed-updates' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'stable-proposed-updates/i18n/Translation-en' as repository 'http://deb.debian.org/debian bookworm-updates InRelease' doesn't have the component 'stable-proposed-updates' (component misspelt in sources.
--
I'll use nouveau driver in the meantime. But do you have any solution(s) for me to get nvidia-driver installed properly?
As background, I was using Fedora with Nvidia driver with no issues for a long time, then yesterday I decided I wanted to go back to Debian again and installed it yesterday.
Also, my GPU is an RTX 3080 , so it is indeed the correct driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
