Groestlcoin Forum

Groestl => Tutorials => Topic started by: child_harold on May 09, 2014, 12:54:58 pm

Title: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: child_harold on May 09, 2014, 12:54:58 pm
I have prepared a PDF guide, shortly to be uploaded to site server.
In the meantime you can get it here:
https://mega.co.nz/#!AFxziaoR!TyIyMn34EI3b7Gu2_hHQqkqH4CjWcygHQbGN99Yq8hU
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: Semedisenape on May 09, 2014, 06:41:57 pm
Hope some help.
This is what:
Code: [Select]
dmr@dminer:~/Mining/sph-sgminer$ [b]./autogen.sh[/b]
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:6: installing `./missing'
src/Makefile.am: installing `./depcomp'
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:52: installing `./compile'
configure.ac:22: installing `./missing'
ccan/Makefile.am: installing `./depcomp'

Code: [Select]
dmr@dminer:~/Mining/sph-sgminer$ [b]./configure --prefix=/usr/local/sph-sgminer[/b]
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 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 minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ranlib... ranlib
checking whether gcc needs -traditional... no
checking whether gcc and cc understand -c and -o together... yes
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for mprotect... yes
checking for sigaction... yes
checking for sigaltstack... yes
checking for siginterrupt... yes
checking for mmap... yes
checking for MAP_ANONYMOUS... yes
checking whether memchr works... yes
checking whether memmem is declared... yes
checking for memmem... yes
checking whether memmem works... yes
checking for C/C++ restrict keyword... __restrict
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking whether stdint.h conforms to C99... yes
checking whether memmem is declared without a macro... yes
checking whether mempcpy is declared without a macro... yes
checking whether memrchr is declared without a macro... yes
checking whether rawmemchr is declared without a macro... yes
checking whether stpcpy is declared without a macro... yes
checking whether stpncpy is declared without a macro... yes
checking whether strchrnul is declared without a macro... yes
checking whether strdup is declared without a macro... yes
checking whether strncat is declared without a macro... yes
checking whether strndup is declared without a macro... yes
checking whether strnlen is declared without a macro... yes
checking whether strpbrk is declared without a macro... yes
checking whether strsep is declared without a macro... yes
checking whether strcasestr is declared without a macro... yes
checking whether strtok_r is declared without a macro... yes
checking whether strerror_r is declared without a macro... yes
checking whether strsignal is declared without a macro... yes
checking whether strverscmp is declared without a macro... yes
checking whether memmem works in linear time... yes
checking for memmem... (cached) yes
checking whether memmem works... (cached) yes
checking for struct sigaction.sa_sigaction... yes
checking for volatile sig_atomic_t... yes
checking for sighandler_t... yes
checking whether sigaction is declared without a macro... yes
checking whether sigaddset is declared without a macro... yes
checking whether sigdelset is declared without a macro... yes
checking whether sigemptyset is declared without a macro... yes
checking whether sigfillset is declared without a macro... yes
checking whether sigismember is declared without a macro... yes
checking whether sigpending is declared without a macro... yes
checking whether sigprocmask is declared without a macro... yes
checking for sigprocmask... yes
checking whether NULL can be used in arbitrary expressions... yes
checking for ANSI C header files... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for OpenCL... yes
checking for pthread_create in -lpthread... yes
checking for ./ADL_SDK/adl_sdk.h... yes
checking for library containing addstr... -lncurses
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBCURL... no
checking for LIBCURL... yes
checking whether to use git version if available... checking for git... git
checking for .git/... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating ccan/Makefile
config.status: creating lib/Makefile
config.status: creating sph/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
=== configuring in compat/jansson-2.5 (/home/dmr/Mining/sph-sgminer/compat/jansson-2.5)
configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local/sph-sgminer'  --cache-file=/dev/null --srcdir=.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for int32_t... yes
checking for long long int... yes
checking for inline... inline
checking for strtoll... yes
checking for localeconv... yes
configure: creating ./config.status
config.status: creating jansson.pc
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/jansson_config.h
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands



------------------------------------------------------------------------
sgminer 4.1.0
------------------------------------------------------------------------


Configuration Options Summary:

  Use git version......: yes
  libcurl(GBT+getwork).: Enabled: -lcurl 
  curses.TUI...........: FOUND: -lncurses
  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2
  LDFLAGS..............:  -lpthread
  LDADD................: -ldl -lcurl   compat/jansson-2.5/src/.libs/libjansson.a -lpthread -L/opt/AMDAPP/lib/x86_64 -lOpenCL    -lm -lrt

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local/sph-sgminer

Code: [Select]
dmr@dminer:~/Mining/sph-sgminer$ sudo make
[sudo] password for dmr:
make  all-recursive
make[1]: ingresso nella directory "/home/dmr/Mining/sph-sgminer"
Making all in lib
make[2]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/lib"
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/lib"
make[4]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/lib"
  CC     dummy.o
  AR     libgnu.a
make[4]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/lib"
make[3]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/lib"
make[2]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/lib"
Making all in compat
make[2]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat"
Making all in jansson-2.5
make[3]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
make  all-recursive
make[4]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
Making all in src
make[5]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5/src"
  CC     dump.lo
  CC     error.lo
  CC     hashtable.lo
  CC     load.lo
  CC     memory.lo
  CC     pack_unpack.lo
  CC     strbuffer.lo
  CC     strconv.lo
  CC     utf.lo
  CC     value.lo
  CCLD   libjansson.la
make[5]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5/src"
make[5]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
make[5]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
make[4]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
make[3]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat/jansson-2.5"
make[3]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/compat"
make[3]: Nessuna operazione da eseguire per "all-am".
make[3]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat"
make[2]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/compat"
Making all in ccan
make[2]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/ccan"
  CC     opt/libccan_a-helpers.o
  CC     opt/libccan_a-opt.o
  CC     opt/libccan_a-parse.o
  CC     opt/libccan_a-usage.o
  AR     libccan.a
make[2]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/ccan"
Making all in sph
make[2]: ingresso nella directory "/home/dmr/Mining/sph-sgminer/sph"
  CC     bmw.o
  CC     echo.o
  CC     jh.o
  CC     luffa.o
  CC     simd.o
  CC     blake.o
  CC     cubehash.o
  CC     groestl.o
  CC     keccak.o
  CC     shavite.o
  CC     skein.o
  CC     sha2.o
  CC     sha2big.o
  CC     fugue.o
  CC     hamsi.o
  CC     panama.o
  AR     libsph.a
make[2]: uscita dalla directory "/home/dmr/Mining/sph-sgminer/sph"
make[2]: ingresso nella directory "/home/dmr/Mining/sph-sgminer"
  CC     sgminer-sgminer.o
sgminer.c: In function ‘set_difficulty_multiplier’:
sgminer.c:1065:35: warning: comparison of distinct pointer types lacks a cast [enabled by default]
sgminer.c: In function ‘app_restart’:
sgminer.c:3179:2: warning: passing argument 2 of ‘execv’ from incompatible pointer type [enabled by default]
/usr/include/unistd.h:564:12: note: expected ‘char * const*’ but argument is of type ‘const char * const*’
  CC     sgminer-api.o
  CC     sgminer-util.o
  CC     sgminer-sha2.o
  CC     sgminer-logging.o
  CC     sgminer-driver-opencl.o
  CC     sgminer-ocl.o
  CC     sgminer-findnonce.o
  CC     sgminer-adl.o
  CC     sgminer-scrypt.o
  CC     sgminer-darkcoin.o
  CC     sgminer-qubitcoin.o
  CC     sgminer-quarkcoin.o
  CC     sgminer-myriadcoin-groestl.o
  CC     sgminer-fuguecoin.osudo make
  CC     sgminer-inkcoin.o
  CC     sgminer-animecoin.o
  CC     sgminer-groestlcoin.o
  CC     sgminer-sifcoin.o
  CC     sgminer-twecoin.o
  CC     sgminer-marucoin.o
  CCLD   sgminer
make[2]: uscita dalla directory "/home/dmr/Mining/sph-sgminer"
make[1]: uscita dalla directory "/home/dmr/Mining/sph-sgminer"
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: Semedisenape on May 09, 2014, 06:42:41 pm
So then:

Code: [Select]
[18:35:39] Started sgminer 4.1.0-103-g00015
[18:35:40] ATI ADL Overdrive6's API is missing or broken.

[18:35:39] Started sgminer 4.1.0-103-g00015
[18:35:40] ATI ADL Overdrive6's API is missing or broken.
[18:35:40] Kernel groestlcoin is experimental.
[18:35:41] Error -11: Building Program (clBuildProgram)
[18:35:41] /usr/local/sph-sgminer/bin/groestl.cl(107): warning: type qualifier
specified
          more than once
  __constant static const sph_u64 T0[] = {
                    ^

/usr/local/sph-sgminer/bin/groestl.cl(107): error: a global-scope declaration

[18:35:41] Failed to init GPU thread 0, disabling device 0
[18:35:41] Restarting the GPU from the menu will not fix this.
[18:35:41] Try restarting sgminer.

Restart:
Code: [Select]
[18:40:36] Failed to reinit GPU thread 0
[18:40:36] Thread 0 no longer exists
[18:40:36] Thread 1 no longer exists
[18:40:36] Thread 2 no longer exists
[18:40:36] Thread 3 no longer exists
[18:40:36] Kernel groestlcoin is experimental.
[18:40:37] Error -11: Building Program (clBuildProgram)
[18:40:37] /usr/local/sph-sgminer/bin/groestl.cl(107): warning: type qualifier
specified
          more than once
  __constant static const sph_u64 T0[] = {
                    ^

/usr/local/sph-sgminer/bin/groestl.cl(107): error: a global-scope declaration

[18:40:37] Failed to reinit GPU thread 0

In sph-sgminer they wrote:
Code: [Select]
Error -11: Building Program (clBuildProgram) - execute miner from the directory where "kernel" directory is present
But that is my directory.

Thanks a lot.
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: srcxxx on May 09, 2014, 11:05:27 pm
Hi!

This seems to me that you have a too old / too new AMD driver.

Perhaps try BAMT?

ALso, sgminer has its official support forum. I definitely have seen the duplicate "const" error there.

I'd recommend that you check here: https://bitcointalk.org/index.php?topic=475795.0
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: jackielove4u on May 10, 2014, 12:58:53 am
hi,

what catalyst version did u install? Can u post ur config here.

Try this:
1. Reinstall/upgrade/downgrade to catalyst 13.12
2. After catalyst upgrade, run sudo aticonfig --adapter=all --initial -f and reboot
3. Check that aticonfig detects card properly, and reinstall AMD-APP-SDK 2.9
4. Re-compile sph-sgminer

Otherwise try BAMT or Windows 8.1 (i can have a look with teamviewer if needed).
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: Semedisenape on May 10, 2014, 02:26:43 pm
Thanks guys.
After that I have read I think that you are right.

I'm on Xubuntu 12.04 with ADM 11.11 that was OK for scrypt mining and keccak,
but too old for groestl.

Now I try to update to 13.9. Do you think 13.12 are better?
I've got HD 5970 and 2x5870.
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: jackielove4u on May 10, 2014, 02:40:43 pm
I recommend using 13.12, it is considered more stable.
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: Semedisenape on May 11, 2014, 11:40:21 pm
[SOLVED] My problem was the driver.
With 14.4 and amd app sdk 2.9 everything works fine.

Once question. My cpu with sph-sgminer works more than cgminer.
Can I make something for it?
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: child_harold on May 12, 2014, 11:01:25 am
I dont think you can reduce cpu footprint of sph - maybe someone knows better…
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: jackielove4u on May 13, 2014, 04:21:12 pm
I have prepared a PDF guide, shortly to be uploaded to site server.
In the meantime you can get it here:
https://mega.co.nz/#!AFxziaoR!TyIyMn34EI3b7Gu2_hHQqkqH4CjWcygHQbGN99Yq8hU

Great pdf!

Some suggestions:
i would insert these into the bat:
--difficulty-multiplier 0.00390625

and i would remove this one:
--lookupgap 2

Optional:
setx GPU_MAX_HEAP_SIZE 50
--no-submit-stale (depens of pool)
--failover-only -o stratum+tcp://pool:port -u username.workername -p password (always setup a backup server)
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: bbbbbb2014 on May 14, 2014, 12:31:08 am
I have prepared a PDF guide, shortly to be uploaded to site server.
In the meantime you can get it here:
https://mega.co.nz/#!AFxziaoR!TyIyMn34EI3b7Gu2_hHQqkqH4CjWcygHQbGN99Yq8hU

Hi there!

For some reason, I am not able to push R9 280x pass 6.4 MHash/s mark. I am using the following miner:

https://github.com/badman74/sph-sgminer

I am not able to use your suggested miner as it does not submit any shares at dwarfpool.com. The machine hashes and hashes - AND EVEN IF I MINE with your miner and your suggested settings, I cannot push it over 6.3 MHash/s mark.

The card is in good shape, I have always able to push it when mining Scrypt. GPU clock is set to 1100, mem clock is set to 1500.

Settings I use, are:
    "auto-fan" : true,
    "gpu-fan": "30-99",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "79",
    "worksize": "256",
    "intensity" : "20",
    "gpu-threads" : "1",
    "thread-concurrency" : "8192",
    "lookup-gap" : "0",
    "vectors" : "1",
    "shaders" : "2048",
    "api-port": "4028",
    "api-listen": true,
    "api-allow": "W:127.0.0.1",
    "failover-only" : true,
    "no-pool-disable": true,
    "no-submit-stale" : true,
    "queue": "0",
    "log" : "5",
    "gpu-powertune" : "20",
    "algorithm" : "groestlcoin",


Iam using BAMT 1.6.0 and I have compiled miners from scratch without any problems. The card is not overheating and I have a good PSU.
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: bbbbbb2014 on May 14, 2014, 12:38:56 am
I have prepared a PDF guide, shortly to be uploaded to site server.
In the meantime you can get it here:
https://mega.co.nz/#!AFxziaoR!TyIyMn34EI3b7Gu2_hHQqkqH4CjWcygHQbGN99Yq8hU

And very similar -  HD 5850 was cited to hash at 6 MHash/s speeds. Once again - I cannot push it over 5.4 MHash/s mark.

    "auto-fan" : true,
    "gpu-fan": "30-99",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "79",
    "worksize": "256",
    "xintensity" : "182",
    "gpu-threads" : "2",
    "thread-concurrency" : "6144",
    "lookup-gap" : "2",
    "vectors" : "1",
    "shaders" : "1440",
    "api-port": "4028",
    "api-listen": true,
    "api-allow": "W:127.0.0.1",
    "failover-only" : true,
    "no-pool-disable": true,
    "no-submit-stale" : true,
    "queue": "0",
    "log" : "5",
    "gpu-powertune" : "20",
    "algorithm" : "groestlcoin",
    "kernel-path": "/usr/local/bin"


Core speed is 850, mem speed is 1000. Once again - platform BAMT 1.6.0, good quality card and a PSU.
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: child_harold on May 14, 2014, 09:10:57 am
[Copied from my btctalk answer to same Q]

1.If u are experiencing difficulty running suggested/latest miner pls try this tip from the official FAQ:
http://www.groestlcoin.org/faq/

Quote
My AMD GPU is hashing, but no shares are accepted and I don't see my hashrate on the pool. What's wrong?
Try adding

--difficulty-multiplier 0.0039062500

parameter to your sgminer command line. If your sgminer reports unrecognized option – please update to the recent version from here If this doesn’t help – report the problem in bitcointalk thread

Apologies for not including this tip in the tutorial. Will update pdf soon.


2. What core-clock speed r  u running? Have you used TrixX or AFterburner to overclock core and underclock mem as described in the pdf?

thanks
CH



Download my complete guide for Groestlcoin AMD mining from the official GRS Forum:
http://groestlcoin.org/forum/index.php?topic=23.0

THX!

Hi there!

For some reason, I am not able to push R9 280x pass 6.4 MHash/s mark. I am using the following miner:

https://github.com/badman74/sph-sgminer

I am not able to use your suggested miner as it does not submit any shares at dwarfpool.com. The machine hashes and hashes - AND EVEN IF I MINE with your miner and your suggested settings, I cannot push it over 6.3 MHash/s mark.

The card is in good shape, I have always able to push it when mining Scrypt. GPU clock is set to 1100, mem clock is set to 1500.

Settings I use, are:
    "auto-fan" : true,
    "gpu-fan": "30-99",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "79",
    "worksize": "256",
    "intensity" : "20",
    "gpu-threads" : "1",
    "thread-concurrency" : "8192",
    "lookup-gap" : "0",
    "vectors" : "1",
    "shaders" : "2048",
    "api-port": "4028",
    "api-listen": true,
    "api-allow": "W:127.0.0.1",
    "failover-only" : true,
    "no-pool-disable": true,
    "no-submit-stale" : true,
    "queue": "0",
    "log" : "5",
    "gpu-powertune" : "20",
    "algorithm" : "groestlcoin",


Iam using BAMT 1.6.0 and I have compiled miners from scratch without any problems. The card is not overheating and I have a good PSU.

Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: bbbbbb2014 on May 14, 2014, 03:08:39 pm
It seems that only AMD drivers could be the problem, albeit I am running 13.25 drivers already. I'd like to recompile drivers with 13.xx latest drivers. But no 13.25 (or other stable drivers) are available from AMDs site. Only 14.40 drivers are avail<ble, but people are reporting loosing hashes instead of gaining them...

So, where are latest 13.xx drivers?

2. What core-clock speed r  u running? Have you used TrixX or AFterburner to overclock core and underclock mem as described in the pdf?

thanks
CH



Download my complete guide for Groestlcoin AMD mining from the official GRS Forum:
http://groestlcoin.org/forum/index.php?topic=23.0

THX!

Hi there!

For some reason, I am not able to push R9 280x pass 6.4 MHash/s mark. I am using the following miner:

https://github.com/badman74/sph-sgminer

I am not able to use your suggested miner as it does not submit any shares at dwarfpool.com. The machine hashes and hashes - AND EVEN IF I MINE with your miner and your suggested settings, I cannot push it over 6.3 MHash/s mark.

The card is in good shape, I have always able to push it when mining Scrypt. GPU clock is set to 1100, mem clock is set to 1500.

Settings I use, are:
    "auto-fan" : true,
    "gpu-fan": "30-99",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "79",
    "worksize": "256",
    "intensity" : "20",
    "gpu-threads" : "1",
    "thread-concurrency" : "8192",
    "lookup-gap" : "0",
    "vectors" : "1",
    "shaders" : "2048",
    "api-port": "4028",
    "api-listen": true,
    "api-allow": "W:127.0.0.1",
    "failover-only" : true,
    "no-pool-disable": true,
    "no-submit-stale" : true,
    "queue": "0",
    "log" : "5",
    "gpu-powertune" : "20",
    "algorithm" : "groestlcoin",


Iam using BAMT 1.6.0 and I have compiled miners from scratch without any problems. The card is not overheating and I have a good PSU.

Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: jackielove4u on May 14, 2014, 03:25:01 pm
So, where are latest 13.xx drivers?

http://geeko.ioda.net/mirror/amd-fglrx/raw-src/
Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: commandrix on June 20, 2014, 04:02:50 pm
Mining GroestlCoin for beginners using SPH4SGMiner (AMD)

Greetings miners and welcome into the world of Groestl, an advanced hashing
algorithm.
What is Grøstl?
This new algorithm has many new advantages; it provides a very efficient way
to mine coins. In fact, the Grøstl algorithm requires NOTICEABLY less power;
thus produces a lot less heat. It also improves the lifetime of your mining
hardware because of the previous 2 advantages.
With the summer approaching, Grøstl will become very handy and will have
you save a ton of money over power and cooling. It is new, revolutionary and
the coin that brought it to life is GroestlCoin. Backed by a strong community,
this algorithm has many advantages.
Grøstl is unlike any other algos in the SHA4family. The Grøstl algo has a unique
similarity to AES compared to other algos, allowing devices with AES
Acceleration implementations (e.g. AES4NI for Intel and NEON for ARM) to
provide dramatic improvements when hashing Grøstl.
The humorous name is a play on words meaning Hash (hashed browns) in
Austrian. The word Grøstl is spelt with a Danish ø, because the Grøstl Team is a
'hash' of Danish and Austrian cryptographers.
How can I mine it?
To begin mining GrøstlCoin you need to subscribe to a pool.
To find pools for your Grøstl coin of your choice, you can select from the
available pools in the Official Pool list of the forum. On this guide, we will use
grs.cryptohunger.com which offers reliability and good support. 
You also need to setup a miner, or mining software on your computer that you
will be mining with. We will only show how to mine with some models of the
latest AMD cards, which are usually the standard in mining. Some might have
older GPUs, the settings will differ a lot. Please consult our database of device
settings if yours is not mentioned below.
Once you acquired the miner, and registered on a pool, you will need to
configure your miner. We will cover that later.
 
Registering on a pool
First, you should start by registering at grs.cryptohunger.com. On the top4right,
you will see a drop4down menu. Simply go over there and select register.
Enter all the required information, select a complex password, and also a PIN.
You will need that NIP later to withdraw your coins or change settngs in your
accounts.

Creating workers

In order for your mining software to reach the pool and starts mining, you
need to have “workers”. Different workers should be used for each of your
mining rigs.
Log in the pool, and select the “My Workers” link under the My Account tab.
When creating your workers, make sure NOT to use the same password you
use for your account.
The worker passwords do not need to be too crazy as they can be seen by the
pool administrators and are transmitted in plain text. The “worse” thing that
could happen, if somebody has your worker password, is that he could mine on
your worker. Basically, that would credit YOU for whatever he mines on YOUR
workers, so no worry here you can use any password there.
Your workers will be used in your mining software combined with your pool
username. If your username is joeblow123 and your worker is miner1 with a
password like pass1, the string you would use as your username in your mining
configuration would be joeblow.123 .
 
Mining software
In order to mine GroestlCoin, you will need to use a compatible mining
software. We recommend using sph4sgminer 4.1.0 and up, as it supports the
GroestlCoin (Grøstl) kernel.
Here is a couple of links where you can grab SPH4SGMINER and download it to
your PC:
 
      Official Forum Thread: h`ps://bitcointalk.org/index.php?
topic=475795.0
     
Quote
Windows (SPH): 

h`ps://mega.co.nz/# ftAYgiDbT
8dQtGr2H5C5JKbH9ljUn7oHzB9ij3If7HFCKmSEFw48 
      Windows (Regular) : h`p://www.sgminerwindows.com/ 
      Linux Source (SPH): h`ps://github.com/pre`yhatemachine/sph4
sgminer 
      Linux Source (Regular): h`ps://github.com/sgminer4dev/sgminer 
 

Install AMD Catalyst Control Center

First you must install the correct driver and version of Catalyst Control Center
for your GPU. Installing CCC also installs the OpenCL libraries required for
mining. Use the AMD support page to identify to software version you require:
h`p://support.amd.com/en4us/download
 
Install TrixX 
Download and install Sapphire TrixX (or MSI Afterburner). This software will
allow you to over/under clock your GPU core4clock and memory clock speed. It
will also display your current (default) clock settngs. You need this information
to configure SPH4SGMiner.
You can download Trixx from: h`ps://www.sapphireselectclub.com/ssc/Triftft/
You can download Afterburner from: h`p://event.msi.com/vga/afterburner/
download.htm
 
Configuring SPH-SGMiner
Extract the downloaded zip file wherever you want on your computer. Once
you have a sgminer folder, you can start preparing your BATCH file. This will
start the miner along with your desired configuration proper to the mining
hardware you are using.
Open NOTEPAD, and start creating your batch executable. Some fields will
require modifications; we will cover that after this step.
Start by pasting the following:
You will need to replace USERNAME.WORKERNAME with the username and
worker you have setup earlier on the pool. Returning to our example, we
would be entering “4u joeblow.123 4p pass1”
The thread-concurrency, I, lookup-gap, workersize, g, gpu-engine and gpumemclock
settngs will differ depending on the model of video card you are
using for mining. Use the table below to find basic settngs for different types
of cards. Check in Trixx to make sure (same GPU model may vary).
Save the .txt file as ”sgstart.bat” and make sure to save it in your SGMINER’s
folder. You can create a shortcut from there to your desktop, but the BATCH file
has to be in sgminer’s folder. Now that you are all set, you can start mining 
Simply double click your sgstart.bat file and enjoy mining Grøstl 
Quote
setx GPU_MAft_ALLOC_PERCENT
100

setx GPU_USE_SYNC_OBJECTS
1

sgminer.exe --kernel groestlcoin -o stratum+tcp://
cryptohunger.com:3333 -u USERNAME.WORKERNAME -p
WORKERPASSWORD --thread-concurrency 8192 -I 20 --lookupgap
2 -- worksize 256 -g 1 --gpu-engine 1100 --gpumemclock
1500 --gpu- powertune 20

 
AMD GPU Model Settings
For a detailed list see here
 
"
 
Once you get going, you can then further tweak your settngs. The relevant
ones are Intensity, Coreclock and Memclock settngs. 
WARNING'
Changing your AMD GPU’s default clock settngs should be done using Trixx or
MSI Afterburner before editing your .bat accordingly. Editing the .bat without
using over4clocking software may harm your GPU and result in errors

Model Hashrate Settings
Quote
2ti0x ~11MH/s
 I#20# w#256#  lookup gap#2#  thread concurrency#81ti2#  gpu #
powertune#20#  gpu engine#ti70#  gpu memclock#1400
2ti0 ~tiMH/s 4I 20 4g 1 4w 256 44gpu4engine 1100 —gpu4memclock 1500 44thread4
concurrency 22400 44gpu4 powertune 20
280x ~7MH/s 4I 20 4g 1 44thread4concurrency 81ti2 44gpu4engine 1100 44gpu4
memclock 1500 4w 256 44gpu4 powertune 20
7ti50 ~5.5MH/s
 I#20# g#1#  thread concurrency#22400#  gpu engine#1100#  gpu
memclock#1000# w#256#  gpu #powertune#20
5770 ~3.2MH/s
 I#20# g#1#  thread concurrency#81ti2#  gpu engine#850#  gpu
memclock#1250# w#128#  gpu #powertune#20
To make sure your miner is properly configured, you need to check in your
miner if you are gettng hardware errors. This can be seen as HW:0 in sgminer,
which would be a good sign.
If you ever get HW errors, turn of the machine immediately and contact us in
the forum or on IRC. Bad hardware will also produce those errors, but most of
the time it’s related to configuration settngs.
*Note: A lot of people who paste their config settngs from Scrypt4configs
might experience a lot of HW errors. You will need to lower down your
memclock speed until you see it is stable. You then raise the Coreclock slowly
upwards. Try to add small amounts at the time. If you fiddle with your settngs
enough, you might get decent hashpower gains out of it.
Compared to scrypt, Grøstl has increased hashrate. You want to aim for; 
Quote
Rti 2ti0x ~ 11.5Mh/s

Rti 2ti0 ~ tiMh/s

Rti 280x ~7Mh/s                                                                                                   
HD7ti50 ~ 5.5Mh/s
What might get you confused is the low number of accepts. This is normal and
your WU should be really low.
 
Multiple GPU Settings
If you have more than one AMD card you will need to add extra commands
after commas. In the example below we have created a command for two 280x
cards. See how it differs to the one above.
Quote
setx GPU_MAft_ALLOC_PERCENT
100

setx GPU_USE_SYNC_OBJECTS
1

sgminer.exe --kernel groestlcoin -o stratum+tcp://
cryptohunger.com:3333 -u USERNAME.WORKERNAME -p
WORKERPASSWORD --thread-concurrency 8192, 8192 -I 20, 20
--lookup-gap 2, 2 -- worksize 256, 256 -g 1, 1 --gpuengine
1100, 1100 --gpu-memclock 1500, 1500 --gpu-
powertune 20, 20

So now if I add a third 280x to my rig the command would looks like:
Quote
setx GPU_MAft_ALLOC_PERCENT
100

setx GPU_USE_SYNC_OBJECTS
1

sgminer.exe --kernel groestlcoin -o stratum+tcp://
cryptohunger.com:3333 -u USERNAME.WORKERNAME -p
WORKERPASSWORD --thread-concurrency 8192, 8192, 8192 -I
20, 20, 20 --lookup-gap 2, 2, 2 -- worksize 256, 256, 256
-g 1, 1, 1 --gpu-engine 1100, 1100, 1100 --gpu-memclock
1500, 1500, 1500 --gpu- powertune 20, 20, 20
Remember these settngs differ for every model of card.
If you are using different models of GPU you need to determine what ORDER
the cards go in when writing your command (does my 5770 come before or
after my 280x when creating this command?, for example)
sgminer.exe -n
This will show you your cards labelled 0, 1 , 2 etc. and the order your gpu
commands should go in.
 
 
The conf file
Instead of issuing the command above some users prefer to create/edit a .conf
file. The conf file is created in the SGMiner folder just like the bat was using
Notepad. The bat command changes to point at the conf file, like this:
 
Quote
setx GPU_MAft_ALLOC_PERCENT
100

setx GPU_USE_SYNC_OBJECTS
1

sgminer.exe -c name-of-your.conf
 
Using a conf makes it is easier to gain granular control over your cards.  The
configuration (conf) file for a single 280x should something look like this
(depending on which 280x you have):
 
 
From the GroestlCoin Team

Quote
{
"pools" : [
  {
    "url" : "stratum+tcp://first-pool.com:3333",
    "user" : “your.worker”,
    "pass" : “your pass”
  },
  {
    "url" : "stratum+tcp://backup-pool1.com:3333",
    "user" : “your.worker”,
    "pass" : “your pass”  }
],
 "
kernel" : “groestlcoin”
"intensity" : “20, 20”,
"thread-concurrency" : “8192, 8192”,
"lookup-gap" : “2, 2",
"worksize" : “256, 256",
"gpu-engine" : “1100, 1100",
"gpu-fan" : “0-85, 0-85”,
"gpu-memclock" : “1500, 1500”,
"gpu-threads" : “2, 2",
"gpu-powertune" : “20, 20”,
"temp-cutoff" : “83, 83",
"temp-overheat" : “80, 80",
"temp-target" : “70, 70",
 "
auto-fan" : true,
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"log" : "5",
"queue" : "4",
"scan-time" : "40",
"temp-hysteresis" : "3",
"no-submit-stale" : true

 
 
Copy/Paste the above into a Notepad file and save it as whatever.conf. Edit the
pool, backup pool and gpu information accordingly. As before a multi4gpu conf
will have extra commands after commas. This is not necessary for every
parameter as you’ll observe:
 
 
Quote
{
"pools" : [
  {
    "url" : "stratum+tcp://first-pool.com:3333",
    "user" : “your.worker”,
    "pass" : “your pass”
  },
  {
    "url" : "stratum+tcp://backup-pool1.com:3333",
    "user" : “your.worker”,
    "pass" : “your pass”  }
],
 "
kernel" : “groestlcoin”
"intensity" : “20”,
"thread-concurrency" : “8192”,
"lookup-gap" : "0",
"worksize" : “256",
"gpu-threads" : "2",
"gpu-engine" : "1100",
"gpu-fan" : “0-85",
"gpu-memclock" : "1500”,
"gpu-powertune" : “20”,
"temp-cutoff" : "83",
"temp-overheat" : "80",
"temp-target" : "70",
 "
auto-fan" : true,
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"log" : "5",
"queue" : "4",
"scan-time" : "40",
"temp-hysteresis" : "3",
"no-submit-stale" : true
 }
 

We hope all those informations were enough to get you going. Our mining
community is very active, and are always helpful to beginners,
Happy mining

From the GroestlCoin Team

Title: Re: Beginners Guide to Mining GroestlCoin with AMD cards and SPH-SGMiner
Post by: klarakos on August 05, 2014, 08:40:46 am
Hi!

This seems to me that you have a too old / too new AMD driver.

Perhaps try BAMT?