just fyi diablo works just fine for me ...
mhash: 389,5/388,7 | accept: 528 | reject: 1 | hw error: 4
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 984. (Read 4382653 times)
August 11, 2011, 07:10:09 AM
August 10, 2011, 09:45:05 PM
I'm new to SLUSH. How do I withdraw immediate? Before I continue to mine at SLUSH, I need to know if
1) If I can withdraw immediate
2) if I can withdraw all 8 decimal places of btc.
I have set it at 1.0 btc for auto payout; but now I just set it at 0.01 btc. I have more confirmed btc than the 0.01 threshold but the payout was not initiated. HELP!
1) If I can withdraw immediate
2) if I can withdraw all 8 decimal places of btc.
I have set it at 1.0 btc for auto payout; but now I just set it at 0.01 btc. I have more confirmed btc than the 0.01 threshold but the payout was not initiated. HELP!
August 10, 2011, 05:22:56 PM
Using diablo linux, with -f 10 -v 2 -w 128
got two 6950 cards, with a combined hashrate of 666 Mh/s
had to switch to a different pool after mining for several minutes on your pool with a ratio of 82 accepts / 74 rejects
got two 6950 cards, with a combined hashrate of 666 Mh/s
had to switch to a different pool after mining for several minutes on your pool with a ratio of 82 accepts / 74 rejects
Oh well... Diablo isn't working properly for some technical reasons; Diablo changed some stuff in his miner few weeks ago and refused to "fix" it to be backward compatible. Please use another miner (I recommend phoenix or poclbm).
I'm using poclbm and I'm getting ridiculously high reject ratio as well. Is there a limit to how much work can be turned in per worker?
I'm showing at least 60% or so of my work that is being turned in rejected by the server. It wasn't this bad when I mined at slush while back, but I then I had it with separated to each gpu per worker for monitoring at the time. Now that I'm back and trying to setup slush again, it's giving me massive rejections because I am trying to turn in work to a single worker instead.
August 10, 2011, 10:54:09 AM
Using diablo linux, with -f 10 -v 2 -w 128
got two 6950 cards, with a combined hashrate of 666 Mh/s
had to switch to a different pool after mining for several minutes on your pool with a ratio of 82 accepts / 74 rejects
got two 6950 cards, with a combined hashrate of 666 Mh/s
had to switch to a different pool after mining for several minutes on your pool with a ratio of 82 accepts / 74 rejects
Oh well... Diablo isn't working properly for some technical reasons; Diablo changed some stuff in his miner few weeks ago and refused to "fix" it to be backward compatible. Please use another miner (I recommend phoenix or poclbm).
August 10, 2011, 05:50:46 AM
Why is the reject rate THAT hight? so far, I have 49 accepted and 39 rejected!
I don't have enough info, but - of course - it does not sounds healthy
. What miner parameters are you using? Something might be wrong here...Using diablo linux, with -f 10 -v 2 -w 128
got two 6950 cards, with a combined hashrate of 666 Mh/s
had to switch to a different pool after mining for several minutes on your pool with a ratio of 82 accepts / 74 rejects
August 10, 2011, 05:08:39 AM
Why is the reject rate THAT hight? so far, I have 49 accepted and 39 rejected!
I don't have enough info, but - of course - it does not sounds healthy
. What miner parameters are you using? Something might be wrong here... August 10, 2011, 05:06:38 AM
Bad miners simply do not connect at all. Ever. Miner before that would get ZERO connection until i switched from api2 to api.. Pinging them works great though.
What miner are you using? There were such troubles with phoenix older than 1.50...
August 10, 2011, 04:43:38 AM
Why is the reject rate THAT hight? so far, I have 49 accepted and 39 rejected!
August 09, 2011, 06:12:18 AM
I have 3 workers, each one running in a 5850 with phoenix/phatk and all pointing to api2.
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
Do you see any error messages in the 'bad' miner? Idling messages or higher stale ratio? If it is just lower miner performance, it might be some hardware issue. But hard to say without more info...
1.5% is in expected range.
Bad miners simply do not connect at all. Ever. Miner before that would get ZERO connection until i switched from api2 to api.. Pinging them works great though.
August 09, 2011, 05:22:47 AM
I can not figure out why I can't access http://mining.bitcoin.cz/ web page from my laptop but it works OK from my PC (same network)
I can access http://www.bitcoin.cz/ from both computers (and all the other web pages out there too).
Any ideas?
I can access http://www.bitcoin.cz/ from both computers (and all the other web pages out there too).
Any ideas?
August 08, 2011, 05:42:40 AM
I have 3 workers, each one running in a 5850 with phoenix/phatk and all pointing to api2.
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
Do you see any error messages in the 'bad' miner? Idling messages or higher stale ratio? If it is just lower miner performance, it might be some hardware issue. But hard to say without more info...
1.5% is in expected range.
Seems to be more stable for the las 24 hours. No idea what happened before:
Temp Fan% (rpm) Load Rate Accept/Invalid Status
0: 70.5c 80% (3744-) 97% 383 Mhs 7312/109 (1.47%) api2.bitcoin.cz
1: 67.5c 70% (3400+) 99% 389 Mhs 7529/132 (1.72%) api2.bitcoin.cz
2: 68.5c 70% (3466+) 99% 389 Mhs 7500/104 (1.37%) api2.bitcoin.cz
Total: 1162.54 Mhash/s 22341 accepted, 345 invalid (1.52%)
August 08, 2011, 03:46:24 AM
I have 3 workers, each one running in a 5850 with phoenix/phatk and all pointing to api2.
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
Do you see any error messages in the 'bad' miner? Idling messages or higher stale ratio? If it is just lower miner performance, it might be some hardware issue. But hard to say without more info...
1.5% is in expected range.
August 08, 2011, 03:42:46 AM
api2.bitcoin.cz isn't letting all of my miners connect. it took me hours to figure out to try api.bitcoin.cz
you should really say why api2 exists, newer server vs second server for more connections
you should really say why api2 exists, newer server vs second server for more connections
Actually there's no difference between api.bitcoin.cz and api2.bitcoin.cz. Your miners should work with both URLs. Can you try some network tools to analyze connection between you and servers? Ping, traceroute, telnet (mainly if server let you open the connection to put any request).
August 08, 2011, 02:21:29 AM
bump
August 07, 2011, 06:34:16 AM
I cant connect!
api is only taking 2 connections and api2 is taking 10.
I need 2 more!
api is only taking 2 connections and api2 is taking 10.
I need 2 more!
I have 3 workers, each one running in a 5850 with phoenix/phatk and all pointing to api2.
I have just seen that two of them have the same amount of submitted shares after 48 hours (last reboot), but one of them have 3 times less than the other two in the same time. May be a problem connecting to the pool ?
BTW, what is an approximate "right" value for stale/invalid shares ? I'm having about 1.5%
August 07, 2011, 05:59:58 AM
I cant connect!
api is only taking 2 connections and api2 is taking 10.
I need 2 more!
api is only taking 2 connections and api2 is taking 10.
I need 2 more!
August 06, 2011, 06:23:49 PM
replace the ; in the command with \;
all semicolons need to be escaped, otherwise bash treats them as separate commands
all semicolons need to be escaped, otherwise bash treats them as separate commands
Like this? api2.bitcoin.cz:8332/\;askrate=10 -k let me try
That does it thanks a lot
August 06, 2011, 05:43:01 PM
replace the ; in the command with \;
all semicolons need to be escaped, otherwise bash treats them as separate commands
all semicolons need to be escaped, otherwise bash treats them as separate commands
August 06, 2011, 03:44:18 PM
I'm trying to set askrate since there's no longpolling but it fails. This is what i do:
python phoenix.py -u http://xxxx.xxxx:[email protected]:8332/;askrate=10 -k phatk DEVICE=1 VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT FASTLOOP=false
Then i get this:
phoenix$ python phoenix.py -u http://XXXX.XXXX:[email protected]:8332/;askrate=10 -k phatk DEVICE=1 VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT FASTLOOP=false
No device specified or device not found, use DEVICE=ID to specify one of the following
Anyone knows what i got wrong here?
python phoenix.py -u http://xxxx.xxxx:[email protected]:8332/;askrate=10 -k phatk DEVICE=1 VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT FASTLOOP=false
Then i get this:
phoenix$ python phoenix.py -u http://XXXX.XXXX:[email protected]:8332/;askrate=10 -k phatk DEVICE=1 VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT FASTLOOP=false
No device specified or device not found, use DEVICE=ID to specify one of the following
- AMD Athlon(tm) II X2 250 Processor [1] Cypress
[2] Cypress
Anyone knows what i got wrong here?
August 06, 2011, 04:15:58 AM
api2.bitcoin.cz isn't letting all of my miners connect. it took me hours to figure out to try api.bitcoin.cz
you should really say why api2 exists, newer server vs second server for more connections
you should really say why api2 exists, newer server vs second server for more connections
Jump to: