[OS] nvOC easy-to-use Linux Nvidia Mining

[bdog1234]

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

[1714478225]

1714478225

[1714478225]

1714478225

[1714478225]

1714478225

[1714478225]

1714478225

[sikke1]

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

The pastebin.com script is already doing this. I have setup unique url for each miner and then edit in browser. Miner updates itself automatic. Or you can force reboot with ssh.

[ha5hi5h]

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

[papampi]

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

[papampi]

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

The pastebin.com script is already doing this. I have setup unique url for each miner and then edit in browser. Miner updates itself automatic. Or you can force reboot with ssh.

If you set ssh=yes
you can use sftp.

[ha5hi5h]

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

I have. Not USB issue. Tried 3 different ones including two fresh new ones. All 3 works with v19 without issues. Wondering if anyone else is having the same issue.

[papampi]

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

I have. Not USB issue. Tried 3 different ones including two fresh new ones. All 3 works with v19 without issues. Wondering if anyone else is having the same issue.

May be the downloaded image has problem, download and flash again.

[FFI2013]

First let me say I think NVOC is awesome I've been running amd rx cards and win 10 pro on my rigs but after setting up this nvidia trial rig I'm hooked I just got two 1070's and a 1060 to see what cards I want to go with both my 1060 and 1070 are msi gaming cards and my other 1070 is a pny what would be the best over clocking setting for these I was thinking of using algo specific oc settings but would there be a problem with running the same clocks for 1060 and 1070 also in 1bash there's two different sets of algo specific oc's what is the difference one is halfway down and the other is at the bottom

My motherboard is asus M5A97 R2.0 with amd sempron 145 cpu don't know if you want to add it to supported hardware

[meligo]

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

hey , I have an Asrock H110 as well and with me it's working perfectly, have you tried with one 1 gpu in the slot closest to the CPU?

[snhelix]

Hello everyone, and thank the authors of this mining os.
I'm new to using the system, but I've started everything right.Everything works nicely for 1-2 hours and then terminates the miners' work and I get this down report.

Please if anyone has a suggestion for repair.After restart all repeats in the circuit.

srry for my bad english


nvOC_v0019-1.4
sudo: unable to resolve host 19_1_4


rig IP: 192.168.5.13


rig MAC: bc:5f:f4:0a:22:90 


01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)


Sat Nov 25 17:58:01 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.12                 Driver Version: 387.12                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
| 24%   34C    P0    28W / 120W |    175MiB /  6071MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
| 24%   28C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:07:00.0 Off |                  N/A |
| 24%   29C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:08:00.0 Off |                  N/A |
| 38%   30C    P8     5W / 120W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1065      G   /usr/lib/xorg/Xorg                           133MiB |
|    0      1823      G   compiz                                        39MiB |
|    1      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    2      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    3      1065      G   /usr/lib/xorg/Xorg                             6MiB |
+-----------------------------------------------------------------------------+

sudo: unable to resolve host 19_1_4
Power limit for GPU 00000000:01:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:07:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:08:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
sudo: unable to resolve host 19_1_4

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

** (guake:2099): WARNING **: Binding 'F12' failed!
-h
--help

[Stubo]

Hello everyone, and thank the authors of this mining os.
I'm new to using the system, but I've started everything right.Everything works nicely for 1-2 hours and then terminates the miners' work and I get this down report.

Please if anyone has a suggestion for repair.After restart all repeats in the circuit.

srry for my bad english


nvOC_v0019-1.4
sudo: unable to resolve host 19_1_4


rig IP: 192.168.5.13


rig MAC: bc:5f:f4:0a:22:90 


01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)


Sat Nov 25 17:58:01 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.12                 Driver Version: 387.12                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
| 24%   34C    P0    28W / 120W |    175MiB /  6071MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
| 24%   28C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:07:00.0 Off |                  N/A |
| 24%   29C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:08:00.0 Off |                  N/A |
| 38%   30C    P8     5W / 120W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1065      G   /usr/lib/xorg/Xorg                           133MiB |
|    0      1823      G   compiz                                        39MiB |
|    1      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    2      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    3      1065      G   /usr/lib/xorg/Xorg                             6MiB |
+-----------------------------------------------------------------------------+

sudo: unable to resolve host 19_1_4
Power limit for GPU 00000000:01:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:07:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:08:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
sudo: unable to resolve host 19_1_4

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

** (guake:2099): WARNING **: Binding 'F12' failed!
-h
--help

You can clean up the "unable to resolve host 19_1_4" errors by editing /etc/hostname and changing "19_1_4" to "m1-desktop", then reboot. I am not familiar with error "libglade-WARNING **: unknown attribute `swapped' for <signal>.". Please look in file /home/m1/screenlog.0 for miner errors at about the time it failed for additional clues on what is happening.

Hope this helps.

[snhelix]

Okay, thank you for the answer, I'll try and inform....

[papampi]

Okay, thank you for the answer, I'll try and inform....

libglade-warning is guake error and has been solved with latest updates, weird its shows again
Does the error appear when guake terminal is open (f12) or it appears with it close too ?

May be try to do a package update upgrade
In an ssh session or terminal with ctrl+alt+f1 run :

Code:

pkill -f gnome-terminal
pkill -f DOG
pkill -f TEMP
pkill -e screen
sudo apt update && sudo apt upgrade

Then reboot the rig and see how it goes.
Be careful, nvidia just posted a new update, make sure miner and wdog are not running before start update/upgrade

[6x1070ethsia]

Hi all.

 Totally new here,

I am currently running nvOC 0019 with 6x1070s mining eth / sia on an gigabyte H110-D3A

Everything works fine except my over clock settings appear to have no affect on hash rates, and I am pretty sure they are not even being applied.

Any ideas?

[papampi]

Hi all.

 Totally new here,

I am currently running nvOC 0019 with 6x1070s mining eth / sia on an gigabyte H110-D3A

Everything works fine except my over clock settings appear to have no affect on hash rates, and I am pretty sure they are not even being applied.

Any ideas?

I remember there was a bug in earlier versions
set the clocks and the power you want in the individual clock and power settings at the bottom of 1bash, I think it reads from the first one "gpu0"

[6x1070ethsia]

[/quote]
I remember there was a bug in earlier versions
set the clocks and the power you want in the individual clock and power settings at the bottom of 1bash, I think it reads from the first one "gpu0"
[/quote]

I would enable "YES" for individual clock settings right?

[jsenden]

Does this OS only work with these motherboards?

partially supported motherboard links:
ASUS B250 MINING EXPERT (13x gpu) Link

fully supported motherboard links:
ASRock H110 PRO BTC+ (13x gpu) Link
BIOSTAR TB250-BTC PRO (12x gpu) Link
ASRock H81 PRO BTC (6x gpu) Link
BIOSTAR TB85 (6x gpu) Link
MSI Z270-A PRO (6x gpu: 7x if you use 1x m2 adapter) Link
GIGABYTE GA-B250M-Gaming 3 (4x gpu) Link
BIOSTAR TB250-BTC (6x gpu) Link
ASUS Z270-F GAMING (7x gpu: 9x if you use 2x m2 adapters)  Link
MSI Z170A GAMING M5 (7x gpu) Link
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
GIGABYTE GA-Z270P-D3 (6x gpu) Link
ASUS PRIME H270-PLUS (6x gpu: 8x if you use 2x m2 adapters) Link

Or will it also work for my mainboard (Gigabyte h110-d3a) ??

[Stubo]

Does this OS only work with these motherboards?

partially supported motherboard links:
ASUS B250 MINING EXPERT (13x gpu) Link

fully supported motherboard links:
ASRock H110 PRO BTC+ (13x gpu) Link
BIOSTAR TB250-BTC PRO (12x gpu) Link
ASRock H81 PRO BTC (6x gpu) Link
BIOSTAR TB85 (6x gpu) Link
MSI Z270-A PRO (6x gpu: 7x if you use 1x m2 adapter) Link
GIGABYTE GA-B250M-Gaming 3 (4x gpu) Link
BIOSTAR TB250-BTC (6x gpu) Link
ASUS Z270-F GAMING (7x gpu: 9x if you use 2x m2 adapters)  Link
MSI Z170A GAMING M5 (7x gpu) Link
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
GIGABYTE GA-Z270P-D3 (6x gpu) Link
ASUS PRIME H270-PLUS (6x gpu: 8x if you use 2x m2 adapters) Link

Or will it also work for my mainboard (Gigabyte h110-d3a) ??

I believe those are just ones that folks have confirmed that it works on. I am reasonably certain that nvOC will work as long as the underlying Ubuntu installation works on your hardware. For example, I have 2 rigs that run an X99 based board that is not even on that list at all. Give it a go and if you have issues, post them here and we will try to resolve them with you.

[jsenden]

Does this OS only work with these motherboards?

partially supported motherboard links:
ASUS B250 MINING EXPERT (13x gpu) Link

fully supported motherboard links:
ASRock H110 PRO BTC+ (13x gpu) Link
BIOSTAR TB250-BTC PRO (12x gpu) Link
ASRock H81 PRO BTC (6x gpu) Link
BIOSTAR TB85 (6x gpu) Link
MSI Z270-A PRO (6x gpu: 7x if you use 1x m2 adapter) Link
GIGABYTE GA-B250M-Gaming 3 (4x gpu) Link
BIOSTAR TB250-BTC (6x gpu) Link
ASUS Z270-F GAMING (7x gpu: 9x if you use 2x m2 adapters)  Link
MSI Z170A GAMING M5 (7x gpu) Link
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
GIGABYTE GA-Z270P-D3 (6x gpu) Link
ASUS PRIME H270-PLUS (6x gpu: 8x if you use 2x m2 adapters) Link

Or will it also work for my mainboard (Gigabyte h110-d3a) ??

I believe those are just ones that folks have confirmed that it works on. I am reasonably certain that nvOC will work as long as the underlying Ubuntu installation works on your hardware. For example, I have 2 rigs that run an X99 based board that is not even on that list at all. Give it a go and if you have issues, post them here and we will try to resolve them with you.

Thank u for your reply, the reason I want to try it, is because now im using simplemining OS, and im experiencing issues with Ethereum mining, every equihash is fine. On windows I get 22-23mh/s with my Gigabyte P106-100 cards, but for some reason on Simplemining OS I cant get higher than 19.3Mh/S whatever setting I use, so thats why im looking for alternative OS's

[papampi]

I remember there was a bug in earlier versions
set the clocks and the power you want in the individual clock and power settings at the bottom of 1bash, I think it reads from the first one "gpu0"

I would enable "YES" for individual clock settings right?

You have an old version, sorry I don't remember
Try out and see how it goes