DiabloMiner GPU Miner - page 86. | Bitcointalksearch.org

Judson

newbie

Activity: 22

Merit: 0

Weird, I get:

Code:

Added Radeon HD 4670 (8 CU, 2x vector, local work size of 
ERROR: [CL_INVALID_BUILD_OPTIONS] : OpenCL Error : clBuildProgram failed: Invalid build options "-D VECTORS=2 -D NS="(u)((nonce * 2) + 0, (nonce * 2) + 1)" -D CHECKOUTPUT="if(H.s0 == 0) {output[0] = ns.s0;}if(H.s1 == 0) {output[1] = ns.s1;}" -D WORKGROUPSIZE="""


Exception in thread "main" java.lang.Exception: Failed to build program on Radeon HD 4670
	at com.diablominer.DiabloMiner.DiabloMiner$DeviceState.(DiabloMiner.java:368)
	at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:195)
	at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:88)

when trying to run DiabloMiner-OSX.sh with my username and pass.

slush

legendary

Activity: 1386

Merit: 1097

Hi Diablo, I just tested your miner against current (0.3.17) client version (unpatched) and this does not work. There is getwork feature already included in official client. Do you plan to update your API to accept default client implementation? It would be cool.

One more question. Is possible to add parameter to specify port or even whole URL to client? Now you only accept 'host' parameter, so both port or path inside uri are hardcoded inside. I'm working on cooperative mining and I would like to test it against your miner, too. Full URL in command line whould help me a lot.

Thanks, Marek

SmokeTooMuch

legendary

Activity: 860

Merit: 1021

Try

Code:

./DiabloMiner-Linux.sh -w 128 -u user -p pass

Maybe it works when you specify the work size (-w switch)

taypan

newbie

Activity: 1

Merit: 0

Hi, I am trying the latest DiabloMiner build.
But when i run

Code:

./DiabloMiner-Linux.sh -u user -p pass

i am still getting same error:

Code:

Added GeForce 8800 GTS (12 CU, 1x vector, local work size of clang: Too many positional arguments specified!
Can specify at most 1 positional arguments: See: clang --help

I am runnig Debian Testing and my GPU is GeForce 8800 GTS.

Can someone help me?

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Sigh, -s did not work as well as I had hoped, and now it is gone. There goes my 99.1% efficiency, back to 95% I go.

I've updated the mhash counter code to average over 30 seconds, and I've also added executor lockup detection (which should never happen, but apparently does on really fubar machines).

Fixing it to work on satoshi's getwork impl is still on my todo list.

Also, for those having the lwjgl ELFCLASS32 bug on Ubuntu x86-64, I've discovered the fix: your DISPLAY is unset because you're running it headless over ssh. Do export DISPLAY=:0 before running and it should work fine now.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: SmokeTooMuch on November 25, 2010, 08:31:26 AM

does diablominer work with the new getwork from the official client ?

Not yet, still gotta use m0's version instead.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

As a side note, do not try -s on Radeon 5xxx. It is slower, and it can also lead to random segfaults because I think I'm hitting a bug in the driver.

Now, as for the gigantic hash problem is, the hash counter is increased every time a kernel is queued... if the kernel fails to queue (which I just added detection of in the build I just pushed out), it would still increase the hash counter. Now, it quits and bitches.

UukGoblin on IRC found a slight tiny bug in the new code I wrote for split, so I just fixed that, it effected people not using split. This should cure some of the problems some of you were having.

So, everyone upgrade and see if you're still experiencing bugs.

neptop

sr. member

Activity: 314

Merit: 251

Got the same problem.
-w 256 says 3210932050 khashes here
Would be really nice Wink

SmokeTooMuch

legendary

Activity: 860

Merit: 1021

Quote from: DiabloD3 on November 25, 2010, 01:40:12 AM

Something is not working right here on your machine. There is no way you should be getting above 94 mhash. What do you get with mine with split not enabled?

Code:

java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -w 64 -u NAME -p PW

leads to ~80mh/s (no matter whether -w 64, -w 128 or -w 256)

SmokeTooMuch

legendary

Activity: 860

Merit: 1021

does diablominer work with the new getwork from the official client ?

teknohog

sr. member

Activity: 519

Merit: 252

555

Quote from: DiabloD3 on November 25, 2010, 01:40:12 AM

Something is not working right here on your machine. There is no way you should be getting above 94 mhash. What do you get with mine with split not enabled?

Similarly, my HD5570 shows about 400 Mhash/s with -s, which is quite an improvement from the usual 60 Wink

It has succesfully generated blocks on the test network, but much slower than expected. At the moment it does not even run without -s:

Code:

Added Redwood (5 CU, 1x vector, local work size of Exception in thread "main" java.lang.NullPointerException
        at org.lwjgl.opencl.CL10.clGetKernelWorkGroupInfo(CL10.java:1586)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState.(DiabloMiner.java:392)
        at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:198)
        at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:87)

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Something is not working right here on your machine. There is no way you should be getting above 94 mhash. What do you get with mine with split not enabled?

Also, yes, -s completely destroys desktop interactivity. Try using -f 240 on top of that until I commit a change to implicitly do that with -s (4xxx needs -f 120 to begin to operate normally without destroying desktop interactivity)

SmokeTooMuch

legendary

Activity: 860

Merit: 1021

Quote from: DiabloD3 on November 24, 2010, 07:24:12 AM

Update: added Radeon 4xxx mode that splits the OpenCL kernel payload in half... use -s. I am now 99.1% efficient on Radeon 4xxx hardware.

gonna test that on my hd4870.

EDIT:
WOW O.O
from ~77mh/s (m0mchil) to 300+mh/s !!!

but somehow it is decreasing continously ... any explanation for that ?
--> stopped decreasing at ~274mh/s (but somehow still slightly decreasing)

btw: desktop responsiveness is still a horror

used:

Code:

java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -s -u MYNAME -p MYPASSWORD

EDIT2: started it again ans this time it seems like its behaviour is normal.
instead of steadily decreasing, it is now increasing. ~250mh/s

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Update: added Radeon 4xxx mode that splits the OpenCL kernel payload in half... use -s. I am now 99.1% efficient on Radeon 4xxx hardware.

MrFlibble

newbie

Activity: 25

Merit: 0

Thanks for the stats - I used the posts above in this thread to compile a table at https://www.bitcoin.org/wiki/doku.php?id=bitcoin_miners . Some data is missing, please feel free to edit.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Update: You no longer have to edit the OpenCL to enable the bitalign hack for SDK 2.1 and Radeon 5xxx anymore: just start the program with -a

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

There is a small problem, slush: I wasn't aware Ions supported OpenCL at all. -w and -v should only be used by people who know what they're doing. -w 1024 is too high for any platform I've seen, and the nvidia driver should reject it.

43 ghash/sec sounds like the miner isn't running at all, which I'm not sure how my app arrived at such a point if Nvidia's drivers are written correctly... which, its Nvidia, when have they ever written anything correctly.

slush

legendary

Activity: 1386

Merit: 1097

Hi Diablo, I just tried your miner on Nvidia ION; it is quite impressive machine, because your hashmeter showing me 43Ghash/s at this moment Wink

. I was playing with -v and -w parameters and because I don't have an idea what it means, after setting up -w 1024 it become crazy. With default settings I have 2000khash/s which is very poor, but reasonable for this machine.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Updated miner. As mentioned in updated op, on ATI 2.1 + 10.10 (which is slower than 10.9), using -w 64 -v 1 (not -v 2), I get almost 75 mhash on my Radeon 4850 which gives me above 95% estimated efficiency; using only 1% CPU in the miner and 0% CPU in X.

Oh, and as a side note, it does not automatically detect Radeon 5xxx on SDK 2.1; for the time being, you have to edit DiabloMiner.cl in the jar, comment the first line and uncomment the second and third lines. This is not required for SDK 2.2.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

So, I just installed Cat 10.10... on my miner, -w 64 -v 2 is no longer optimal... -w 256 -v 1 is, and my speed is lower than it should be (about 66 mhash vs 70). So, they improved one issue (-v 2 should not have been performing better than -v 1), but got worse somewhere else. Bleh.

Topic: DiabloMiner GPU Miner - page 86. (Read 866206 times)