yes, i mada error in setting it up; now its function Beowulf;

would be nice if there is an "ption" to "transport" the nvidia-legacy-340xx over atleast to Devuan 4.0!

kernel is 4.19.-27

Linux devuan 4.19.0-27-amd64

however there are no correspondent linux-headers available in the repo

I think that is not really true. From:
https://pkginfo.devuan.org/cgi-bin/poli … *&x=submit

linux-headers-4.19.0-27-common - 4.19.316-1
http://deb.devuan.org/merged   beowulf-security/main   amd64
http://deb.devuan.org/merged   beowulf-security/main   i386
http://deb.devuan.org/merged   beowulf-security/main   arm64

They are available, but not in the main section, you have to enable security!

but now there seem new problems;

Beowulf is in legacy BIOS mode (Mac 2010 model and think has not yet proper UEFI mode)

kernel is 4.19.-27

Linux devuan 4.19.0-27-amd64

however there are no correspondent linux-headers available in the repo

linux-headers-4.19.0-20-all          linux-headers-4.19.0-21-amd64
linux-headers-4.19.0-20-all-amd64    linux-headers-4.19.0-21-cloud-amd64
linux-headers-4.19.0-20-amd64        linux-headers-4.19.0-21-common
linux-headers-4.19.0-20-cloud-amd64  linux-headers-4.19.0-21-common-rt
linux-headers-4.19.0-20-common       linux-headers-4.19.0-21-rt-amd64
linux-headers-4.19.0-20-common-rt    linux-headers-amd64
linux-headers-4.19.0-20-rt-amd64     linux-headers-cloud-amd64
linux-headers-4.19.0-21-all          linux-headers-rt-amd64
linux-headers-4.19.0-21-all-amd64    

such that the install of nvidia-legacy-340xx-driver is probably botched since i am getting error during boot

could not insert nvidia ...not permitted

probably this can be bettered by using a kernel from backports?
is it possible to use devuan backports on the archives for Beowulf?

But even if have it up and running, would still probably need to upgrade to Devuan 4.0 atleast, since for connecting to university i need newer Cisco package for the VPN sometimes (although they seem now accepting also openconnect as alternative).

EDIT: upgrading to Chimaera Devuan.4.0 yielded the following:

Setting up linux-image-5.10.0-35-amd64 (5.10.237-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-32-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-32-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-35-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-35-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-35-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j2 modules KERNEL_UNAME=5.10.0-35-amd64; env CCACHE_DI
SABLE=1 NV_VERBOSE=1 make -C uvm modules KERNEL_UNAME=5.10.0-35-amd64 KBUILD_EXTMOD=/var/
lib/dkms/nvidia-legacy-340xx/340.108/build/uvm.............(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.0-35-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for more information.

/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-35-amd64
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg357766.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...

and after reboot during bootup the following error (but it bould into desktop)

FYI, if interested, See here.
Interesting, but probably not worth all the hassle and risks involved.

As always, YMMV.

Best,

A.

Not so fast.  8^°

The current status of the Devuan releases can be seen here.

As you can see, the stable/maintained releases are these:
Daedalus / Bookworm
Chimaera / Bullseye

The archived releases are these:
Beowulf / Buster
ASCII / Stretch
Jessie / Jessie

The next* Devuan release, Excalibur (Trixie) is still in the developement / testing phase and has not been released yet.
* as always, it will be ready when it is ready.

Last but not least, there is Ceres, Devuan unstable (Sid).
It has not and will not ever (?) be a release as we know it.
It is a platform for experimentation which is why you have a 340XX package available.

As for the nvidia-legacy-340xx-driver, it is still available for Beowulf but not for Daedalus or Excalibur.
It has been so for a good while now and I have serious doubts as to its viability in future releases.

I asked (previous post) to see if anyone out there had experimented with the various recipes for installing that are making the rounds in the web lately. 

Best,

A.

Apparently so ...

See here.

Q: has anyone installed this 340XX driver in Devuan Daedalus?
I thought it was no longer available for any reelase past Beowulf ... 8^°

Best,

A.

is this Nvidia-legacy 340 still available for Devuan 4.0 or will i have to install Devuan Beowulf to get it running.

Just installed Devuan 4.0 on an older Mac but it seem not finding anything related to Nvidia-legacy-340.

Thanks.

i tried this solution for my laptop, but i dont seem to get "suspend" working; when i close laptop lid, the system wont resume.
https://dev1galaxy.org/viewtopic.php?pid=24694#p24694

before had used "Nvidia-Linux-x86_64-340-xx.run" (on Devuan Jessie an Ascii) and had no major problems, and resume worked fine.
But now , with Beowulf, if i would install Nvidia.run on a fresh install, and then let nvidia-xconfig create config file, after reboot there would be just a black screen. On Chimaera, it would not even install properly (probably due to 5.10 kernel).

do you guys have no problems with suspend and 340-legacy drivers?
on a different partition have installed ubuntu 22.04 and the 333/ppa for nvidia-legacy, and it works, also resume functions, but it is really slow, and would prefer devuan to use, but cant get to work it properly with newer fresh install of devuan beowulf (upgrading from devuan jessie to beowulf seems to work, though)
sorry but i am not very experienced with nvidia  cards and linux in general.

https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy

EDIT: it seems the problems with suspend / lock / resume from suspend occur mainly  on XFCE4

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991788

switching to Cinnamon does not yield these problems, so problem seems "solved" on this laptop with Beowulf;
however, the .run file from Nvidia 340
https://www.nvidia.com/en-us/drivers/unix/

does build correctly on latest 4.19, but would not produce a viable login on my laptop; i am still open to suggestion on how to solve this;
first the installer asks if he should blacklist nouveau (yes), then after reboot install the driver via .run which builds correctly, then asks if nvidia xconfig should produce config file (yes) and after another reboot instead of login screen greeted with blank screen and not even str+alt+1 does function from there.

Indeed ...
As expected.  8^D!

OpenCL subsystem isn't available   <- it would seem that there is no such thing in your laptop.

Does your video card actually support OpenCL?
I think it probably does not.

See this table: https://www.notebookcheck.net/Quadro-FX … 598.0.html

but ...

The NVIDIA Quadro FX 380M is a newer card and supports OpenCL but the NVIDIA Quadro FX 770M (~ a year + five months older) apparently does not.

My advise is to remove the OpenCL driver which obviously does not work in your laptop.

Best,

A.

and it was very useful as it finally seemed to install the Nvidia Driver properly on the Fujitsu Worksation Laptop with Nvidia Quadro FX770m Graphics.

I did also "nvidia-xconfig" and the install went fine, however the program then still complained of

14:27:58.934 [I]: CPU: Intel Core2 Duo T9900 [base frequency 2133 MHz, 2 threads]
14:27:58.935 [W]: Video: OpenCL subsystem isn't available, try to reinstall video drivers

therefore i tried to add "OPENCL" with

sudo apt install nvidia-legacy-340xx-opencl-icd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libnvidia-cfg1 libnvidia-legacy-340xx-compiler libnvidia-legacy-340xx-cuda1
  nvidia-alternative nvidia-legacy-340xx-smi nvidia-legacy-check
  nvidia-opencl-common nvidia-persistenced ocl-icd-libopencl1
Suggested packages:
  nvidia-cuda-mps nvidia-opencl-icd | nvidia-legacy-390xx-opencl-icd
Recommended packages:
  libnvidia-legacy-340xx-cuda1-i386
The following NEW packages will be installed:
  libnvidia-cfg1 libnvidia-legacy-340xx-compiler libnvidia-legacy-340xx-cuda1
  nvidia-alternative nvidia-legacy-340xx-opencl-icd nvidia-legacy-340xx-smi
  nvidia-legacy-check nvidia-opencl-common nvidia-persistenced
  ocl-icd-libopencl1
0 upgraded, 10 newly installed, 0 to remove and 1 not upgraded.
Need to get 16.2 MB of archives.
After this operation, 55.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 nvidia-legacy-check amd64 390.138-1 [200 kB]
Get:2 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 nvidia-alternative amd64 390.138-1 [196 kB]
Get:3 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 libnvidia-cfg1 amd64 390.138-1 [257 kB]
Get:4 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 libnvidia-legacy-340xx-compiler amd64 340.108-3~deb9u1 [6,294 kB]
Get:5 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 libnvidia-legacy-340xx-cuda1 amd64 340.108-3~deb9u1 [4,421 kB]
Get:6 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 nvidia-opencl-common amd64 390.138-1 [194 kB]
Get:7 [url]http://deb.devuan.org//merged[/url] ascii/main amd64 ocl-icd-libopencl1 amd64 2.2.11-1 [36.8 kB]
Get:8 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 nvidia-legacy-340xx-opencl-icd amd64 340.108-3~deb9u1 [4,460 kB]
Get:9 [url]http://deb.devuan.org//merged[/url] ascii/non-free amd64 nvidia-legacy-340xx-smi amd64 340.108-3~deb9u1 [165 kB]
Get:10 [url]http://deb.devuan.org//merged[/url] ascii/contrib amd64 nvidia-persistenced amd64 390.87-1~deb9u1 [24.5 kB]
Fetched 16.2 MB in 2s (6,663 kB/s)              
Preconfiguring packages ...
Selecting previously unselected package nvidia-legacy-check.
(Reading database ... 135519 files and directories currently installed.)
Preparing to unpack .../nvidia-legacy-check_390.138-1_amd64.deb ...
*** The following unsupported devices are present in the machine:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GLM [Quadro FX 770M] [10de:065c] (rev a1)
Aborting nvidia driver installation.
dpkg: error processing archive /var/cache/apt/archives/nvidia-legacy-check_390.138-1_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/nvidia-legacy-check_390.138-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

however, now the system would say that the graphics chip is not supported?
it is calling legacy-check for nvidia-390 although there is nvidia-legacy-340xx installed?

But I would never purchase hardware from those NVIDIA bastards so I'm not speaking from personal experience and anyway the proprietary drivers are not part of the official release so users are pretty much on their own.

Those particular bastards recently announced that they will acquire ARM: https://www.theguardian.com/business/20 … -40bn-deal

Makes them harder to avoid.

But I would never purchase hardware from those NVIDIA bastards so I'm not speaking from personal experience and anyway the proprietary drivers are not part of the official release so users are pretty much on their own.

Maybe let sgfxi handle it?

I was just going to suggest that. That is the only tool I use when installing Nvidia. The thing handles everything at once.