My system does not process CUDA?

No, presently ALL your system CAN process is CUDA60 tasks if you get the app. You don't have any support for the alternative gpu applications SAH and SoG which need the OpenCL component of the Nvidia drivers. The Nvidia driver package can drop the OpenCL component occasionally. Then you have to install it separately. You need to figure out what Debian has that is the equivalent to the ocl-icd-libopencl1 package.

[Edit] Google finds this:
https://packages.debian.org/buster/ocl-icd-libopencl1

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I thought that Jord proved that <no_cuda>1</no_cuda> works over at Github. I see it referenced several times in conversation.

I'll read the code and do some testing later. I can update the documentation if that's the problem.

Edit - on a quick glance, it's used when you deselect NVidia cards on a project server, and passes a "don't request" flag in the sched_reply. So, NOT a client config option.

Having said that, cc_config does allow <no_opencl>, so I don't see why it shouldn't have <no_cuda> to match. I might try adding it later.

As far as I know that's only an option in the account_*.xml file as essentially it's what the projects preferences page does for the Use Nvidia GPU? setting. But I could be wrong, haven't looked in GitHub lately what I said there, hardly ever go there these days.

(I am the Jord referenced, aren't I? 😉
Trouble is, I don't know how I prove the setting to work, seeing how I run AMD GPUs... But alas!)

Edit: the GT 710 is a Kepler GPU, is that still supported by present drivers?

---

Edit: the GT 710 is a Kepler GPU, is that still supported by present drivers?

Yes. I have one machine where a 750 is paired with a 1660, and both are working with - obviously - the same driver. That's under Windows 7.

It was working until I did the update and added the second GPU.

Do you have a monitor or dummy plug attached to the second videocard? (Is that required under Linux?)

---

GTX 750 is Maxwell, not Kepler. But yes even a GT 710 is still covered by the latest Linux 440.44 driver.

No you don't need a dummy plug or monitor attached to a second card.

[Edit] You may run into issues with dual AMD and Nvidia cards in a host trying to run OpenCL under Windows because the OpenCL components are exclusive. Install one flavor and it uninstalls the other.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I have two video cards installed . I installed the driver directly from the Nvidia site; both cards take the same driver.
===

lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}

01:00.0 VGA compatible controller: NVIDIA Corporation TU107 (rev a1) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. TU107
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 4000 [size=128]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

04:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 710B] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710]
Flags: fast devsel, IRQ 16
[virtual] Memory at f3000000 (32-bit, non-prefetchable) [size=16M]
Memory at e8000000 (64-bit, prefetchable) [size=128M]
Memory at f0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 2000 [size=128]
[virtual] Expansion ROM at f4000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

I ran that command on my machine and received this;

lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: ZOTAC International (MCO) Ltd. GM107 [GeForce GTX 750 Ti]
	Flags: bus master, fast devsel, latency 0, IRQ 26
	Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
	Memory at b0000000 (64-bit, prefetchable) [size=256M]
	Memory at c0000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 3000 [size=128]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: nvidia
	Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

02:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti]
	Flags: bus master, fast devsel, latency 0, IRQ 27
	Memory at e2000000 (32-bit, non-prefetchable) [size=16M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Memory at e0000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 2000 [size=128]
	[virtual] Expansion ROM at e3080000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nvidia
	Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

So, it appears you are only using the nouveau driver on that machine.
I installed the driver the same on all my machines, following the instructions here; https://setiathome.berkeley.edu/forum_thread.php?id=84927&postid=2022017#2022017

I am not sure where to go on this. I installed the

 ocl-icd-libopencl1

with no apparent errors but still do not have it right. I have tried the three options above with the same results.

Any other suggestions?

HAPPY NEW YEAR!

---

Radjin~

Is there a particular reason you need to use Debian 10 instead of something else? I think you’ll have a much easier time with something more conventional like Ubuntu.

But if you’re insistent to stick with Debian, I would try re-installing the Nvidia drivers from the .run or .deb files like you did before.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Is there a particular reason you need to use Debian 10 instead of something else? I think you’ll have a much easier time with something more conventional like Ubuntu.

But if you’re insistent to stick with Debian, I would try re-installing the Nvidia drivers from the .run or .deb files like you did before.

If I had to do it over I would install a fresh Ubuntu as there seems to be a lot more support. But moving now would mean moving my webserver and it’s database to backup, then back on to the server once installed. At some point in the future I will probably do that. I have a friend that helps now and then and I may do the above if he has time in the near future. I am not experienced enough to go much further than installs and such using the standard apt. When it gets into compiling or changing configuration files I start getting over my head.

---

Radjin~

You have rebooted the machine to use the Nvidia drivers . . . . haven't you??

If you don't reboot the machine after installing the Nvidia drivers you never load the new recompiled kernel that contains the Nvidia drivers.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You have rebooted the machine to use the Nvidia drivers . . . . haven't you??

If you don't reboot the machine after installing the Nvidia drivers you never load the new recompiled kernel that contains the Nvidia drivers.

Yes, although overkill, I reboot after any install/upgrade.

---

Radjin~

You have rebooted the machine to use the Nvidia drivers . . . . haven't you??

If you don't reboot the machine after installing the Nvidia drivers you never load the new recompiled kernel that contains the Nvidia drivers.

Throws a look at Keith......hahaha

---

Looking at the Ubuntu options? Anyone use Encryption or LVM?

---

Radjin~

nope.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I tried it once (very early version) and didn't really find any advantage on the small & simple set of partitions I needed. In general such things don't really come into play unless you have large disc arrays with multiple (dynamic) partitions which are not the usual case for the home user. Beware that if one gets things wrong it is possible not just to destroy the partition you were working on, but the whole array, and there is very little chance of rescuing it.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Using the three different methods to install the drivers I get one of two responses.

With the standard repository install:

apt-get install nvidia-driver

once I reboot the system stalls and requires a hard reboot into recovery to purge/autoremove anything Nvidia. Once rebooted everything is back to normal.

Using https://linuxusers.net/debian/how_install_debian_10_buster_with_nvidia.php on step 5 using back ports, or installing via the latest Nvidia drivers from their site the install shows no errors however does not activate the drivers.

There must be a step I am missing. Is there a command I need to run after installing the drivers?

---

Radjin~

I tried it once (very early version) and didn't really find any advantage on the small & simple set of partitions I needed. In general such things don't really come into play unless you have large disc arrays with multiple (dynamic) partitions which are not the usual case for the home user. Beware that if one gets things wrong it is possible not just to destroy the partition you were working on, but the whole array, and there is very little chance of rescuing it.

Thanks for the replies on this. I have talked to two others and only one uses LVM.

---

Radjin~

If you are installing the drivers from the command line, you can watch the drivers being compiled into the kernel. There is nothing that needs to be done other than reboot the system to reload the new compiled kernel image with the drivers in it.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

If you are installing the drivers from the command line, you can watch the drivers being compiled into the kernel. There is nothing that needs to be done other than reboot the system to reload the new compiled kernel image with the drivers in it.

Yet the drivers will not run. There must be some missing dependency that keeps the drivers from activating. Is there a command to check the status of the drivers?

I ran the command after purging everything nvidia and I can see that only nouveau is shown where before it was: Kernel modules: nouveau, nvidia_drm, nvidia

lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
01:00.0 VGA compatible controller: NVIDIA Corporation TU107 (rev a1) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. TU107
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 4000 [size=128]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel modules: nouveau

04:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 710B] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710]
Flags: fast devsel, IRQ 11
Memory at f3000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at e8000000 (64-bit, prefetchable) [disabled] [size=128M]
Memory at f0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at 2000 [disabled] [size=128]
Expansion ROM at f4000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel modules: nouveau

---

Radjin~