Not wanting to get banned or put on that Stop-Forum-Spam list (yes, it happened once) I started a new thread on cooling GPUS

Reference Keith Myers post (thanks Keith!)
http://www.gpugrid.org/forum_thread.php?id=4955&nowrap=true#52269

With the following GPU:

From what I have tried, nvidia-settings will only work if a monitor is physically attached, or a monitor dummy plug is fitted.
If there are other ways would love to find out!

To enable ssh server to start when booting the pc, use this command:
Debian based distros: sudo systemctl enable ssh
Redhat based distros: sudo systemctl enable sshd.service

Also, forgot to mention, the first command in your script

sudo nvidia-xconfig -a --cool-bits=4

only needs to be run once, so does not need to be in your script.

Also, forgot to mention, the first command in your script

sudo nvidia-xconfig -a --cool-bits=4

only needs to be run once, so does not need to be in your script.

From what I have tried, nvidia-settings will only work if a monitor is physically attached, or a monitor dummy plug is fitted.

OK, got it working at login

First tested the following script

You only have one fan interface on Pascal cards. So you don't need to increment a fan designator for successive cards. Simply enabling the fan for each card and setting its speed is enough. Probably should have used my Pascal only machine as an example

From what I have tried, nvidia-settings will only work if a monitor is physically attached, or a monitor dummy plug is fitted.
If there are other ways would love to find out!

To enable ssh server to start when booting the pc, use this command:
Debian based distros: sudo systemctl enable ssh
Redhat based distros: sudo systemctl enable sshd.service

I've started up Linux PCs many times and used the GUI to set OC and fan speeds without a monitor plugged in.

OK, got it working at login

I've started up Linux PCs many times and used the GUI to set OC and fan speeds without a monitor plugged in.

It would be nice to know how you do this, a couple of questions:
Are you controlling the Linux PC from another Linux PC? (Controlling the host from another Linux PC, I suspect would be easier to setup.)
Are you using X forwarding or enabling XDMCP server on the host?
Do you invoke Nvidia Settings GUI remotely or via a script to set the OC and fan speeds?

The underlying issue, as I understand, is how the Remote Display is setup in xorg.conf on the host. The X server needs to "think" it is outputting to a real display for nvidia-settings to work.

Any tips you could offer would be most appreciated.

Some older FAH guides at Overclock.net mention editing xorg to create a monitor

I've remotely controlled PCs with TeamViewer

"Before we disable Wayland, we need to switch to open source linux video driver instead of Nvidia third party driver"

You don't need to pay for a Teamviewer subscription if you are not a business. You can have as many computers as you want for free. I've used it for years.

You don't need to pay for a Teamviewer subscription if you are not a business. You can have as many computers as you want for free. I've used it for years.

As long as both computers (this means phones too) have an internet connection, the connection will be established.

You can also teamviewer to a computer without a monitor attached.

18.04 after reading about Wayland compatibility and
"Before we disable Wayland, we need to switch to open source linux video driver instead of Nvidia third party driver"
I take that to mean I lose CUDA and OpenCL with opensource drivers.

You don't need to pay for a Teamviewer subscription if you are not a business. You can have as many computers as you want for free. I've used it for years.

I had problems with TV as it fought I use it for commercial use. So I have switched to DWService - free to use and access is from any web browser. Win, Linux agents available.

Added PCIe splitter to get 7 GPU on a 6 slot mombo and lost control of fans on two GPUs.

If anyone has used splitters (4-in-1 etc) I would like to know if they got the coolbits working OK.

My xorg looks fine and monitor works fine but instead of buss IDs of 1..6, I am seeing 1..4 then 9 and "A" on nvidia-smi. nvidia-settings missing sliders for temp for fans "4" and "6".

Not going to post details here as I posted problem at AskUbuntu.
https://askubuntu.com/questions/1161242/coolbits-missing-fans-after-adding-pcie-splitter

All the boards work ok, just cant crunch gpugrid right now but seti works on all 7 just fine.

You don't need to pay for a Teamviewer subscription if you are not a business. You can have as many computers as you want for free. I've used it for years.

I wish I knew how to write a script that would shutdown at 1:00 and power on at 6:00.

re: my problem with only 5 out of 7 GPUs having fan control.

This was unexpectedly fixed when I swapped a pair of video boards. There must be some type of timing problem with nvidia-settings when a lot of GPUs are on a motherboard. I have an assortment, cheap from eBay & used, different vendors, pair of 1070 and five 1060 one of which is 6gb the others 3 and simply swapping the USB riser cable on the two 1070 boards was enough to enable the temperature slider on all 7 boards. One of the sliders I had to set to 100 the other 6 were already at 100. The 2 I swapped were different models. Should have made no difference but yet it did.

The posts from the high-gpu count Seti users that have multiple gpus in mining type motherboards usually comes down to fixing the problems with replacing the USB cables from the risers with higher quality shielded cables.

All sorts of problems ranging from gpus disappearing to gpus with limited control seem to be fixed with replacement of the USB cables.

Has anyone tried using nfancurve?

"A small and lightweight POSIX script for using a custom fan curve in Linux for those with an Nvidia GPU."

https://github.com/nan0s7/nfancurve

Another set of instructions for use.

https://www.techticity.com/howto/how-to-control-nvidia-graphics-card-fan-speed-in-linux/

looks promising. The "to do" list on the first link does mention support still to be added for headless applications. So limited in that respect. Still looking for a fully scripted solution for a headless environment.

I have checked that scirpt - it works good for 1 GPU 1080Ti (sorry don't have more to check).

I'd like to figure out how nvidia-settings uses the fan control interface identifier on the Turing cards to differentiate the two interfaces.

I have a fan control application with a nice GUI interface written in Python, that does not work on the Turing cards with the two interfaces. The first interface is enabled and can be controlled, but the second interface is missing. I've looked through the code and can't figure out what the variable name is for the fan interface. I thought it would be simple enough to increment the variable for each interface found, but nothing is obvious to me.

The best part of the application is that is has curves and not just static levels like the fan speed slider in Nvidia X Server Settings app.

I'd like to figure out how nvidia-settings uses the fan control interface identifier on the Turing cards to differentiate the two interfaces.

I'd like to figure out how nvidia-settings uses the fan control interface identifier on the Turing cards to differentiate the two interfaces.

Does the below link help? I dont have a Turing based card so cant test this.
https://linustechtips.com/main/topic/1048251-turing-rtx-linux-cli-fan-control/

FYI, here's how I set fan speed at login.

https://wiki.archlinux.org/index.php/NVIDIA/Tips_and_tricks#Set_fan_speed_at_login

FYI, here's how I set fan speed at login.

https://wiki.archlinux.org/index.php/NVIDIA/Tips_and_tricks#Set_fan_speed_at_login

I've been controlling heat on my cards by lowering the power limit in watts by using nvidia-smi. It's not an ideal solution but it works for me.

I'd like to figure out how nvidia-settings uses the fan control interface identifier on the Turing cards to differentiate the two interfaces.

Does the below link help? I dont have a Turing based card so cant test this.
https://linustechtips.com/main/topic/1048251-turing-rtx-linux-cli-fan-control/

I wish I knew how to write a script that would shutdown at 1:00 and power on at 6:00.

Shutdown: https://forums.linuxmint.com/viewtopic.php?t=22251
Power on: it can be configured in the BIOS. You should check your local time, and the BIOS clock, as Linux tends to set GMT (=UTC) in the BIOS, so the wake up time should be set according to this.

I wish I knew how to write a script that would shutdown at 1:00 and power on at 6:00.

Shutdown: https://forums.linuxmint.com/viewtopic.php?t=22251
Power on: it can be configured in the BIOS. You should check your local time, and the BIOS clock, as Linux tends to set GMT (=UTC) in the BIOS, so the wake up time should be set according to this.

Thanks. I installed Gshutdown but it seems only able to handle one time events. I need something that will shut down all computers at 1:00 either M-F if TOU electric rate is the issue or every day if heat is the issue. I've heard of cronjob scripts so maybe that's what I need to learn about.
I've seen the wake on timer line in the BIOS. I'll test drive that too.