mxlinux 21.2 nvdia driver problem  [Solved]

When you run into problems installing MX Linux XFCE
Forum rules
Post Reply
Message
Author
Qiset
Posts: 15
Joined: Fri Feb 18, 2022 10:10 pm

mxlinux 21.2 nvdia driver problem  [Solved]

#1 Post by Qiset »

I upgraded one of my systems from 19.4 to 21.2. What that really means is that installed 21.2 on the system.
It is the same hardware, but in 21.2 the nvidia drivers won't install.
Here's what is displayed during an attempt to install the drivers:
=====================================================================================
Loading new nvidia-current-470.141.03 DKMS files...
Building for 5.10.0-18-amd64
Building initial module for 5.10.0-18-amd64
Error! Bad return status for module build on kernel: 5.10.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/470.141.03/build/make.log for more information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
nvidia-driver depends on nvidia-kernel-dkms (= 470.141.03-1~deb11u1) | nvidia-kernel-470.141.03; however:
Package nvidia-kernel-dkms is not configured yet.
Package nvidia-kernel-470.141.03 is not installed.
Package nvidia-kernel-dkms which provides nvidia-kernel-470.141.03 is not configured yet.

dpkg: error processing package nvidia-driver (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
nvidia-kernel-dkms
nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)

full upgrade complete (or was canceled)

this terminal window can now be closed
==========================================================================================
The mx-package installer produces the same output.

Is there anyway around this?

---------------------------------------------------------
Here is the Quick System Info:
===============================================================================================

Code: Select all

System:    Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-18-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: FM2A68M-DG3+ serial: <filter> 
           UEFI-[Legacy]: American Megatrends v: P5.20 date: 02/18/2019 
CPU:       Info: Quad Core model: AMD Athlon X4 740 bits: 64 type: MCP arch: Piledriver 
           family: 15 (21) model-id: 10 (16) stepping: 1 microcode: 6001119 cache: L2: 2 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 25554 
           Speed: 1973 MHz min/max: 1400/3200 MHz boost: enabled Core speeds (MHz): 1: 1973 
           2: 2089 3: 1987 4: 2192 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT vulnerable 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nouveau 
           v: kernel alternate: nvidia bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300 
           Device-2: Sunplus SPCA1527A/SPCA1528 SD card camera (Mass Storage mode) type: USB 
           driver: usb-storage bus-ID: 1-2:3 chip-ID: 04fc:0171 class-ID: 0806 serial: <filter> 
           Device-3: HD 2MP WEBCAM HD 2MP WEBCAM type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 2-1:2 chip-ID: 1d6c:0103 class-ID: 0102 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: VGA-1 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
           diag: 584mm (23") 
           OpenGL: renderer: NV106 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:14.2 
           chip-ID: 1022:780d class-ID: 0403 
           Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403 
           Device-3: HD 2MP WEBCAM HD 2MP WEBCAM type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 2-1:2 chip-ID: 1d6c:0103 class-ID: 0102 serial: <filter> 
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 754.6 GiB used: 59.94 GiB (7.9%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 0010 scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD3200AAJS-56M0A0 
           size: 298.09 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 3E01 scheme: MBR 
           ID-3: /dev/sdc maj-min: 8:32 type: USB model: General USB Flash Disk size: 231.1 GiB 
           block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 
           scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
           ID-4: /dev/sdd maj-min: 8:48 type: USB model: Sunplus Co Ltd General size: 1.83 GiB 
           block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 290.08 GiB size: 284.47 GiB (98.06%) used: 24.18 GiB (8.5%) fs: ext4 
           dev: /dev/sdb1 maj-min: 8:17 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2 
           maj-min: 8:18 
Sensors:   System Temperatures: cpu: 13.8 C mobo: N/A gpu: nouveau temp: 48.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2079 note: see --pkg apt: 2073 lib: 1065 flatpak: 6 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 219 Uptime: 1h 36m wakeups: 1 Memory: 7.73 GiB used: 1.3 GiB (16.8%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
====================================================================================================
Top
User avatar
Stevo
Developer
Posts: 14447
Joined: Fri Dec 15, 2006 7:07 pm

Re: mxlinux 21.2 nvdia driver problem

#2 Post by Stevo »

That's the stock debian 11 kernel and nvidia-drivers, so it's been building for other people with the same packages. That is quite odd.

Could you

Code: Select all

Consult /var/lib/dkms/nvidia-current/470.141.03/build/make.log for more information.
For newcomers, that means open that log file in a text editor or viewer.
Top
User avatar
dolphin_oracle
Developer
Posts: 22062
Joined: Sun Dec 16, 2007 12:17 pm

Re: mxlinux 21.2 nvdia driver problem

#3 Post by dolphin_oracle »

hmmm its not even really a bad build error.

are the linux-headers-5.10.0-18-amd64 installed? they should be by default.

Code: Select all

apt-cache policy linux-headers-5.10.0-18-amd64 linux-headers-amd64
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
paulfsams
Posts: 20
Joined: Thu Dec 06, 2018 12:16 pm

Re: mxlinux 21.2 nvdia driver problem

#4 Post by paulfsams »

I received an error message nvidia on a debian bullseye install, however, after a reboot, everything was working as it was supposed to do. I still would receive an error message on the next few times I used synaptic. The next time I used that computer, the error message was gone. But, I'm sure someone would find an error message bothersome. It bothered me.
Top
Qiset
Posts: 15
Joined: Fri Feb 18, 2022 10:10 pm

Re: mxlinux 21.2 nvdia driver problem

#5 Post by Qiset »

Figured it out. Turns out it was a strange kind of operator error. The old version of the operating system was on a separate harddrive and mounted. For what ever reason, part of the attempt to put the new drivers saw that drive and tried to use it. A line in the logs referenced it is what let me in on the issue. I removed that harddrive and everything worked as it should. Thanks for any consideration on this issue.
Top
Post Reply

Return to “Installation”