Search content
Sort by
Showing 20 of 24 results by Tia
Re: [2000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
Two questions for Luke Jr and WizKid...
1. Now that the fire is under control and server is happy, Any chance of having you add a 'local time' clock on the Stats page, So I could easily correlate the graphs (which I love!) to my time zone?
2. I have an Android App "Miner Status" by David Greene that I'd like to set to monitor my mining account on your pool. While it has an option for Eligius, it doesn't appear to work right now, so I ask if anything has changed with the new server that could have broken that functionality?
1. Now that the fire is under control and server is happy, Any chance of having you add a 'local time' clock on the Stats page, So I could easily correlate the graphs (which I love!) to my time zone?
2. I have an Android App "Miner Status" by David Greene that I'd like to set to monitor my mining account on your pool. While it has an option for Eligius, it doesn't appear to work right now, so I ask if anything has changed with the new server that could have broken that functionality?
Re: [2000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
Thank you for the update and the work, wizkid057. Everything looks normal again from my chair.
-Sheep
-Sheep
Ditto!
Re: [2000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
Update with pool: everything was breaking everywhere, so I rushed to get the new server working.
New server Postgres is screwed up, so I set it up logging shares to a textfile for now.
Payouts and stats are down as a result, but hopefully it won't take long to recover from this mess.
New server Postgres is screwed up, so I set it up logging shares to a textfile for now.
Payouts and stats are down as a result, but hopefully it won't take long to recover from this mess.
Three day's no Payouts and Stats.........
OK! *clears throat*
... Greetings Eligius Miners!
Its been a rough past few days. Here's what's happened:
- Eligius's server was having some serious problems which appeared to be related to connectivity (bandwidth starved)
- Server was also having software issues related to memory and the virtualization software used to partition the pool and the web server.
- I was able to get a new, higher spec'd server online at a new data center several days before these issues became damaging, and I was unavailable when all hell broke lose with the original server to finish a clean setup.
- In my brief absence, Luke-Jr got in and quickly got the new server up and accepting connections and logged all shares to a well-formatted file.
- This broke stats (since the mining wasnt even on the same server!) and payouts (same issue) until I was able to migrate these key pieces of software and related data.
- I got accepted shares into the database as normal, and parsed the file that was made and added those to the database, then caught up the CPPSRB reward system.
- Coinbase payouts resumed shortly, and a manual payout was sent to catch up all payments missed while the reward system was offline. All payments are current up to the time of this post.
- Stats were offline mainly because of the huge size of the databases involved with the migration. They are now back online.
Just about everything should be back up and running. I will note that IPv6 connectivity is presently not available, but I will be working on that shortly.
I will be looking at all options in the coming days to make sure that Eligius remains stable and stats remain available.
On a side note, a generous miner has volunteered time and effort for a full redesign of the Eligius homepage, which should be online any day now!
Summary: Pool is online. Stats are online. No accepted shares we lost. Payout queue is clear.
Thank you all for you patience!
-wk
,
Probably going to try p2pool next... And happy to see Eligius servers running better for me... Now if only they can swiftly fix the stats! Comeon Whiz!
Used Eligius for a while, loved it. Then they migrated the server and I started having problems with my miners getting work reliably. Hash rate fell. Slow response by pool operators, intially they denied any problems. Now pool is being migrated to different server again.
https://bitcointalk.org/index.php?topic=23768.msg2019613#msg2019613
Switched to Bitminter during this. They are either having a really long run of bad luck, or something is wrong. Expected rewards have been consistently below average expected rewards the past few days in a row:
https://bitminter.com/stats/rewards
Now I'm not sure where to go! BTCGuild is dangerously near 51% (not that my hashrate matters, I'm just a drop in the bucket). Deepbit has high fees. Argh!
Totally agree with you, and we experienced the same thing with Eligius (great until server or whatever problems) switched to BitMinter and paltry payouts, even after factoring in the 10 shift thing...https://bitcointalk.org/index.php?topic=23768.msg2019613#msg2019613
Switched to Bitminter during this. They are either having a really long run of bad luck, or something is wrong. Expected rewards have been consistently below average expected rewards the past few days in a row:
https://bitminter.com/stats/rewards
Now I'm not sure where to go! BTCGuild is dangerously near 51% (not that my hashrate matters, I'm just a drop in the bucket). Deepbit has high fees. Argh!
Probably going to try p2pool next... And happy to see Eligius servers running better for me... Now if only they can swiftly fix the stats! Comeon Whiz!
Re: [2000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
Update with pool: everything was breaking everywhere, so I rushed to get the new server working.
New server Postgres is screwed up, so I set it up logging shares to a textfile for now.
Payouts and stats are down as a result, but hopefully it won't take long to recover from this mess.
Cool, cause I like your pool, but things were awful. Glad to see the server is helping. Got any idea when the stats might be back up? I'm testing some with your pool to see how it works for me now.New server Postgres is screwed up, so I set it up logging shares to a textfile for now.
Payouts and stats are down as a result, but hopefully it won't take long to recover from this mess.
Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.1.0
Any bright types out here seen something like this before? Is there anything actionable I should take aware from this:
[2013-05-03 22:03:47] New block: 0124e5430a473503... diff 10.1M
[2013-05-03 22:03:47] JSON-RPC decode failed: [
20,
"_stratum_mining_subscribe() takes exactly 1 positional argument (3 given)",
"Traceback (most recent call last):\n File \"/home/bitcoinpool/eloipool/stratumserver.py\", line 91, in found_terminator\n rv = getattr(self, funcname)(*rpc['params'])\nTypeError: _stratum_mining_subscribe() takes exactly 1 positional argument (3 given)\n"
]
[2013-05-03 22:03:48] Stratum authorisation success for pool 2
[2013-05-03 22:03:47] New block: 0124e5430a473503... diff 10.1M
[2013-05-03 22:03:47] JSON-RPC decode failed: [
20,
"_stratum_mining_subscribe() takes exactly 1 positional argument (3 given)",
"Traceback (most recent call last):\n File \"/home/bitcoinpool/eloipool/stratumserver.py\", line 91, in found_terminator\n rv = getattr(self, funcname)(*rpc['params'])\nTypeError: _stratum_mining_subscribe() takes exactly 1 positional argument (3 given)\n"
]
[2013-05-03 22:03:48] Stratum authorisation success for pool 2
Re: [2000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
https://en.bitcoin.it/wiki/Difficulty
Pools "often do" pdiff, but it seems bdiff is what bitcoin actually does internally. Wouldn't that make bdiff the defacto standard? Since pdiff ends up slightly higher, there's no harm done. Anything hitting the pdiff target also meets the bdiff target. But isn't bdiff the true standard?
There's two different standards, but bdiff only makes sense in the context of Bitcoin because of its floating-point block target.Pools "often do" pdiff, but it seems bdiff is what bitcoin actually does internally. Wouldn't that make bdiff the defacto standard? Since pdiff ends up slightly higher, there's no harm done. Anything hitting the pdiff target also meets the bdiff target. But isn't bdiff the true standard?
Pdiff makes more sense for pools, miners, and blockchain-independent difficulty measurements, especially since it can be easily compressed down to a single byte (by counting the number of zero bits).
Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.1.0
I have a Bitcoin machine running W8 Pro, Radeon 7850 + 7970 and CGminer 2.11.4
I am looking for finer tuning suggestions, and wanted your thoughts as to what you think I may have overlooked or should consider trying. Of the configs I've tried the following seems to run the best, but I'm sure there are more refinements I've not tried, including worksize.
Here is my Config:
"intensity" : "15,15",
"vectors" : "1,1",
"worksize" : "256,64",
"kernel" : "diablo,diablo",
"lookup-gap" : "0,0",
"thread-concurrency" : "0,0",
"shaders" : "0,0",
"gpu-engine" : "800-1100,900-1100",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1180,1190",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "18,18",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "95,95",
"temp-overheat" : "85,85",
"temp-target" : "75,75",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "155",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"per-device-stats" : true,
"queue" : "1",
"scan-time" : "60",
"temp-hysteresis" : "3",
"verbose" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin"
I am looking for finer tuning suggestions, and wanted your thoughts as to what you think I may have overlooked or should consider trying. Of the configs I've tried the following seems to run the best, but I'm sure there are more refinements I've not tried, including worksize.
Here is my Config:
"intensity" : "15,15",
"vectors" : "1,1",
"worksize" : "256,64",
"kernel" : "diablo,diablo",
"lookup-gap" : "0,0",
"thread-concurrency" : "0,0",
"shaders" : "0,0",
"gpu-engine" : "800-1100,900-1100",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1180,1190",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "18,18",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "95,95",
"temp-overheat" : "85,85",
"temp-target" : "75,75",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "155",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"per-device-stats" : true,
"queue" : "1",
"scan-time" : "60",
"temp-hysteresis" : "3",
"verbose" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin"
Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.1.0
Pool2: eligius.st:80
Should be
Code:
mining.
in front of that hostname, but the pool is broken anyway. Try another pool.Thanks for your response nathanrees19!
Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.1.0
[2013-05-02 20:07:53] ALL (5s):1.043G (avg):989.3Mh/s | A:125 R:6 HW:0 U:12.6/m WU:13.6/m
[2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[2013-05-02 20:08:05] Setting GPU 0 fan percentage to 47
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[/quote]
Looks like a pool problem.
[/quote]
Well, to honest this is the first time I've tried port 80 on Eligius. I've been plagued with problems on Eligius pool lately. Had been running pretty solid via :8332, then out of the blue myself and many others ran into problems there with terrible hashrates, stales, unable to retrieve work, and so on. Was just playing with the options of other ports there to see if anything works better. So far I'd say the stratum pool at :3334 seems best but not very good for me. But I digress, not trying to get off topic for this thread, sorry. I was wanting to make sure I wasn't missing something in my config with CGminer.
Here is my call via batch file: cgminer -o http://eligius.st:3334 -u xXXxxXXxxx -p x -I 14,15 --kernel diablo --gpu-memclock 1180,1190 --gpu-engine 800-1100,900-1100 --auto-fan --gpu-map 1:0,0:1 --gpu-powertune 18,18 --expiry 150 --per-device-stats --sharelog %userprofile%\desktop\minedshares.log 2>>%temp%\CGminer.log
And keep in mind the alternate pools are stored in my Config file. I'm open to suggestions for further tweaks as well...
Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.1.0
Anyone have an idea what this might be indicative of? Suggestions?
This machine is W8 Pro, 7850 + 7970 and CGminer 2.11.4
Pool 0: eligius.st:3334 Pool1: mint.bitminter.com:8332 Pool2: eligius.st:80 Pool3: eligius.st:8337 And Ibelieve confirmed this log was while I was running with Pool Load Balancing Failover only setting, while running on Pool 1. I am wondering if it was just CGMiner trying to re-check the availability/viability of Pool2 and essentially failing, then trying again (see this error multiple times).
[2013-05-02 20:07:53] ALL (5s):1.043G (avg):989.3Mh/s | A:125 R:6 HW:0 U:12.6/m WU:13.6/m
[2013-05-02 20:07:53] GPU1 73.0C 3392RPM | (5s):716.7M (avg):661.3Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
[2013-05-02 20:07:55] GPU0 73.0C 2047RPM | (5s):330.9M (avg):331.6Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
[2013-05-02 20:07:57] Setting GPU 0 fan percentage to 48
[2013-05-02 20:07:57] Setting GPU 1 fan percentage to 74
[2013-05-02 20:07:58] ALL (5s):1.029G (avg):989.4Mh/s | A:125 R:6 HW:0 U:12.5/m WU:13.5/m
[2013-05-02 20:07:58] GPU1 73.0C 3406RPM | (5s):743.5M (avg):660.8Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
[2013-05-02 20:07:59] Setting GPU 0 fan percentage to 47
[2013-05-02 20:08:03] ALL (5s):950.3M (avg):987.9Mh/s | A:125 R:6 HW:0 U:12.4/m WU:13.4/m
[2013-05-02 20:08:03] Setting GPU 0 fan percentage to 48
[2013-05-02 20:08:03] Setting GPU 1 fan percentage to 73
[2013-05-02 20:08:04] GPU1 74.0C 3398RPM | (5s):722.5M (avg):660.4Mh/s | A:94 R:6 HW:0 U:9.3/m I:15
[2013-05-02 20:08:05] Testing pool http://eligius.st:80
[2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
[2013-05-02 20:08:05] GPU0 74.0C 2173RPM | (5s):337.0M (avg):331.1Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
[2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[2013-05-02 20:08:05] Setting GPU 0 fan percentage to 47
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[2013-05-02 20:08:05] Closing socket for stratum pool 2
This machine is W8 Pro, 7850 + 7970 and CGminer 2.11.4
Pool 0: eligius.st:3334 Pool1: mint.bitminter.com:8332 Pool2: eligius.st:80 Pool3: eligius.st:8337 And I
[2013-05-02 20:07:53] ALL (5s):1.043G (avg):989.3Mh/s | A:125 R:6 HW:0 U:12.6/m WU:13.6/m
[2013-05-02 20:07:53] GPU1 73.0C 3392RPM | (5s):716.7M (avg):661.3Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
[2013-05-02 20:07:55] GPU0 73.0C 2047RPM | (5s):330.9M (avg):331.6Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
[2013-05-02 20:07:57] Setting GPU 0 fan percentage to 48
[2013-05-02 20:07:57] Setting GPU 1 fan percentage to 74
[2013-05-02 20:07:58] ALL (5s):1.029G (avg):989.4Mh/s | A:125 R:6 HW:0 U:12.5/m WU:13.5/m
[2013-05-02 20:07:58] GPU1 73.0C 3406RPM | (5s):743.5M (avg):660.8Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
[2013-05-02 20:07:59] Setting GPU 0 fan percentage to 47
[2013-05-02 20:08:03] ALL (5s):950.3M (avg):987.9Mh/s | A:125 R:6 HW:0 U:12.4/m WU:13.4/m
[2013-05-02 20:08:03] Setting GPU 0 fan percentage to 48
[2013-05-02 20:08:03] Setting GPU 1 fan percentage to 73
[2013-05-02 20:08:04] GPU1 74.0C 3398RPM | (5s):722.5M (avg):660.4Mh/s | A:94 R:6 HW:0 U:9.3/m I:15
[2013-05-02 20:08:05] Testing pool http://eligius.st:80
[2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
[2013-05-02 20:08:05] GPU0 74.0C 2173RPM | (5s):337.0M (avg):331.1Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
[2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[2013-05-02 20:08:05] Setting GPU 0 fan percentage to 47
[2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[2013-05-02 20:08:05] Closing socket for stratum pool 2
Re: [5000 GH] Eligius: Decntrlzd, ASIC-rdy, 0Fee CPPSRB, 0reg, BTC, 877 # support
There is something going on, I have been having connection issues as well:
http://i.imgur.com/CMQMeZ5.png
And same here, for several days. Pathetic really. Was very happy with things running smoothly and then WHAM. Server stats went offline for part of the day today, like the web server crashed. I am pretty sure Luke and Wiz are working on things but I'm also forced to switch pools for the time being. I haven't changed things on my end, and I'll even entertain the idea that something could be going on with routing of our traffic. Speaking of that, any of you people with the same problems happen to be running over VPN? I am not. http://i.imgur.com/CMQMeZ5.png
Oh, and I'm using CGminer 2.11.4, but we all know it's not a problem specific to our Miner app, so lets not point that finger anymore, ok? We can at least put our heads together and provide some useful info to help isolate the issue. My ISP is Comcast. Anyone else care to share yours?
Re: BFGMiner 3.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, BFLSC/Avln
Can bfgminer run on a windows 8 tablet?
Windows 8 will run mining software fine. The performance may not be great without a radeon card, IMO.Windows RT however (MS Surface RT) does not run Windows software, as it is it's own OS.
Re: CGMINER GPU FPGA overc monit fanspd RPC stratum linux/windws/osx/mip/r-pi 2.11.4
I have been noticing my cgminer 2.11.4 has been alternating the order of the cards between my 7850 and my 7970. Refer to my per device logs below. At first I thought it was saying my 7850 was cranking at the 7970 rate, but later I realized that it was just swapping the order of report. Anyone else seeing this? Thoughts on what options I have? I have read the README over and over, and tweaked a number of settings and remapped the GPUs since they were originally flipped. Am running W8Pro, AMD APP SDK v2.7. I've also been seeing cases of driver crash and recovering (mostly as I get aggressive with OC (<7850,7970> --gpu-engine 800-1100,900-1110 --gpu-memclock 1240,1430). My 7850 is on the cooler side of the case and it likes 340-350 MH/s, but my 7970 seems to be wimpy. I am a newb so please forgive any ignorance on my part!
[2013-04-19 23:48:50] Started cgminer 2.11.4
[2013-04-19 23:48:50] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:50] CL Platform 0 name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:50] CL Platform 0 version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:50] Platform 0 devices: 2
[2013-04-19 23:48:50] 0 Pitcairn
[2013-04-19 23:48:50] 1 Tahiti
[2013-04-19 23:48:50] Mapping OpenCL device 0 to ADL device 1
[2013-04-19 23:48:50] Mapping OpenCL device 1 to ADL device 0
[2013-04-19 23:48:50] GPU 0 AMD Radeon HD 7800 Series hardware monitoring enabled
[2013-04-19 23:48:50] GPU 1 AMD Radeon HD 7900 Series hardware monitoring enabled
[2013-04-19 23:48:50] Probing for an alive pool
[2013-04-19 23:48:50] Testing pool http://xxxx
[2013-04-19 23:48:54] Pool 0 http://xxxx alive
[2013-04-19 23:48:54] GBT longpoll ID activated for http://xxxx
[2013-04-19 23:48:54] Init GPU thread 0 GPU 0 virtual GPU 0
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 0: Pitcairn
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 256
[2013-04-19 23:48:54] initCl() finished. Found Pitcairn
[2013-04-19 23:48:54] Init GPU thread 1 GPU 0 virtual GPU 0
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 0: Pitcairn
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 256
[2013-04-19 23:48:54] initCl() finished. Found Pitcairn
[2013-04-19 23:48:54] Init GPU thread 2 GPU 1 virtual GPU 1
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 1: Tahiti
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 64
[2013-04-19 23:48:54] initCl() finished. Found Tahiti
[2013-04-19 23:48:54] Init GPU thread 3 GPU 1 virtual GPU 1
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 1: Tahiti
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 64
[2013-04-19 23:48:54] initCl() finished. Found Tahiti
[2013-04-19 23:48:54] 4 gpu miner threads started
[2013-04-19 23:48:54] New block: 010943077xxxx82... diff 8.97M
[2013-04-19 23:48:56] GPU0 56.0C 2159RPM | (5s):58.64M (avg):268.4Mh/s | A:0 R:0 HW:0 U:0.0/m I:13
[2013-04-19 23:48:56] GPU1 56.0C 2460RPM | (5s):116.9M (avg):536.9Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:00] ALL (5s):464.3M (avg):733.5Mh/s | A:0 R:0 HW:0 U:0.0/m WU:10.9/m
[2013-04-19 23:49:00] Accepted 2xxxxx61 Diff 6/1 GPU 0
[2013-04-19 23:49:00] Setting GPU 0 fan percentage to 49
[2013-04-19 23:49:00] Setting GPU 1 fan percentage to 49
[2013-04-19 23:49:01] GPU0 58.0C 2069RPM | (5s):235.5M (avg):293.4Mh/s | A:1 R:0 HW:0 U:10.9/m I:13
[2013-04-19 23:49:02] GPU1 58.0C 2391RPM | (5s):541.7M (avg):782.5Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:04] Setting GPU 0 fan percentage to 48
[2013-04-19 23:49:06] ALL (5s):726.0M (avg):807.8Mh/s | A:1 R:0 HW:0 U:5.3/m WU:5.3/m
[2013-04-19 23:49:06] Accepted 1xxxxx34 Diff 8/1 GPU 0
[2013-04-19 23:49:06] Setting GPU 0 fan percentage to 47
[2013-04-19 23:49:06] Setting GPU 1 fan percentage to 48
[2013-04-19 23:49:08] GPU0 58.0C 1848RPM | (5s):270.6M (avg):285.1Mh/s | A:2 R:0 HW:0 U:10.6/m I:13
[2013-04-19 23:49:08] GPU1 60.0C 2349RPM | (5s):598.5M (avg):665.2Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:08] Setting GPU 0 fan percentage to 46
[2013-04-19 23:49:10] Setting GPU 0 fan percentage to 45
[2013-04-19 23:49:12] ALL (5s):745.2M (avg):797.2Mh/s | A:2 R:0 HW:0 U:6.9/m WU:6.9/m
[2013-04-19 23:49:12] Setting GPU 1 fan percentage to 47
[2013-04-19 23:49:14] GPU1 61.0C 2273RPM | (5s):631.8M (avg):643.9Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:14] GPU0 59.0C 1654RPM | (5s):259.1M (avg):276.0Mh/s | A:2 R:0 HW:0 U:6.9/m I:13
[2013-04-19 23:49:14] Setting GPU 0 fan percentage to 44
[2013-04-19 23:49:14] Setting GPU 1 fan percentage to 46
[2013-04-19 23:49:16] Accepted 8xxxxxa4 Diff 1/1 GPU 1
[2013-04-19 23:49:16] Setting GPU 0 fan percentage to 43
[2013-04-19 23:49:17] ALL (5s):833.4M (avg):840.2Mh/s | A:3 R:0 HW:0 U:7.9/m WU:7.9/m
[2013-04-19 23:49:18] Setting GPU 0 fan percentage to 42
[2013-04-19 23:49:19] GPU1 63.0C 2225RPM | (5s):683.1M (avg):639.0Mh/s | A:1 R:0 HW:0 U:2.6/m I:14
[2013-04-19 23:49:19] GPU0 59.0C 1410RPM | (5s):264.2M (avg):284.0Mh/s | A:2 R:0 HW:0 U:5.3/m I:13
[2013-04-19 23:49:20] Setting GPU 0 fan percentage to 41
[2013-04-19 23:49:20] Setting GPU 1 fan percentage to 45
[2013-04-19 23:49:22] ALL (5s):819.2M (avg):831.9Mh/s | A:3 R:0 HW:0 U:6.5/m WU:6.5/m
[2013-04-19 23:49:23] Setting GPU 1 fan percentage to 44
[2013-04-19 23:49:25] Setting GPU 0 fan percentage to 40
[2013-04-19 23:49:25] GPU0 60.0C 1283RPM | (5s):266.3M (avg):280.5Mh/s | A:2 R:0 HW:0 U:4.3/m I:13
[2013-04-19 23:49:26] GPU1 64.0C 2094RPM | (5s):608.2M (avg):657.8Mh/s | A:1 R:0 HW:0 U:2.2/m I:14
Do you have recommendations for best versions to try with my setup?
[2013-04-19 23:48:50] Started cgminer 2.11.4
[2013-04-19 23:48:50] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:50] CL Platform 0 name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:50] CL Platform 0 version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:50] Platform 0 devices: 2
[2013-04-19 23:48:50] 0 Pitcairn
[2013-04-19 23:48:50] 1 Tahiti
[2013-04-19 23:48:50] Mapping OpenCL device 0 to ADL device 1
[2013-04-19 23:48:50] Mapping OpenCL device 1 to ADL device 0
[2013-04-19 23:48:50] GPU 0 AMD Radeon HD 7800 Series hardware monitoring enabled
[2013-04-19 23:48:50] GPU 1 AMD Radeon HD 7900 Series hardware monitoring enabled
[2013-04-19 23:48:50] Probing for an alive pool
[2013-04-19 23:48:50] Testing pool http://xxxx
[2013-04-19 23:48:54] Pool 0 http://xxxx alive
[2013-04-19 23:48:54] GBT longpoll ID activated for http://xxxx
[2013-04-19 23:48:54] Init GPU thread 0 GPU 0 virtual GPU 0
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 0: Pitcairn
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 256
[2013-04-19 23:48:54] initCl() finished. Found Pitcairn
[2013-04-19 23:48:54] Init GPU thread 1 GPU 0 virtual GPU 0
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 0: Pitcairn
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 256
[2013-04-19 23:48:54] initCl() finished. Found Pitcairn
[2013-04-19 23:48:54] Init GPU thread 2 GPU 1 virtual GPU 1
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 1: Tahiti
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 64
[2013-04-19 23:48:54] initCl() finished. Found Tahiti
[2013-04-19 23:48:54] Init GPU thread 3 GPU 1 virtual GPU 1
[2013-04-19 23:48:54] CL Platform vendor: Advanced Micro Devices, Inc.
[2013-04-19 23:48:54] CL Platform name: AMD Accelerated Parallel Processing
[2013-04-19 23:48:54] CL Platform version: OpenCL 1.2 AMD-APP (1084.4)
[2013-04-19 23:48:54] List of devices:
[2013-04-19 23:48:54] 0 Pitcairn
[2013-04-19 23:48:54] 1 Tahiti
[2013-04-19 23:48:54] Selected 1: Tahiti
[2013-04-19 23:48:54] Initialising kernel diablo130302.cl with bitalign, 1 vectors and worksize 64
[2013-04-19 23:48:54] initCl() finished. Found Tahiti
[2013-04-19 23:48:54] 4 gpu miner threads started
[2013-04-19 23:48:54] New block: 010943077xxxx82... diff 8.97M
[2013-04-19 23:48:56] GPU0 56.0C 2159RPM | (5s):58.64M (avg):268.4Mh/s | A:0 R:0 HW:0 U:0.0/m I:13
[2013-04-19 23:48:56] GPU1 56.0C 2460RPM | (5s):116.9M (avg):536.9Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:00] ALL (5s):464.3M (avg):733.5Mh/s | A:0 R:0 HW:0 U:0.0/m WU:10.9/m
[2013-04-19 23:49:00] Accepted 2xxxxx61 Diff 6/1 GPU 0
[2013-04-19 23:49:00] Setting GPU 0 fan percentage to 49
[2013-04-19 23:49:00] Setting GPU 1 fan percentage to 49
[2013-04-19 23:49:01] GPU0 58.0C 2069RPM | (5s):235.5M (avg):293.4Mh/s | A:1 R:0 HW:0 U:10.9/m I:13
[2013-04-19 23:49:02] GPU1 58.0C 2391RPM | (5s):541.7M (avg):782.5Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:04] Setting GPU 0 fan percentage to 48
[2013-04-19 23:49:06] ALL (5s):726.0M (avg):807.8Mh/s | A:1 R:0 HW:0 U:5.3/m WU:5.3/m
[2013-04-19 23:49:06] Accepted 1xxxxx34 Diff 8/1 GPU 0
[2013-04-19 23:49:06] Setting GPU 0 fan percentage to 47
[2013-04-19 23:49:06] Setting GPU 1 fan percentage to 48
[2013-04-19 23:49:08] GPU0 58.0C 1848RPM | (5s):270.6M (avg):285.1Mh/s | A:2 R:0 HW:0 U:10.6/m I:13
[2013-04-19 23:49:08] GPU1 60.0C 2349RPM | (5s):598.5M (avg):665.2Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:08] Setting GPU 0 fan percentage to 46
[2013-04-19 23:49:10] Setting GPU 0 fan percentage to 45
[2013-04-19 23:49:12] ALL (5s):745.2M (avg):797.2Mh/s | A:2 R:0 HW:0 U:6.9/m WU:6.9/m
[2013-04-19 23:49:12] Setting GPU 1 fan percentage to 47
[2013-04-19 23:49:14] GPU1 61.0C 2273RPM | (5s):631.8M (avg):643.9Mh/s | A:0 R:0 HW:0 U:0.0/m I:14
[2013-04-19 23:49:14] GPU0 59.0C 1654RPM | (5s):259.1M (avg):276.0Mh/s | A:2 R:0 HW:0 U:6.9/m I:13
[2013-04-19 23:49:14] Setting GPU 0 fan percentage to 44
[2013-04-19 23:49:14] Setting GPU 1 fan percentage to 46
[2013-04-19 23:49:16] Accepted 8xxxxxa4 Diff 1/1 GPU 1
[2013-04-19 23:49:16] Setting GPU 0 fan percentage to 43
[2013-04-19 23:49:17] ALL (5s):833.4M (avg):840.2Mh/s | A:3 R:0 HW:0 U:7.9/m WU:7.9/m
[2013-04-19 23:49:18] Setting GPU 0 fan percentage to 42
[2013-04-19 23:49:19] GPU1 63.0C 2225RPM | (5s):683.1M (avg):639.0Mh/s | A:1 R:0 HW:0 U:2.6/m I:14
[2013-04-19 23:49:19] GPU0 59.0C 1410RPM | (5s):264.2M (avg):284.0Mh/s | A:2 R:0 HW:0 U:5.3/m I:13
[2013-04-19 23:49:20] Setting GPU 0 fan percentage to 41
[2013-04-19 23:49:20] Setting GPU 1 fan percentage to 45
[2013-04-19 23:49:22] ALL (5s):819.2M (avg):831.9Mh/s | A:3 R:0 HW:0 U:6.5/m WU:6.5/m
[2013-04-19 23:49:23] Setting GPU 1 fan percentage to 44
[2013-04-19 23:49:25] Setting GPU 0 fan percentage to 40
[2013-04-19 23:49:25] GPU0 60.0C 1283RPM | (5s):266.3M (avg):280.5Mh/s | A:2 R:0 HW:0 U:4.3/m I:13
[2013-04-19 23:49:26] GPU1 64.0C 2094RPM | (5s):608.2M (avg):657.8Mh/s | A:1 R:0 HW:0 U:2.2/m I:14
Do you have recommendations for best versions to try with my setup?
I have basically the same overclock as you, I have MSI afterburner running the fans near to 100 though :/
Heres a picture of my Ghetto miner lol
http://postimg.org/image/3z1aw2u7v/
Heres a picture of my Ghetto miner lol
http://postimg.org/image/3z1aw2u7v/
OMG, and I thought you were kidding! LMAO! So what has your average Btc earnings per week or month been (recent numbers please)? What is your Mh/s ?
Thanks for the reply GPU Rigs. So are you saying that your chip-maker of choice is using their own existing chip design and can't get it working smoothly, or did you provide them your own masks/architecture?
I just started a blog this week where me and a buddy or two will post our mining experiences. I posted my first round of math there and all the info that backs up my conclusion. Please check it out and give me your feedback here.
http://mineshaft.me/2013/04/initial-roi-estimates/
Thanks! Looking forward to the discussion.
Thanks for your work and thoughts on this trance. Will look forward to your analysis as the days and weeks go on, because I'm sure you can start comparing the daily hash rates and see just how quickly they increase and once you've got that statistic plotted you can overlay that to your numbers and see a few things; like: "Does the hash rate increase seem to match your proposed new ASICs influx?" or "Does the influx of new GPU miners account for the more gradual build in the hash rate"?
Wishing you the best!
I am very new to Bitcoin, but have spent the previous 2 weeks reading a looot, BFL is one of the subjects I kept think about for long, will they ever ship? I don't know, 50/50 they have any devices at all! when? delay after delay after delay, you can expect them to ship when the difficulty is 10x, maybe
I hope they don't ship and refund all that money. GPU mining would suddenly look appealing once again. In fact, I've pondered a few things... What is to say that BFL wasn't bought out or paid off by millionaires who DON'T Want these released, but rather take that deposit money, build these by the droves, and when they are ready, turn them on, mine like heck, hashing over 51% and take over the blockchain... Wouldn't they be able to OWN and control bitcoins at that point? I guess we'll know if it happens because the hash rate will skyrocket.
My other thought is they could start mining at a more gradual rate, bringing a few more on every day, and when people scream loud enough and the law comes knocking on BFL's door they could start shipping a few. Hell, they could even package these used units back up as new units and finally start shipping them, a little at a time meanwhile they continue to mine with the rest earning countless Btc at the purchasers expense. Seems to me that if BFL was on the up and up they'd have shipped and we wouldn't be reading all these posts about 'I've been waiting for mine since October,...'
Don't get me wrong, I'm not wishing harm or scams on anyone here, just thinking like the skeptical cynic that I probably am. Or maybe I'm bitter that I never started mining 2 years ago, haha!
Thanks for the response. I don't know why that was so hard to find an answer to that. So that leaves the question... wtf do I do with the Address Book address? Or is that my private key for my wallet? The bitcoinqt wallet is so confusing to me...
I hope that BFL ASICs is the big scam I think it is and the hash rates will stay down for a bit. That would mean GPU's are in for awhile longer... 