this will generate one that enables most features
My guess is your problem is related to the P106_100s and normal GPUs working best with different coolbits settings. Hard to know without one of those to test with.
hey just wondering if anyone can help? A puzzle for someone....
I have 12 x1080's and have always had an issue wth the auto temp/fan speed for the 12th (GPU 11). Anyways, since I updated to the NVOC in dec to nvOC-19-2-update (by_fullzero_unofficial), it has mined anything no issues. and the only thing was as I mentioned..
Suddenly the end of December it constantly crashes on Equihash on both ZM and EWBF. The error was always that GPU 11 was lost. Anyhow, after some digging I found that in the Nvidia X Server Settings for GPU 11 the box was not there to tick for the fan speed.
After some more digging I found that in the etc/X11/xorg.conf file, the GPU 11 was not set correctly. It is in pci slot 18, and in the Section "Device" it only went up to PCI-17.
I did as in the quote sudo nvidia-xconfig --enable-all-gpus --cool-bits=31 and that didnt work either (so had to restore original), but it did give me all the correct pci locations of the GPU devices, so I have updated the xorg.conf with the relevant pci settings.
Now the auto temp/fan speed errors have gone and the tick box appears in Nvidia X Server Settings for GPU 11 .
But, it still crashes on Equihash, it says
"Unable to determine the device handel for GPU 0000:1200.0 GPU is lost."
I updated NVOC on the 4th JAN to the nvOC v0019-2.0 - community release. Any suggestions anyone?
Also, why does my etc/X11/xorg.conf file say Im using 1050's when I am using 1080's? Does it even matter?
I do not know if you have updated from version 0019-1.4 to version 19-2.0 with papampi scripts.
If so, is it possible for you to try to use the latest papampi image from the links we just posted and apply the latest updates from papampi.
Of course, you will not forget to save your current system with HDDrawCopy or diskdump (dd) for example, in another medium.
I had problems with version 19-1.4 too. not of this type, but I have a month since I installed the 19-2.0 and repared the disk by adding swap. I know it has nothing to do with the problem you are describing
I am using https://github.com/papampi/nvOC_by_fullzero_Community_Release
I would do the reimaging, but my linux command knowlege is limited, and I a bit unsure as to how to go about that, if anyone could take me though that great ly appreciate it :-)
so.....
I gave it another crack with the