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

[leenoox]

Same PSU, too? You can tell if they are using identical power with:

Code:

nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too

Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...

Removed all cards and restart rig with only 1 card direct connect to motherboard no risers,
Same low speed, 18-19 MH/s on eth

If everything is same and you swapped card from the "fast" rig and it perform worst on the "slow" rig it must be something wrong with the "slow" rig's motherboard or some bios settings are not exactly same. Are bios versions of the mobo's same?

On the "slow" rig reflash the bios, load bios default (or optimized) settings, save and reboot (F10), go into bios again and set everything same as on the "fast" mobo. Don't skip any options, open and check all settings are same. Take one GPU from the fast rig and try it. If it still underperform RMA the motherboard, I can't think of anything else.

[1714288819]

1714288819

[medi91]

Tried my best to search for an answer, but no luck so far...

has anyone successfully gotten rid of the login loop issue?

Ive console logged in, did a re-image, tried different versions, and every ubuntu based fix i could find online (clear and .Xauthority fixes)

Board is a HP z400 board

[mikespax]

Is anyone here mining lyra2rev (vertcoin, lbry, mona, etc) on 19 cards? I can't get any of the miners to boot, so I'm stuck with claymore or ewbf only. Would reallllly like to get some vertcoin going, but it just throws up cuda errors or instacrashes regardless of intensity or overclocks.

[leenoox]

Tried my best to search for an answer, but no luck so far...

has anyone successfully gotten rid of the login loop issue?

Ive console logged in, did a re-image, tried different versions, and every ubuntu based fix i could find online (clear and .Xauthority fixes)

Board is a HP z400 board

Try this:
press CTRL- ALT- F1 together, terminal window will open. Login as m1, pass miner1

type:

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Please reply with results

[fullzero]

Cautionary note:

I flashed and first-booted a rig with the v0019-1.3 build this evening, just before you posted v0019-1.4, and it pulled down the 2unix file from pastebin: UmaMW0Pc

This 2unix file checks for "0019-1.4" in 1bash, which it can't find, so flips into update mode, and then goes into a boot loop... all the command in update were commented out except:

Code:

sleep 15
sudo reboot

I don't know if this will be affecting others who might use the autoupdate with older builds, going forward, you might want to look at it, @fullzero.

(I fixed it by setting 2unix to look for "0019-1.3".)

I will have to change that paste to prevent boot loops.

[wi$em@n]

can i fire h110 btc+ 13 gpu mobo right up with nvoc

Or will I have to make changes in bios / to recognize 12x 1080 TI?

Works for me with 13 1050tis. After first boot only 11 worked. The bios reset (just removed battery) did the trick, that's all, didn't do any changes. The only bug: had to insert USB 3.0 Flash with nvOC into the USB 2.0 port, in USB 3.0 port motherboard doesn't see USB flash after reboot.

[codereddew12]

how hard would it be to incorporate a web interface that allows us to switch the coin being mined (e.g. similar to simplemining.net)? Just asking for pure speculative purposes as I know fullzero has done a phenomenal job with nvOC already! 

[lectar]

Hi guys,

I have problem with ccminer lyra2v2.
Asrock h110, x13 Gigabyte 1070
NVOC 0.19

Code:

*** ccminer 1.8.2 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0

  Originally based on Christian Buchner and Christian H. project
  Include some of the work of djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2017-10-31 09:31:01] Starting on stratum+tcp://mona.suprnova.cc:2995
[2017-10-31 09:31:02] NVML GPU monitoring enabled.
[2017-10-31 09:31:02] 13 miner threads started, using 'lyra2v2' algorithm.
[2017-10-31 09:31:02] Stratum difficulty set to 16
[2017-10-31 09:31:26] mona.suprnova.cc:2995 lyra2v2 block 1148602
[2017-10-31 09:31:37] mona.suprnova.cc:2995 lyra2v2 block 1148603
*** Error in `./SPccminer/ccminer': free(): invalid size: 0x00007f7791538980 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f77d65367e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f77d653f37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f77d654353c]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1fc88f)[0x7f77d0d8988f]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x10187b)[0x7f77d0c8e87b]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x25bb48)[0x7f77d0de8b48]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1f50c8)[0x7f77d0d820c8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f77d7c016ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f77d65c63dd]

Othe two rig with x3 Palit 1070 working well.

[Godm0de]

When I run dmesg, I got a lot of those lines:

Code:

[133920.746977] nvidia-modeset: Freed GPU:5 (GPU-12f9f4a9-0b6a-feef-b2d6-93e0ce5428cd) @ PCI:0000:09:00.0
[133920.901801] nvidia-modeset: Freed GPU:4 (GPU-15387c93-2a5d-b45c-77b0-cb88e629425e) @ PCI:0000:08:00.0
[133921.032925] nvidia-modeset: Freed GPU:3 (GPU-c6762bb7-6a0e-486b-6878-ecfc6eb1f7ef) @ PCI:0000:07:00.0
[133921.142072] nvidia-modeset: Freed GPU:2 (GPU-f256d3d8-c898-c915-3106-76e808cc362e) @ PCI:0000:06:00.0
[133921.236166] nvidia-modeset: Freed GPU:1 (GPU-a3452d3f-ed35-5125-c8af-481622d9adf9) @ PCI:0000:03:00.0
[133922.043551] nvidia-modeset: Freed GPU:0 (GPU-df08cdf1-b3ff-f312-4a54-74f401f5e4be) @ PCI:0000:01:00.0
[133973.039094] nvidia-modeset: Allocated GPU:0 (GPU-df08cdf1-b3ff-f312-4a54-74f401f5e4be) @ PCI:0000:01:00.0
[133973.694116] nvidia-modeset: Allocated GPU:1 (GPU-a3452d3f-ed35-5125-c8af-481622d9adf9) @ PCI:0000:03:00.0

Any idea what causes this issue? The rig doesn't mine.

Is there a way how I can detect a faulty GPU/Riser, without removing the GPUs one by one? I thought maybe the GPU utilization log could do it, but I don't know if the GPU numbering there is the same like the numbering of slots of my motherboard?

[papampi]

Same PSU, too? You can tell if they are using identical power with:

Code:

nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too

Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...

Removed all cards and restart rig with only 1 card direct connect to motherboard no risers,
Same low speed, 18-19 MH/s on eth

If everything is same and you swapped card from the "fast" rig and it perform worst on the "slow" rig it must be something wrong with the "slow" rig's motherboard or some bios settings are not exactly same. Are bios versions of the mobo's same?

On the "slow" rig reflash the bios, load bios default (or optimized) settings, save and reboot (F10), go into bios again and set everything same as on the "fast" mobo. Don't skip any options, open and check all settings are same. Take one GPU from the fast rig and try it. If it still underperform RMA the motherboard, I can't think of anything else.

Already done flash, erase, ... of bios ... no go.
I was suspected of mobo too, gonna send it back and see how it goes.

[ComputerGenie]

Already done flash, erase, ... of bios ... no go.
I was suspected of mobo too, gonna send it back and see how it goes.

That was my 1st thought. 'Twas my reason for asking about the drive, I wasn't quite following what you wrote.

[Havesovgosh]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

[Stubo]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

That version was and always will be a BETA. The latest stable version is 19 and the next planned is 20. The latest BETA is 19-1.4 and was released yesterday. I have been mining with it on all of my rigs for about 24 hours with no issues. At present, there is no upgrade path to it - you have to start with the full release (link on first page).

Hope this helps.

[sergixc]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

[Stubo]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

I think that means it is supported but there are known issues when going beyond a certain number of GPUs. I am running that mobo but with only 7 GPU ATM and everything is great. Take a look at previous posts like this one for more information:

https://bitcointalk.org/index.php?topic=1854250.msg23785755#msg23785755

Hope this helps.

[leenoox]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

Have you attached 3rd PSU?
One PSU = 7 GPU
Two PSU's = 13 GPU
Three PSU's = 19 GPU

Partial support means that not all GPU's can be overclocked, first 16 GPU can be overclocked, last 3 GPU will work on stock settings. See the post from two pages back regarding TB250

https://bitcointalk.org/index.php?topic=1854250.msg23785755#msg23785755

[zimmix]

Thank you very much for your kindly explanation, I'll give it a try!

[Havesovgosh]

Hey Everyone,

If you have more than 16 GPUs, the key is to have no more than 16 cards listed in the ServerLayout part of your xorg.conf. Those are the ones that will OC. You will have all 19 listed in the Device and Screen sections and the three that remain will run but won't OC. If you add a 17th under ServerLayout, the miner will not be able to OC any because X will crash when it starts when it hits the 17th card.

If you look at nvidia-smi output, you *should* see, at the bottom an instance of X AND a miner process for each GPU. The ones that only have a miner process attached cannot be OC'd. For me this is GPUs 17, 18, 19.

I've had to edit my rclocal.sh to copy a custom xorg.conf from ~ into /etc/X11 to keep it correct. The problem (for me) is that the script that auto creates the xorg.conf won't stop at 16 in the ServerLayout section and thus makes it so that X won't start and thus none of them OC.

Also, for my Gigabyte P106 cards (I'm running 19) for those first 16 (which will OC), I've not been able to get beyond 100 core and 250 mem, producing 18-18.1 MH/s for ETH only.

Let me know if this helps!
-z

```
# xorg.conf for 19 P106 on Asus ME that gets me 16 OC and 3 non-OC

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidiascreen-00"
    Screen 1 "nvidiascreen-01"
    Screen 2 "nvidiascreen-02"
    Screen 3 "nvidiascreen-03"
    Screen 4 "nvidiascreen-04"
    Screen 5 "nvidiascreen-05"
    Screen 6 "nvidiascreen-06"
    Screen 7 "nvidiascreen-07"
    Screen 8 "nvidiascreen-08"
    Screen 9 "nvidiascreen-09"
    Screen 10 "nvidiascreen-10"
    Screen 11 "nvidiascreen-11"
    Screen 12 "nvidiascreen-12"
    Screen 13 "nvidiascreen-13"
    Screen 14 "nvidiascreen-14"
    Screen 15 "nvidiascreen-15"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "None"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia-00"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-00"
    Device "nvidia-00"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-01"
    Driver "nvidia"
    BusID "PCI:2@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-01"
    Device "nvidia-01"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-02"
    Driver "nvidia"
    BusID "PCI:3@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-02"
    Device "nvidia-02"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-03"
    Driver "nvidia"
    BusID "PCI:6@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-03"
    Device "nvidia-03"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-04"
    Driver "nvidia"
    BusID "PCI:7@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-04"
    Device "nvidia-04"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-05"
    Driver "nvidia"
    BusID "PCI:8@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-05"
    Device "nvidia-05"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-06"
    Driver "nvidia"
    BusID "PCI:9@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-06"
    Device "nvidia-06"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-07"
    Driver "nvidia"
    BusID "PCI:10@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-07"
    Device "nvidia-07"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-08"
    Driver "nvidia"
    BusID "PCI:11@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-08"
    Device "nvidia-08"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-09"
    Driver "nvidia"
    BusID "PCI:12@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-09"
    Device "nvidia-09"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-10"
    Driver "nvidia"
    BusID "PCI:13@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-10"
    Device "nvidia-10"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-11"
    Driver "nvidia"
    BusID "PCI:14@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-11"
    Device "nvidia-11"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-12"
    Driver "nvidia"
    BusID "PCI:15@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-12"
    Device "nvidia-12"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-13"
    Driver "nvidia"
    BusID "PCI:16@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-13"
    Device "nvidia-13"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-14"
    Driver "nvidia"
    BusID "PCI:17@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-14"
    Device "nvidia-14"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-15"
    Driver "nvidia"
    BusID "PCI:18@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-15"
    Device "nvidia-15"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-16"
    Driver "nvidia"
    BusID "PCI:19@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-16"
    Device "nvidia-16"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-17"
    Driver "nvidia"
    BusID "PCI:20@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-17"
    Device "nvidia-17"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-18"
    Driver "nvidia"
    BusID "PCI:21@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-18"
    Device "nvidia-18"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

```

Hello,
what version is NVOC, 0019 or 0019 1.2

[Havesovgosh]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

That version was and always will be a BETA. The latest stable version is 19 and the next planned is 20. The latest BETA is 19-1.4 and was released yesterday. I have been mining with it on all of my rigs for about 24 hours with no issues. At present, there is no upgrade path to it - you have to start with the full release (link on first page).

Hope this helps.

Thanks.

[JayneL]

Still great mining OS for me thanks for all the effort guys.

Just want to know is it possible to have an individual Overclock if I'm using Nicehash or Mining pool hub autoswitch?

Thanks

God Bless

More Power