Bitclockers does its best to protect its users, to protect the pool from hoppers bitclockers uses anti hopper protections to mitigate the hoppers bonuses over other miners in the pool
With the Hopping bonus mitigated Hoppers are paid 100% for the shares they mined. NON-Hoppers are not effected and payouts remain 100% of shares mined.
then why my average daily income is 1.6-1.8 where i can get around 2.2 to 2.3 on bitlc, when i tried full time on your pool, without hopping? don't tell me "it's the variance" Its the variance. |
|
|
|
I wonder if (000)-000-0000 is deepbit's phone number too....   0.0.0.0 - 0.255.255.255 4676 Admiralty Way, Suite 330 Marina del Rey, CA US Internet Corporation for Assigned Names and Number abuse@iana.org+1-310-301-5820 WHAT THE FUCK |
|
|
|
|
Apparently, it seems if BitcoinCharts is down when my cronjob runs, my Predictinator can't download history and then doesn't update on time. Lawlz.
|
|
|
|
Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors... (I have to drive to the remote location and spend much time I need somewhere else...) One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story  Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?! Its not. 85c is the maximum safe limit for 24/7 mining, the cards can survive up to 120c for short periods of time without damage. What arguments are you using? None and/or just -v 1 -w 256? I'm using -v1 -w256. Also note this is a "mixed" setup (5xxx, 6xxx and 7970) so I have to run two instances of DM. I don't know if this is relevant, but the 2nd instance is causing 50% load on a dualcore (affinity set to both cores, so it does not look like the "classic" cpu-bug) Huh, I wonder if its an obscure driver bug. Almost no one runs DM more than once. Try just running once instance instead, the one for the 7970 only. |
|
|
|
Read somewhere that you can game while using Diablo miner in the background. Do games run smoothly as if you weren't actually mining (ie. only using spare clock cycles on mining or something to that effect)? Or will there be some noticeable degradation in gaming performance? Also, apparently all optimizations are for SDK2.6 only now. Will I be getting the kind of hash rates using Diablo + SDK2.6 that I would with CGMiner + SDK2.1? From OP: SDK 2.4 supports everything 2.1 does, plus:
Any 6xxx-like VLIW5 (aka Barts): 6790, 68xx, 69xxM
Any 6xxx-like VLIW4 (aka Caicos, Turks, Cayman): 64xx, 65xx, 66xx, 69xx, 64xxM, 66xxM, 67xxM
Any Fusion APU VLIW5 (aka Wrestler, WinterPark): 62xx, 63xx, 64xx
SDK 2.6 supports everything 2.4 does, plus:
79xx GCN
You shouldn't mine in the background, drivers still do not have any sort of priority system. Even setting like -f 1000 will still cause slower games and destroy your hashrate in the process. cgminer now ships with my kernel, so if you're using my kernel on cgminer (it supports several) you should still use 2.6. My old kernel on 2.1 vs my new kernel on 2.6 is basically tied for speed on VLIW5, faster vs 2.5 on VLIW5 and VLIW6, and faster on GCN. |
|
|
|
Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors... (I have to drive to the remote location and spend much time I need somewhere else...) One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?! Its not. 85c is the maximum safe limit for 24/7 mining, the cards can survive up to 120c for short periods of time without damage. What arguments are you using? None and/or just -v 1 -w 256? |
|
|
|
Here's yet another reason why everyone should use p2pool.
Damned straight. |
|
|
|
How many hw errors are ok for a 7970? I currently have 0,17% (52/29410) hw errors, card running overclocked (1125 Mhz) and undervolted (1100 mV).
Everything running stable for >2 days now.
Significant errors like that is insane. Set stock clocks and volts and see if it still does it, if it does its a driver bug, if it doesn't, you overclocked too far. You shouldn't see more than 1 or 2 HW errors per 10k shares give or take, if it starts skyrocketing you went too far. With stock clock/voltage I now have 10/1738 hw errors... so still way too much. What does this mean now? I'm using the latest driver (12.2 pre-cert), latest DM, Windows 7 32-bit. Can I ignore the hw errors and just live with a higher reject rate or is there something I should/can/must do? What GPU temp? |
|
|
|
DiabloMiner-Linux noob question, sorry if it's been asked, but I couldn't find anything anywhere on this forum or google regarding this error. I downloaded python-jsonrpc and ran setup.py, installed the SDK and drivers, etc, when I run Diablo I get this:
DM isn't written in python. user@HOST:~/DiabloMiner$ ./DiabloMiner-Linux.sh -u user.worker -p password -o api2.bitcoin.cz -r 8332 [2/23/12 11:12:09 PM] Started [2/23/12 11:12:09 PM] Connecting to: http://api2.bitcoin.cz:8332/ [2/23/12 11:12:09 PM] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10) You should be using 2.6 now. [2/23/12 11:12:09 PM] ERROR: Cannot connect to api2.bitcoin.cz: Bitcoin returned unparsable JSON
[2/23/12 11:12:10 PM] BFI_INT patching enabled, disabling hardware check errors
[2/23/12 11:12:10 PM] Added Turks (#1) (6 CU, local work size of 256)
[2/23/12 11:12:11 PM] ERROR: Cannot connect to api2.bitcoin.cz: Bitcoin returned unparsable JSON
Did I screw up and forget to install something important?
Hrm, dunno. It shouldn't do that. I wonder if slush screwed something up with his pool. |
|
|
|
+1 to historical data
Looks good, we'll see if the price jumps up in a couple days eh
Yeah, but we have to get past that drop first. |
|
|
|
Would be nice if the historical data contains TWO lines: the actual numbers and the predicted numbers.
It basically does. Its split down the middle, past numbers are -30 through 0, future numbers are 0 through 30. Yes but what I'm saying is, to the RIGHT of the 0, we should see only one line (the prediction) whereas to the LEFT of the 0, we should see two lines (two colors) with one color showing the historical data for each data point while the other color shows what the prediction had been for that same data point. That we can can see not only the historical data, and the prediction data, but we can see HOW THE prediction data measured up against the historical data WITHOUT having to compare to other images or data sets. Yeah, but that would require me to record the prediction which requires more code than I've really wanted to put in it. In addition, what would I record? Merely the next day? The whole 30 days is a complete prediction, so it may get the exact days wrong, but it'll get the general shape over the next 30 days right give or take. So, what you really want is for me to just allow you to predict the past on demand. |
|
|
|
How many hw errors are ok for a 7970? I currently have 0,17% (52/29410) hw errors, card running overclocked (1125 Mhz) and undervolted (1100 mV).
Everything running stable for >2 days now.
Significant errors like that is insane. Set stock clocks and volts and see if it still does it, if it does its a driver bug, if it doesn't, you overclocked too far. You shouldn't see more than 1 or 2 HW errors per 10k shares give or take, if it starts skyrocketing you went too far. |
|
|
|
Hi all, I've searched the thread, but came up with nothing... My desktop PC has 2 GPUs: an Nvidia GTX480 as my primary work and gaming card, and a brand new Radeon 7970, just for mining. I'd like to just run diablo on the 7970, and have it ignore the 480. Is there a command line switch for this? Please keep in mind that I'm really new at mining and configuring miners, so please spell it out as though you were explaining it to your granny. Thanks, Elmojo Use -D, it counts starting 1 not 0. So most likely you want -D 1 (assuming your 7970 is listed first at startup, -D 2 otherwise). Edit: Heh, someone beat me to it |
|
|
|
|
Update: Looks a little more refined. Still can't figure out why the price of BTC is rising so quickly on mtgox.
|
|
|
|
No historical data, I don't feel like adding any sort of db features. Just, like, screenshot or something so you dont want anyone to see how accurate it's past predictions have been? You just drew that in paint didnt you? Have you tried to import than line into the game line rider? did the racer get stuck where the price plunge? is it too early to start my garden? Look at the source, its not an image, its SVG drawn by D3, a popular graphing toolkit. And theres no past predictions because this was the first day I ran it. Its also predicting low, high, and volume as well, the graph just doesn't draw those yet. lol, you need to make it predict better lows and highs.. right now it's predicting a huge trading range all the time. { avg: 6.30721081627292, min: 5.97717029571505, max: 6.68582636534018, volume: 131578.285038269, volume_adj: 0.933032931862247 }, { avg: 6.33598841166913, min: 6.05555391021388, max: 6.59937395447541, volume: 89228.2373129519, volume_adj: 0.785357711657259 }, { avg: 6.41077179654739, min: 6.03910318723335, max: 6.74578869292621, volume: 108922.844700112, volume_adj: 0.854033088403317 }, { avg: 6.18726587862432, min: 5.80770199484833, max: 6.59185889633733, volume: 113371.697694707, volume_adj: 0.869546302222994 }, { avg: 6.47914226820999, min: 6.16057628518267, max: 6.72323286114458, volume: 85413.260047896, volume_adj: 0.772054831543682 }, { avg: 6.27209567437812, min: 5.95757302516065, max: 6.60335116667514, volume: 80036.9799200255, volume_adj: 0.753307666087896 }, Thats not the bug you think it is. |
|
|
|
No historical data, I don't feel like adding any sort of db features. Just, like, screenshot or something so you dont want anyone to see how accurate it's past predictions have been? You just drew that in paint didnt you? Have you tried to import than line into the game line rider? did the racer get stuck where the price plunge? is it too early to start my garden? Look at the source, its not an image, its SVG drawn by D3, a popular graphing toolkit. And theres no past predictions because this was the first day I ran it. Its also predicting low, high, and volume as well, the graph just doesn't draw those yet. |
|
|
|
How are these predictions made? Algorithmically or by-hand?
Magically. |
|
|
|
Can you make it 1000 ?
I laughed So, any details on how the predictions are made? Is there historical data from past predictions? No historical data, I don't feel like adding any sort of db features. Just, like, screenshot or something |
|
|
|
Would be nice if the historical data contains TWO lines: the actual numbers and the predicted numbers.
It basically does. Its split down the middle, past numbers are -30 through 0, future numbers are 0 through 30. |
|
|
|
Nice! It's a little scant on detail though - care to elaborate?  USD on the left On the bottom, -30 through 0 is historical data, 0 through 30 is the prediction. |
|
|
|
|
Show Posts
