DiabloMiner GPU Miner

[DiabloD3]

Github repo, issue tracker, and wiki
Newest binary, always updated to match newest git revision

I moved the README to the repo.

[LobsterMan]

Just chiming in, on windows, you need to create a bitcoin.conf file and define your rpc username and pw in order to be able to launch 'bitcoin.exe -daemon', then you use the username and pw you specify here to call diablo's miner

Code:

rpcuser=username
rpcpassword=password

likely located in C:\Users\[your win username]\AppData\Roaming\Bitcoin\bitcoin.conf in win7

And I cannot recall where that would go in XP off hand, but wherever the rest of the bitcoin stuff is stored


Also, I don't think that java is appended to PATH by default, so you will probably want to add that as well to use 'java' from the command line

Code:

C:\Program Files (x86)\Java\jre6\bin

win32 patched getwork binaries at:
http://bitcointalk.org/index.php?topic=1334.0 No longer needed

[DiabloD3]

Until Nvidia ships non-beta drivers that aren't ancient, it seems you can find them here.

[dust]

Does this miner have the 100% CPU usage problems that are present when using SDK 2.2 on linux?

[teknohog]

On my Radeon HD 5570, the hashing rate is about 35 Mhash/s after 10 minutes. It seems to have increased slowly and ever slower, apparently it is calculated over the total running time. m0mchil's version gives 52 to 61 Mhash/s depending on settings.

[DiabloD3]

Does this miner have the 100% CPU usage problems that are present when using SDK 2.2 on linux?

With m0's on 2.2, I get around 50% usage for X, 50% usage for python (out of 200%) and the desktop is unusably slow.

For mine, I get around 15% X usage, 75% usage for Java, and the desktop is smooth as silk.

[DiabloD3]

On my Radeon HD 5570, the hashing rate is about 35 Mhash/s after 10 minutes. It seems to have increased slowly and ever slower, apparently it is calculated over the total running time. m0mchil's version gives 52 to 61 Mhash/s depending on settings.

What OS? And yes, my hash meter is an average of the whole run time, m0's isnt. Its not accurate until it stops going up, which might take an hour on some hardware, maybe more.

[bitcoin2]

Where can I enter the IP from RPC host?
Thanks

[DiabloD3]

Where can I enter the IP from RPC host?
Thanks

Hmm, I seem to have forgotten something. I probably should add that.

[neptop]

Nice work!

I have a feature request. If m0mchil's miner can't connect to Bitcoin (because it is not running) it will tell you so and wait for it to come up. This miner just closes.

Could you change this? It makes things easier when you want to run it after startup, because Bitcoin takes a while. It's also nice if you have to restart BC, because you want to change some parameter or want to switch to an other version.

[DiabloD3]

I've added the command line arguments for host and ip, and it now eats the exception when it can't connect to bitcoin so you can shut bitcoin off and the miner doesn't die. I've also fixed potential concurrency issues; it seems to have improved the mhash meter display.

[teknohog]

On my Radeon HD 5570, the hashing rate is about 35 Mhash/s after 10 minutes. It seems to have increased slowly and ever slower, apparently it is calculated over the total running time. m0mchil's version gives 52 to 61 Mhash/s depending on settings.

What OS? And yes, my hash meter is an average of the whole run time, m0's isnt. Its not accurate until it stops going up, which might take an hour on some hardware, maybe more.

Gentoo Linux. There may be some bus/CPU issues here, since my system has an Atom D510, and only 1x PCIe slots.

[DiabloD3]

Hrm, try my newest build. I wonder how badly the concurrency issues screwed the mhash meter.

[Cdecker]

This is great news. Time for me to dip my toes into OpenCL mining :-)

[teknohog]

Hrm, try my newest build. I wonder how badly the concurrency issues screwed the mhash meter.

The newest build does not give any noticeable improvement. I probably won't be testing this one very much, since the other implementation works well on my system, and I only have this one GPU for mining.

[SmokeTooMuch]

Hmm, Windows 7 64-Bit, Radeon 4870 here.

m0mchil's poclbm is ~1000khashes/s faster and my desktop stays more reponsive than with yours.
I guess I'll stick to poclbm ;P

[DiabloD3]

Hmm, Windows 7 64-Bit, Radeon 4870 here.

m0mchil's poclbm is ~1000khashes/s faster and my desktop stays more responsive than with yours.
I guess I'll stick to poclbm ;P

Try running my miner on your 4870 with -v 2 -w 64 and see who wins. Also, if you have responsiveness issues, try using -f 120... you shouldn't need it, but Windows sucks dick badly.

[SmokeTooMuch]

I guess -w defines the worksize, but what exactly does -v do ?

[DiabloD3]

Vector width. I have a 4850, -w 64 -v 2 is the most optimum settings for GPUs like ours. m0mchil's doesn't seem to have a comparable option.

[DiabloD3]

Hrm, try my newest build. I wonder how badly the concurrency issues screwed the mhash meter.

The newest build does not give any noticeable improvement. I probably won't be testing this one very much, since the other implementation works well on my system, and I only have this one GPU for mining.

After much thought, I'm not sure why you're having this issue, especially if m0's works well. Try running with -f 30; this will lag your desktop, but will reduce the overhead caused by OpenCL itself. You can go down to -f 2 safely if needed, it just slows down X.