Author

Topic: having trouble mining with gridseeds (Read 283 times)

legendary
Activity: 1078
Merit: 1011
October 30, 2017, 04:02:37 PM
#5
I'd highly recommend Minera for your gridseeds.

Also, keep in mind the difficulty has skyrocketed since 2014, so you should set it appropriately on the pool side.

I would suspect this is the problem as well. Your little gridseeds are so old that even finding a default pool share might take quite a bit of time. As wavelengths said, if it is possible to adjust your difficulty on the pool you are using I would start with that.
member
Activity: 103
Merit: 10
October 30, 2017, 03:57:32 PM
#4
I'd highly recommend Minera for your gridseeds.

Also, keep in mind the difficulty has skyrocketed since 2014, so you should set it appropriately on the pool side.

+1 for Minera, it's the only way I got up and running w/ a Raspberry Pi
full member
Activity: 658
Merit: 118
October 22, 2017, 04:04:46 PM
#3
I'd highly recommend Minera for your gridseeds.

Also, keep in mind the difficulty has skyrocketed since 2014, so you should set it appropriately on the pool side.
member
Activity: 103
Merit: 10
October 22, 2017, 03:03:08 PM
#2
What program are you running on the pi? Have you already tried different software?
newbie
Activity: 15
Merit: 0
October 21, 2017, 01:15:24 AM
#1
I have 2 little mining towers i put together years ago, 10 gridseed orb miners. I mined pretty easily from 2014-15 but stopped..... I got the bug again and tried to point my miners to a pool, but i hit a road block. everything looks good on the end of my raspberry pi, but nothing is reaching the pool.

Is there something that has changed about using these miners? I'm running a freshly installed linux build released by highoncoins back in 2014, could that be the issue? It was always fairly reliable when i used to use it.

Any suggestions would be super appreciated, I got the bug and i can't figure this out. Was attempting to mine BCCS at cempool.com and am getting nothing through the dashboard, but my pi looks like it's working... I've tried it multiple times at different places with the same result.

Jump to: