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

[lbrasi]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

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

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

I tested from a linux VM I have and the same result

I tested this today and found there is a new problem resulting (most likely) from my adding support for up to 14 GPUs. 

I found that if I waited the screen would still connect to the mining process after failing to connect 3 or 4 times.

If you are using linux you can resolve this error by adding the following argument when SSHing into the rig:

Code:

-X

so that from a terminal I would enter:

Code:

ssh m1@rigipaddress -X

so for a rig with an ip of 192.168.1.22. I would use:

Code:

ssh m1@192.168.1.22 -X

If you are using putty with windows the -X will not work; but after showing the error 3 or 4  times the screen should still connect to the mining process


I also tested using the -dmS argument when calling screen.

if you call screen with:

Code:

screen -dmS rig1

screen with start as a background process (so you can disconnect your ssh session and the miner will continue to mine on its own)

after starting screen you will need to connect to the screen (as it is running in the background)

you do this by entering:

Code:

screen -r

you can close the ssh session whenever and then reSSH in and enter:

Code:

screen -r

to return to the mining process whenever desired.

Tested with -X on the SSH command from my linux VM and now I am getting the below;

ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUGraphicsClockOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUMemoryTransferRateOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUGraphicsClockOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUMemoryTransferRateOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment '[gpu:0]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:0' (No targets match target
       specification), specified in assignment '[fan:0]/GPUTargetFanSpeed=65'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment '[gpu:1]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:1' (No targets match target
       specification), specified in assignment '[fan:1]/GPUTargetFanSpeed=65'.

When you enter:

Code:

lspci | grep VGA 

what is the output?

01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)

try this

on the rig open a guake terminal and enter:

gksu gedit '/etc/X11/xorg.conf'

then select all and delete:

replace with this:

Code:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 1920 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection


Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:01:00:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:02:00:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

save

then logout

login

see if this solved the problem.

Not sure if this will work; but its worth a try

Replaced the xorg.conf with what you provided.

ssh without -X

Code:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

ssh with -X

Code:

ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUGraphicsClockOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUMemoryTransferRateOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUGraphicsClockOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUMemoryTransferRateOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment '[gpu:0]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:0' (No targets match target
       specification), specified in assignment '[fan:0]/GPUTargetFanSpeed=65'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment '[gpu:1]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:1' (No targets match target
       specification), specified in assignment '[fan:1]/GPUTargetFanSpeed=65'.

Maybe this:

open guake and enter:

Code:

sudo cp /usr/share/nvidia-378/* /usr/share/nvidia/

and tell me if it outputs the messages:

Code:

cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-key-documentation' and '/usr/share/nvidia/nvidia-application-profiles-378.13-key-documentation' are the same file
cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-rc' and '/usr/share/nvidia/nvidia-application-profiles-378.13-rc' are the same file

Correct output is as expected.

Code:

cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-key-documentation' and '/usr/share/nvidia/nvidia-application-profiles-378.13-key-documentation' are the same file
cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-rc' and '/usr/share/nvidia/nvidia-application-profiles-378.13-rc' are the same file

If after SSHing into the rig and killing the currently running mining Process you enter:

Code:

bash '/media/m1/1263-A96E/oneBash'

before opening screen:

Does it correctly start the mining process?

The mining process does start with the below errors before it starts

Code:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Hopefully this will work:

open guake and enter:

Code:

export DISPLAY=:0

then see if screen is working


if screen is still not working go back to rig and enter:

Code:

export DISPLAY=:1

then see if screen is working

I think we got it.
I performed the following in SSH session from a Windows host via putty

Code:

export DISPLAY=:0
screen -dmS rig1
bash '/media/m1/1263-A96E/oneBash'

Thank you for all the support fullzero, you rock!

[1714027268]

1714027268

[1714027268]

1714027268

[1714027268]

1714027268

[1714027268]

1714027268

[fullzero]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

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

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

I tested from a linux VM I have and the same result

I tested this today and found there is a new problem resulting (most likely) from my adding support for up to 14 GPUs. 

I found that if I waited the screen would still connect to the mining process after failing to connect 3 or 4 times.

If you are using linux you can resolve this error by adding the following argument when SSHing into the rig:

Code:

-X

so that from a terminal I would enter:

Code:

ssh m1@rigipaddress -X

so for a rig with an ip of 192.168.1.22. I would use:

Code:

ssh m1@192.168.1.22 -X

If you are using putty with windows the -X will not work; but after showing the error 3 or 4  times the screen should still connect to the mining process


I also tested using the -dmS argument when calling screen.

if you call screen with:

Code:

screen -dmS rig1

screen with start as a background process (so you can disconnect your ssh session and the miner will continue to mine on its own)

after starting screen you will need to connect to the screen (as it is running in the background)

you do this by entering:

Code:

screen -r

you can close the ssh session whenever and then reSSH in and enter:

Code:

screen -r

to return to the mining process whenever desired.

Tested with -X on the SSH command from my linux VM and now I am getting the below;

ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUGraphicsClockOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUMemoryTransferRateOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUGraphicsClockOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUMemoryTransferRateOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment '[gpu:0]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:0' (No targets match target
       specification), specified in assignment '[fan:0]/GPUTargetFanSpeed=65'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment '[gpu:1]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:1' (No targets match target
       specification), specified in assignment '[fan:1]/GPUTargetFanSpeed=65'.

When you enter:

Code:

lspci | grep VGA 

what is the output?

01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)

try this

on the rig open a guake terminal and enter:

gksu gedit '/etc/X11/xorg.conf'

then select all and delete:

replace with this:

Code:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 1920 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection


Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:01:00:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:02:00:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

save

then logout

login

see if this solved the problem.

Not sure if this will work; but its worth a try

Replaced the xorg.conf with what you provided.

ssh without -X

Code:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

ssh with -X

Code:

ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUGraphicsClockOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment
       '[gpu:0]/GPUMemoryTransferRateOffset[3]=0'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUGraphicsClockOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment
       '[gpu:1]/GPUMemoryTransferRateOffset[3]=50'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:0' (No targets match target
       specification), specified in assignment '[gpu:0]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:0' (No targets match target
       specification), specified in assignment '[fan:0]/GPUTargetFanSpeed=65'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'gpu:1' (No targets match target
       specification), specified in assignment '[gpu:1]/GPUFanControlState=1'.


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).



ERROR: Error resolving target specification 'fan:1' (No targets match target
       specification), specified in assignment '[fan:1]/GPUTargetFanSpeed=65'.

Maybe this:

open guake and enter:

Code:

sudo cp /usr/share/nvidia-378/* /usr/share/nvidia/

and tell me if it outputs the messages:

Code:

cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-key-documentation' and '/usr/share/nvidia/nvidia-application-profiles-378.13-key-documentation' are the same file
cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-rc' and '/usr/share/nvidia/nvidia-application-profiles-378.13-rc' are the same file

Correct output is as expected.

Code:

cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-key-documentation' and '/usr/share/nvidia/nvidia-application-profiles-378.13-key-documentation' are the same file
cp: '/usr/share/nvidia-378/nvidia-application-profiles-378.13-rc' and '/usr/share/nvidia/nvidia-application-profiles-378.13-rc' are the same file

If after SSHing into the rig and killing the currently running mining Process you enter:

Code:

bash '/media/m1/1263-A96E/oneBash'

before opening screen:

Does it correctly start the mining process?

The mining process does start with the below errors before it starts

Code:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

Hopefully this will work:

open guake and enter:

Code:

export DISPLAY=:0

then see if screen is working


if screen is still not working go back to rig and enter:

Code:

export DISPLAY=:1

then see if screen is working

I think we got it.
I performed the following in SSH session from a Windows host via putty

Code:

export DISPLAY=:0
screen -dmS rig1
bash '/media/m1/1263-A96E/oneBash'

Thank you for all the support fullzero, you rock!

Glad we found the problem. 

[tleilaxu_eyes]

Very neat OP, great work. How can users verify their download though? Do you have a checksum for the original file?

[7abazlam]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

[bentcrypto]

I can't seem to get v16 to work on tb-250.

It boots up then terminal pops up and says:

dos2unix: converting file /media/m1/1263-A96E/onebash to unix format

xorg problem detected

restarting xorg

rebooting in 5

Have tried different USB's and also booting with only one card but still have the same problem.

Anyone know what the problem might be?

[Maxximus007]

@fullzero, perhaps this can be of use to combat the issues with Mir, while wanting to re-run oneBash because of changes. Start the mining process with screen:

Code:

until screen -D -RR -S miner $HCD....
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done

After that you can remotely attach to the mining process with:

Code:

screen -x miner

Ending the current mining session, and rerun oneBash automatically (after attaching in multi screen mode as above):

Code:

Ctrl-A K

Since the screen is killed it will return in the until loop and restarts oneBash. It might have side effects, so more testing could be needed. The advantage is that there is already a screen, so you don't have to kill the mining session and restart it just to have a look at the output.

[VoskCoin]

What pools are people finding the best results on right now? I have been on the stock nanopool and going to try flypool next, eventually I'm thinking of running one worker on all ZEC pools I can find to compare 3 days of earnings . .

Also any pools with 0 fees? .5? and 1%?

I know nanopool is 1% as well as flypool

[VoskCoin]

I set individual power yes and set the limits on the correct GPU - the miner boots - code reads that it understands my command and populates it but then when the actual miner begins mining. . . the values are not set? How can I fix this?

Also how to fix - error target fan speed ?

[Maxximus007]

I set individual power yes and set the limits on the correct GPU - the miner boots - code reads that it understands my command and populates it but then when the actual miner begins mining. . . the values are not set? How can I fix this?

Also how to fix - error target fan speed ?

Hi, what version of nvOC are you using? What cards? What values are not set, the Powerlimits, or the OC values?

[Maxximus007]

What pools are people finding the best results on right now? I have been on the stock nanopool and going to try flypool next, eventually I'm thinking of running one worker on all ZEC pools I can find to compare 3 days of earnings . .

Also any pools with 0 fees? .5? and 1%?

I know nanopool is 1% as well as flypool

There are so many pools, but only a few big ones. I'm currently using flypool but for no particular reason TBH. Zecmine.pro has 0% fees, but since there are only 20 miners it can take quite some time to find a block and get payed. They have other pools that are nice. So, please share your findings.

[VoskCoin]

Another issue has occured . . lol . .

I adjusted some settings in my other rig (not having any of the above issues) and now it is asking for password upon loading -- did ubuntu update itself ? do I need to reload the USB now? -- if so . . can I simply perform the same procedure over the drive or is this drive scrapped and I need another

homescreen shows 16.04 LTS

[VoskCoin]

I set individual power yes and set the limits on the correct GPU - the miner boots - code reads that it understands my command and populates it but then when the actual miner begins mining. . . the values are not set? How can I fix this?

Also how to fix - error target fan speed ?

Hi, what version of nvOC are you using? What cards? What values are not set, the Powerlimits, or the OC values?

latest version v00015

2x 1080 TI 1x 1080 Mini

I have not adjusted any OC values currently just adjusting power settings

[fullzero]

Very neat OP, great work. How can users verify their download though? Do you have a checksum for the original file?

the SHA256 hash is:

Code:

7193de203cdbc31f213fc7d9aa01ae41b0115be85021e46e48387e0d65c4bb40

If you are using windows:

open a cmd prompt:

click the start button and type: 

Code:

cmd

then press enter:

type the following:

Code:

CertUtil -hashfile PATH_TO_IMAGE_ZIP_HERE SHA256

and press enter

if the result is:

Code:

7193de203cdbc31f213fc7d9aa01ae41b0115be85021e46e48387e0d65c4bb40

then the ZIP_containing_the_image is good

Note: you can find the file path by right clicking the zip and selecting properties


If you are using linux:

open a terminal and enter the following:

Code:

sha256sum 'PATH_TO_IMAGE_ZIP_HERE'

and press enter

if the result is:

Code:

7193de203cdbc31f213fc7d9aa01ae41b0115be85021e46e48387e0d65c4bb40

then the ZIP_containing_the_image is good

Note: you can also type sha256sum then drag the zip to the terminal window to add the absolute path without typing it.


If you are using OSX:

open a terminal and enter the following:

Code:

shasum -a 256 'PATH_TO_IMAGE_ZIP_HERE'

and press enter

if the result is:

Code:

7193de203cdbc31f213fc7d9aa01ae41b0115be85021e46e48387e0d65c4bb40

then the ZIP_containing_the_image is good

[fullzero]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

I am not sure; but I believe you would need to mount and then copy each partition separately if using dd; in order for the resulting usb to work as intended. 

It is a lot easier to download https://etcher.io/ for linux and then use it to image a USB or SSD.

I have done this and can verify it works.

[VoskCoin]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

I am not sure; but I believe you would need to mount and then copy each partition separately if using dd; in order for the resulting usb to work as intended. 

It is a lot easier to download https://etcher.io/ for linux and then use it to image a USB or SSD.

I have done this and can verify it works.

Is it possible to update from 15 to 16 or will I need to burn the USB's again?

[fullzero]

I can't seem to get v16 to work on tb-250.

It boots up then terminal pops up and says:

dos2unix: converting file /media/m1/1263-A96E/onebash to unix format

xorg problem detected

restarting xorg

rebooting in 5

Have tried different USB's and also booting with only one card but still have the same problem.

Anyone know what the problem might be?

Have you waited for the second boot?

If you are using one GPU it is expected that oneBash will need to rebuild the xorg file and reboot before OC will work as intended.

It should work without rebooting on the second boot; unless you have connected the monitor directly to the motherboard (always connect a monitor to the primary GPU).

I have had one member report that their rig is caught in an infinite loop of reboots; so I would like to know if this is happening to you as well.

[fullzero]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

I am not sure; but I believe you would need to mount and then copy each partition separately if using dd; in order for the resulting usb to work as intended. 

It is a lot easier to download https://etcher.io/ for linux and then use it to image a USB or SSD.

I have done this and can verify it works.

Is it possible to update from 15 to 16 or will I need to burn the USB's again?

I am making an update implementation; but for now you will have to reimage the USB.  Also I saw your PM, just haven't gotten to it yet.

are the problems you are having with v0015 or v0016?

If they are with v0015; they may be fixed by v0016: so it is probably be worth trying as a potential easy solution.

[VoskCoin]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

I am not sure; but I believe you would need to mount and then copy each partition separately if using dd; in order for the resulting usb to work as intended. 

It is a lot easier to download https://etcher.io/ for linux and then use it to image a USB or SSD.

I have done this and can verify it works.

Is it possible to update from 15 to 16 or will I need to burn the USB's again?

I am making an update implementation; but for now you will have to reimage the USB.  Also I saw your PM, just haven't gotten to it yet.

are the problems you are having with v0015 or v0016?

If they are with v0015; they may be fixed by v0016: so it is probably be worth trying as a potential easy solution.

I understand no worries I imagine you're swamped xD

they are all v15  . . I just now realized v16 is out. I seem to have fixed the issue for now by unplugging, adjusting settings, one rig has power limit and individual power limit on, and individual power limit is registering, the other is just individual power and it's registering after a couple restarts and cards being unplugged / replugged

Is it possible for me to edit the master file, so that when I burn a USB it will automatically have say the pool I want, my wallet, power settings etc? If so how can I do this?

[fullzero]

@fullzero, perhaps this can be of use to combat the issues with Mir, while wanting to re-run oneBash because of changes. Start the mining process with screen:

Code:

until screen -D -RR -S miner $HCD....
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done

After that you can remotely attach to the mining process with:

Code:

screen -x miner

Ending the current mining session, and rerun oneBash automatically (after attaching in multi screen mode as above):

Code:

Ctrl-A K

Since the screen is killed it will return in the until loop and restarts oneBash. It might have side effects, so more testing could be needed. The advantage is that there is already a screen, so you don't have to kill the mining session and restart it just to have a look at the output.

I think adding a step of entering:

Code:

export DISPLAY=:0

before calling screen will resolve the mir problem; but I haven't verified this myself yet.

I do think it is a good idea to start the mining process with screen.

I had already identified automating killing the existing mining process as an area for improvement; this might be a good solution.  In general I want to do a lot more testing before releasing in the future. 

[fullzero]

Has anyone managed to burn img to a USB drive and copy oneBash into it under Linux?

I clone nvOC_v0016.img to USD as follows:

Code:

sudo dd if=nvOC_v0016.img of=/dev/sdd1 bs=1M

What happens later is that I cannot mount the usb in order to copy oneBash file to it. This is not unusual though. Burning ubuntu image into a usd results in the same unmountable drive, but it still boots fine.

Thanks

I am not sure; but I believe you would need to mount and then copy each partition separately if using dd; in order for the resulting usb to work as intended. 

It is a lot easier to download https://etcher.io/ for linux and then use it to image a USB or SSD.

I have done this and can verify it works.

Is it possible to update from 15 to 16 or will I need to burn the USB's again?

I am making an update implementation; but for now you will have to reimage the USB.  Also I saw your PM, just haven't gotten to it yet.

are the problems you are having with v0015 or v0016?

If they are with v0015; they may be fixed by v0016: so it is probably be worth trying as a potential easy solution.

I understand no worries I imagine you're swamped xD

they are all v15  . . I just now realized v16 is out. I seem to have fixed the issue for now by unplugging, adjusting settings, one rig has power limit and individual power limit on, and individual power limit is registering, the other is just individual power and it's registering after a couple restarts and cards being unplugged / replugged

Is it possible for me to edit the master file, so that when I burn a USB it will automatically have say the pool I want, my wallet, power settings etc? If so how can I do this?

The easiest way to do this is to image a usb normally, edit the oneBash to be the way you want; verify it is working as you want: then attach it to a windows computer and use hddrawcopy to make an image of the usb (rather than imaging to the usb).

You can then image subsequent USB keys with your modified image (I would recommend changing worker names in oneBash).