Show Posts
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.
I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU. I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.
I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?
Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed. I attempt to launch the miner again and get the below error but the process does start;
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.
When the mining process starts do you see OC messages like this?
https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ
If you don't:
At any point did you boot with the monitor connected to the motherboard?
Did you at anytime boot with only one GPU attached?
If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )
then follow this process:
https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945
I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process. If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?
With v0015 you would have to enable openssh server before you could SSH in. You would also have to be able to know the rigs IP; which can be done in several ways.
With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.
I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig. However I am still getting the error via SSH when trying to start.
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.
What type of OS is the client computer; and what are the IPs of the client and rig?
Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6
So when you enter
m1@192.168.1.19
using port 22
with SSH selected
and click open it gives you the error above?
Sorry let me try and clear some things up. I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.
I also really appreciate your support and rapid response.
Are you killing the existing mining process before launching another via SSH?
Also; when you are launching the mining process via SSH are you using the cmd:
Code:
bash '/media/m1/1263-A96E/oneBash'
I am SSHing and executing the following commands.
ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'
Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.
after you have SSHed in enter the cmd:
Code:
echo $DISPLAY
and tell me what it outputs
That does not output anything at all.
It seems, im having the same troubles. So i will do the same here and post my results.
