|
141
|
Bitcoin / Mining / Re: Setup Guide 6990 with latest phoenix - hope it helps
|
on: May 15, 2011, 11:34:41 PM
|
I lost, for some reason about 10mh/s with fastloops off  dont know why, it shouldnt make a difference but it did! Don't you get a warning at startup for having FASTLOOP enabled when AGGRESSION is >8? Not in 1.45 and newer since the stale shares problem was fixed. |
|
|
|
|
143
|
Bitcoin / Mining software (miners) / Re: [MINER] Phoenix - New efficient, fast, modular miner **BFI_INT support!**
|
on: May 15, 2011, 11:25:58 AM
|
My main gains came from going from BFI_INT* to just BFI_INT without the "*" and setting my worksize to 128 - the aggression always helps too
The * was to indicate that trying to use BFI_INT on ATI 4xxx series cards wouldn't work. I'm also curious why you were following the "Midrange and older ATI cards (48xx, 57xx, ect)" recommendation instead of the "High-end ATI cards (58xx, 5970, 68xx, 69xx)" one. In any case, nice guide. I edited the first post a bit so that hopefully nobody else tries using BFI_INT* instead of BFI_INT. |
|
|
|
|
144
|
Bitcoin / Mining software (miners) / Re: python OpenCL bitcoin miner
|
on: May 15, 2011, 11:22:45 AM
|
I have a problem. I got an XFX 6850 card overclocked to 900 core clock and 1150 memory clock with SDK version 2.4 and driver version 11.4.
When I try to use poclmb, I can't get more than ~2 Mhash/s! But when I'm using DiabloMiner I get up to ~200 Mhash/s. Anybody know whats causing this?
You probably have the CPU selected as the device to mine with. Change your -d/--device setting. For SDK 2.4 device 0 should be the first GPU. (it's 1 on earlier SDK versions) |
|
|
|
|
146
|
Bitcoin / Mining software (miners) / Re: [MINER] Phoenix - New efficient, fast, modular miner **BFI_INT support!**
|
on: May 15, 2011, 07:50:25 AM
|
jedi, on what phoenix relies to find its kernel??? atill getting "cant find kernel" on WinPe
This I don't know exactly. The OS level dependencies are within Python itself. This is the code to import kernels: import imp
...
...
...
def makeKernel(self, requester):
if not self.kernel:
module = self.parsedSettings.kernel
try:
file, filename, smt = imp.find_module(module, ['kernels'])
except ImportError:
print("Could not locate the specified kernel!")
exit()
kernelModule = imp.load_module(module, file, filename, smt)
self.kernel = kernelModule.MiningKernel(requester)
return self.kernel
Good grief man, this is some seriously fragmented code! It's a frustrating maze of functions one must navigate through to understand what exactly is going on everywhere... And what makes it even worse is the number of files the functions are spread over.
That being said, this is some nice work - good job! You clearly know your stuff. It sure would be nice if things were consolidated into fewer functions and files though.
This is one of the results of the modular design. I can see how it would be confusing for some users, but the advantage is you can write a new kernel without necessarily knowing the rest of the code. It's also much easier to re-use the same code in other programs. For example, CFSworks' MultiMiner uses the exact same protocol implementation as Phoenix. (mineruitl) |
|
|
|
|
147
|
Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support)
|
on: May 15, 2011, 07:39:10 AM
|
Update: BFI_INT support.
I now have the fastest miner known to man.
On my Radeon 5850 @ 765 /w SDK 2.1
Phoenix DEVICE=1 VECTORS WORKSIZE=128 BFI_INT AGGRESSION=5, 7, 11, 13, with or without FASTLOOP = 273
poclbm -v -w 128 -f 60 = 292
DiabloMiner -v 2 -w 128 -f 60 = 302
I don't think so Tim. On my Radeon 5850 @ 725 /w SDK 2.4 on Win7 x64 DiabloMiner -v 2 -w 128 -f 60 254 MHash/sDiabloMiner -v 2 -w 128 -f 1 270 MHash/sPhoenix 1.47 -k phatk DEVICE=0 VECTORS WORKSIZE=128 BFI_INT AGGRESSION=12 282 MHash/sI haven't found the optimum settings for 2.4 yet. Try playing with the settings and see if you can get higher numbers. Every machine is different. I don't think any combination of -v -w and -f is going to make up that difference in speed. The .cl itself needs to be modified to maximize ALU usage on SDK 2.4. This is what the phatk kernel does. (1418 vs 1484 ALU ops) (for reference poclbm on SDK 2.1 (Linux) is 1421 ALU ops) For me the speed difference with phatk is 409 Mhash/sec vs 394 Mhash/sec with poclbm. Assuming the same performance increase this gives (409/394) * 270 = 280 Mhash/sec |
|
|
|
|
151
|
Bitcoin / Mining software (miners) / Re: Modified Kernel for Phoenix 1.4
|
on: May 12, 2011, 07:59:58 AM
|
2x 5870's "-k poclbm device=1 WORKSIZE=128 VECTORS BFI_INT AGGRESSION=7 FASTLOOP " core on both is at 935.
I got 385mhash on both with poclbm and now i'm getting 398 on both with phatk.
Does fastloop work with this or not? I'm working on upping my aggression and overclocking still.
It does, but it has the same behavior as the poclbm kernel included in Phoenix 1.4. This means it doesn't have as much of a speed benefit at low aggression and it causes stale shares if used with high aggression. |
|
|
|
|
152
|
Bitcoin / Mining software (miners) / Re: Modified Kernel for Phoenix 1.4
|
on: May 11, 2011, 11:30:43 PM
|
5850 900/300
Went from 361 to 355 VECTORS AGGRESSION=12 BFI_INT
This is probably because it's optimized for SDK 2.4. If you are using the Linux + SDK 2.1 setup in your sig then it's probably better to stick with the poclbm kernel. The advantage of phatk is that it produces similar speed to poclbm + SDK 2.1 with SDK 2.4. |
|
|
|
|
153
|
Bitcoin / Mining software (miners) / Re: Modified Kernel for Phoenix 1.4
|
on: May 11, 2011, 10:38:49 PM
|
Very nice! I am getting 408 Mhash/sec now vs 394 Mhash/sec using the poclbm kernel. There is also no difference in desktop responsiveness compared to the poclbm kernel. This is very close to what I get with the poclbm kernel on Linux with SDK 2.1. (410 Mhash/sec, but that's at AGGRESSION=11) 5870 @ 930/300 (Win7 x64, 11.5 + SDK 2.4) Arguments: FASTLOOP VECTORS BFI_INT AGGRESSION=8 Also, it appears you used an older revision of the poclbm kernel as the base for phatk. It doesn't include the FASTLOOP changes in Phoenix 1.45 and newer. The hashrate comparison above is with the FASTLOOP updates added to phatk, however with these particular settings it should be nearly identical. Donation coming your way  |
|
|
|
|
155
|
Other / Obsolete (buying) / Re: WTB: ATI 5870 reference cooler
|
on: May 11, 2011, 06:03:11 AM
|
I've got a spare reference cooler off of an asus EAH5870. Looks brand new and the thermal pads are clean and intact.
13 BTC
Offer accepted, please send me a PM with the address for payment. |
|
|
|
|
156
|
Bitcoin / Pools / Re: BTC Guild - 0% Fee Mining Pool (Long polling, JSON API)
|
on: May 10, 2011, 11:13:32 AM
|
My miner (phoenix 1.45) appears hung. Last share sent 21:36:38 PST. (30 Min ago)
does not appear to be attempting reconnect, Just sitting at 0 MH/s.
restarting it.
Edit: running another instance connected immediately.
This is a bug in Phoenix that has been fixed in 1.46. |
|
|
|
|
157
|
Bitcoin / Mining software (miners) / Re: [MINER] Phoenix - New efficient, fast, modular miner **BFI_INT support!**
|
on: May 10, 2011, 11:11:24 AM
|
As I asked before .. how does Phoenix calculate local hashrate?
I observed that at aggression 7 I can get 430MH/sec, while at aggression 10 I can get only 405, but at this lower local hashrate I am able to finish succesfully more work shares than at aggression 7 (tested for half a day, card compared to card, etc.).
So, better aggression yields in hotter GPU and better yield, while the local hashrate is actually reported lower.
The displayed hashrate is the average over several kernel executions. (configure with -a, default is 10) Each sample in the average is calculated using: (nonces per execution/time taken) Higher AGGRESSION increases both the number of nonces per execution and the time taken. I have tried AGGRESSION values up to 14 and the displayed hashrate continues to increase with each step. |
|
|
|
|
158
|
Bitcoin / Mining / Re: Possible to mine with an nvidia and an ATI card at the same time?
|
on: May 10, 2011, 09:21:43 AM
|
|
I have this working under Windows 7.
2x GTX 580s + 5870. All of them can mine at once or I can play games using the 580s and leave just the 5870 mining.
Just install both display drivers. It seems to work better for me if I don't install CCC with the ATI driver. (not necessary for pure OpenCL use)
|
|
|
|
|
Show Posts
