You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to test the miner, but it's getting me 0 Sol/s both on the CPU and GPU alike, and this is when I try to connect through the RPC port, as the default port 30303 gets me: connection reset by peer.
I'm on Ubuntu 17.10, any idea what's going wrong? Or is it like that because the official mining hasn't started yet?
I need to test it only for the Hash power of my rig, and the -b (benchmark mode) runs only for 25 seconds, which is not enough to real test the hardware, I believe.
Thanks for your input.
The text was updated successfully, but these errors were encountered:
Are you able to connect to the solo_pool? The miner requires the pool to be assigned work at the moment. By default the pool will listen to client connections on port 3333 and connect to the kernel on port 8545.
For now if you want to run a longer benchmark you are able to specify the number of trials. When you use the -b flag the default behaviour is to run 200 iterations, if you specify a number follow the -b flag you can increase the number of iterations.
I was trying to use the miner with Beta kernel at port 8545, since the 30303 is reset instantly, and what I'm trying now to do is to compile the pool myself, which is throwing a bunch of node errors. It goes fine until the point to cd into the pool dir and try to "npm install"
At that stage errors stop it from continuing. Not sure what are all the dependencies here, but had installed node-gyp, bindings, and bignum.
Just to re-iterate, when I try the miner with the beta kernel pool, it says connected! but doesn't show any hash, as it remains idling at 0 Sol/s, and if I shutdown the local pool, the miner disconnects too, which means it's working fine, but no jobs are assigned to it.
Hello,
I'm trying to test the miner, but it's getting me 0 Sol/s both on the CPU and GPU alike, and this is when I try to connect through the RPC port, as the default port 30303 gets me: connection reset by peer.
I'm on Ubuntu 17.10, any idea what's going wrong? Or is it like that because the official mining hasn't started yet?
I need to test it only for the Hash power of my rig, and the -b (benchmark mode) runs only for 25 seconds, which is not enough to real test the hardware, I believe.
Thanks for your input.
The text was updated successfully, but these errors were encountered: