[SOLVED] nvidia drivers - and more

damo · 2021-03-21 04:33:00

Sector11 wrote:

...
You did not see this damo?
"I" must be bugged!
I really do not want to mess with this bug

I haven't needed to do it since installing the first time. Package bugs are going to be dependant on your timing.

Why not try holding back dkms?

unklar · 2021-03-21 08:26:52

^This bug is almost a year old. It was reported in April 2020 and fixed in June 2020.
You can't expect that when you have such an "old graphics card".
that it will run without problems. Here you have also chosen(!) nvidia, which is known for its counterproductivity against Linux.

I don't have nvidia, I've always avoided it.

So, as @damo notes, you'll have to update dkms (which will surely require a newer kernel again), or set it to "hold" as well.
Beyond that, you're making a mistake:

apt-get install nvidia-driver

According to your own link you have to do:

 2.  Update the list of available packages, then we can install the nvidia-legacy-390xx-driver package, plus the necessary firmware:

    # apt update
    # apt install [b]nvidia-legacy-390xx-driver[/b] firmware-misc-nonfree
 3.  DKMS will build the nvidia module for your system, via the nvidia-legacy
390xx-kernel-dkms package.

390xxx means that this driver supplies nvidia cards from e.g. GT400 to GT900 with this chip [10de:128b], where your GT710B here is.

Last edited by unklar (2021-03-21 08:30:50)

Sector11 · 2021-03-21 12:29:28

@ damo - dkms is a dependency

@ unklar

Well, the "update" was done at tty1 before even trying any of this as I did my normal "up2" before trying stuff:

alias up2='sudo apt update && sudo apt upgrade --no-install-recommends'

trying nvidia-legacy-390xx-driver and I'm back to a mess with the i386 stuff

Running "nvidia-detect" says:

 21 Mar 21 @ 09:08:04 ~
   $ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)

Checking card:  NVIDIA Corporation GK208 [GeForce GT 710B] (rev a1)
Your card is supported by the default drivers and legacy driver series 390.
It is recommended to install the
    nvidia-driver
package.
 
 21 Mar 21 @ 09:08:16 ~
   $

and we hit the dkms bug:

 21 Mar 21 @ 09:08:16 ~
   $ get nvidia-driver
[sudo] password for sector11: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions libegl-nvidia0 libgl1-nvidia-glvnd-glx libglx-nvidia0
  libnvidia-eglcore libnvidia-glcore libnvidia-ml1 nvidia-alternative nvidia-driver-bin nvidia-driver-libs nvidia-egl-common
  nvidia-egl-icd nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check
  nvidia-modprobe nvidia-support nvidia-vdpau-driver update-glx xserver-xorg-video-nvidia
Suggested packages:
  python3-apport
Recommended packages:
  nvidia-settings libnvidia-cfg1 nvidia-persistenced nvidia-driver-libs-i386 libopengl0 | libopengl0-glvnd-nvidia libgles-nvidia1
  libgles-nvidia2 nvidia-vulkan-icd
The following NEW packages will be installed:
  dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions libegl-nvidia0 libgl1-nvidia-glvnd-glx libglx-nvidia0
  libnvidia-eglcore libnvidia-glcore libnvidia-ml1 nvidia-alternative nvidia-driver nvidia-driver-bin nvidia-driver-libs
  nvidia-egl-common nvidia-egl-icd nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support
  nvidia-legacy-check nvidia-modprobe nvidia-support nvidia-vdpau-driver update-glx xserver-xorg-video-nvidia
0 upgraded, 26 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/32.2 MB of archives.
After this operation, 119 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of dkms (→ 2.6.1-4) <Resolved in some Version>
 b1 - #956245 - /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command. (Fixed: dkms/2.8.2-1 dkms/2.8.2-2)
Summary:
 dkms(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]

OK so lets look at the "nvidia-legacy-390xx-driver" that the Debian websites mentions.

GRRRR! Hit enter when I should not have and it is installing "nvidia-legacy-390xx-driver" on tty1 my running system

Probably just BORKED it!

PHEW! remv and aremv worked.

alias aremv='sudo apt-get autoremove --purge'
alias saremv='apt-get autoremove --purge --simulate'
alias remv='sudo apt remove'
alias sremv='apt remove --simulate'
alias prg='sudo apt-get purge'
alias sprg='apt-get purge --simulate'

except for:

Warning: The home dir /var/run/nvpd/ you specified can't be accessed: No such file or directory
Adding system user `nvpd' (UID 116) ...
Adding new group `nvpd' (GID 125) ...
Adding new user `nvpd' (UID 116) with group `nvpd' ...
Not creating home directory `/var/run/nvpd/'.
Created symlink /etc/systemd/system/multi-user.target.wants/nvidia-persistenced.service → /lib/systemd/system/nvidia-persistenced.service.
Job for nvidia-persistenced.service failed because the control process exited with error code.
See "systemctl status nvidia-persistenced.service" and "journalctl -xe" for details.
Setting up nvidia-legacy-390xx-egl-icd:amd64 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-egl-icd:i386 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-vulkan-icd:amd64 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-vulkan-icd:i386 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-driver-bin (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-driver-libs:amd64 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-driver-libs:i386 (390.141-2~deb10u1) ...
Setting up nvidia-legacy-390xx-driver-libs-i386:i386 (390.141-2~deb10u1) ...
Processing triggers for nvidia-legacy-390xx-alternative (390.141-2~deb10u1) ...
update-alternatives: updating alternative /usr/lib/nvidia/legacy-390xx because link group nvidia has changed slave links
Setting up nvidia-legacy-390xx-kernel-dkms (390.141-2~deb10u1) ...
Loading new nvidia-legacy-390xx-390.141 DKMS files...
Building for 4.19.0-14-amd64
Building initial module for 4.19.0-14-amd64
Done.

nvidia-legacy-390xx.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-14-amd64/updates/dkms/

nvidia-legacy-390xx-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-14-amd64/updates/dkms/

nvidia-legacy-390xx-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-14-amd64/updates/dkms/

nvidia-legacy-390xx-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-14-amd64/updates/dkms/

depmod....

DKMS: install completed.
Setting up nvidia-legacy-390xx-driver (390.141-2~deb10u1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for glx-alternative-mesa (1.0.0) ...
Processing triggers for systemd (241-7~deb10u6) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
localepurge: Disk space freed in /usr/share/locale: 904 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB

Total disk space freed by localepurge: 904 KiB

NOT Happy

unklar · 2021-03-21 13:14:15

You could still try

sudo apt install ./dkms_2.8.4-3_all.deb

although other dependencies will certainly run counter.

Only 64-bit x86 buster backports (for new hardware support) remain.

or, you can wait for the Iso's after bullseye

Sector11 · 2021-03-21 16:24:00

I have reinstalled my system, have not added i386 architecture - yet.

sharpbang-buster-10.8.0-amd64.hybrid.iso

Hmmm I thought I had that. Seems like I do not.

Just put it on a stick ... will try.

Sector11 · 2021-03-21 16:55:34

It will not boot for me ??

 21 Mar 21 @ 13:56:28 /media/10/DEBs
   $ ls
conky_1.9.0-4_all.deb  palemoon_29.1.0-1.gtk2_amd64.deb
discord-0.0.13.deb     sha512sum.amd64
dpkg.txt	       sharpbang-buster-10.8.0-amd64.hybrid.iso
 
 21 Mar 21 @ 13:56:34 /media/10/DEBs
   $ sha512sum -c sha512sum.amd64
sharpbang-buster-10.8.0-amd64.hybrid.iso: OK
 
 21 Mar 21 @ 13:56:52 /media/10/DEBs
   $

Yet there it is:

 21 Mar 21 @ 13:58:41 /media/sector11/SHARPBANG_BUSTER
   $ ls
autorun.inf  dists    firmware	 install   md5sum.txt  tools
boot	     EFI      g2ldr	 isolinux  pool        win32-loader.ini
debian	     efi.img  g2ldr.mbr  live	   setup.exe
 
 21 Mar 21 @ 13:58:46 /media/sector11/SHARPBANG_BUSTER
   $

This new MOBO has jinxed me:

 21 Mar 21 @ 13:59:57 ~
   $ sys
System:    Host: sector11 Kernel: 4.19.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 dm: startx 
           Distro: Debian GNU/Linux 10 (buster) 
 
 21 Mar 21 @ 14:00:14 ~
   $ mac
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <root required> UEFI: American Megatrends 
           v: 5603 date: 10/14/2020 
 
 21 Mar 21 @ 14:00:17 ~
   $

unklar · 2021-03-22 13:49:51

^^I would have installed 64-bit x86 buster backports.

because, but you already know that otherwise you can now wait "forever" for the fix

Sector11 wrote:

Grave byg of dkms(→ 2.6.1-4) <resolved in some versions>
b1 - #956245 - /etc/kernel/header_postinst.d/dkms: error! You must be root to use this command (fixed dkms/2.8.2-1 dkms/2.8.2-2)

https://forums.bunsenlabs.org/viewtopic … 25#p112625

DeepDayze · 2021-03-22 15:29:21

I don't see the fixed version of dkms available in backports. If it is in some other source, let me know, but I can apply the fix as noted in that bug report for now.

Currently have:

~$ apt policy dkms
dkms:
  Installed: 2.6.1-4
  Candidate: 2.6.1-4
  Version table:
 *** 2.6.1-4 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

Last edited by DeepDayze (2021-03-22 15:32:57)

Sector11 · 2021-03-24 15:53:32

unklar wrote:

^^I would have installed 64-bit x86 buster backports.

As I said here I have it, it checks out "OK" and does not start up let alone install.

Debian SID: dkms (2.8.4-3)
Debian Testing: dkms (2.8.4-3)

Does not seem to be in Debian 10 backports

Sector11 · 2021-03-24 16:27:43

unklar wrote:

You could still try
sudo apt install ./dkms_2.8.4-3_all.deb
although other dependencies will certainly run counter.

Looked like it just MIGHT work until I saw:

Note, selecting 'dkms' instead of 'dkms_2.8.4-3_all.deb'

 24 Mar 21 @ 13:17:52 ~
   $ cd /media/10/DEBs/test-sid/
 
 24 Mar 21 @ 13:17:59 /media/10/DEBs/test-sid
   $ sudo apt install dkms_2.8.4-3_all.deb
[sudo] password for sector11: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'dkms' instead of 'dkms_2.8.4-3_all.deb'
The following additional packages will be installed:
  dctrl-tools linux-compiler-gcc-8-x86 linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-amd64 linux-kbuild-4.19
Suggested packages:
  debtags
The following NEW packages will be installed:
  dctrl-tools dkms linux-compiler-gcc-8-x86 linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-amd64
  linux-kbuild-4.19
0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
Need to get 10.8 MB/10.9 MB of archives.
After this operation, 59.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
 
 24 Mar 21 @ 13:18:56 /media/10/DEBs/test-sid
   $ sudo apt install dkms_2.8.4-3_all.deb --simulate
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'dkms' instead of 'dkms_2.8.4-3_all.deb'
The following additional packages will be installed:
  dctrl-tools linux-compiler-gcc-8-x86 linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-amd64 linux-kbuild-4.19
Suggested packages:
  debtags
The following NEW packages will be installed:
  dctrl-tools dkms linux-compiler-gcc-8-x86 linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-amd64
  linux-kbuild-4.19
0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
Inst dctrl-tools (2.24-3 Debian:10.8/stable [amd64])
Inst dkms (2.8.4-3 local-deb [all])
Inst linux-compiler-gcc-8-x86 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Inst linux-headers-4.19.0-14-common (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [all])
Inst linux-kbuild-4.19 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Inst linux-headers-4.19.0-14-amd64 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Inst linux-headers-amd64 (4.19+105+deb10u9 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Conf dctrl-tools (2.24-3 Debian:10.8/stable [amd64])
Conf dkms (2.8.4-3 local-deb [all])
Conf linux-compiler-gcc-8-x86 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Conf linux-headers-4.19.0-14-common (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [all])
Conf linux-kbuild-4.19 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Conf linux-headers-4.19.0-14-amd64 (4.19.171-2 Debian:10.8/stable, Debian-Security:10/stable [amd64])
Conf linux-headers-amd64 (4.19+105+deb10u9 Debian:10.8/stable, Debian-Security:10/stable [amd64])
 
 24 Mar 21 @ 13:19:06 /media/10/DEBs/test-sid
   $

So that is a no go.

DeepDayze · 2021-03-24 18:13:48

Weird why that would install the old 4.19 kernel packages???

jeffreyC · 2021-03-24 18:21:53

But it would install that deb:

Inst dkms (2.8.4-3 local-deb [all])

Conf dkms (2.8.4-3 local-deb [all])

Those show that the local file would be what is installed.
apt is just doing the usual confusing wording that they use.

Sector11 · 2021-03-24 19:00:42

No. It is not installing the

dkms_2.8.4-3_all.deb

Re-read this:

Note, selecting 'dkms' instead of 'dkms_2.8.4-3_all.deb'

It is going to install:

   $ sho dkms
alias = aptitude show filename
Package: dkms                     
Version: 2.6.1-4
State: not installed
Multi-Arch: foreign
Priority: optional
Section: kernel

And that is the one with the BUG

DeepDayze · 2021-03-24 19:09:06

Sector11 wrote:

No. It is not installing the

dkms_2.8.4-3_all.deb

Re-read this:

Note, selecting 'dkms' instead of 'dkms_2.8.4-3_all.deb'

It is going to install:

   $ sho dkms
alias = aptitude show filename
Package: dkms                     
Version: 2.6.1-4
State: not installed
Multi-Arch: foreign
Priority: optional
Section: kernel

And that is the one with the BUG

Why not try to backport the one from Sid?

Sector11 · 2021-03-25 02:49:40

DeepDayze wrote:

Why not try to backport the one from Sid?

To be honest, I'm afraid it will bork my system - again!

DeepDayze · 2021-03-25 03:10:32

Sector11 wrote:

DeepDayze wrote:
Why not try to backport the one from Sid?
To be honest, I'm afraid it will bork my system - again!

If you have another hard drive to try, why not temporarily swap out your daily driver drive and do a test install and do a backport of dkms then test the nvidia driver build again?

To me installing a local package (such as one backported or downloaded) should not cause any side effects other than maybe complaining about dependencies. Something might not be right with your setup.

Another thing to try:

Use dpkg -i <package>. This may complain about missing deps but if you backported the sid package it should (hopefully) install clean. I find that using apt rather than dpkg to install local packages seems to have side effects like this.

Last edited by DeepDayze (2021-03-25 03:17:20)

DeepDayze · 2021-03-25 03:22:28

I came across this nugget:

https://superuser.com/questions/196864/ … et/1244531

Does this thread help?

Sector11 · 2021-03-25 03:57:52

@ DeepDayze

Key word: IF I have another drive - I do not

aaaa "it should (hopefully) install clean" - I have reinstalled Linux twice now over trying to get this card to work.

I have resigned myself to using the onboard graphics card until the bug is over and done with.

Sector11 · 2021-03-25 04:02:10

DeepDayze wrote:

I came across this nugget:
https://superuser.com/questions/196864/ … et/1244531
Does this thread help?

Saw that a while back while researching this. It's 10 years old.
But basically the same stuff - just "apt" now vs "apt-get"

unklar · 2021-03-25 08:04:35

DeepDayze wrote:

Use dpkg -i <package>. This may complain about missing deps but if you backported the sid package it should (hopefully) install clean. I find that using apt rather than dpkg to install local packages seems to have side effects like this.

Wrong!
I have been working with sid(uction) for 10 years.
The use of dpkg -i is vehemently rejected there because dpkg does NOT resolve dependencies, unlike apt!

That's why I had written:

You could still try
sudo apt install ./dkms_2.8.4-3_all.deb
although other dependencies will certainly run counter.

S11 just did not understand that he should download this package locally.
Apt will then already tell him what is fact.

#21 2021-03-21 04:33:00

Re: [SOLVED] nvidia drivers - and more

#22 2021-03-21 08:26:52

Re: [SOLVED] nvidia drivers - and more

#23 2021-03-21 12:29:28

Re: [SOLVED] nvidia drivers - and more

#24 2021-03-21 13:14:15

Re: [SOLVED] nvidia drivers - and more

#25 2021-03-21 16:24:00

Re: [SOLVED] nvidia drivers - and more

#26 2021-03-21 16:55:34

Re: [SOLVED] nvidia drivers - and more

#27 2021-03-22 13:49:51

Re: [SOLVED] nvidia drivers - and more

#28 2021-03-22 15:29:21

Re: [SOLVED] nvidia drivers - and more

#29 2021-03-24 15:53:32

Re: [SOLVED] nvidia drivers - and more

#30 2021-03-24 16:27:43

Re: [SOLVED] nvidia drivers - and more

#31 2021-03-24 18:13:48

Re: [SOLVED] nvidia drivers - and more

#32 2021-03-24 18:21:53

Re: [SOLVED] nvidia drivers - and more

#33 2021-03-24 19:00:42

Re: [SOLVED] nvidia drivers - and more

#34 2021-03-24 19:09:06

Re: [SOLVED] nvidia drivers - and more

#35 2021-03-25 02:49:40

Re: [SOLVED] nvidia drivers - and more

#36 2021-03-25 03:10:32

Re: [SOLVED] nvidia drivers - and more

#37 2021-03-25 03:22:28

Re: [SOLVED] nvidia drivers - and more

#38 2021-03-25 03:57:52

Re: [SOLVED] nvidia drivers - and more

#39 2021-03-25 04:02:10

Re: [SOLVED] nvidia drivers - and more

#40 2021-03-25 08:04:35

Re: [SOLVED] nvidia drivers - and more

Board footer