The officially official Devuan Forum!

You are not logged in.

#1 Installation » Refracta2usb not in Beowulf repo? » Yesterday 22:38:36

Altoid
Replies: 1

Hello:

Can't find refracta2usb in the Beowulf repository.
I recall the same thing happening when I wanted to install it in ascii but cannot recall how that got solved.

Also ...

On installing refractasnapshot-gui I got these warnings:

---
Setting up live-tools (1:20171207) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start runlevel arguments (none) do not match live-tools Default-Start values (S)
Setting up uuid-runtime (2.33.1-0.1+devuan1~beowulf2) ...
Adding group `uuidd' (GID 118) ...
Done.

Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory
Adding system user `uuidd' (UID 111) ...
Adding new user `uuidd' (UID 111) with group `uuidd' ...
Not creating home directory `/run/uuidd'.
Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory

So I checked and found a uuidd group so I added myself to it.

The directory /run/uuidd exists.

/$ locate /run/uuidd
/run/uuidd
/run/uuidd/request
/run/uuidd/uuidd.pid
/$ 

Is there something I should do about the update-rc.d: warnings?

I also got this:

cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
nor crypto modules. If that's on purpose, you may want to uninstall the 
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
integration and avoid this warning.

Should I uninstall the 'cryptsetup-initramfs' package?
I'm not using encryption (for now) but would need it if I eventually decide to use tomb.
Although not sure it is worth it as it is described as being for fairly strong encryption.

Thanks in advance,

A.

#2 Re: Desktop and Multimedia » 'Drop to terminal' question » 2020-09-22 22:48:52

Hello:

Head_on_a_Stick wrote:

... login screen) will launch the graphical desktop on TTY7 by default ...

Right.

So, when I drop to a terminal via  Ctrl+Alt+F1 I will be on TTY1 (or TTYn depending on the Fn used) save for TTY7 which is already running and which I get back to by means of Ctrl+Alt+F7. Yes?

Thanks for the explanation.

Cheers,

A.

#3 Desktop and Multimedia » 'Drop to terminal' question » 2020-09-22 19:52:11

Altoid
Replies: 2

Hello:

I know that Ctrl+Alt+F1 will drop me to a log-in terminal and that Ctrl+Alt+F7 will get me back to the desktop.
But I don't have much of a clue as to what is happening 'behind the scenes' so to speak.

eg:
How does getting a terminal with Ctrl+Alt+F1 relate to booting to a log-in terminal, logging in, doing startx and opening up a terminal as root?

If I start a terminal with Ctrl+Alt+F1, log in and and then do startx, are there two users (both me) with the same userid or am I being taken to my original desktop?

Rather confused as to how it works.

Thanks in advance,

A.

#4 Re: Forum Feedback » Unable to edit any of my own posts » 2020-09-22 13:47:57

Hello:

Vernon wrote:

... which would prove your critics correct that Devuan is more about tantrums ...
... changing editing times instead of leaving well enough alone.

I find the tone in your posts to be both unwarranted and out of place, a view that I expect many here at Dev1 share.

I would personally appreciate your showing more respect to those who volunteer their work to keep this site working.

Thank you.

A.

#5 Re: Forum Feedback » Unable to edit any of my own posts » 2020-09-21 23:55:08

Hello:

ralph.ronnquist wrote:

... discussion site becomes a wiki site merely by claiming that it is one.

+1

ralph.ronnquist wrote:

... proclaim that a discussion site is an uninteresting extra and close it down ...

Please don't.

ralph.ronnquist wrote:

... the benefit of allowing such editing well outweighs the risk of communal loss ...

It does not.

However small the risk of communal loss may seem, it is far too much if it is communal loss of any sort.

Just my $0.02

A.

#6 Re: Installation » Linux - Locale conundrum » 2020-09-21 21:59:04

Hello:

Altoid wrote:

... get back later on.

Apparently it is all fixed.
I'll have to see how things go with the logfiles and MSOffice/LibreOffice stuff.

~$ cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="latam"
XKBVARIANT="deadtilde"
XKBOPTIONS="lv3:ralt_switch,terminate:ctrl_alt_bksp"

BACKSPACE="guess"
~$ 

Took me a while because I was incorrectly setting nodeadtilde, fussing up the layout.

~$ cat /etc/default/locale
#  File generated by update-locale
LANG=en_GB.UTF-8
#LANGUAGE=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF.8"
LC_COLLATE="en_GB.UTF-8"
# LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
~$ 
~$ locale -a
C
C.UTF-8
en_GB.utf8
es_AR.utf8
POSIX
~$ 

For future reference in case anyone else comes across a similar problem, this is the keyboard layout -> http://kbdlayout.info/KBDLA/
No, I don't use a MS kb. this web page is very useful (has scan codes, virtual keys, etc.) and references to kbdla.dll which is a MS file. 8^P

Thanks for your input.

Cheers,

A.

#7 Re: Installation » Linux - Locale conundrum » 2020-09-21 18:58:04

Hello:

Head_on_a_Stick wrote:

... excellent.

Thanks. =-)
Methinks rather lacking in volcabulary.

Head_on_a_Stick wrote:

... tried selecting UTF-8 as the encoding?

Yes.

Head_on_a_Stick wrote:

... log files need root ...

I was opening them as root.

Head_on_a_Stick wrote:
# dpkg-reconfigure locales keyboard-configuration

Ahh .....

I was doing dpkg-reconfigure keyboard-configuration and dpkg-reconfigure locales and not dpkg-reconfigure locales keyboard-configuration.
So I was getting errors.

I'll try this and get back later on.

Thanks for your input.

A.

#8 Installation » Linux - Locale conundrum » 2020-09-20 19:59:11

Altoid
Replies: 3

Hello:

I have an unsolved issue of sorts involving locale settings which I have not been able to get around for the longest while.

A short explanation is in order.

My mother tongue is Spanish, my second language being English.

My exposure to IT was from the very start in English and for some reason I have never been to feel comfortable with IT in Spanish.
Notwithstanding, when I work with others in IT in my mother tongue and as trhere are words to explain most everything, I insist that the proper Spanish terms be used.
One of my pet peeves.

Being my initial exposure to IT in English all the OSs I have ever used, from DOS back in the day onwards to Linux today have been/are in English.

But ...

My time zone is GMT -03:00, my date/time format of choice is DD/MM/YYYY - HH:MM:SS and because I work in the two languages I speak (occassionally dabbling in French) I have preferred a keyboard layout that has most if not all the needed letters and symbols. ie: Latin American with the standard 105-key layout and then some (if I can remember where they are).

eg:

         | 1 2 3 4 5 6 7 8 9 0 ' ¿
Shift ° ! " # $ % & / ( ) = ? ¡
AltGr ¬ | @ · ~ ½ ¬ { [ ] } \ ¸

         q w e r t y u i o p ' +
Shift Q W E R T Y U I O P " *
AtGr @ ł € ¶ ŧ ← ↓ → ø þ " ~

         a s d f g h j k l ñ { }
Shift A S D F G H J K L Ñ [ ]
AltGr æ ß ð đ ŋ ħ̉ ̉  ĸ ł ~ ^ `

        < z x c v b n m , . -
Shift > Z X C V B N M ; : _
AltGr « » ¢ “ ” n µ   · ̣

There are sometimes problems related to the opening/saving of spreadsheets (MSOffice/Libre Office) and the /var/log/ files which can be parsed in a terminal but not be seen properly with some editors due to ISO encodings.

eg: Pluma + /var/log/auth.log, kern.log, messages ...

pluma has not been able to detect the character encoding.
Please check that you are not trying to open a binary file.
Select a character encoding from the menu and try again.

Basically, what I want is that my Linux box be 100% in English (en-GB preferred), be able to use the keyboard layout I need and be able to look at log files with an editor without problems.

Any suggestions?

Thanks in advance,

A.

#9 Re: Forum Feedback » Unable to edit any of my own posts » 2020-09-20 13:20:06

Hello:

yeti wrote:

Re: Changed context after reply
... always quote the relevant parts.

Always do that and (of course) never top post.
So I instantly realised what had transpired.

Cheers,

A.

#10 Re: Forum Feedback » Unable to edit any of my own posts » 2020-09-20 00:27:23

Hello:

golinux wrote:

... suggest time limits for consideration.

I think that posts which have not received an answer should have no time limit for edition by the OP, who should also be able to delete it if deemed necessary.

But, if a post has received an answer the OP should not be able to delete it.

With respect to editing a post that has received an answer, I'd say that it depends on the forum.

I have had a forum member (not here, of course ...) edit his original post and in doing so make my answer look out of place.
ie: like if I was replying to something that he did not write, to the extent of making me doubt for a second as to what I had read.

It's only happened to me once in more that 20 years of participating in different fora, but I found it to be rather unsettling.

I'm sure that here at Dev1 it could be allowed (with the provision of automatic edit notices) for as long as it takes for a second reply to come in.
From the on, that particular post would be closed to editing.

Make sense?

Cheers,

A.

#11 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 23:40:01

Hello:

GlennW wrote:

Thank you for documenting ...

You're welcome ...

But the merit is all HeavyDevy's.
I would not have known where to start.

Cheers,

A.

#12 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 16:11:56

Hello:

HevyDevy wrote:

... the debian wiki guide that this needs to be done as a separate set of commands/instruction ...

I see ...

But I have not had to do this in any of the other instances where I installed these same legacy-340xx drivers in other Linux distributons.

It did not happen when I moved from Linux Mint to a fresh Devuan Jesse installation either.
So why does it happen now in Beowulf?

The legacy-340xx driver is in the Beowulf distribution just as it was in the Jesse distribution.

Thanks for the heads-up, I'll keep the link in the Devuan bookmarks folder.

Once again, thanks for your help.
I certainly would not have my three screens in Beowulf without it.

Cheers,

A.

#13 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 13:43:48

Hello:

HevyDevy wrote:

... install the linux-headers first, i dont know ...

I would think that anything that was needed by the installer would have been listed as a dependency.
Or a warning that linux-headers were not installed issued and the installation aborted.

HevyDevy wrote:

... definetly something buggy going on due to that nvidia-persistenced ...

Indeed ...
There was that post last year to which I made reference in this thread.
But it seems no one at Debian took notice.

HevyDevy wrote:

... few of the steps i did were probably not needed ...
... depmod, update-initramfs and update-grub ...

Well ...
And it got me through. ;- )

I worry things such as these ie: a severely broken installation, don't get looked at by maintainers.
I expect to be using the same box with the same perfectly working video cards when I switch to Ceres.

Cheers,

A.

#14 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#15 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#16 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#17 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#18 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#19 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#20 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#21 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#22 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#23 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#24 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 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.

#25 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 15:16:49

Hello:

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.

Board footer

Forum Software