Pages:
Author

Topic: hashkill - testing bitcoin miner plugin (Read 90911 times)

newbie
Activity: 5
Merit: 0
September 02, 2013, 10:32:17 AM
Here's the error I get:


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


Any ideas?
I have the same error on Debian 7. Cannot install AMD SDK, because it's already in the Debian packages. See here: https://wiki.debian.org/ATIStream

clinfo is working fine:
Code:
Number of platforms: 1
  Platform Profile: FULL_PROFILE
  Platform Version: OpenCL 1.2 AMD-APP (938.2)
  Platform Name: AMD Accelerated Parallel Processing
  Platform Vendor: Advanced Micro Devices, Inc.
  Platform Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices


  Platform Name: AMD Accelerated Parallel Processing
Number of devices: 2
  Device Type: CL_DEVICE_TYPE_GPU
  Device ID: 4098
  Board name: AMD Radeon HD 7400A Series
  Device Topology: PCI[ B#1, D#0, F#0 ]
  Max compute units: 2
  Max work items dimensions: 3
    Max work items[0]: 256
    Max work items[1]: 256
    Max work items[2]: 256
  Max work group size: 256
  Preferred vector width char: 16
  Preferred vector width short: 8
  Preferred vector width int: 4
  Preferred vector width long: 2
  Preferred vector width float: 4
  Preferred vector width double: 0
  Native vector width char: 16
  Native vector width short: 8
  Native vector width int: 4
  Native vector width long: 2
  Native vector width float: 4
  Native vector width double: 0
  Max clock frequency: 625Mhz
  Address bits: 32
  Max memory allocation: 134217728
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 8192
  Max image 2D height: 8192
  Max image 3D width: 2048
  Max image 3D height: 2048
  Max image 3D depth: 2048
  Max samplers within kernel: 16
  Max size of kernel argument: 1024
  Alignment (bits) of base address: 2048
  Minimum alignment (bytes) for any datatype: 128
  Single precision floating point capability
    Denorms: No
    Quiet NaNs: Yes
    Round to nearest even: Yes
    Round to zero: Yes
    Round to +ve and infinity: Yes
    IEEE754-2008 fused multiply-add: Yes
  Cache type: None
  Cache line size: 0
  Cache size: 0
  Global memory size: 536870912
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Kernel Preferred work group size multiple: 64
  Error correction support: 0
  Unified memory for Host and Device: 0
  Profiling timer resolution: 1
  Device endianess: Little
  Available: Yes
  Compiler available: Yes
  Execution capabilities:
    Execute OpenCL kernels: Yes
    Execute native function: No
  Queue properties:
    Out-of-Order: No
    Profiling : Yes
  Platform ID: 0x7fe461cdcce0
  Name: Caicos
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: CAL 1.4.1741
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (938.2)
  Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt


  Device Type: CL_DEVICE_TYPE_CPU
  Device ID: 4098
  Board name:
  Max compute units: 4
  Max work items dimensions: 3
    Max work items[0]: 1024
    Max work items[1]: 1024
    Max work items[2]: 1024
  Max work group size: 1024
  Preferred vector width char: 16
  Preferred vector width short: 8
  Preferred vector width int: 4
  Preferred vector width long: 2
  Preferred vector width float: 4
  Preferred vector width double: 0
  Native vector width char: 16
  Native vector width short: 8
  Native vector width int: 4
  Native vector width long: 2
  Native vector width float: 4
  Native vector width double: 0
  Max clock frequency: 3300Mhz
  Address bits: 64
  Max memory allocation: 2147483648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 8192
  Max image 2D height: 8192
  Max image 3D width: 2048
  Max image 3D height: 2048
  Max image 3D depth: 2048
  Max samplers within kernel: 16
  Max size of kernel argument: 4096
  Alignment (bits) of base address: 1024
  Minimum alignment (bytes) for any datatype: 128
  Single precision floating point capability
    Denorms: Yes
    Quiet NaNs: Yes
    Round to nearest even: Yes
    Round to zero: Yes
    Round to +ve and infinity: Yes
    IEEE754-2008 fused multiply-add: Yes
  Cache type: Read/Write
  Cache line size: 64
  Cache size: 32768
  Global memory size: 4142911488
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Global
  Local memory size: 32768
  Kernel Preferred work group size multiple: 1
  Error correction support: 0
  Unified memory for Host and Device: 1
  Profiling timer resolution: 1
  Device endianess: Little
  Available: Yes
  Compiler available: Yes
  Execution capabilities:
    Execute OpenCL kernels: Yes
    Execute native function: Yes
  Queue properties:
    Out-of-Order: No
    Profiling : Yes
  Platform ID: 0x7fe461cdcce0
  Name: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
  Vendor: GenuineIntel
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2.0 (sse2,avx)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (938.2)
  Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt

So must be a problem with hashkill-gpu
legendary
Activity: 980
Merit: 1008
September 28, 2011, 03:56:47 PM
The aforementioned results were on a 5770 (195 Mh/s without any options, 195-198 with -D -G2). I also tried it on my 5870 which got 333-336 Mh/s with -D -G2. The 5870 gives me about 430 Mh/s with cgminer.
sr. member
Activity: 256
Merit: 250
September 28, 2011, 02:44:47 AM
What GPU are you using and what command-line arguments?
legendary
Activity: 980
Merit: 1008
September 23, 2011, 09:44:02 AM
Hi,

after installing hashkill I get this error:

Quote
[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.
hero member
Activity: 658
Merit: 500
September 13, 2011, 08:07:05 PM
Hey gat3way, are you developing a specific attack or a more general engine?
sr. member
Activity: 256
Merit: 250
August 29, 2011, 02:27:05 AM
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.
newbie
Activity: 6
Merit: 0
August 26, 2011, 01:56:24 PM
Hi,

after installing hashkill I get this error:

Quote
[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
sr. member
Activity: 467
Merit: 250

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:


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


member
Activity: 97
Merit: 10
umm is ur site down or what i cant connect
newbie
Activity: 43
Merit: 0
thanks for the answer. gonna use that json  Cheesy
sr. member
Activity: 256
Merit: 250
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 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.
newbie
Activity: 43
Merit: 0
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   Shocked

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" Wink
Is there a way to do this?
sr. member
Activity: 256
Merit: 250
Yes.
full member
Activity: 126
Merit: 100
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?
sr. member
Activity: 256
Merit: 250
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.
newbie
Activity: 27
Merit: 0
How 'bout just downclocking it via aticonfig --odsc=gpu,mem
or for a wider range (often) use AMDOverdriveCtl.
sr. member
Activity: 406
Merit: 250
hey gat3way, do you have a sleep parameter (to keep sensitive cards from overheating)?

Thanks.
sr. member
Activity: 256
Merit: 250
Use SDK 2.4.
member
Activity: 99
Merit: 10
Here's the error I get:


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


Any ideas?
newbie
Activity: 30
Merit: 0
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 [email protected]_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.

Quote
[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
Pages:
Jump to: