-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux build issues #7
Comments
@jonano614 |
well it only happened on ethos.
it’s not a huge issue but i think it the miner.
there are other small things with the miner, like sometimes the need to run seperate instances for each card etc.
however, there is obviously some issues with pools. our first pool would disconnect every 48hrs, so we have moved to another server. it has been two weeks now and we are just almost sync!
overall it just looks like minor bugs in all parts of the software.
…Sent from my iPhone
On 29 Mar 2018, at 07:17, Rui Xie ***@***.***> wrote:
@jonano614
Do you think it's an issue of pool or GPU miner?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@rgsnedds Thanks for reply. And if it's a miner issue, I will move it to GPU miner and close this one. |
Hi,
Yes our pool is in the whitelist.
We have spent the past two weeks ensuring that the pool is connecting. It connects OK and loads blocks from local storage, but when the local blocks are loaded, it begins again from zero and loads again.
It’s almost fully loaded now so hopefully we will be running soon
R
… On 29 Mar 2018, at 14:52, Rui Xie ***@***.***> wrote:
@rgsnedds <https://github.com/rgsnedds>
Thanks for reply.
Not sure if your IP of pool is added to white-list or not.
Please check current white-list.
And if it's a miner issue, I will move it to GPU miner and close this one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjIxcVT2nBDlrBbsMPJnM6TKEyCPTnHDks5tjOcsgaJpZM4STFCc>.
|
It's unrelated to linux build. Close. |
sgaragagghu
added a commit
that referenced
this issue
Jul 22, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GPU's show correct hash-rate in terminal, but pools only seeing a small percentage of hash-rate and rewards not paying correctly, tested on multiple pools over the course of many hours (8 hrs overnight)
The text was updated successfully, but these errors were encountered: