The officially official Devuan Forum!

Micronaut

Member

Registered: 2019-07-04

Posts: 273  

Update of nvidia drivers failed in Daedalus

Today I started my system and found an update for the nvidia drivers had been issued. I've updated them many times before with zero glitches. But today got errors:

dpkg: dependency problems prevent configuration of nvidia-driver:
 nvidia-driver depends on nvidia-kernel-dkms (= 535.309.01-0+deb12u1) | nvidia-k
ernel-535.309.01 | nvidia-open-kernel-535.309.01; however:
  Version of nvidia-kernel-dkms on system is 535.261.03-1.
  Package nvidia-kernel-535.309.01 is not installed.
  Package nvidia-open-kernel-535.309.01 is not installed.

When I try to update DKMS specifically, it complains that DKMS is the wrong version. No shit! So how do you update something that blocks its own update?

Linux hacienda 6.1.0-52-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.180-1 (2026-08-03) x86_64 GNU/Linux

Micronaut

Member

Registered: 2019-07-04

Posts: 273  

Re: Update of nvidia drivers failed in Daedalus

After trying to purge it all and go back to noveau from the recovery prompt, I find that it can't do that either. Everything it tries to do, even apt update, hits the same error about mismatched nvidia modules. This entire system is dead and unrecoverable due to some video driver version mismatch! I guess I'll have to reinstall something else.

fsmithred

Administrator

Registered: 2016-11-25

Posts: 2,972  

Re: Update of nvidia drivers failed in Daedalus

Maybe it will work better like this:

apt install nvidia-driver=535.309.01-0+deb12u1 nvidia-kernel-dkms=535.309.01-0+deb12u1

Micronaut

Member

Registered: 2019-07-04

Posts: 273  

Re: Update of nvidia drivers failed in Daedalus

The error message I am getting says this version of the firmware is "not installable". Does that mean it's not compatible? Or just not in the repository for Debian 12? Is there a backports repository that might have it?

Edit: And I'm also getting errors for some Devuan repositories not being accessible. Like they are down or not in the DNS servers.

Last edited by Micronaut (2026-08-24 21:00:10)

greenjeans

Member

Registered: 2017-04-07

Posts: 1,748  

Website

Re: Update of nvidia drivers failed in Daedalus

Edit: And I'm also getting errors for some Devuan repositories not being accessible. Like they are down or not in the DNS servers.

Possibly the entire problem right there, try a direct connect to a repo in your area. If you are in the US gnlug works great.

 deb http://gnlug.org/pub/devuan/merged/ daedalus non-free-firmware non-free contrib main  
 deb http://gnlug.org/pub/devuan/merged/ daedalus-updates main non-free-firmware non-free contrib  
 deb http://gnlug.org/pub/devuan/merged/ daedalus-security main non-free-firmware non-free contrib  

---

https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do. Now with Xlibre as well.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/ Apps source : https://git.devuan.org/greenjeans

Micronaut

Member

Registered: 2019-07-04

Posts: 273  

Re: Update of nvidia drivers failed in Daedalus

Whatever is going on, it's blocking gnlug.org just like the other mirrors. All I get are "could not resolve" errors for both the original and these repositories. But I can boot another system running another distro (MX Linux) and it can connect to its own repositories.

A very weird problem. But I've got a copy of Excalibur installed on another disk. I'll see if I can move the data without too much trouble.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,728  

Re: Update of nvidia drivers failed in Daedalus

What does the following say

apt-cache policy nvidia-driver nvidia-kernel-dkms

You could also go to pkginfo.devuan.org to investigate which package versions are available and from where.

rbit

Administrator

Registered: 2018-06-12

Posts: 141  

Re: Update of nvidia drivers failed in Daedalus

from what I'm seeing on daedalus, nvidia-driver and nvidia-kernel-dkms are at version 535.261.03-1 (daedalus), 535.309.01-0+deb12u1 (daedalus-security), and oddly 535.216.03-2-bpo12+1 (daedalus-backports).
maybe this would work?

apt install nvidia-driver/daedalus-security nvidia-kernel-dkms/daedalus-security

Of course, you'll need to have apt working properly first.

rbit

Administrator

Registered: 2018-06-12

Posts: 141  

Re: Update of nvidia drivers failed in Daedalus

Whatever is going on, it's blocking gnlug.org just like the other mirrors. All I get are "could not resolve" errors for both the original and these repositories.

That's odd. Is your nameserver accessible?  What's in /etc/resolv.conf?

Micronaut

Member

Registered: 2019-07-04

Posts: 273  

Re: Update of nvidia drivers failed in Daedalus

After some more fiddling I am just giving up on this system. There is something going on with the Devuan repositories. When I installed Excalibur on another disk I had to use a different repository. The first/default doesn't work. But this goes far beyond that with the broken one. It won't find the repositories no matter what names I use. "Cannot resolve" names that work on any other machine I try. When I was pinging us.deb.devuan.org from another machine, I discovered it's the same as gnlug.org, but both of these cannot be reached by apt from that broken system. Absolutely bizarre. I've never heard of or seen anything like this.

All of my systems are configured to use the local router DNS through DHCP, and that has been directed to use Quad9. It works fine for everything else. But I've tried manually editing resolv.conf to use something else, like Google's 8.8.8.8 and it makes no difference. Repository hosts cannot be resolved by any DNS service this machine is configured to use. Like I said, bizarre.

Altoid

Member

Registered: 2017-05-07

Posts: 2,102  

Re: Update of nvidia drivers failed in Daedalus

Hello:

... manually editing resolv.conf to use something else, like Google's 8.8.8.8 ...

TL;DR
Edit [resolv.conf] to what you need.
eg: the same [resolv.conf] used by the properly working systems.

That done, save the file and then make it immutable.

ie:
as root

# chattr +i /etc/resolv.conf 
#

This because [/sbin/dhclient-script] has instructions to change the contents of the [/etc/resolv.conf] file.
It is part of the [DHCP] protocol.
See here: https://dev1galaxy.org/viewtopic.php?pid=52247#p52247

You will find it between lines [38] and [42] 

--- snip ---
# update /etc/resolv.conf based on received values     <---- ####### this
  make_resolv_conf() {
      local new_resolv_conf
--- snip ---  

Now, check if it is working as intended (the package [ifupdown] must be installed):

1. log out and back in.
2. open a terminal and (as root or with privileges) do:

$ sudo ifdown eth0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp
$

$ sudo ifup eth0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:14:4f:4a:a2:81
Sending on   LPF/eth0/00:14:4f:4a:a2:81
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPOFFER of 192.168.1.10 from 192.168.1.1
DHCPREQUEST for 192.168.1.10 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.10 from 192.168.1.1
/sbin/dhclient-script: 88: cannot create /etc/resolv.conf: Operation not permitted    #### < you should see this string.
bound to 192.168.1.10 -- renewal in 11808 seconds.  < here the IP should be the one in the edited [/etc/resolv.conf file].
$ 

Now check if the system works as you expect it to work.
Just a shot in the dark.

Best,

A.

Last edited by Altoid (Today 00:22:51)