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

Quote from: fullzero on July 04, 2017, 06:18:49 AM

Quote from: gigi8114 on July 03, 2017, 11:23:45 PM

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

Code:

ETHERMINEdotORG="YES"

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

Code:

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'