Topic: DiabloMiner GPU Miner - page 7. (Read 866206 times)
Update: Force OSX to do -w 64 by default, improve -56 test
Update: Forcefully disconnect HTTP on any error
Should fix issues with some pools not properly killing the connection and spamming errors until DM restart.
Should fix issues with some pools not properly killing the connection and spamming errors until DM restart.
Update: I didn't fix issue #48. Everyone who was getting -56 errors, update to this release and tell me the number
Code:
Spurious CL_INVALID_GLOBAL_OFFSET error
says after it. At least the -56 error won't halt DM anymore.
Update: Fixed issue #48, fixed possible overflow in outputBuffer
Update: Fixed -g
Thanks 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.
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.
Update: Fixed -g
start DiabloMiner-Windows.exe -u [email protected]_0 -p ******** -o pit.deepbit.net -r 8332 -D 1 -g 5 -f 240
start DiabloMiner-Windows.exe -u [email protected]_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.
start DiabloMiner-Windows.exe -u [email protected]_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.
start DiabloMiner-Windows.exe -u [email protected]_0 -p ******** -o pit.deepbit.net -r 8332 -D 1 -g 5 -f 240
start DiabloMiner-Windows.exe -u [email protected]_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.
start DiabloMiner-Windows.exe -u [email protected]_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.
I'm getting an error after the latest update: 
please fix it...
OS: Windows 7 x64 with latest driver and updates
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.
I'm getting an error after the latest update:
please fix it...
OS: Windows 7 x64 with latest driver and updates
please fix it...
OS: Windows 7 x64 with latest driver and updates
Strange. What pool is this?
http://pool.itzod.ru/
I'm getting an error after the latest update:
please fix it...
OS: Windows 7 x64 with latest driver and updates
please fix it...
OS: Windows 7 x64 with latest driver and updates
Strange. What pool is this?
i get the same error, I even deleted my DiabloMiner folder and took a fresh one, no luck there.
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
http://i50.fastpic.ru/big/2012/1204/f1/0fc3463b697c1bc2baea9308edb8edf1.jpg
please fix it...
OS: Windows 7 x64 with latest driver and updates
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?
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.
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?
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?
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.(Sys.java:118)
at org.lwjgl.opencl.CL.(CL.java:52)
at com.diablominer.DiabloMiner.DeviceState.GPUHardwareType.(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?
[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.
at org.lwjgl.opencl.CL.
at com.diablominer.DiabloMiner.DeviceState.GPUHardwareType.
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.
I remember you stating before about the usb support. Oh well. I can wish.
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.
Jump to: