Bullseye legacy nvidia driver update fail [SOLVED]

Kernels & Hardware, configuring network, installing services

Bullseye legacy nvidia driver update fail [SOLVED]

Postby ticketman » 2020-01-11 18:32

A recent bullseye update failed to rebuild my legacy nvidia driver (340xx).
I think the gpu is a GT210.
The automated build failed because it couldn't find the required linux header files.

uname -a gives me:
5.3.0-3-amd64 #1 SMP Debian 5.3.15-1 ((2019-12-07) x86-64


Code: Select all
dpkg-reconfigure nvidia-legacy-340xx-kernel-dkms

gives
Module build for kernel 5.3.0-3-amd64 was skipped since the kernel headers for this kernel does not seem to be installed


doing a
Code: Select all
apt-get install  linux-headers-5.3.0-0-amd64

gives error 'can't find the package'
Similarly for linux-headers-5.3.0-3-amd64

Where do I go from here?
Last edited by ticketman on 2020-01-21 13:51, edited 1 time in total.
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby Head_on_a_Stick » 2020-01-11 20:04

The headers are newer than the kernel in bullseye atm. SNAFU.
User avatar
Head_on_a_Stick
 
Posts: 11204
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Bullseye legacy nvidia driver update fail

Postby stevepusser » 2020-01-11 20:35

Have you tried module-assistant's "m-a prepare" command to get the headers?
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Kodi 18.5, Blender 2.8.2, 5.5 kernels, Openshot 2.5.0, Telegram-desktop 1.9.14, LibreOffice 6.4.1~rc1
User avatar
stevepusser
 
Posts: 11458
Joined: 2009-10-06 05:53

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-11 20:52

Steve,

module-assistant's "m-a prepare" command


Not at all familiar with that - can you elaborate?

If the headers aren't there in the repo, seems like there's not much I can do until they appear?
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-12 13:38

I was able to install module-assistant and issue the "m-a prepare" command.
It was also not able to find the required headers.

This morning I tried a apt update and it downloaded the 5.4.0-2 kernel. Yay!
It also automatically ran dkms and built the nvidia stuff, no errors.
I booted to the new kernel. No sytem errors this time, but ... all I got was a blank screen that didn't respond to alt-ctl-F1.
Progress, but still no usable system and now I don't know what is wrong since the dkms problem has been fixed.

In the rescue mode I tried
dpkg-reconfigure nvidia-legacy-340xx-kernel-dkms
This completed with no errors.

I then did
update-initramfs - u - k all
and this threw a ton of errors of the type
"depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file 'var/tmp/mkinitramfs_DPWprk/lib/modules/... ",
but eventually completed.

I still get a blank unresponsive screen on reboot.
I am beginning to think that [nVidia + testing repo] is a bad combination ...
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-20 17:19

Had to purge all nvidia stuff and activate nouveau driver - only way to get back my desktop.

BUT now the latest kernel 5.4.0-2 fails critically - drops me into emergency mode. A data disk fails to mount:
Dependency failed for local file systems


Network is up, but when I do a apt-get update I get this:

Err1: http://ftp.uk.debian.org/debian testing InRelease
Temporary failure resolving 'ftp.uk.debian.org'


I don't remember this 'InRelease' parameter - what on earth is going on??
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby dilberts_left_nut » 2020-01-20 18:39

ticketman wrote:what on earth is going on??

You are running testing.
Isn't it fun.
AdrianTM wrote:There's no hacker in my grandma...
User avatar
dilberts_left_nut
 
Posts: 5029
Joined: 2009-10-05 07:54
Location: enzed

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-20 19:13

I've been running it for several years, never had this sort of trouble before.
Have the repo sources changed? what is 'InRelease' all about?
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby Head_on_a_Stick » 2020-01-20 19:19

Can you ping google.com? Looks like your nameservers may be mis-configured.
User avatar
Head_on_a_Stick
 
Posts: 11204
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-20 19:30

ping produced "Temporary failure in name resolution"
I can't understand why this kernel is so messed up - how could nameserver be wrong and the system unable to access a local disc, when the other kernels I load don't have such issues?
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby Head_on_a_Stick » 2020-01-20 19:43

Can you ping 8.8.8.8?

If so then what is the disposition of resolv.conf?
Code: Select all
ls -l /etc/resolv.conf
cat /etc/resolv.conf
User avatar
Head_on_a_Stick
 
Posts: 11204
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-21 09:12

Had to retire and shutdown. Switch PC back on today.
This time the latest kernel booted to the desktop - go figure!

cat /etc/resolv.conf gives:
# Generated by NetworkManager
search lan
nameserver 192.168.1.254




This is my sources.list :

Code: Select all
deb http://ftp.uk.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security testing-security main contrib non-free


Is this correct for bullseye? (in particular, is deb http://security.debian.org/debian-security correct?
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Re: Bullseye legacy nvidia driver update fail

Postby Head_on_a_Stick » 2020-01-21 10:09

ticketman wrote:This is my sources.list :

Code: Select all
deb http://ftp.uk.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security testing-security main contrib non-free


Is this correct for bullseye? (in particular, is deb http://security.debian.org/debian-security correct?

Well you probably want to specify "bullseye" rather than "testing" (unless you want to change to the next testing version as soon as it is released) and in respect of security coverage see https://www.debian.org/security/faq#testing

If security is a concern then Debian testing is a terrible choice.

EDIT: and to repeat...
I wrote:Can you ping 8.8.8.8?
User avatar
Head_on_a_Stick
 
Posts: 11204
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Bullseye legacy nvidia driver update fail

Postby ticketman » 2020-01-21 12:56

Since I have a desktop now, ping 8.8.8.8 works.
I prefer a rolling distribution, so prefer to stay with testing (despite this experience!)

The sources generator at https://debgen.simplylinux.ch/index.php?generate produces:

Code: Select all
#------------------------------------------------------------------------------#
#                   OFFICIAL DEBIAN REPOS                   
#------------------------------------------------------------------------------#

###### Debian Main Repos
deb http://ftp.uk.debian.org/debian/ testing main contrib non-free

deb http://ftp.uk.debian.org/debian/ testing-updates main contrib non-free

deb http://security.debian.org/ testing-security main


so I am going to try using that.

Looks like something must have changed in sources - I don't see how I ended up with something different.
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06

Bullseye legacy nvidia driver update fail [SOLVED]

Postby ticketman » 2020-01-21 13:50

With the new sources.list, apt is happy and the system boots normally.
I'll mark as solved, but it is all still a mystery how I got borked.
Also, I am now running nouveau as I have kicked out all of the nvidia drivers.
Looking forward to using AMD gpus in the future!
ticketman
 
Posts: 91
Joined: 2012-06-30 11:06


Return to System configuration

Who is online

Users browsing this forum: No registered users and 10 guests

fashionable