[Solved] Beowulf - Nvidia legacy 340XX driver will not install.

Altoid · 2020-09-13 22:50:50

Hello:

I'm attempting to install the Nvidia legacy 340XX driver to be able to use my three monitor setup in Beowulf.

The two or three times I have done this with different Linux distributions, it was a matter of transplanting a previously working xorg.conf file and 'maybe' tweaking it a bit, never had serious issues.

The first transplant to a Devuan installation was from PCLinuxOS to the Devuan Jesse and from then onwards.

This is the second time I am attempting to install the proprietary driver in Beowulf and as I know what will happen, I have avoided a reboot so I can get the data. ='7

Here's what synaptic had to say (previous driver installation was with apt but the printout was lost):

E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1

I then opened a terminal to see what was going on:

oot@devuan3:~# dkms status
nvidia-legacy-340xx, 340.108: added
root@devuan3:~#

Seems the driver is installed (?)

So then I tried to see if anything was missing:

groucho@devuan3:~$ su -
Password: 
root@devuan3:~# apt install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

1 not fully installed or removed.  <--- THIS seems to be the problem.

After this operation, 0 B of additional disk space will be used.
Setting up nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon

nvidia-persistenced failed to initialize. Check syslog for more details.  <--- THIS seems to have caused the problem.

invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
 installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@devuan3:~#

This confirmed what synaptic said.

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

root@devuan3:/# ls /dev/nvidia
ls: cannot access '/dev/nvidia': No such file or directory
root@devuan3:/#

What's going on?

I will leave this here, reboot and see about cleaning up, otherwise I will not have X.

Any ideas welcome.

Thanks in advance,

A.

Last edited by Altoid (2020-09-16 19:08:09)

HevyDevy · 2020-09-14 12:23:21

Maybe need to modprobe /dev/nvidia* ?

Have you tried nvidia-xconfig, or is that not a good idea ? I remember using it when i had nvidia setup that used the 340xx to get it working.

Altoid · 2020-09-14 14:10:48

Hello:

HevyDevy wrote:

Maybe need to modprobe /dev/nvidia* ?

Yes.
But like I mentioned previously, the files are not there.

HevyDevy wrote:

... tried nvidia-xconfig ...

Not there either.

Before rebooting (and after) I tried apt purge nvidia-persistenced and then apt install nvidia-persistenced but it does not nstall.
The issue E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1 remains.

The only way out is apt purge *nvidia* to recover the desktop.

There seems to be a problem with the nvidia-persistenced package (seems to be a daemon) which will not start because the nvidia device files (/dev/nvidia*) are not where they should be.

Maybe a bug in the package?

Thanks for your input.

A.

HevyDevy · 2020-09-14 14:44:05

Do you have https://packages.debian.org/buster/libn … 340xx-cfg1 installed ?

nvidia-xconfig is there https://packages.debian.org/buster/nvidia-xconfig

Last edited by HevyDevy (2020-09-14 14:45:23)

Altoid · 2020-09-14 15:16:49

Hello:

HevyDevy wrote:

Do you have https://packages.debian.org/buster/libn … 340xx-cfg1 installed ?
nvidia-xconfig is there https://packages.debian.org/buster/nvidia-xconfig

My ascii installation has both.

groucho@devuan:~$ apt list | grep libnvidia-legacy-340xx-cfg1
libnvidia-legacy-340xx-cfg1/oldstable,now 340.108-3~deb9u1 amd64 [installed,automatic]
groucho@devuan:~$

groucho@devuan:~$ apt list | grep nvidia-xconfig
nvidia-xconfig/oldstable 390.87-1~deb9u1 amd64
groucho@devuan:~$

nvidia-xconfig was there when I tried to install the driver (sorry for the lapse) but it would not work.

My sources list (from the Devuan GNU/Linux 3.0 (beowulf) amd64 - netinstall 20200526) are these:

deb http://pkgmaster.devuan.org/merged beowulf main non-free contrib
deb http://pkgmaster.devuan.org/merged beowulf-security main contrib non-free

# beowulf-updates, previously known as 'volatile'
deb http://pkgmaster.devuan.org/merged beowulf-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-backports main contrib non-free

I saw no reason to modify them as I understand that if a package is in the Debian repository it will then be in the Devuan repositories, save for the systemd stuff.

Thanks for your input.

Cheers,

A.

HevyDevy · 2020-09-14 15:21:23

what does your ascii installation have to with your issue, are you using beowulf or ascii ?

Also, why not follow this guide ?

https://wiki.debian.org/NvidiaGraphicsDrivers

Last edited by HevyDevy (2020-09-14 15:30:19)

chris2be8 · 2020-09-14 16:14:56

Altoid wrote:

root@devuan3:/# ls /dev/nvidia
ls: cannot access '/dev/nvidia': No such file or directory
root@devuan3:/#

Try ls -l /dev/nvidia* (the file names just start /dev/nvidia so the * is important). And ls -l to see what permissions they have is useful.

I get:

chris@rigel:~/bin$ ls -l /dev/nvidia*
crw-rw-rw-+ 1 root root 195,   0 Aug 25  2019 /dev/nvidia0
crw-rw-rw-+ 1 root root 195, 255 Aug 25  2019 /dev/nvidiactl
crw-rw-rw-+ 1 root root 195, 254 Aug 25  2019 /dev/nvidia-modeset
crw-rw-rw-+ 1 root root 248,   0 Aug 27  2019 /dev/nvidia-uvm
crw-rw-rw-+ 1 root root 248,   1 Aug 27  2019 /dev/nvidia-uvm-tools

Chris

Altoid · 2020-09-14 16:32:54

Hello:

HevyDevy wrote:

what does your ascii installation have to ...

Nothing.
I was comparing my working ascii installation with what nvidia drivers was installing in Beowulf.

HevyDevy wrote:

... using beowulf or ascii ?

Like I mention in my OP, my working installation is ascii and I'm installing Beowulf on a separate drive to see how it goes.

HevyDevy wrote:

Also, why not follow this guide ?
https://wiki.debian.org/NvidiaGraphicsDrivers

I installed the these nvidia-340XX legacy drivers in Beowulf in the very same way I have done it in Devaun ascii, Jesse, PCLinuxOS, Linux Mint and others. ie: ever since I retired my old rig with 'ancient' Matrox G550 PCI cards as there were no available drivers for Linux.

I'll have a look at the guide (*) but if these drivers installed with no issues on this box (exact same hardware) running ascii, I'd say there is a high probability that the problem lies with the Beowulf Nvidia-340xx package or something that has changed in Beowulf that creates some incompatibility.

There has been an important change in Beowulf wrt how su works, now we have to use su - instead.
Could this output from var/log/syslog be a clue?

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

Thanks for your input.

Cheers,

A.

(*)

Nvidia Graphics Drivers Wiki wrote:

--- snip ---
DKMS will build the nvidia module for your system, via the nvidia-legacy-340xx-kernel-dkms package.
--- snip ---

This is what (for whatever reason) is not happening.

Last edited by Altoid (2020-09-14 16:53:37)

Altoid · 2020-09-14 21:47:24

Hello:

I hate quoting myself ...

Altoid wrote:

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

As I wrote previously, the NVIDIA device files (/dev/nvidia*) do not exist.

Now, looking around the web I found this: https://forums.developer.nvidia.com/t/d … t/110139/4

forums.developer.nvidia wrote:

The content of your /etc/modprobe.d/nvidia.conf file is not correct. It should read options nvidia NVreg_DeviceFileMode=0660 You forgot ‘nvidia’ – and NVreg_ModifyDeviceFiles=0 means to not create /dev/nvidia* nodes at all.

Also this:

forums.developer.nvidia wrote:

You need to recreate your initrd to make the changes to /etc/modprobe.d/nvidia.conf effective.
Note that there is no proper rights management for the nvidia device files. They are expected to be rw for everyone, otherwise things don’t work. That’s why nvidia-modprobe exists. It’s suid root and will (among other things) fixup everything to be 0666. nvidia-smi calls it if necessary.

If I get (?) the idea behind these texts, /etc/modprobe.d/nvidia.conf (probably part of the drivers installation) could be incorrect and reading something other than nvidia NVreg_DeviceFileMode=0660 and have NVreg_ModifyDeviceFiles option set to =0.

If this is so (fail to understand how this could be) this, it would explain why the /dev/nvidia* files are missing.

Any idea as to how to proceed and check the /etc/modprobe.d/nvidia.conf?
I don't have one in my Beowulf installation.

Thanks in advance,

A.

Last edited by Altoid (2020-09-14 21:49:25)

GlennW · 2020-09-14 22:13:16

here's what a backup looks like...

there isn't one on my system in use atm.

/home/glenn/local/other/backup/backup-etc-sys/etc/modprobe.d/nvidia.conf

install nvidia modprobe -i nvidia-current $CMDLINE_OPTS

install nvidia-modeset modprobe nvidia ; modprobe -i nvidia-current-modeset $CMDLINE_OPTS

install nvidia-drm modprobe nvidia-modeset ; modprobe -i nvidia-current-drm $CMDLINE_OPTS

install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-current-uvm $CMDLINE_OPTS

remove nvidia modprobe -r -i nvidia-drm nvidia-modeset nvidia-uvm nvidia

remove nvidia-modeset modprobe -r -i nvidia-drm nvidia-modeset

# These aliases are defined in *all* nvidia modules.
# Duplicating them here sets higher precedence and ensures the selected
# module gets loaded instead of a random first match if more than one
# version is installed. See #798207.
alias	pci:v000010DEd00000E00sv*sd*bc04sc80i00*	nvidia
alias	pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*	nvidia
alias	pci:v000010DEd*sv*sd*bc03sc02i00*		nvidia
alias	pci:v000010DEd*sv*sd*bc03sc00i00*		nvidia

/home/glenn/local/other/backup/backup-etc-sys/etc/modules-load.d/nvidia.conf

nvidia-drm

Altoid · 2020-09-14 22:58:46

Hello:

GlennW wrote:

here's what a backup looks like...
there isn't one on my system in use atm.

It does not seem to have the contents of the files I have seen on the web.
eg: here.

FILE /etc/modprobe.d/nvidia.confSetting nvidia NVreg_EnableMSI
# Nvidia drivers support
alias char-major-195 nvidia
alias /dev/nvidiactl char-major-195

# To tweak the driver the following options can be used, note that
# you should be careful, as it could cause instability!! For more
# options see /usr/share/doc/nvidia-drivers-337.19/README
#
# !!! SECURITY WARNING !!!
# DO NOT MODIFY OR REMOVE THE DEVICE FILE RELATED OPTIONS UNLESS YOU KNOW
# WHAT YOU ARE DOING.
# ONLY ADD TRUSTED USERS TO THE VIDEO GROUP, THESE USERS MAY BE ABLE TO CRASH,
# COMPROMISE, OR IRREPARABLY DAMAGE THE MACHINE.
options nvidia NVreg_DeviceFileMode=0660 NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=27 NVreg_ModifyDeviceFiles=1 NVreg_EnableMSI=0

I'll see if I can download and open up the *.deb file from the Beowulf repository to see what is inside.

Thanks for your input.

Cheers,

A.

Altoid · 2020-09-15 13:42:09

Hello:

Altoid wrote:

... download and open up the *.deb file from the Beowulf repository ...

Not possible to see the files.
So I reinstalled the driver and stopped before rebooting the system.

First I opened a terminal and looked for the nvidia.conf file and found it in two instances:

root@devuan3:~# updatedb
root@devuan3:~# locate nvidia.conf
/etc/modprobe.d/nvidia.conf   <-- here
/etc/modules-load.d/nvidia.conf      <-- here 
root@devuan3:~#

I opened them up to see what was there:

root@devuan3:~# cat /etc/modprobe.d/nvidia.conf
install nvidia modprobe -i nvidia-legacy-340xx $CMDLINE_OPTS

install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-legacy-340xx-uvm $CMDLINE_OPTS

remove nvidia modprobe -r -i nvidia-uvm nvidia

# These aliases are defined in *all* nvidia modules.
# Duplicating them here sets higher precedence and ensures the selected
# module gets loaded instead of a random first match if more than one
# version is installed. See #798207.
alias	pci:v000010DEd00000E00sv*sd*bc04sc80i00*	nvidia
alias	pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*	nvidia
alias	pci:v000010DEd*sv*sd*bc03sc02i00*		nvidia
alias	pci:v000010DEd*sv*sd*bc03sc00i00*		nvidia
root@devuan3:~#

root@devuan3:~# cat /etc/modules-load.d/nvidia.conf
nvidia
root@devuan3:~#

Neither file had the data I expected to find (see previous post) so I looked to see what else was in /etc/modprobe.d and /etc/modules-load.d and found this:

root@devuan3:~# ls /etc/modprobe.d
dkms.conf  nvidia-blacklists-nouveau.conf  nvidia.conf  nvidia-kernel-common.conf
root@devuan3:~#

root@devuan3:~# ls /etc/modules-load.d
cups-filters.conf  nvidia.conf
root@devuan3:~#

I then opened them up to see what was there and found this:

root@devuan3:~# cat /etc/modprobe.d/dkms.conf
# modprobe information used for DKMS modules
#
# This is a stub file, should be edited when needed,
# used by default by DKMS.
root@devuan3:~#

root@devuan3:~# cat /etc/modprobe.d/nvidia-blacklists-nouveau.conf
# You need to run "update-initramfs -u" after editing this file.

# see #580894
blacklist nouveau

root@devuan3:~# cat /etc/modprobe.d/nvidia-kernel-common.conf
alias char-major-195* nvidia
#options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660
# To enable FastWrites and Sidebus addressing, uncomment these lines
# options nvidia NVreg_EnableAGPSBA=1
# options nvidia NVreg_EnableAGPFW=1
root@devuan3:~#

root@devuan3:~# cat /etc/modules-load.d/cups-filters.conf
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc
root@devuan3:~#

This file nvidia-kernel-common.conf had the data I was looking for:

options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660

ie:
The options that are related to how the driver installer sets up /dev/nvidia* and its permissions.

NVreg_DeviceFileUID=0 <--- keeps the installer from creating /dev/nvidia*. Should be =1 (?)
NVreg_DeviceFileMode=0660 <--- allows the installer to write what it needs where it needs it.

BUT the options nvidia line is commented out so none of the options are set, the most important being the creation of /dev/nvidia*, which is what nvidia-persistenced looks for but cannot find.

That's all I have been able to weed out.
But don't know how to go on from here.

Any ideas?

Thanks in advance,

A.

F_Sauce · 2020-09-15 14:23:58

It may be that there is an issue with the legacy driver, I don't know.

But one thing I have experienced is that combining the official repoes and backports may result in conflicts; I haven't followed the thread closely so might have overlooked if you'we already done this, but I would try to get rid of all NVIDIA packages, disable the backports repo and start a fresh.

BTW, I have two computers running Beowulf, I have no issues with them; the problem I refer to was with ASCII, I learned from that and has not tried the same approach which gave me problems in ASCII on Beowulf.

Olav

Last edited by F_Sauce (2020-09-15 14:28:20)

HevyDevy · 2020-09-15 14:53:43

What kernel are you using Altoid ?

Will try to install nvidia again on the machine i have that uses 340xx again with beowulf and see if i run into same issues.

Edit: Just doing a little researching, can you confirm where the nvidia-persistenced binary is located Altoid ?

is it in /usr/bin or /usr/lib/ ?

Last edited by HevyDevy (2020-09-15 15:14:13)

Altoid · 2020-09-15 15:12:07

Hello:

F_Sauce wrote:

... an issue with the legacy driver, I don't know.

As the driver will not install properly, would seem so.

F_Sauce wrote:

... combining the official repoes and backports may result in conflicts ...
... disable the backports repo and start a fresh.

This is my /etc/apt/sources.list:

groucho@devuan3:~$ cat /etc/apt/sources.list

deb http://pkgmaster.devuan.org/merged beowulf main non-free contrib
deb http://pkgmaster.devuan.org/merged beowulf-security main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-backports main contrib non-free
groucho@devuan3:~$

According to https://pkginfo.devuan.org/ the Nvidia driver version in beowulf is 340.108-3-deb10u1 and the version in beowulf-backports is 340.108-6-bpo10+1.

I had thought about this beowulf vs. beowulf-backports you mention and as I do have beowulf-backports in my /etc/apt/sources.list I looked to see what version apt was installing.

groucho@devuan3:~$ apt list | grep 340xx-driver

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

nvidia-legacy-340xx-driver-bin/stable 340.108-3~deb10u1 amd64
nvidia-legacy-340xx-driver-libs/stable 340.108-3~deb10u1 amd64
nvidia-legacy-340xx-driver/stable 340.108-3~deb10u1 amd64        <---- this is the version apt will install
groucho@devuan3:~$

When I look at the driver version that would install via synaptic, I get the same result: synaptic installs version 340.108-3~deb10u1 by default and to install version 340.108-6-bpo10+1 you have to use the force version option.

Thanks for your input.

Cheers,

A.

HevyDevy · 2020-09-15 15:28:38

If you have a look at the debian package tracker it looks like there is issues with nvida-persistence and it is being removed, i dont know how this affects Beowulf stable kernel but it affects module building in the latest kernels, so if you are using a kernel from testing or som such latest kernel this is maybe why you are having issues.

https://tracker.debian.org/pkg/nvidia-persistenced

Altoid · 2020-09-15 16:12:26

Hello:

HevyDevy wrote:

What kernel ...

Devian3 - Beowulf stable.

groucho@devuan3:~$ uname -a
Linux devuan3 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan3:~$

HevyDevy wrote:

Will try to install nvidia again on the machine i have that uses 340xx again with beowulf ...

Thanks for the effort ... ;- )

HevyDevy wrote:

... can you confirm where the nvidia-persistenced binary is located ...

I installed the driver again (but no reboot) and this is what I get:

root@devuan3:~# locate nvidia-persistenced
/etc/init.d/nvidia-persistenced
/etc/rc0.d/K01nvidia-persistenced
/etc/rc1.d/K01nvidia-persistenced
/etc/rc2.d/S02nvidia-persistenced
/etc/rc3.d/S02nvidia-persistenced
/etc/rc4.d/S02nvidia-persistenced
/etc/rc5.d/S02nvidia-persistenced
/etc/rc6.d/K01nvidia-persistenced
/lib/systemd/system/nvidia-persistenced.service
/run/nvidia-persistenced

/usr/bin/nvidia-persistenced    <- here it is

/usr/share/doc/nvidia-legacy-340xx-driver/html/nvidia-persistenced.html
/usr/share/doc/nvidia-persistenced
/usr/share/doc/nvidia-persistenced/changelog.Debian.gz
/usr/share/doc/nvidia-persistenced/copyright
/usr/share/lintian/overrides/nvidia-persistenced
/usr/share/man/man1/nvidia-persistenced.1.gz
/var/cache/apt/archives/nvidia-persistenced_418.56-1_amd64.deb
/var/lib/dpkg/info/nvidia-persistenced.conffiles
/var/lib/dpkg/info/nvidia-persistenced.list
/var/lib/dpkg/info/nvidia-persistenced.md5sums
/var/lib/dpkg/info/nvidia-persistenced.postinst
/var/lib/dpkg/info/nvidia-persistenced.postrm
/var/lib/dpkg/info/nvidia-persistenced.prerm
root@devuan3:~#

Thanks for your help,

A.

Altoid · 2020-09-15 16:20:13

Hello:

HevyDevy wrote:

... look at the debian package tracker ...
... issues with nvida-persistence ...
... being removed ...

Then I hope that they remove it from Beowulf stable.
asap.

HevyDevy wrote:

... dont know how this affects Beowulf stable ...

Evidently, not in a good way.

HevyDevy wrote:

... if you are using a kernel from testing or ...

No ...
Not that adventurous, bleeding edge is not where I want or need to be.

I'm a Debian user/greybeard at heart.
I always found the (original) Debian (pre systemd) philosophy to be the way to do things.

Cheers,

A.

Last edited by Altoid (2020-09-16 01:09:32)

Altoid · 2020-09-16 01:35:26

Hello:

Altoid wrote:

... hope that they remove it from Beowulf stable.

May not be necessary?

As luck (or whatever it is) would have it, I found an interesting post right here: --> https://dev1galaxy.org/viewtopic.php?pid=20903#p20903
Yes, under my nose.

A Dev1 member (Marjorie) had more or less the same problem a bit over a year ago.

Found out that nvidia-persistenced is a suggested package so simply did not install it ...
ie: apt-get --no-install-recommends install nvidia-legacy-340xx-driver

... which solved the issue I had with nvidia-persistenced itself.
ie:

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

There was another problem related to stopping an existing nvidia-persistenced service for which she modified an installation script, but as mine is a clean netinstall (uses nouveau), it was not required.

The driver apparently installed with no issues.
I rebooted but SLiM did not start and startx showed errors.

So feeling very confident, I transplanted the xorg.conf file from ascii and rebooted.

No cigar ...

Unfortunately, this did not solve my problem which revealed to have yet another part to it.
At the very start of the /var/log/Xorg.0.log file, this is what you see:

modprobe: FATAL: module nvidia-legacy-340xx not found in directory /lib/modules/4.19.0-9-amd64

I checked and, as the output clearly states, the module is not there.

Now I've run out of ideas ...

Anyone?

Thanks in advance,

A.

golinux · 2020-09-16 02:18:25

Maybe let sgfxi handle it?

HevyDevy · 2020-09-16 04:13:50

Ok i managed to get it working.

This is what i did.

first blacklist nouveau driver.

sudo nano /etc/modprobe.d/nvidia-blacklists-nouveau.conf

# You need to run "update-initramfs -u" after editing this file.

# see #580894
blacklist nouveau

then

sudo apt install linux-headers-$(uname -r) build-essential

sudo apt install nvidia-legacy-340xx-kernel-dkms --no-install-recommends

sudo apt install nvidia-legacy-340xx-driver --no-install-recommends

sudo depmod

sudo update-initramfs -u

sudo update-grub

my xorg.conf

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 450.57

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now reboot !

This may work for you it may not.

lspci -knn | grep -iA3 nvidia
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2)
	Subsystem: Toshiba Corporation GT216M [GeForce GT 330M] [1179:fd30]
	Kernel driver in use: nvidia
	Kernel modules: nvidia

Last edited by HevyDevy (2020-09-16 05:02:09)

Altoid · 2020-09-16 12:32:11

Hello:

golinux wrote:

Maybe let sgfxi handle it?

I'll have a look ...

But I recall having used it once but unless I'm not remembering right, sgfxi is for getting xorg.conf set up properly.
I used it when I was setting up my first devuan (Jesse) and it did no better than my efforts with a xorg.conf file patched together with bits from web examples.

Methinks this is an installer problem.

Thanks for your input.

A.

Altoid · 2020-09-16 13:19:36

Hello:

HevyDevy wrote:

... managed to get it working.
This is what i did.

Great ! =-D!

Here's the terminal printout of the same process in my Beowulf installation:

groucho@devuan3:~$ su -
Password: 
root@devuan3:~#

root@devuan3:~# jed /etc/modprobe.d/nvidia-blacklist-nouveau.conf
root@devuan3:~# 
root@devuan3:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64

root@devuan3:~# apt install linux-headers-$(uname -r) build-essential
Reading package lists... Done
Building dependency tree       
Reading state information... Done
build-essential is already the newest version (12.6).
build-essential set to manually installed.
The following additional packages will be installed:
  linux-compiler-gcc-8-x86 linux-headers-4.19.0-9-common linux-kbuild-4.19
The following NEW packages will be installed:
  linux-compiler-gcc-8-x86 linux-headers-4.19.0-9-amd64 linux-headers-4.19.0-9-common linux-kbuild-4.19
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.4 MB of archives.
After this operation, 57.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-compiler-gcc-8-x86 amd64 4.19.132-1 [458 kB]
Get:2 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-headers-4.19.0-9-common all 4.19.118-2+deb10u1 [8,371 kB]
Get:3 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-kbuild-4.19 amd64 4.19.132-1 [691 kB]                                    
Get:4 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-headers-4.19.0-9-amd64 amd64 4.19.118-2+deb10u1 [917 kB]                 
Fetched 10.4 MB in 8s (1,265 kB/s)                                                                                                         
Selecting previously unselected package linux-compiler-gcc-8-x86.
(Reading database ... 75161 files and directories currently installed.)
Preparing to unpack .../linux-compiler-gcc-8-x86_4.19.132-1_amd64.deb ...
Unpacking linux-compiler-gcc-8-x86 (4.19.132-1) ...
Selecting previously unselected package linux-headers-4.19.0-9-common.
Preparing to unpack .../linux-headers-4.19.0-9-common_4.19.118-2+deb10u1_all.deb ...
Unpacking linux-headers-4.19.0-9-common (4.19.118-2+deb10u1) ...
Selecting previously unselected package linux-kbuild-4.19.
Preparing to unpack .../linux-kbuild-4.19_4.19.132-1_amd64.deb ...
Unpacking linux-kbuild-4.19 (4.19.132-1) ...
Selecting previously unselected package linux-headers-4.19.0-9-amd64.
Preparing to unpack .../linux-headers-4.19.0-9-amd64_4.19.118-2+deb10u1_amd64.deb ...
Unpacking linux-headers-4.19.0-9-amd64 (4.19.118-2+deb10u1) ...
Setting up linux-compiler-gcc-8-x86 (4.19.132-1) ...
Setting up linux-kbuild-4.19 (4.19.132-1) ...
Setting up linux-headers-4.19.0-9-common (4.19.118-2+deb10u1) ...
Setting up linux-headers-4.19.0-9-amd64 (4.19.118-2+deb10u1) ...
root@devuan3:~#

root@devuan3:~# apt install nvidia-legacy-340xx-kernel-dkms --no-install-recommends
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 nvidia-installer-cleanup nvidia-kernel-common
  nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-support nvidia-modprobe update-glx
Suggested packages:
  python3-apport menu nvidia-driver
Recommended packages:
  linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers nvidia-legacy-340xx-driver
  | libnvidia-legacy-340xx-cuda1
The following NEW packages will be installed:
  dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common
  nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-kernel-support nvidia-modprobe update-glx
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4,313 kB of archives.
After this operation, 16.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Preconfiguring packages ...
Selecting previously unselected package update-glx.
(Reading database ... 92511 files and directories currently installed.)
Preparing to unpack .../update-glx_1.0.0_amd64.deb ...
Unpacking update-glx (1.0.0) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.0.0_amd64.deb ...
Unpacking glx-alternative-mesa (1.0.0) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20151021+9_amd64.deb ...
Unpacking nvidia-installer-cleanup (20151021+9) ...
Setting up nvidia-installer-cleanup (20151021+9) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 92612 files and directories currently installed.)
Preparing to unpack .../0-glx-diversions_1.0.0_amd64.deb ...
Unpacking glx-diversions (1.0.0) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../1-glx-alternative-nvidia_1.0.0_amd64.deb ...
Unpacking glx-alternative-nvidia (1.0.0) ...
Selecting previously unselected package nvidia-legacy-340xx-alternative.
Preparing to unpack .../2-nvidia-legacy-340xx-alternative_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Selecting previously unselected package dkms.
Preparing to unpack .../3-dkms_2.6.1-4_all.deb ...
Unpacking dkms (2.6.1-4) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../4-nvidia-kernel-common_20151021+9_amd64.deb ...
Unpacking nvidia-kernel-common (20151021+9) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../5-nvidia-modprobe_418.56-1_amd64.deb ...
Unpacking nvidia-modprobe (418.56-1) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-support.
Preparing to unpack .../6-nvidia-legacy-340xx-kernel-support_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-kernel-support (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-dkms.
Preparing to unpack .../7-nvidia-legacy-340xx-kernel-dkms_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-kernel-dkms (340.108-3~deb10u1) ...
Setting up nvidia-kernel-common (20151021+9) ...
Setting up update-glx (1.0.0) ...
Setting up dkms (2.6.1-4) ...
Setting up nvidia-modprobe (418.56-1) ...
Setting up glx-alternative-mesa (1.0.0) ...
Setting up glx-diversions (1.0.0) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for glx-alternative-mesa (1.0.0) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in auto mode
Setting up glx-alternative-nvidia (1.0.0) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Setting up nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-kernel-support (340.108-3~deb10u1) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-3~deb10u1) ...
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 4.19.0-9-amd64
Building initial module for 4.19.0-9-amd64
Done.

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

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

depmod.......

DKMS: install completed.
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-9-amd64
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
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-9-amd64
root@devuan3:~#

root@devuan3:~# apt install nvidia-legacy-340xx-driver --no-install-recommends
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libegl1-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-glcore
  libnvidia-legacy-340xx-ml1 nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-vdpau-driver
  nvidia-support xserver-xorg-video-nvidia-legacy-340xx
Recommended packages:
  nvidia-settings-legacy-340xx nvidia-persistenced nvidia-legacy-340xx-driver-libs-i386 libgles1-nvidia-legacy-340xx
  libgles2-nvidia-legacy-340xx libnvidia-legacy-340xx-cfg1
The following NEW packages will be installed:
  libegl1-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-glcore
  libnvidia-legacy-340xx-ml1 nvidia-legacy-340xx-driver nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs
  nvidia-legacy-340xx-vdpau-driver nvidia-support xserver-xorg-video-nvidia-legacy-340xx
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/19.4 MB of archives.
After this operation, 121 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Preconfiguring packages ...
Selecting previously unselected package libnvidia-legacy-340xx-glcore:amd64.
(Reading database ... 92882 files and directories currently installed.)
Preparing to unpack .../00-libnvidia-legacy-340xx-glcore_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-glcore:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../01-nvidia-support_20151021+9_amd64.deb ...
Unpacking nvidia-support (20151021+9) ...
Selecting previously unselected package libgl1-nvidia-legacy-340xx-glx:amd64.
Preparing to unpack .../02-libgl1-nvidia-legacy-340xx-glx_340.108-3~deb10u1_amd64.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libnvidia-legacy-340xx-eglcore:amd64.
Preparing to unpack .../03-libnvidia-legacy-340xx-eglcore_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-eglcore:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libegl1-nvidia-legacy-340xx:amd64.
Preparing to unpack .../04-libegl1-nvidia-legacy-340xx_340.108-3~deb10u1_amd64.deb ...
Unpacking libegl1-nvidia-legacy-340xx:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-libs:amd64.
Preparing to unpack .../05-nvidia-legacy-340xx-driver-libs_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver-libs:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libnvidia-legacy-340xx-ml1:amd64.
Preparing to unpack .../06-libnvidia-legacy-340xx-ml1_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-ml1:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-bin.
Preparing to unpack .../07-nvidia-legacy-340xx-driver-bin_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver-bin (340.108-3~deb10u1) ...
Selecting previously unselected package xserver-xorg-video-nvidia-legacy-340xx.
Preparing to unpack .../08-xserver-xorg-video-nvidia-legacy-340xx_340.108-3~deb10u1_amd64.deb ...
Unpacking xserver-xorg-video-nvidia-legacy-340xx (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-vdpau-driver:amd64.
Preparing to unpack .../09-nvidia-legacy-340xx-vdpau-driver_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-vdpau-driver:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver.
Preparing to unpack .../10-nvidia-legacy-340xx-driver_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver (340.108-3~deb10u1) ...
Setting up nvidia-support (20151021+9) ...
Setting up libnvidia-legacy-340xx-ml1:amd64 (340.108-3~deb10u1) ...
Setting up libnvidia-legacy-340xx-glcore:amd64 (340.108-3~deb10u1) ...
Setting up libgl1-nvidia-legacy-340xx-glx:amd64 (340.108-3~deb10u1) ...
Setting up xserver-xorg-video-nvidia-legacy-340xx (340.108-3~deb10u1) ...
Setting up libnvidia-legacy-340xx-eglcore:amd64 (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-vdpau-driver:amd64 (340.108-3~deb10u1) ...
Setting up libegl1-nvidia-legacy-340xx:amd64 (340.108-3~deb10u1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
update-alternatives: using /usr/lib/nvidia/legacy-340xx to provide /usr/lib/nvidia/nvidia (nvidia) in auto mode
Processing triggers for man-db (2.8.5-2) ...
Setting up nvidia-legacy-340xx-driver-bin (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-driver-libs:amd64 (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-driver (340.108-3~deb10u1) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
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 libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
root@devuan3:~#

root@devuan3:~# depmod
root@devuan3:~#

root@devuan3:~# 
root@devuan3:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
root@devuan3:~# 
root@devuan3:~# update-grub
Generating grub configuration file ...
Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-4.19.0-9-amd64
Found initrd image: /boot/initrd.img-4.19.0-9-amd64
Found Devuan GNU/Linux ascii on /dev/sde1
done
root@devuan3:~#

Just to see, I tried to run nvidia-xconfig but had to install it because it was not there.
It does not detect my three monitors, only one so it is not much use.

groucho@devuan3:~$ lspci -knn | grep -iA3 nvidia
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1)
	Subsystem: NVIDIA Corporation G96GL [Quadro FX 580] [10de:063a]
	Kernel driver in use: nvidia
	Kernel modules: nvidia
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1)
	Subsystem: NVIDIA Corporation G96GL [Quadro FX 580] [10de:063a]
	Kernel driver in use: nvidia
	Kernel modules: nvidia
--- snip ---
groucho@devuan3:~$

HevyDevy wrote:

This may work ...

It did ... 8-D!
Thanks a lot for your effort.

Now it should just be a matter of setting up xorg.conf and everything should be allright.
A transplant from my ascii setup should do, as always.
Should not (?) need any changes, but you never know with Nvidia.

--->
Edit:
Transplanted the ascii /etc/X11/xorg.conf to Beowulf and it all works perfectly well.
Main difference is that now I'll be using Openbox, so I have to configure it and Tint2 for three screens.

The /var/log/xorg.0.log file has the same warnings related to Composite+Xinerama, disabled RandR, missing cyrilic fonts and fbGetGCPrivateKey unresolved, so it seems that there's nothing new there.
<---

Q:
Am I correct in assuming that this is a problem with the installer scripts in the nvidia-legacy-340xx-driver package in the Beowulf repository?

I say this is probably so because the nvidia 340xx driver has not been updated by Nvidia for a few years now.
ie: it is the same code, has not had any maintenance.

So if there's anything that has changed, I can only think that it has been something within the Devuan/Debian distribution and/or the installer scripts in the package.
A Debian issue then?

Once again, thanks a lot for your help.

Cheers,

A.

Last edited by Altoid (2020-09-16 13:45:37)

HevyDevy · 2020-09-17 08:02:21

No worries Altoid glad it worked for ya.

Can you setup X from nvidia-settings for the 3 monitors. Ive never messed with nvidia settings as i dont game or doing anything hard on a computer other than watching videos and reading ebooks.

package https://packages.debian.org/buster/nvidia-settings

To answer your question about the driver, i have no idea sorry.

Last edited by HevyDevy (2020-09-17 08:24:00)

Altoid · 2020-09-17 12:39:55

Hello:

HevyDevy wrote:

... glad it worked for ya.

I would not have know how to fix it.
It is a severe issue, no clues anywhere.
Thanks again. =^)

HevyDevy wrote:

... setup X from nvidia-settings for the 3 monitors ...

No.
In my experience, you have to get xorg.conf right first.
This could be (?) because the xserver disables RandR if Xinerama is enabled.

[ 29.157] (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which
[ 29.157] (WW) NVIDIA:     is an unsupported configuration.  The driver will continue
[ 29.157] (WW) NVIDIA:     to load, but may behave strangely.
[ 29.157] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the NVIDIA: X server.

When I got this box and got the twin Nvidia cards, I had to go through literally dozens of re-boots while testing an xorg.conf file I went along patching together with bits of different samples posted online. You would think that being to identical Nvidia cards it would be a simpler task with nvidia-xsettings.

Once you get xorg.conf right, you can play with nvidia-settings but I just use them to get an idea of what is going on.

The good thing is that (for now) I just cp the xorg.conf from one drive to the other and it works and as I don't play games or use anything of the sort, I really don't have to touch it once it is working properly.

HevyDevy wrote:

... about the driver, i have no idea sorry.

There must be a maintainer for this at Debian, maybe there is one here at Devuan who should know about this.

Q:
The process you wrote up to install this driver, how does it differ from what the installer does?
I mean, besides working properly ... 8^*

Thanks in advance,

A.

The officially official Devuan Forum!

#1 2020-09-13 22:50:50

[Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#2 2020-09-14 12:23:21

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#3 2020-09-14 14:10:48

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#4 2020-09-14 14:44:05

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#5 2020-09-14 15:16:49

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#6 2020-09-14 15:21:23

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#7 2020-09-14 16:14:56

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#8 2020-09-14 16:32:54

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#9 2020-09-14 21:47:24

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#10 2020-09-14 22:13:16

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#11 2020-09-14 22:58:46

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#12 2020-09-15 13:42:09

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#13 2020-09-15 14:23:58

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#14 2020-09-15 14:53:43

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#15 2020-09-15 15:12:07

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#16 2020-09-15 15:28:38

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#17 2020-09-15 16:12:26

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#18 2020-09-15 16:20:13

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#19 2020-09-16 01:35:26

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#20 2020-09-16 02:18:25

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#21 2020-09-16 04:13:50

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#22 2020-09-16 12:32:11

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#23 2020-09-16 13:19:36

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#24 2020-09-17 08:02:21

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

#25 2020-09-17 12:39:55

Re: [Solved] Beowulf - Nvidia legacy 340XX driver will not install.

Board footer