 Show Posts
|
|
Pages: [1] 2 »
|
|
CryptoRekt - Yesterday at 11:54 PM
its because of OCminer that the entire fucking internet got on our ass
"herp derp lets make a public post"
Dumbass
|
|
|
|
I think I've figured out why my profitability switcher was having problems with some coins. I noticed it when I tried switching my rig from Genoil back to Claymore (I'm having trouble getting Genoil to run for more than 24 hours without crashing)...the script would run, and I'd end up with two or more instances of the Claymore miner running.
pgrep and pkill, when called with the -f option (to look at the whole command line), need to have "+" escaped for some reason...most likely the pattern is processed as a regular expression and not a simple string. Any miner command string that included "stratum+tcp" (that's basically all of them except the equihash and Genoil daggerhashimoto miners) thus wasn't searchable or killable.
I've committed a fix that should take care of that. It also prepends the search string with "^" to match on the miner process itself, not the screen process that spawned it. (Killing the miner will automatically kill the parent screen process.)
Please test and ensure with confidence; that it is rock solid: then I will integrate these changes. It would be helpful if you did so with the integrated oneBash + switch version I made (swap the relevant part of switch with your updated code); so I can be sure it works as intended. I will be glad to test, just not sure what needs to be changed  I uploaded the Newest oneBash and versions of additional files; including a new switch file that merges salfters changes with the implementation. I did a once over on the new switch / seemed good except for pascal which seemed to reinitialize everytime. Awesome let me try this out... |
|
|
|
I think I've figured out why my profitability switcher was having problems with some coins. I noticed it when I tried switching my rig from Genoil back to Claymore (I'm having trouble getting Genoil to run for more than 24 hours without crashing)...the script would run, and I'd end up with two or more instances of the Claymore miner running.
pgrep and pkill, when called with the -f option (to look at the whole command line), need to have "+" escaped for some reason...most likely the pattern is processed as a regular expression and not a simple string. Any miner command string that included "stratum+tcp" (that's basically all of them except the equihash and Genoil daggerhashimoto miners) thus wasn't searchable or killable.
I've committed a fix that should take care of that. It also prepends the search string with "^" to match on the miner process itself, not the screen process that spawned it. (Killing the miner will automatically kill the parent screen process.)
Please test and ensure with confidence; that it is rock solid: then I will integrate these changes. It would be helpful if you did so with the integrated oneBash + switch version I made (swap the relevant part of switch with your updated code); so I can be sure it works as intended. I will be glad to test, just not sure what needs to be changed |
|
|
|
I have had a lot of requests for this; so here is a new oneBash and modded switch file which implement full integration of SALFTER_NICEHASH_PROFIT_SWITCHING see the OP for links: Replace your current oneBash with the new one. extract switch and move it to the: directory (the one which opens when you click the Files icon on the left) configure the following in oneBash SALFTER_NICEHASH_PROFIT_SWITCHING="YES"
# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH
LOCALorREMOTE="LOCAL" # LOCAL or REMOTE
CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER
daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75
equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75
neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75
lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75
lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75
pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75 remember to thank salfter if you use this  Thanks for implementing this, but for some odd reason I keep getting two instances of the miner screen running which causes the system to crash, I will do some more testing to try and figure out what is going on. EDIT: Actually the kill code does not seem to work causing multiple miner screens, this is how the system is crashing. Are you using LOCAL or REMOTE? Please walk me through how you got multiple instances running so I can recreate this myself. I am using REMOTE. I am connecting via SSH attaching the screen with "screen -r miner" for testing purposes I am altering the algo speed manually in the switch file waiting 10 mins for it to change and I noticed it is hit and miss for the kill code to function correctly. I am also experiencing for LBRY and LYRA the mining process is executed twice. Maybe I should start from scratch... I tested the same way; changing the speed of one algo to force a switch. I also changed the timeout in oneBash to 10 seconds instead of 600. I tested this out and found salfters logic works well for switching between Ethash and Equihash; but not any of the other algos. It does seem to endlessly spawn new ccminer instances as well. I don't want to spend a lot of time on this; so I implemented killing all mining processes every time: then launching a new one. It should work without issue now. I also edited the oneBash logic to conditionally add salfters IPv6 fix, and reattach the screen to the guake terminal every reinit when in local mode. If you have added the cronjob: 0,10,20,30,40,50 * * * * (cd /media/m1/1263-A96E && python2.7 switch.py) I would remove it; as the oneBash implementation doesn't use it: and it may be (most likely is) causing additional launches of salfters original switch. Note: I uploaded a new oneBash and switch with these changes. They are linked on the OP. Thank you, I use use the new switch now Thanks for finding this problem; let me know if find any others. No problem I will let you know if I find anything else. Also do you believe killing the miner every 10 mins will impact performance/hash rates reporting to nicehash? Can this possibly mean less of a payout? |
|
|
|
I have had a lot of requests for this; so here is a new oneBash and modded switch file which implement full integration of SALFTER_NICEHASH_PROFIT_SWITCHING see the OP for links: Replace your current oneBash with the new one. extract switch and move it to the: directory (the one which opens when you click the Files icon on the left) configure the following in oneBash SALFTER_NICEHASH_PROFIT_SWITCHING="YES"
# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH
LOCALorREMOTE="LOCAL" # LOCAL or REMOTE
CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER
daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75
equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75
neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75
lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75
lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75
pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75 remember to thank salfter if you use this Thanks for implementing this, but for some odd reason I keep getting two instances of the miner screen running which causes the system to crash, I will do some more testing to try and figure out what is going on. EDIT: Actually the kill code does not seem to work causing multiple miner screens, this is how the system is crashing. Are you using LOCAL or REMOTE? Please walk me through how you got multiple instances running so I can recreate this myself. I am using REMOTE. I am connecting via SSH attaching the screen with "screen -r miner" for testing purposes I am altering the algo speed manually in the switch file waiting 10 mins for it to change and I noticed it is hit and miss for the kill code to function correctly. I am also experiencing for LBRY and LYRA the mining process is executed twice. Maybe I should start from scratch... I tested the same way; changing the speed of one algo to force a switch. I also changed the timeout in oneBash to 10 seconds instead of 600. I tested this out and found salfters logic works well for switching between Ethash and Equihash; but not any of the other algos. It does seem to endlessly spawn new ccminer instances as well. I don't want to spend a lot of time on this; so I implemented killing all mining processes every time: then launching a new one. It should work without issue now. I also edited the oneBash logic to conditionally add salfters IPv6 fix, and reattach the screen to the guake terminal every reinit when in local mode. If you have added the cronjob: 0,10,20,30,40,50 * * * * (cd /media/m1/1263-A96E && python2.7 switch.py) I would remove it; as the oneBash implementation doesn't use it: and it may be (most likely is) causing additional launches of salfters original switch. Note: I uploaded a new oneBash and switch with these changes. They are linked on the OP. Thank you, I use use the new switch now |
|
|
|
I have had a lot of requests for this; so here is a new oneBash and modded switch file which implement full integration of SALFTER_NICEHASH_PROFIT_SWITCHING see the OP for links: Replace your current oneBash with the new one. extract switch and move it to the: directory (the one which opens when you click the Files icon on the left) configure the following in oneBash SALFTER_NICEHASH_PROFIT_SWITCHING="YES"
# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH
LOCALorREMOTE="LOCAL" # LOCAL or REMOTE
CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER
daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75
equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75
neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75
lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75
lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75
pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75 remember to thank salfter if you use this Thanks for implementing this, but for some odd reason I keep getting two instances of the miner screen running which causes the system to crash, I will do some more testing to try and figure out what is going on. EDIT: Actually the kill code does not seem to work causing multiple miner screens, this is how the system is crashing. Are you using LOCAL or REMOTE? Please walk me through how you got multiple instances running so I can recreate this myself. I am using REMOTE. I am connecting via SSH attaching the screen with "screen -r miner" for testing purposes I am altering the algo speed manually in the switch file waiting 10 mins for it to change and I noticed it is hit and miss for the kill code to function correctly. I am also experiencing for LBRY and LYRA the mining process is executed twice. Maybe I should start from scratch... |
|
|
|
I have had a lot of requests for this; so here is a new oneBash and modded switch file which implement full integration of SALFTER_NICEHASH_PROFIT_SWITCHING see the OP for links: Replace your current oneBash with the new one. extract switch and move it to the: directory (the one which opens when you click the Files icon on the left) configure the following in oneBash SALFTER_NICEHASH_PROFIT_SWITCHING="YES"
# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH
LOCALorREMOTE="LOCAL" # LOCAL or REMOTE
CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER
daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75
equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75
neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75
lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75
lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75
pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75 remember to thank salfter if you use this Thanks for implementing this, but for some odd reason I keep getting two instances of the miner screen running which causes the system to crash, I will do some more testing to try and figure out what is going on. EDIT: Actually the kill code does not seem to work causing multiple miner screens, this is how the system is crashing. |
|
|
|
For some odd reason since you consolidated all the code to the switch.py, now the only miner that runs is equihash.
Mine's been running daggerhashimoto almost exclusively since the latest release. Looking at current-profit, we have: I am noticing if something other than equihash is more profitable in "current-profit" it does kill the equihash mining processes but fails to start anything else. I manually switched to equihash, let it get up and running, and then fired up the script. It killed the equihash miner and restarted the daggerhashimoto miner. You are aware that the miner runs in a screen session, right? When the script switches from one algo to another, the screen session associated with the first miner ends and a new one is started with the second miner. screen -dr miner will bring up the currently-running miner. I was able to resolve the issue by removing all the old mine_ALGO.sh files from the /media/m1/1263-A96E directory. I assumed these would not interfere with the new switch.py script. |
|
|
|
I will hold off on integrating this for now then (and wait for your changes); in the meantime I will make a link to your repo on the OP.
I've committed an update that, if it pans out, rolls everything into one Python script...no auxiliary shell scripts. I'm testing it right now to verify that it behaves the same as the previous version. I suspect I'll know in the morning.Edit: Just did some accelerated testing by manually switching to a less-profitable coin first...the script killed the miner and fired up the appropriate miner. I think the most recent update is ready for wider testing: https://gitlab.com/salfter/nvoc-nicehash-switcherFor some odd reason since you consolidated all the code to the switch.py, now the only miner that runs is equihash. Mine's been running daggerhashimoto almost exclusively since the latest release. Looking at current-profit, we have: neoscrypt: 0.00122266 BTC/day (3.14 USD/day)
lyra2rev2: 0.00044478 BTC/day (1.14 USD/day)
daggerhashimoto: 0.00221102 BTC/day (5.67 USD/day)
lbry: 0.00039243 BTC/day (1.01 USD/day)
equihash: 0.00163831 BTC/day (4.20 USD/day)
pascal: -0.00003248 BTC/day (-0.08 USD/day) I now have it logging the data (instead of overwriting it), and I have the current unpaid balances at NiceHash. I'll let it keep running and see what happens. I am noticing if something other than equihash is more profitable in "current-profit" it does kill the equihash mining processes but fails to start anything else. |
|
|
|
I will hold off on integrating this for now then (and wait for your changes); in the meantime I will make a link to your repo on the OP.
I've committed an update that, if it pans out, rolls everything into one Python script...no auxiliary shell scripts. I'm testing it right now to verify that it behaves the same as the previous version. I suspect I'll know in the morning.Edit: Just did some accelerated testing by manually switching to a less-profitable coin first...the script killed the miner and fired up the appropriate miner. I think the most recent update is ready for wider testing: https://gitlab.com/salfter/nvoc-nicehash-switcherFor some odd reason since you consolidated all the code to the switch.py, now the only miner that runs is equihash. |
|
|
|
Hi,
Trying out your OS, but first thing i'm encountering is when trying to change pools to european ones, the miner can't connect anymore (even with nanopool).
Second, when trying to use ethermine as a pool (with the switch turned to YES), it loops to read response failed end of file and cannot resolve hostname and read response failed end of file again, etc etc - no, it's not an internet or dns problem i assure, it works great.
Could you link a working onebash example with eu1.ethermine.org:4444 , so I can see what I did wrong?
are you using the Newest_oneBash linked on the OP? I think you might be having a problem related to the way workers were being named when their host address is less than 100. I fixed this in the Newest_oneBash. also ensure Let me know if this is the problem. Hi, I found the solution, i think it was because i tried to put a custom worker name - maybe you can include such a feature in the future? Also, I couldn't find how I can see the current mining process. I did see the screen -r commands, but that implies killing the current process and restarting it. I'd like to be able to see, from SSH, the current mining process without killing it. Is this possible? I believe you must kill the process first. When the mining process starts from boot up, you can SSH in and type ps aux | grep gnome-terminal (find the PID for gnome-terminal-server)
kill PID
export DISPLAY=:0
screen -dmS rig1 (rig1 can be named whatever you like)
screen -x rig1
bash '/media/m1/1263-A96E/oneBash'
|
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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: 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: 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 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 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: sudo cp /usr/share/nvidia-378/* /usr/share/nvidia/ and tell me if it outputs the messages: 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. 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: 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 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: then see if screen is working if screen is still not working go back to rig and enter: then see if screen is working I think we got it. I performed the following in SSH session from a Windows host via putty export DISPLAY=:0
screen -dmS rig1
bash '/media/m1/1263-A96E/oneBash'
Thank you for all the support fullzero, you rock! |
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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: 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: 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 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 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: sudo cp /usr/share/nvidia-378/* /usr/share/nvidia/ and tell me if it outputs the messages: 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. 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: 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 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.
|
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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: 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: 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 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 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: sudo cp /usr/share/nvidia-378/* /usr/share/nvidia/ and tell me if it outputs the messages: 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. 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
|
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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: 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: 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 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 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'.
|
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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: 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) |
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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: so that from a terminal I would enter: so for a rig with an ip of 192.168.1.22. I would use: 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: 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: you can close the ssh session whenever and then reSSH in and enter: 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'. |
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: 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 |
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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: and tell me what it outputs That does not output anything at all. |
|
|
|
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_FaeljjYQIf 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#msg19449945I 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: 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. |
|
|
|
|
