DiabloMiner GPU Miner

[DiabloD3]

If this is just totally unsupported, feel free to smack me. I'm running on a MacPro with both a 5870 and a 5770 in it, which seems perfectly okay doing normal OS things, including games.

If I try running DiabloMiner without any special flags, I get:

[5/20/11 1:17:33 PM] Added ATI Radeon HD 5870 (#1) (10 CU, local work size of 256)
[5/20/11 1:17:34 PM] Added ATI Radeon HD 5870 (#2) (20 CU, local work size of 256)

which doesn't seem right. I'm guessing the 5770 is #1.

With no special flags at all, I'm getting roughly 125M/sec. If I use -D 1 to make it only attach to the first card, it only drops to roughly 100M/sec which leads me to believe something very inefficient is going on.

I've tried various combos of -f, -v and -w and don't seem to be able to do anything but make it worse.

Is this configuration just not going to work at all? Is there any way I can force it to only use the 5870 instead?

I assume OSX is just naming your second card wrong. However, mining in OSX isn't worth it... on Radeon 5xxxs you lose about 40% of your speed. However, it shouldn't be nearly that bad.

I also suspect this cannot be fixed, OSX's OpenCL implementation is braindead.

[1714775284]

1714775284

[1714775284]

1714775284

[jakemates]

Hey guys,

Need some help getting this working.

I ran bitcoin --daemon, then did ./DiabloMiner-OSX.sh --url http://myusername:password@69.172.229.136:8337/

Although I've set rpcuser and rpcpassword in bitcoin.conf, all I get is

Code:

[5/20/11 1:47:00 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:00 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:05 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:05 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:06 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:10 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:10 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:11 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden

Any ideas?

Thanks!

[DiabloD3]

I got the profiler working... that was a lot easier than I thought it would be.  I haven't done too much Java outside of Google's DalvikVM, but it's not a true Java implementation so some things are done a little bit differently.

Anyway, I'm running the first batch of samples now

Are you going to be modifying the kernel much?  I'm curious as to how phatk reduced the operation count by that amount...

I did a lot of examining of phatk. I can't tell where he thinks hes saving cycles. Not only that, it runs exactly the same on SDK 2.1 and SDK 2.4 on my 5850 vs phoenix's standard kernel. Plus, if he is in fact exploiting anything, it probably isn't exploiting it as much as -v 3 -w 128 on mine on 69xx.

The key difference is not in the total number of instructions executed, but that they make better use of the 5-wide ALU design. Have a look at the ASM generated with AMD's KernelAnalyzer. Particularly the number of ALU ops. It's no faster than the poclbm kernel on 2.1, but for most people it eliminates the speed disadvantage of SDK 2.4.

It's also designed with VLIW5 in mind, so it's obviously not going to be optimal on VLIW4 hardware.

Well the big problem is on 2.4 phoenix-poclbm and phatk give near identical results... and both are still slower than real poclbm on both 2.1 and 2.4. And -v 18 and 19 give interesting results on 58xx on 2.4 which beats phatk's lackluster speed.

So... ymm so fucking v.

I've yet to replicate the same results on my system, In fact with 2.4 every time phatk has beaten your miner. Every time I've tried anything other then -v 2 I get slower speeds.
This is on a Sapphire Extreme 5850 on Windows 7 x64.

I wonder if phatk only works well on specific Catalyst releases. No matter what I try, phatk scores the same as phoenix -k poclbm (which both are always slower than real poclbm and mine).

If I can't make phatk run as fast as its supposed to, I can't replicate it's techniques.

[BOARBEAR]

BTW, I am not going to accept a patch containing a custom concat setup. This is not C.

what do you mean by that?

[DiabloD3]

BTW, I am not going to accept a patch containing a custom concat setup. This is not C.

what do you mean by that?

I mean that this is Java and there is a limit to how ugly code should get before its deemed unmaintainable. Plus, clever use of StringBuilder will do the same thing anyhow.

[DiabloD3]

Hey guys,

Need some help getting this working.

I ran bitcoin --daemon, then did ./DiabloMiner-OSX.sh --url http://myusername:password@69.172.229.136:8337/

Although I've set rpcuser and rpcpassword in bitcoin.conf, all I get is

Code:

[5/20/11 1:47:00 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:00 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:05 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:05 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:06 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:10 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:10 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden
[5/20/11 1:47:11 PM] ERROR: Can't connect to Bitcoin: Bitcoin disconnected during response: 403 access forbidden

Any ideas?

Thanks!

The default RPC port on Bitcoin is 8332 not 8337, and if you're connecting to a remote machine you need to add rpcallowip to the bitcoin.conf.

[jakemates]

The default RPC port on Bitcoin is 8332 not 8337, and if you're connecting to a remote machine you need to add rpcallowip to the bitcoin.conf.

Thanks for the response

I checked and 8337 is the port for the pool I'm trying to connect to. I added

Code:

rpcallowip=69.172.229.136:8337
rpcallowip=69.172.229.136

to bitcoin.conf and am still getting the error. Do you think it could be anything else?

[DiabloD3]

The default RPC port on Bitcoin is 8332 not 8337, and if you're connecting to a remote machine you need to add rpcallowip to the bitcoin.conf.

Thanks for the response

I checked and 8337 is the port for the pool I'm trying to connect to. I added

Code:

rpcallowip=69.172.229.136:8337
rpcallowip=69.172.229.136

to bitcoin.conf and am still getting the error. Do you think it could be anything else?

Erm, if you're connecting to someone else's pool, you don't add anything to bitcoin.conf, and you don't even need bitcoin running.

[jakemates]

Erm, if you're connecting to someone else's pool, you don't add anything to bitcoin.conf, and you don't even need bitcoin running.

Oh, I'm a total bitcoin newb here. So I don't need anything additional to connect to a pool like http://mtred.com/?

[DiabloD3]

Update: Clearn up some code to cut down on String stupidity

[DiabloD3]

Erm, if you're connecting to someone else's pool, you don't add anything to bitcoin.conf, and you don't even need bitcoin running.

Oh, I'm a total bitcoin newb here. So I don't need anything additional to connect to a pool like http://mtred.com/?

Most people just do -u minerusername -p minerpassword -o hostname -r port. mtred seems to have an IRC channel.

[jakemates]

Most people just do -u minerusername -p minerpassword -o hostname -r port. mtred seems to have an IRC channel.

Tried that syntax and still getting the error. Thanks for all your help - I'm going to ask around the IRC channel!

[OtaconEmmerich]

I wonder if phatk only works well on specific Catalyst releases. No matter what I try, phatk scores the same as phoenix -k poclbm (which both are always slower than real poclbm and mine).

If I can't make phatk run as fast as its supposed to, I can't replicate it's techniques.

I'm running 11.5a hotfix right now if that helps any, I honestly have no clue why your machine doesn't care for phatk's improvements. Heck I've tried to run 2.1 SDK and it never seems to be better then 2.4 with poclbm in GUI Miner.

[DiabloD3]

I wonder if phatk only works well on specific Catalyst releases. No matter what I try, phatk scores the same as phoenix -k poclbm (which both are always slower than real poclbm and mine).

If I can't make phatk run as fast as its supposed to, I can't replicate it's techniques.

I'm running 11.5a hotfix right now if that helps any, I honestly have no clue why your machine doesn't care for phatk's improvements. Heck I've tried to run 2.1 SDK and it never seems to be better then 2.4 with poclbm in GUI Miner.

11.5 may or may not have changes in the hardware shader compiler (the thing that takes the output from the GLSL and OpenCL compilers and produces hardware-specific instructions). I'm looking forward to bitching about how its not nearly as good as 10.9-10.11.

[Gareth Nelson]

Posted this in the other thread, but here it is again:
http://www.aspiesforfreedom.com/mining/src < Diablo in a java applet (the settings are hardcoded out of laziness, so edit and recompile)

[DiabloD3]

Posted this in the other thread, but here it is again:
http://www.aspiesforfreedom.com/mining/src < Diablo in a java applet (the settings are hardcoded out of laziness, so edit and recompile)

Have the source for that available?

[DiabloD3]

So, I rebooted to Windows, something I haven't done since Bush was President...

5850@765, 11.5a (using included 2.4 runtime)

-v 2 -w 128: 280 mhash
-v 3 -w 128: 294 mhash

phoenix BFI_INT VECTORS WORKSIZE=128 AGGRESSION=13: 284 mhash
phatk same args: 294 mhash

-v 3 -w 128 -f 30: 302 mhash

... *ahem*. Windows, you fucking bastard. And thats vs the 300 some I get with -v 2 -w 128 on 2.1 in Linux (aka the holy grail).

Basically, as far as I can tell, my default of -f 60 is letting the Windows fail leak through.

So, there, I beat phatk with all of my might.

[Basiley]

So, I rebooted to Windows, something I haven't done since Bush was President...

5850@765, 11.5a (using included 2.4 runtime)

-v 2 -w 128: 280 mhash
-v 3 -w 128: 294 mhash

phoenix BFI_INT VECTORS WORKSIZE=128 AGGRESSION=13: 284 mhash
phatk same args: 294 mhash

-v 3 -w 128 -f 30: 302 mhash

... *ahem*. Windows, you fucking bastard. And thats vs the 300 some I get with -v 2 -w 128 on 2.1 in Linux (aka the holy grail).

Basically, as far as I can tell, my default of -f 60 is letting the Windows fail leak through.

So, there, I beat phatk with all of my might.

Windows WDDM driver model include[notable] end-to-end TPM/HDCP encryption overhead to GPU workload. in scale, similar to mesured[for this GPU].
if thats SO critical, use Windows XP/XP64[WinFoundation for legacy PC's can use WDDM in latest versions].

[DiabloD3]

So, I rebooted to Windows, something I haven't done since Bush was President...

5850@765, 11.5a (using included 2.4 runtime)

-v 2 -w 128: 280 mhash
-v 3 -w 128: 294 mhash

phoenix BFI_INT VECTORS WORKSIZE=128 AGGRESSION=13: 284 mhash
phatk same args: 294 mhash

-v 3 -w 128 -f 30: 302 mhash

... *ahem*. Windows, you fucking bastard. And thats vs the 300 some I get with -v 2 -w 128 on 2.1 in Linux (aka the holy grail).

Basically, as far as I can tell, my default of -f 60 is letting the Windows fail leak through.

So, there, I beat phatk with all of my might.

Windows WDDM driver model include[notable] end-to-end TPM/HDCP encryption overhead to GPU workload. in scale, similar to mesured[for this GPU].
if thats SO critical, use Windows XP/XP64[WinFoundation for legacy PC's can use WDDM in latest versions].

ITYM use Linux.

[Gareth Nelson]

Posted this in the other thread, but here it is again:
http://www.aspiesforfreedom.com/mining/src < Diablo in a java applet (the settings are hardcoded out of laziness, so edit and recompile)

Have the source for that available?

That is the source...