 Show Posts
|
|
Pages: « 1 2 3 4 [5]
|
It happens on and off.. My internet connection is rock steady as I stay connected to my company vpn 24/7 and I basically never get d/c from slush's pool when I mine there.
Any troubleshooting ideas?
All I can suggest is switching servers from Central/West to the other, and/or upgrading your miner. This has been solved. Apparently, the answer was not to upgrade but to downgrade my miner. I was on either phoenix revision 111 or 112. The rewrite for the RPC protocol is finished, and has been uploaded to the SVN.
It works fine in my testing, but more feedback would be great before pushing this as a new version. This SHOULD definitively fix the idle problem, since that was related to the old RPCProtocol.
i tested it and it resulted in constant disconnects from btcguild (all servers). I reverted back to r110 and the problem disappeared. I reverted to 110 as well and so far have not seen disconnects for an hour. |
|
|
|
|
I've been mining from both uswest and uscentral for the past 48 hours and I'm getting a lot of disconnects:
5830:
[159.05 Mhash/sec] [4635 Accepted] [386 Rejected] [RPC (+LP)]
[159.06 Mhash/sec] [4427 Accepted] [389 Rejected] [RPC (+LP)]
6850:
[124.81 Mhash/sec] [1122 Accepted] [136 Rejected] [RPC (+LP)]
[124.82 Mhash/sec] [1093 Accepted] [157 Rejected] [RPC (+LP)]
6850:
[120.70 Mhash/sec] [961 Accepted] [155 Rejected] [RPC (+LP)]
[120.69 Mhash/sec] [977 Accepted] [144 Rejected] [RPC (+LP)]
5770:
[109.04 Mhash/sec] [331 Accepted] [66 Rejected] [RPC (+LP)]
[109.71 Mhash/sec] [333 Accepted] [71 Rejected] [RPC (+LP)]
5770:
[109.46 Mhash/sec] [297 Accepted] [66 Rejected] [RPC (+LP)]
[109.41 Mhash/sec] [296 Accepted] [64 Rejected] [RPC (+LP)]
I seem to get different %'s for different cards/computers on the same network.
Pretty much all of those rejected is from something like this:
[31/07/2011 15:37:19] Result: 82817999 accepted
[31/07/2011 15:38:41] Disconnected from server
[31/07/2011 15:38:41] Result: a35d8225 rejected
[31/07/2011 15:38:44] Connected to server
[31/07/2011 15:39:09] Result: 41217ec4 accepted
[31/07/2011 15:40:42] Disconnected from server
[31/07/2011 15:40:42] Result: d7afebf3 rejected
[31/07/2011 15:40:54] Connected to server
[31/07/2011 15:40:54] Result: 3ea5ff08 accepted
It happens on and off.. My internet connection is rock steady as I stay connected to my company vpn 24/7 and I basically never get d/c from slush's pool when I mine there.
Any troubleshooting ideas?
|
|
|
|
|
Whitelist please.
Long time lurker. I'm almost at 10gh/s and can't even post outside of newbie area. /headdesk
|
|
|
|
|
dime@graendal:~> DISPLAY=:0 aticonfig --odgc --adapter=all
Adapter 0 - ATI Radeon HD 5800 Series
Core (MHz) Memory (MHz)
Current Clocks : 1000 375
Current Peak : 1000 375
Configurable Peak Range : [600-900] [900-1250]
GPU load : 99%
Adapter 1 - AMD Radeon HD 6800 Series
Core (MHz) Memory (MHz)
Current Clocks : 925 1000
Current Peak : 925 300
Configurable Peak Range : [600-875] [1000-1250]
GPU load : 99%
Yes.
|
|
|
|
|
I installed amd drivers from ppa:ubuntu-x-swat/x-updates and aticonfig never lets me go outside the configurable range, but afterwards, I manually install amd drivers from their site and the new aticonfig command lets me set it to whatever I want.
|
|
|
|
|
long time lurker hit by whitelist rules... zee... zee... zee...
|
|
|
|
|
I got a few of these but haven't been able to get anywhere because of json-rpc.org being down. Arghhh.
|
|
|
|
|
Hi, newbie here. I just started with the pool this morning. It's been going since 6am so only 8 hours in. A couple of questions to make sure everything is working as is.
So, I have a shitty card for mining, a gtx275 on my gaming rig. It's running factory settings atm. I didn't bother to oc because I'm just testing out the mining to see what it's like before I set up some ati cards for it.
So I'm getting an average of 45000 khash/s which according to the hardware comparison is about right.
But on my terminal where poclbm is running, there are these:
11/06/2011 13:21:58, warning: job finished, miner is idle
11/06/2011 13:23:36, warning: job finished, miner is idle
11/06/2011 13:24:56, cf1e82ca, invalid or stale
11/06/2011 13:25:14, warning: job finished, miner is idle
11/06/2011 13:27:49, warning: job finished, miner is idle
11/06/2011 13:30:12, 58d871a3, accepted
11/06/2011 13:33:37, warning: job finished, miner is idle
There are plenty of stretches of time where there are more idle messages than job messages. Is anything on my side wrong?
Also, I'm assuming it's just because I haven't been mining long enough and there haven't been any confirmed blocks yet, but at 8 hours I'm showing 0.020xxxxx BTC unconfirmed and 0.0 confirmed. With about ~44mh/s, is this about right? Or will there be a jump once confirmed blocks are found? And what is the average time to next confirmed block?
Thanks for taking the time to read (and possibly answer questions.)
|
|
|
|
|
