 Show Posts
|
|
Pages: [1]
|
Anyone else seeing deepbit timing out after a little bit? Woke up this morning and it's red, and goes red pretty quickly after a couple of shares are sent. 2011-08-09 08:37:21-0700 [HTTPChannel,12,A.B.C.D] RPC request [] submitted to DeepBit
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.TCPTimedOutError: TCP connection timed out: 110: Connection timed out.
2011-08-09 08:37:25-0700 [-] 'Caught, jsonrpc_call insides'
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: exceptions.Exception: Response is none
|
|
|
|
mtred should work by default. Are you using the latest version?
.....
Any hints on how to adjust/troubleshoot the lag detection? For whatever reason mtred is always marked as lagged out for me  check with RedditorRex over at reddit.com/r/mtred - your ip may be blocked. man IDK, looks like they just found a block, and as soon as the # of shares when down it turned red, and if it's anything like last time it's going to stay red until > 40%. It just looks like their json feed gets crippled when everyone hops on or at least it's crippled for me (yet I can hit it find in a browser). Any hints on adjusting the timeout on the lagger? |
|
|
|
mtred should work by default. Are you using the latest version?
.....
Any hints on how to adjust/troubleshoot the lag detection? For whatever reason mtred is always marked as lagged out for me |
|
|
|
rampone:
Red means it lagged out. Are you sure you didn't accientally change the api_address?
I didn't change the address, and of course now it's no longer red... I'll have to watch it again the next time they hit a block. |
|
|
|
with mtred: Never mined, they minted a new block!!  hoppersden invite anyone 4 me plz? Is there something special to get mtred working? I keep getting error decoding json, and it shows up as red on the stats page, and won't switch. Thanks! |
|
|
|
mmm just updated to latest git and bithopper just crash . Traceback (most recent call last):
File "./bitHopper.py", line 7, in <module>
import work
File "/home/miner1/bitHopper/work.py", line 12, in <module>
from bitHopper import *
File "/home/miner1/bitHopper/bitHopper.py", line 9, in <module>
import stats
File "/home/miner1/bitHopper/stats.py", line 6, in <module>
import pool
File "/home/miner1/bitHopper/pool.py", line 21, in <module>
'api_address':'https://mtred.com/api/user/key/' + mtred_user_apikey,
NameError: name 'mtred_user_apikey' is not defined
do you have mtred_user_apikey defined in password.py? |
|
|
|
Is there a way to set the card up with those clocks under Linux? Aticonfig won't let me go outside the defined ranges of 500-840 and 1250-1325 for core and memory respectively.
I can see where cranking the clock that high would get more Mh/s. Similarly, lowering the memory speed would allow the chip to run a bit cooler.
I'm still trying to figure out the optimal settings for core and memory. Dropping either one lowers speed and heat. Seems like core has a bigger impact on speed and memory a bigger impact on heat, but I'm basing that on what I'm reading in forums like this, not from any empirical testing.
You have to edit the bios with RBE to adjust the ranges. Since I use my cards only for mining I just changed all the memory clocks to 300. I changed the core clock to 900 and I did not see any improvement in MH/s. aticonfig would show the edited core clock, but I'm thinking since I couldn't change the voltage the core can't get enough power... Even tried editing the registers via RBE to attempt to overvolt, aticonfig would still only show stock voltage. btw, this is with a reference card, shaders unlocked. |
|
|
|
MSI R6950-2PM2D2GD5 's can do 430 mh/s easy.
voltage 1200
core clock 970
mem clock 800
fan at 75
shaders unlocked.
good air movement around the cards. conditioned air that is.
using pocblm whatever with phatk kernel.. making sure it has all the lastest code tweaks.
and that is not pushing it to the max. i used to run 980 core clock but decided to take it a bit easier on the cards
and get excellent stability at a temp of ~54
the 6950 reference cards at a price of 250 are an excellent deal for mining and gaming.
but with the difficulty going up it will be hard to pay them off now days at a fast rate.
they had a rebate too just a while back.. but be careful you are limited to one rebate per household.
oh.. and be careful buying refurb cards. i bought a 5970 refurb and as soon as i pushed it
the 2nd core on it started giving me problems. it was obviously still bad in some way and i returned
it for a refund.. thank goodness. buying new or seeing it in action before you buy is probably the way
to go unless you can return it no questions asked.
How are you changing the voltage? msi afterburner with the allow overclocking config in it's config file. also using an asus 6950 bios with shaders unlocked but don't quote me on that... I guess I should have asked if you were on windows or linux. I am unable to change the voltage on linux. |
|
|
|
I tried to do just that but: this only works for the earlier cards... they 'hard' locked the shaders now, requiring to open the card and connect two pins of a specific circut. edit: found the instruction on unlocking shaders for non-referenced xfx 6950's http://forums.extremeoverclocking.com/showthread.php?t=355592I was under the impression that there were 1 of 2 things preventing unlocking the newer cards (or possibly a combination of both). 1 - The flash chip is locked, preventing you from flashing a new bios to the card. This requires a simple hardware mod to fix. 2 - Parts of the PCB are actually laser cut to prevent access the the necessary circuity. If this is the case you even a bios flash will not unlock them. |
|
|
|
...
Sounds resonable. Is there a code listing of the stock 6950 BIOS you can point me to that shows exactly what lines to modify? I don't want to screw it up just mucking around ;-)
There is a php script floating around on the forum somewhere that will modify a saved bios file if you don't want to use RBE.... RBE has a checkbox to unlock the shaders. |
|
|
|
I snagged a nice "open box" MSI R6950-2PM2D2GD5 Radeon HD 6950, which is a reference card, on newegg today. I expect I'll flash it to a 6970 and add it to my miner. That will then be a GPU line-up of 6950 (flashed), 6850, and a 5830. All runing on a OCZ EliteXStream OCZ800EXS-B 800W PSU. Should be fine. If not I'll swap out the Tagan 900W PSU from my gaming maching which requires nowhere near that much PSU.
I've got 7 of those cards. You should just unlock the shaders and not flash the 6970 bios. You should see around 360MH/s once you unlock the shaders. Good luck with overclock, I am unable to increase the core voltage since I run linux and just upping the core speed didn't change my hash rate. -- BigBeerJR I though unlocking the shaders required flashing to a 6970 BIOS? I'd be very interested to hear your method. If you download RBE you can simply dump the stock bios via atiflash, open it in RBE and then only unlock the shaders. Afterwards you can flash the modified bios back to the card. On some of the OC boards people don't recommend the 6970 bios because it changes too many timings/etc. |
|
|
|
MSI R6950-2PM2D2GD5 's can do 430 mh/s easy.
voltage 1200
core clock 970
mem clock 800
fan at 75
shaders unlocked.
good air movement around the cards. conditioned air that is.
using pocblm whatever with phatk kernel.. making sure it has all the lastest code tweaks.
and that is not pushing it to the max. i used to run 980 core clock but decided to take it a bit easier on the cards
and get excellent stability at a temp of ~54
the 6950 reference cards at a price of 250 are an excellent deal for mining and gaming.
but with the difficulty going up it will be hard to pay them off now days at a fast rate.
they had a rebate too just a while back.. but be careful you are limited to one rebate per household.
oh.. and be careful buying refurb cards. i bought a 5970 refurb and as soon as i pushed it
the 2nd core on it started giving me problems. it was obviously still bad in some way and i returned
it for a refund.. thank goodness. buying new or seeing it in action before you buy is probably the way
to go unless you can return it no questions asked.
How are you changing the voltage? |
|
|
|
|
What is the deal with commit 22535ca0778280861f9ba5616194aa8cf2ded4b3?
|
|
|
|
Answers:
1) Pastebin?
Yes I like pastbin for large files. I like opening an issue on github even better.
My bad, next time I'll open a ticket. 2) More details?
Your internet probably died for a brief second. It then chewed through every server before defaulting to an extreme corner case I never expected. It will select mineco if literally all the other servers fail. I fixed that now though. However the LP shouldn't have been retried more than once for each server. Let me doublecheck that code.
Edit: 3) More details?
On looking through the logs I realized that some of my debug messages don't make any sense. What happened in your case is most of that spewing was your miner submitting incorrect LP request. Probably because it always submits them and it got extra desperate when it had no work. But I'm rewriting most of my debug output to make this clearer and the normal output to hide it.
Nothing went wrong with the server side LP code. How many miners are you running though? Thats a lot of clients being triggered on a server change.
Network connection was good throughout the rest of my network, maybe I just enabled too many miners at the same time. At this point I am unable to reproduce so I don't expect much to happen on your end. I have 7 pointing to bithopper. |
|
|
|
In case you haven't noticed I got Server Side LP working. And now my rejection rate is 0%. Which is pretty sweet.
I just did a pull and check out this hotness. ~/bitHopper $ ./pool.py
Trying to delag
Calling sharesResponse for btcg
btcguild :5835582
LP Triggering clients on server change to eclipsemc
LP Client Side Reset
Loading the request failed
LP RPC request [] From eclipsemc.com
Calling sharesResponse for mtred
mtred :22972
LP Call pacrim.eclipsemc.com:8337/LP
Calling sharesResponse for bitclockers
bitclockers :47959
Calling sharesResponse for mineco
mineco :2059918
Calling sharesResponse for bclc
bitcoin.lc :2382709
Calling sharesResponse for eclipsemc
eclipsemc :494116
LP Triggering clients on server change to mtred
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
Error in json decoding, Server probably down
LP Triggering clients on server change to bitclockers
Error in json decoding, Server probably down
LP Triggering clients on server change to eclipsemc
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Error in json decoding, Server probably down
LP Triggering clients on server change to eligius
Error in json decoding, Server probably down
MINECO SELECTED THIS SHOULD NEVER HAPPEN
LP Triggering clients on server change to mineco
RPC request [] From mineco.in
LP Call mineco.in:3000/LP
and after that I'm submitting shares to mineco! Restarting has helped for a little bit, and then: LP triggered from server bitclockers
LP Triggering clients on server change to mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
LP Client Side Reset
Loading the request failed
LP RPC request [] From mtred
Error in json decoding, Server probably down
LP Triggering clients on server change to bitclockers
Error in json decoding, Server probably down
LP Triggering clients on server change to eclipsemc
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Error in json decoding, Server probably down
LP Triggering clients on server change to eligius
Error in json decoding, Server probably down
MINECO SELECTED THIS SHOULD NEVER HAPPEN
LP Triggering clients on server change to mineco
Error in json decoding, Server probably down
LP Triggering clients on server change to bclc
Error in json decoding, Server probably down
LP Triggering clients on server change to btcg
Error in json decoding, Server probably down
LP Triggering clients on server change to eligius
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Error in json decoding, Server probably down
Error in json decoding, Server probably down
Error in json decoding, Server probably down
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Error in json decoding, Server probably down
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Calling sharesResponse for btcg
btcguild :6133250
Calling sharesResponse for mtred
mtred :96698
Calling sharesResponse for bitclockers
bitclockers :75968
Calling sharesResponse for mineco
mineco :2088709
Calling sharesResponse for bclc
bitcoin.lc :2472519
LP triggered from server eligius
LP triggering clients manually
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
reading request content failed
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
LP Client Side Reset
Loading the request failed
LP RPC request [] From eligius
Calling sharesResponse for mtred
mtred :96698
Calling sharesResponse for bitclockers
bitclockers :75968
LP Call su.mining.eligius.st:8337/LP
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
caught, Final response/writing
Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
Calling sharesResponse for mineco
mineco :2088709
Calling sharesResponse for bclc
bitcoin.lc :2477036
Calling sharesResponse for btcg
btcguild :6133250
Calling sharesResponse for eclipsemc
eclipsemc :507240
Calling sharesResponse for eclipsemc
and now I'm on eligius.... |
|
|
|
I snagged a nice "open box" MSI R6950-2PM2D2GD5 Radeon HD 6950, which is a reference card, on newegg today. I expect I'll flash it to a 6970 and add it to my miner. That will then be a GPU line-up of 6950 (flashed), 6850, and a 5830. All runing on a OCZ EliteXStream OCZ800EXS-B 800W PSU. Should be fine. If not I'll swap out the Tagan 900W PSU from my gaming maching which requires nowhere near that much PSU.
I've got 7 of those cards. You should just unlock the shaders and not flash the 6970 bios. You should see around 360MH/s once you unlock the shaders. Good luck with overclock, I am unable to increase the core voltage since I run linux and just upping the core speed didn't change my hash rate. -- BigBeerJR |
|
|
|
|
This has been answered to death, but here is what I use to read/edit/flash my 6950s in linux.
- Get USB stick
- Make bootable freedos USB sitck with UNetbootin
- Download ATIFlash and put it on the USB stick
- Reboot the miner from USB
- Dump bios from GPU to USB stick
- Reboot to linux
- Install virtualbox
- Create windows VM
- Install RBE on windows VM
- Copy bios dump from USB to windows VM
- Edit bios with RBE
- Save edited bios back to the USB stick
- Reboot miner from USB
- Flash GPU with ATIFlash
gl!
|
|
|
|
|
I'd like to be added to the whitelist to help out with beta testing bithopper. There was a commit that just went in that breaks me, but I can't report it to the thread.
|
|
|
|
|
sup all,
Just now getting around to registering.
--BigBeerJR
|
|
|
|
|
