hashkill - testing bitcoin miner plugin

[gat3way]

It is in the SVN. BTW there are upcoming changes and hashkill would likely become dual-licensed. The "commercial" version is not targeting bitcoin, so I would continue to develop the plugin when I have more spare time for that. It's just that my focus (understandably) is being shifted to passcracking part, new algorithms and eventually distributing attacks. GPL'd version will follow those enhancements eventually. The problem is that I guess I won't have enough time for that bitcoin stuff. Anyone is free to fork it and do what he wants as long as GPL terms are followed. Sorry but password cracking is more interesting to me (and after all hashkill was designed to do that, the bitcoin plugin was kind of distraction and PoC work - just wanted to have a miner that suits my needs and reused code from the cracker).

[Tartarus]

It is in the SVN. BTW there are upcoming changes and hashkill would likely become dual-licensed. The "commercial" version is not targeting bitcoin, so I would continue to develop the plugin when I have more spare time for that. It's just that my focus (understandably) is being shifted to passcracking part, new algorithms and eventually distributing attacks. GPL'd version will follow those enhancements eventually. The problem is that I guess I won't have enough time for that bitcoin stuff. Anyone is free to fork it and do what he wants as long as GPL terms are followed. Sorry but password cracking is more interesting to me (and after all hashkill was designed to do that, the bitcoin plugin was kind of distraction and PoC work - just wanted to have a miner that suits my needs and reused code from the cracker).

Thanks for all your hard work!

[Gary13579]

Hi again gat3way --

awesome job with the load balancing! the work is much appreciated. think I found a bug with it though... when using deepbit with -f, it segfaults... everytime. I think this is because of the @ symbol in the file?

The following will work:
hashkill-gpu -p bitcoin username@email.com_0:password:deepbit.net:8332

so does this:
hashkill-gpu -p bitcoin -f pools

cat pools:
username_minername:password:uscentral.btcguild.com:8332

But when you try using the deepbit URL in "pools", it segfaults.

[hashkill] Version 0.2.5
[hashkill] Plugin 'bitcoin' loaded successfully
[hashkill] (pools): 1 hashes loaded successfully, 0 errors
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Barts
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Barts
[hashkill] GPU0: AMD Radeon HD 6800 Series [busy:0%] [temp:50C]
[hashkill] GPU1: AMD Radeon HD 6800 Series [busy:0%] [temp:45C]
[hashkill] Temperature threshold set to 90 degrees C
[hashkill] This plugin supports GPU acceleration.
[hashkill] Initialized hash indexes
[hashkill] Initialized thread mutexes
[hashkill] Spawned worker threads
[hashkill] Successfully connected and authorized at deepbit.net:8332
[hashkill] Compiling OpenCL kernel source (amd_bitcoin.cl)
[hashkill] Binary size: 349080
[hashkill] Doing BFI_INT magic...

Mining statistics...
./hashkill.sh: line 7: 23591 Segmentation fault      hashkill-gpu -p bitcoin -f pools

[trumpetx]

Here's the error I get:


[hashkill] Compiling OpenCL kernel source (amd_bitcoin.cl)[error] (ocl_bitcoin.c:1158) clBuildProgram error (-11)


Any ideas?

[gat3way]

Use SDK 2.4.

[simplecoin]

hey gat3way, do you have a sleep parameter (to keep sensitive cards from overheating)?

Thanks.

[SkipDaShu]

How 'bout just downclocking it via aticonfig --odsc=gpu,mem
or for a wider range (often) use AMDOverdriveCtl.

[gat3way]

Yes, there is a temperature threshold (default being 90 but it's configurable via command-line). When it's reached, the GPU sleeps for a minute. Downclocking it is risky.

[dikidera]

Yes, there is a temperature threshold (default being 90 but it's configurable via command-line). When it's reached, the GPU sleeps for a minute. Downclocking it is risky.

Are you using the AMD ADL library to get the temps?

[gat3way]

Yes.

[owowo]

great miner!!! HUUUGHE thank you!

on my four 6850 with 6870 bios clocked to 940core 300mem

I got about 927Mh/s on phoenix VECTORS BFI_INT AGGRESSION=12 FASTLOOP=false  WORKSIZE=256  ASKRATE=12

with hashkill I have 1012Mh/s peak and a constant of 1000Mh/s   

just one thing. Can you specify the options and what they do?
with -G4 i get "Failure connecting and authenticating to server pool ......"   ?!?
with -D it's faster than without -D, i don't use desktop, hence i cannot say anything about desktoplag.

i know -p is for "plugin" -> bitcoin
and -a for API

Another thing.
If i could get the statistics of hashkill send to my RPC-server and displayed in munin I would be "crying of joy"
Is there a way to do this?

[gat3way]

Alright,

1) Since I moved from global queueing mechanism to queue/thread, using -G4 (especially with multi-gpu systems) is rather troublesome. It will not bring you benefits in terms of performance as compared to -G2. It would likely allow you to hit the anti-DDoS protection on pools though. Even if it doesn't, this would likely guarantee you higher stale percentage.

2) Yes, -D is the right thing to do. It provides higher speeds but has theoretically lower efficiency (should be about 0.2% less efficient and speeds should be ~1-2% faster though which makes it "profitable").

Desktop lag using -D can be relatively insignificant with fastest GPUs and really brutal with slow ones.

As for options/naming (those that concern bitcoin plugin in particular):

-D (comes from "double mode" which is more correct with hash cracking, not bitcoin, but I reused the switch anyway): this increases the global work size thus reducing host-device transfers per getwork. The side-effect being that GPU is overhauled with calculations.

-p is the plugin thing, correct

-G option specifies threads/device ratio. Either provide -G2 (for NVidia with newer drivers) or leave it. In most occasions, default setting is best.

-a specifies API key to use for statistics (available with some pools only when you press ENTER while mining)

-f <filename> specifies a file containing a list of pools for the failover mechanism. People reported it to crash with deepbit.net though for a reason I have not investigated.

-T specifies temperature threshold (in Celsius). When some of your GPUs reach it, it would be disabled for a minute or more to avoid overheating and avoid the aggressive driver thermal throttling. Default is 90C.


hashkill cannot send statistics to sockets, but provides a mechanism to get them from external script. Statistics (speed, processed, submitted, stale and eff) are stored in json format once in 3 seconds in ~/.hashkill/bitcoin.json.

[owowo]

thanks for the answer. gonna use that json 

[echo2]

umm is ur site down or what i cant connect

[dlasher]

latest version from sourceforge download (32-bit 2.4) fails to run on Fedora14 installation.

[root@miner6 hashkill-0.2.4-x86]# ./hashkill-gpu --help
./hashkill-gpu: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory

[root@miner6 hashkill-0.2.4-x86]# ldd hashkill-gpu
        linux-gate.so.1 =>  (0x00fab000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00d8a000)
        libdl.so.2 => /lib/libdl.so.2 (0x00d83000)
        libcrypto.so.0.9.8 => not found
        libm.so.6 => /lib/libm.so.6 (0x00db2000)
        librt.so.1 => /lib/librt.so.1 (0x00da7000)
        libssl.so.0.9.8 => not found
        libOpenCL.so => /usr/src/AMD-APP-SDK-v2.4-lnx32//lib/x86/libOpenCL.so (0x00961000)
        libc.so.6 => /lib/libc.so.6 (0x00bf7000)
        /lib/ld-linux.so.2 (0x00bd6000)


Suggestions as to what's missing? Closest match I can find its openssl/openSSL devel, but both are already installed:

<snip>
Package openssl-1.0.0d-1.fc14.i686 already installed and latest version
Package openssl-devel-1.0.0d-1.fc14.i686 already installed and latest version
<snip>

[DasUrmel]

Hi,

after installing hashkill I get this error:

[error] (plugins.c:258) Cannot open plugin library: /usr/share/hashkill/plugins/bitcoin.so
[error] (main.c:412) Cannot load plugin (bitcoin)

And it's correct, there are several .so modules in the directory, but bitcoin.so is missing.

Version is "hashkill-0.2.4-x86_64".

What did I do wrong ?

Thanks,
Thorsten

[gat3way]

Sorry, the bitcoin plugin is a very low priority for me right now, I am working on completely different part related to hash cracking.

As far as your problem is concerned: where did you get hashkill from? Did you build it from source?

The "official" 0.2.4 version does _not_ contain the bitcoin code. It is experimental and meant to be included in 0.2.5 if it gets stable enough. There are still issues with it and unfortunatelly it is a low priority right now. Most of my efforts right now are towards migration to precompiled kernels and the rule engine for password cracking.

[Zoomer]

Hey gat3way, are you developing a specific attack or a more general engine?

[runeks]

Hi,

after installing hashkill I get this error:

[error] (plugins.c:258) Cannot open plugin library: /usr/share/hashkill/plugins/bitcoin.so
[error] (main.c:412) Cannot load plugin (bitcoin)

And it's correct, there are several .so modules in the directory, but bitcoin.so is missing.

Version is "hashkill-0.2.4-x86_64".

What did I do wrong ?

Thanks,
Thorsten

I experienced this problem as well. Copying over all files from the folder hashkill-s/plugins/ contained in hashkill-0.2.4-x86_64.tgz to /usr/share/hashkill/plugins/ fixed this for me. Though it's probably only necessary to copy over bitcoin.so.

I'm only getting ~195 Mh/s though, while cgminer gives me ~230 Mh/s.

[gat3way]

What GPU are you using and what command-line arguments?