LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 12-26-2023, 02:30 PM   #1
ahmedov
LQ Newbie
 
Registered: Dec 2023
Posts: 5

Rep: Reputation: 0
Exclamation Installing old nvidia 390 driver on bookworm


I wanted to install the driver because I have an old video card, but I was saddened that this cannot be done on bookworm and I need to update to sid which will break all system stability.
I followed the advice from the Internet and changed the repository to bullseye and run apt install nvidia-legacy-390xx-driver firmware-misc-nonfree
I received an error:
Code:
Unpacking nvidia-legacy-390xx-kernel-dkms (390.157-1~deb11u1) over (390.154-1~deb10u1) ...
Setting up libnvidia-legacy-390xx-eglcore:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-alternative (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-glcore:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-ptxjitcompiler1:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-fatbinaryloader:amd64 (390.157-1~deb11u1) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for nvidia-legacy-390xx-alternative (390.157-1~deb11u1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvidia/legacy-390xx because link group nvidia is 
broken
Setting up nvidia-legacy-390xx-kernel-support (390.157-1~deb11u1) ...
Setting up xserver-xorg-video-nvidia-legacy-390xx (390.157-1~deb11u1) ...
Setting up libglx-nvidia-legacy-390xx0:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-ml1:amd64 (390.157-1~deb11u1) ...
Setting up libgl1-nvidia-legacy-390xx-glvnd-glx:amd64 (390.157-1~deb11u1) ...
Setting up libegl-nvidia-legacy-390xx0:amd64 (390.157-1~deb11u1) ...
Setting up libgles-nvidia-legacy-390xx2:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-kernel-dkms (390.157-1~deb11u1) ...
Loading new nvidia-legacy-390xx-390.157 DKMS files...
Building for 6.1.0-16-amd64
Building initial module for 6.1.0-16-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/6.1.0-16-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/6.1.0-16-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/6.1.0-16-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/6.1.0-16-amd64/updates/dkms/
depmod....
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xeu systemd-modules-load.service" for details.

DKMS: install completed.
Setting up libnvidia-legacy-390xx-cfg1:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-cuda1:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-nvcuvid1:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-vdpau-driver:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-egl-icd:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-smi (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-vulkan-icd:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-driver-bin (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-driver-libs:amd64 (390.157-1~deb11u1) ...
Setting up libnvidia-legacy-390xx-encode1:amd64 (390.157-1~deb11u1) ...
Setting up nvidia-legacy-390xx-driver (390.157-1~deb11u1) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Processing triggers for glx-alternative-mesa (1.0.0) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-16-amd64
user@linux:~$ sudo journalctl -xeu systemd-modules-load.service
Output journalctl -xeu systemd-modules-load.service:
Code:
Dec 26 23:06:47 linux systemd[1]: systemd-modules-load.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit systemd-modules-load.service has successfully entered the 'dead' state.
Dec 26 23:06:47 linux systemd[1]: Stopped systemd-modules-load.service - Load Kernel Modules.
░░ Subject: A stop job for unit systemd-modules-load.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit systemd-modules-load.service has finished.
░░ 
░░ The job identifier is 3634 and the job result is done.
Dec 26 23:06:47 linux systemd[1]: Stopping systemd-modules-load.service - Load Kernel Modules...
░░ Subject: A stop job for unit systemd-modules-load.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit systemd-modules-load.service has begun execution.
░░ 
░░ The job identifier is 3634.
Dec 26 23:06:47 linux systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
░░ Subject: A start job for unit systemd-modules-load.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit systemd-modules-load.service has begun execution.
░░ 
░░ The job identifier is 3634.
Dec 26 23:06:47 linux systemd-modules-load[58809]: modprobe: ERROR: could not insert 'nvidia_legacy_390xx': No such device
Dec 26 23:06:47 linux systemd-modules-load[58807]: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe -i nvidia-legacy-390xx ' for module nvidia: retcode 1
Dec 26 23:06:47 linux systemd-modules-load[58807]: modprobe: ERROR: could not insert 'nvidia': Invalid argument
Dec 26 23:06:48 linux systemd-modules-load[58811]: modprobe: ERROR: could not insert 'nvidia_legacy_390xx_modeset': No such device
Dec 26 23:06:48 linux systemd-modules-load[58805]: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe nvidia ; modprobe -i nvidia-legacy-390xx-modeset ' for module nvidia_modeset: retcode 1
Dec 26 23:06:48 linux systemd-modules-load[58805]: modprobe: ERROR: could not insert 'nvidia_modeset': Invalid argument
Dec 26 23:06:48 linux systemd-modules-load[58812]: modprobe: ERROR: could not insert 'nvidia_legacy_390xx_drm': No such device
Dec 26 23:06:48 linux systemd-modules-load[58803]: Error running install command 'modprobe nvidia-modeset ; modprobe -i nvidia-legacy-390xx-drm ' for module nvidia_drm: retcode 1
Dec 26 23:06:48 linux systemd-modules-load[58803]: Failed to insert module 'nvidia_drm': Invalid argument
Dec 26 23:06:48 linux systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit systemd-modules-load.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 26 23:06:48 linux systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit systemd-modules-load.service has entered the 'failed' state with result 'exit-code'.
Dec 26 23:06:48 linux systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.
░░ Subject: A start job for unit systemd-modules-load.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit systemd-modules-load.service has finished with a failure.
░░ 
░░ The job identifier is 3634 and the job result is failed.
And what should I do now? Help, otherwise I will again have to switch to another distribution that is more friendly to old hardware. Debian, because of its obsession with security, completely forgot about the freedom of choice of users and removed the package and did not even leave any way to install it, driver nouveau is terrible lags and brakes even on youtube
 
Old 12-26-2023, 03:44 PM   #2
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,147
Blog Entries: 21

Rep: Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483Reputation: 3483
I don't think 390 nvidia installs on ver. 6 kernels.

Try some older lts kernel.

Code:
harry@mx:~
$ inxi -G
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 430] driver: nvidia v: 390.157
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1366x768~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 390.157 renderer: GeForce GT 430/PCIe/SSE2
harry@mx:~
$ uname -r
5.10.0-26-amd64
harry@mx:~

Last edited by rokytnji; 12-26-2023 at 03:45 PM.
 
Old 12-27-2023, 05:10 AM   #3
ahmedov
LQ Newbie
 
Registered: Dec 2023
Posts: 5

Original Poster
Rep: Reputation: 0
Everything worked well on kernel 5.10 and installed without errors
 
Old 12-27-2023, 11:45 AM   #4
enigma9o7
Senior Member
 
Registered: Jul 2018
Location: Silicon Valley
Distribution: Bodhi Linux
Posts: 1,398

Rep: Reputation: 561Reputation: 561Reputation: 561Reputation: 561Reputation: 561Reputation: 561
In theory you should use the driver from sid, not bullseye, to get newer patches and security fixes, etc. They do keep it maintained for latest kernel, and it is intended for use on stable without backporting.

Check out the changelog.... which includes support up to linux 6.6

[Of course, if all is working fine for you, there's always If it aint broke, don't fix it!]

Last edited by enigma9o7; 12-27-2023 at 11:56 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Update on Debian-Bookworm and Why Did Bookworm Remove Some Packages? kevinbenko Linux - Newbie 4 07-09-2022 09:00 AM
[SOLVED] Nvidia 390 driver CUDA? (BOINC) dchmelik Slackware 2 12-24-2018 07:27 PM
LXer: Nvidia 390.77 Linux Graphics Driver Improves Compatibility with Latest Kernels LXer Syndicated Linux News 0 07-18-2018 07:03 AM
Installing cuda toolkit 9.1 with nvidia 390 driver on ubuntu 17.10 ethereal1m Linux - Software 0 03-04-2018 02:45 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 05:26 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration