Quote from: UberDaemon on July 05, 2017, 01:23:05 AM

Quote from: gigi8114 on July 04, 2017, 09:22:07 AM

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?

If you want to monitor the mining process via screen you're going to have to kill the initial gnome-terminal. There's no way around that, as screen can only reconnect to an existing screen session.

This shouldn't be a big deal if you have a stable rig. You only need to do it once per reboot. My process is:

1. From my desktop where I monitor my rigs I initiate a constant ping:

Code:

ping -t 10.20.30.40 # substitute your rig's IP, find it in your router, or by running nmap on your LAN subnet, or by running ifconfig from a guake terminal on the rig if you have a monitor connected

2. Boot the rig
3. Wait until I begin to get ping responses from the rig, thus indicating Ubuntu has booted and rig has network connectivity
4. SSH into the rig (user: m1 password: miner1)
5. Initiate a screen session:

Code:

screen -s [name for your rig, make one up or call it "rig"]

6. Start nvidia-smi dmon to watch for mining process to begin (by waiting until this happens you know OC settings, fan speed settings, etc have been applied. Running those commands from within screen isn't 100% consistent IME as I always see error messages when I tried it that way. It's best to let those settings commands run from gnome-terminal as Ubuntu first boots IMO).

Code:

nvidia-smi dmon

7. Wait until you see wattage go up and GPU utilization go up to 100% (which indicates that the oneBash script concluded and opened the mining process). Exit nvidia-smi with CTRL + c
8. Find the PID for gnome-terminal.

Code:

ps aux | grep gnome-terminal

9. Kill it:

Code:

kill [PID from step 8]

10. Restart mining:

Code:

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

It might seem like a lot of steps, but it takes all of 120 seconds and you shouldn't need to do it very often once your rig is dialed in. You're losing maybe 1 minute's worth of hashes on avg of every week? Pretty negligible considering the convenience of monitoring from another workstation, and you're not using up system resources by using Teamviewer. This also lets you go completely headless if you buy a dummy HDMI plug. I just updated from 16 to 17 and didn't need to haul my extra monitor upstairs to do it. Easy peasy.

run export DISPLAY=:0 before step 5, if not, setp 10 throws erroe.