DiabloMiner GPU Miner

[DiabloD3]

Update: Updated dependencies to newest versions.

[1713456408]

1713456408

[1713456408]

1713456408

[Queelis]

You should use whichever kernel gets you the best speed. Though, in 3-6 months, I don't think its going to matter.

Why won't it?

[DiabloD3]

You should use whichever kernel gets you the best speed. Though, in 3-6 months, I don't think its going to matter.

Why won't it?

ASICs will drive difficulty up so high that GPUs will no longer be profitable

[DiabloD3]

Update: I've modularized the network and device code, so future non-GPU support and future non-SHA256 chains could be supported; also a few bug fixes have slid in as well.

[Joshwaa]

Future non-GPU? Asics? I thought you were not going to support them? Don't get me wrong I will be really happy if you do.

[DiabloD3]

Future non-GPU? Asics? I thought you were not going to support them? Don't get me wrong I will be really happy if you do.

The problem is there is no useful USB solution for Java. Its not that I don't want to support FPGA/ASIC, its just that I'm so fresh Oracle can suck my nuts.

[Joshwaa]

I remember you stating before about the usb support. Oh well. I can wish.

[DiabloD3]

Im getting an error with the latest update:
[11/28/12 11:53:58 AM] Started
[11/28/12 11:53:58 AM] Connecting to: http://us3.eclipsemc.com:8337/
Exception in thread "main" java.lang.LinkageError: Version mismatch: jar version
 is '23', native library version is '24'
        at org.lwjgl.Sys.<clinit>(Sys.java:118)
        at org.lwjgl.opencl.CL.<clinit>(CL.java:52)
        at com.diablominer.DiabloMiner.DeviceState.GPUHardwareType.<init>(GPUHar
dwareType.java:186)
        at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:355)

        at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:90)



Anyone got a fix?

Delete your DiabloMiner directory and unpack the zip again, or if you're building from source delete everything in target and run mvn package again.

[tinman951]

DiabloD3
at the page https://github.com/Diablo-D3/DiabloMiner/commit/fe4122dab6ac3914e02af12ae163c7402afc649f
you mention that you "Add[ed] ability to add LTC and Stratum support".  Does that mean it is only the ability to add stratum in the future, or is it included in the newest release?

[DiabloD3]

DiabloD3
at the page https://github.com/Diablo-D3/DiabloMiner/commit/fe4122dab6ac3914e02af12ae163c7402afc649f
you mention that you "Add[ed] ability to add LTC and Stratum support".  Does that mean it is only the ability to add stratum in the future, or is it included in the newest release?

Only the ability. A lot of the code was not meant to be modularized, so that was a large PITA.

[Gebastos]

I'm getting an error after the latest update: 


http://i50.fastpic.ru/big/2012/1204/f1/0fc3463b697c1bc2baea9308edb8edf1.jpg



please fix it...

OS: Windows 7 x64 with latest driver and updates

[OggerMC]

i get the same error, I even deleted my DiabloMiner folder and took a fresh one, no luck there.

[DiabloD3]

I'm getting an error after the latest update: 






please fix it...

OS: Windows 7 x64 with latest driver and updates

Strange. What pool is this?

[Gebastos]

I'm getting an error after the latest update: 




please fix it...

OS: Windows 7 x64 with latest driver and updates

Strange. What pool is this?

http://pool.itzod.ru/

[DiabloD3]

I'm getting an error after the latest update: 






please fix it...

OS: Windows 7 x64 with latest driver and updates

Strange. What pool is this?

Never mind my question. Line 264 is the code that handles the parsing for -g.

Although, yes, this is technically a bug: what is your command line, because I bet its not right.

[OggerMC]

start DiabloMiner-Windows.exe -u oggermc@hotmail.de_0 -p ******** -o pit.deepbit.net -r 8332 -D 1 -g 5 -f 240
start DiabloMiner-Windows.exe -u oggermc@hotmail.de_1 -p ******** -o pit.deepbit.net -r 8332 -D 2 -g 5 -f 10

EDIT: After removing "-g 5" it works now, but i used -g 5 since i started mining.

[DiabloD3]

start DiabloMiner-Windows.exe -u oggermc@hotmail.de_0 -p ******** -o pit.deepbit.net -r 8332 -D 1 -g 5 -f 240
start DiabloMiner-Windows.exe -u oggermc@hotmail.de_1 -p ******** -o pit.deepbit.net -r 8332 -D 2 -g 5 -f 10

EDIT: After removing "-g 5" it works now, but i used -g 5 since i started mining.

-g is ignored on any pool that explicitly sets expire time or uses longpoll, which is basically every pool. That said, -g should not be broken.

Edit: Derp, I broke it because I forgot to change all occurrences of a constant.

[DiabloD3]

Update: Fixed -g

[OggerMC]

is there an "-f" which almost stops the minier if i play something like Battlefield 3? 240 seems to be too low, but i heared it was the highest possible.

[DiabloD3]

is there an "-f" which almost stops the minier if i play something like Battlefield 3? 240 seems to be too low, but i heared it was the highest possible.

The highest it goes is 1000. You're better off just killing DiabloMiner while you game.