Bitcoin Forum
June 21, 2024, 07:33:47 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 »
21  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 09:02:54 PM
BTW...performance is more stable with -D if you switch from ondemand to performance cpu governor. I am not sure the increased CPU power consumption is worth this though.

I have played around with ondemand-performance-powersave cpufreqs, but i dont see any big differences at first eye.
Hashkill cpu usage is between 2%-4%, when i dont use desktop apps. Compared to poclbm cpu usage around 46%, same conditions.
22  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 06:52:26 PM
How much cpu power is used when mining on gpu? Is hashkill using this for mining performance or goes this to desktop taskst. I rather have my cpu set to powersave mode, but for a better and stable desktop performance i will increase it in steps until it runs smoothly. Maybe setting this to performance mode is a little to much. I will try different modes and see if it makes really difference.
used: sudo sh -c "echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"
23  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 05:48:37 PM
BTW...performance is more stable with -D if you switch from ondemand to performance cpu governor. I am not sure the increased CPU power consumption is worth this though.

I have run it for 30 mintutes with minor desktop/mouse lag, near to none
Before i had a stable 75Mhash/s
now:
without the -D or -G1  between 75-77Mhash/s
with -G1 or G2 and -D ~78Mhash/s - Speed: 78 MHash/sec [cur: 68%] [proc: 9] [subm: 7] [stale: 4] [eff: 77%]
Maybe the high stale rate is a fluke, must run it longer to know for shure

(where do i change ondemand to performance cpu governor in hashkill)
24  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 04:49:57 PM
Network connectivity restored.

yep, download is working again
25  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 11:50:11 AM
Apparently there are connectivity problems. Unfortunately I am away and can't do anything for the next 4-5 hours Sad

Oke, will try again later  Smiley
26  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 12, 2011, 11:22:21 AM
I cant download the latest hashkill. Your site is not reachable for more than 12 hours now.
27  Bitcoin / Mining software (miners) / Re: Modified Kernel for Phoenix 1.4 on: May 11, 2011, 05:48:11 PM
on my test machine HD5570 OC@700Mhz

poclbm          72MH/s no desktop lag
phoenix          73MH/s no desktop lag
hashkill          75MH/s sometimes slow mouse
phoenix-phatk 76MH/s very slow desktop environment/must be good for headless
28  Bitcoin / Development & Technical Discussion / Re: Bitcoin Hacker's Toolkit on: May 11, 2011, 12:06:56 PM
Oh yes interested, if the pythonscripts are open and readable. Where can i find them?
29  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 11, 2011, 10:42:44 AM

Hm BTW just one last question, is your GPU at stock clocks or OC'd ?

I have installed  AMDOverdriveCtrl and set max speed to 700mhz

OC' ed running steady at 75Mhash/s with peaks up to 79Mhash, compared to stockspeed at 70/71MHash/s

Hashkill Mining statistics...
Speed: 75 MHash/sec [cur: 73%] [proc: 3] [subm: 3] [stale: 0] [eff: 100%]    
Long polling: got new block!
Speed: 79 MHash/sec [cur: 68%] [proc: 6] [subm: 8] [stale: 2] [eff: 133%]

Btw, do you have a git or svn repository for hashkill?
30  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 09:32:41 PM
Hm, don't try -G4, you need really fast CPU for that. It does not matter for bitcoin at all, you are just rising your power consumption for no good use. There are some cases with hash cracking where it helps (again you need fast CPU and lots of RAM). I would not recommend anything above -G2.

OK so -D does not bring much of performance (not enough to round up to the next integer MH/s, 71 that is). It brings about 2MH/s on my 6870 (from 270 to 272) and it brings a lot for 6990. I guess it does not matter that much for slower GPUs.

As for the segfaults....ummm well probably the static-built binary is not really optimal for all users. Probably the best way to get full performance and avoid crashes is to build it yourself like you did. Mmmm this means I should work on the build stuff as currently it's too complicated and makes a lot of assumptions.

Hm BTW just one last question, is your GPU at stock clocks or OC'd ?

The tryout version is on stock, did not come to installing oc software yet, but when i do i will post hashkill oc results
31  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 08:04:23 PM
Looks like the -G1 option fixed this (if I understand correct and the prebuilt version also works with -G1).

Unfortunately this is not optimal performance-wise, you are losing about 1.5% due to that (which is not much though, about 1M/s, you are likelly to get more with -D). Well, I am not sure what's the root cause yet. SDK2.3 should be thread-safe, it could be either my code or the ADL library. I am more inclined to blame my code though Smiley

Stupid thing is I cannot reproduce that here.

OK just one more thing - could you try running that with -G1 -D and also -G2 -D ? I guess -G2 -D would crash, still that would be an interesting experiment.


P.S this is the same as the entry in my estimations table though - at least I am glad about that Smiley

http://www.gat3way.eu/est.php

Oke,
i have tried with -G -D, no desktop lag, works great, i ran it for 30 minutes, only 1 stale this time: Speed: 70 MHash/sec [cur: 63%] [proc: 54] [subm: 56] [stale: 1] [eff: 103%]
-G1 -D give sometimes slow mouse movements
-G2 -D and desktop becomes slow in moving screens around
-G4 -D and moving desktop stuff around becomes near to impossible

I am still a little unsatisfied about the segmentation fault, is there no install log file with compiling errors that could clear up this segmentation fault? It must start somewhere.
Maybe i'll try it again 2morrow, clean install (as in install tread before) with only hashkill source and some way to find a install log (if there is one).
32  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 06:21:17 PM
Hmmm could you try with -G1 command line option?

When i got this segmentation fault, the normal hashkill didn't work either, so in the normal hashkill i re ./install.sh
and now the source compiled also works, but is this due to the normal reinstall or do i have to reinstall the source compiled one to when i want to run that version?

khash@UbuntuMiner:/usr/bin$ ./hashkill-gpu -p bitcoin xxxxx -G1
[hashkill] Version 0.2.4
[hashkill] Plugin 'bitcoin' loaded successfully
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Redwood
[hashkill] GPU0: ATI Radeon HD 5570 [busy:3%] [temp:60C]
[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: 348936
[hashkill] Doing BFI_INT magic...
[hashkill] Long polling available, starting LP thread.

Mining statistics...
Speed: 70 MHash/sec [cur: 97%] [proc: 2] [subm: 1] [stale: 0] [eff: 50%]     ^C
[hashkill] Interrupted by user request!

[hashkill] Done!
[hashkill] Attack took 64 seconds.
[hashkill] Bye bye Smiley
33  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 05:40:34 PM
this time it compiled the whole way thru, (do you need the output of the complilation?)

khash@UbuntuMiner:/usr/bin$ ./hashkill-gpu -p bitcoin xxxxx
[hashkill] Version 0.2.4
[hashkill] Plugin 'bitcoin' loaded successfully
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Redwood
[hashkill] GPU0: ATI Radeon HD 5570 [busy:0%] [temp:48C]
[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: 348696
[hashkill] Doing BFI_INT magic...
[hashkill] Long polling available, starting LP thread.

Mining statistics...
Segmentation fault
34  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 05:16:55 PM
Alright, skip the make depclean part then, just go on with the next ones exactly as I posted

oke i'm back, with a new clean system where the normal hashkill works

first step: hashkill-source  ./configure returns

khash@UbuntuMiner:~/Downloads/hashkillsource/hashkill$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for stdlib.h... (cached) yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking openssl/md5.h usability... yes
checking openssl/md5.h presence... yes
checking for openssl/md5.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking openssl/sha1.h usability... no
checking openssl/sha1.h presence... no
checking for openssl/sha1.h... no
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking json/json.h usability... yes
checking json/json.h presence... yes
checking for json/json.h... yes
checking curl/curl.h usability... yes
checking curl/curl.h presence... yes
checking for curl/curl.h... yes
checking for size_t... yes
checking for uint64_t... yes
checking for uint32_t... yes
checking for uint16_t... yes
checking for ssize_t... yes
checking for inline... inline
checking for working alloca.h... yes
checking for alloca... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for uid_t in sys/types.h... yes
checking for x86 cpuid 0x00000001 output... 100f62:1020800:802009:178bfbff
checking whether sse2 is supported... yes
checking whether C compiler accepts -msse2... yes
configure: error: cannot run /bin/bash ./config.sub
35  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 03:53:02 PM
brb, have to buy some food, we'll go on in an hour
36  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 02:50:47 PM
Ummm, OK, just use that exact sequence of commands:

Quote
export ATISTREAMSDKROOT=/opt/ati-stream-sdk-v2.3-lnx64
export ADLROOT=/opt/ADL_SDK_3.0
make depclean
./rebuild.sh
./configure
make
sudo make install

i must be doing something wrong

khash@UbuntuMiner:~/Downloads/hashkill/source/hashkill$ export ATISTREAMSDKROOT=/opt/ati-stream-sdk-v2.3-lnx64
khash@UbuntuMiner:~/Downloads/hashkill/source/hashkill$ export ADLROOT=/opt/ADL_SDK_3.0
khash@UbuntuMiner:~/Downloads/hashkill/source/hashkill$ make depclean
make: *** No rule to make target `depclean'.  Stop.
37  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 10, 2011, 01:39:12 PM
On the prerequisites i had to additionally install curl and libcurl4-openssl-dev, afaik libcurl3-dev was replaced with libcurl4-openssl-dev

export ATISTREAMSDKROOT=/opt/ati-stream-sdk-v2.3-lnx64
export ADLROOT=/opt/ADL_SDK_3.0

./configure returned no errors

make returned this error:

gcc -DPACKAGE_NAME=\"hashkill\" -DPACKAGE_TARNAME=\"hashkill\" -DPACKAGE_VERSION=\"0.1.0\" -DPACKAGE_STRING=\"hashkill\ 0.1.0\" -DPACKAGE_BUGREPORT=\"gat3way@gat3way.eu\" -DPACKAGE_URL=\"\" -DPACKAGE=\"hashkill\" -DVERSION=\"0.1.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_FCNTL_H=1 -DHAVE_STDLIB_H=1 -DHAVE_PTHREAD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE_OPENSSL_MD5_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_ZLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_JSON_JSON_H=1 -DHAVE_CURL_CURL_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_SSE2=/\*\*/ -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_BZERO=1 -DHAVE_STRSTR=1 -DHAVE_SYSINFO=1 -DHAVE_STRERROR=1 -DHAVE_ENDPWENT=1 -DHAVE_GETCWD=1 -DHAVE_STRCHR=1 -DHAVE_STRCSPN=1 -DHAVE_STRTOUL=1 -DHAVE_MEMSET=1 -DHAVE_STRTOL=1 -I. -msse2  -ljson -lcurl -DHAVE_CURL_CURL_H -DHAVE_ADL_SDK_H -I/include   -I/include -O3 -funroll-loops  -g -O2 -MT hashkill-ocl-adl.o -MD -MP -MF .deps/hashkill-ocl-adl.Tpo -c -o hashkill-ocl-adl.o `test -f 'ocl-adl.c' || echo './'`ocl-adl.c
ocl-adl.c:3:21: fatal error: adl_sdk.h: No such file or directory
compilation terminated.
make[2]: *** [hashkill-ocl-adl.o] Error 1


and rebuild returned

khash@UbuntuMiner:~/Downloads/hashkill/source/hashkill$ ./rebuild.sh
configure.ac: warning: missing AC_CHECK_FUNCS([mkdir]) wanted by: src/sessions.c:150
configure.ac: warning: missing AC_CHECK_FUNCS([setenv]) wanted by: src/main.c:297
configure.ac: warning: missing AC_PROG_CXX wanted by: src/amd_bitcoin.ll
configure.ac: warning: missing AC_PROG_LN_S wanted by: 64bitset.sh:7
Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf line 196.
Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf line 196.
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --no-force
src/Makefile.am:20: compiling `plugins.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.ac'
autoreconf: Leaving directory `.'
src/Makefile.am:20: compiling `plugins.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.ac'

any suggestions?

38  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 09, 2011, 09:47:01 PM
Quote
Thus far I have those:

* on some GPUs performance is rather degraded, root cause not identified. Seen that on 5870 and 5850, probably others. Some 5870 user reported expected speed so this might turn out to be outside hashkill's scope.

* Those crashes (unfortunately I cannot reproduce them). Still wondering what may be the root cause. Will increase verbosity to see where it fails

* Apparently there are issues with thermal monitoring and dual-GPU cards. Also I do not handle the case with an onboard ATI GPU that is not supported by OpenCL - that is a potential issue with some systems.


If you cant reproduce those tryout version crashes, i could try to build that version from source on my machine (if you have a tryout source version and directions for me)


39  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 09, 2011, 08:32:53 PM
@Bolapara

go to the dir where your hashkill-gpu is and do:

ldd hashkill-gpu | grep OpenCL

and you'll see this:

   libOpenCL.so => /opt/ati-stream-sdk-v2.3-lnx64/lib/x86_64/libOpenCL.so (0x00007f1c94159000)

then you know if you got the right SDK

edit@bolapara
didn't scroll down in the included screen to see you already did this

must be a form of my dislectia  Wink
40  Bitcoin / Mining software (miners) / Re: hashkill - testing bitcoin miner plugin on: May 09, 2011, 05:46:11 PM
Rather weird. Tried with another pool?

I get the stale problem with every pool, this is with your first version, your tryout version gives me this segmentation fault on install

Your first version:
Mining statistics...
Speed: 71 MHash/sec [cur: 91%] [proc: 101] [subm: 71] [stale: 10] [eff: 70%]

When i run phoenix it keeps jumping to Warning: work queue empty, miner is idle, even on AGGRESSION=7 and gives me [0 Khash/sec] [1 Accepted] [0 Rejected] [RPC] for many minutes

When i run poclbm i get no stales or rejects
Pages: « 1 [2] 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!