Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: Wolf0 on August 29, 2016, 09:34:25 AM



Title: Wolf's XMR GPU Miner
Post by: Wolf0 on August 29, 2016, 09:34:25 AM
NaN.


Title: Re: Wolf's XMR GPU Miner
Post by: adaseb on August 29, 2016, 10:39:47 AM
Is there an executable file somewhere?

From what I recall, speeds are exactly the same as Claymore but no 2.5% fee, correct?


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on August 29, 2016, 11:10:47 AM
https://github.com/wolf9466/wolf-xmr-miner/releases (https://github.com/wolf9466/wolf-xmr-miner/releases)

On my test rig wolf is -10% to claymore but also consuming 33% less power. Haven't done any tweaking yet just some quick tests.


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on August 29, 2016, 03:15:14 PM
https://github.com/wolf9466/wolf-xmr-miner/releases (https://github.com/wolf9466/wolf-xmr-miner/releases)

On my test rig wolf is -10% to claymore but also consuming 33% less power. Haven't done any tweaking yet just some quick tests.

You'll wanna play with rawintensity - should get close to equal, at least on Hawaii and up.

Does your miner still need 15.7.1 drivers to work well? Also is there a switch to reduce cpu load? It is killing my E8400 with 15.12 drivers + win 7x64. Playing with hawaii's.

That another miner has no problems and is bloody fast. Looks like memory manufacturer matters a lot.


Title: Re: Wolf's XMR GPU Miner
Post by: grrrgrrr on August 29, 2016, 03:18:31 PM
How much did you get out of Hawaii stock?
With

"rawintensity": 1024,
"worksize": 8

I ended up at 630h/s and then went back to eth mining. (elpida  :-\)

Edit: but nice job wolf0.


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on August 29, 2016, 03:43:24 PM
How much did you get out of Hawaii stock?
With

"rawintensity": 1024,
"worksize": 8

I ended up at 630h/s and then went back to eth mining. (elpida  :-\)

1408,8@1100/1500 gave closer to 800 but that was no fair test because of that high load on weak cpu.

If you after best profit today this probably isn't your thing...

-edit- on 290x


Title: Re: Wolf's XMR GPU Miner
Post by: Subw on August 29, 2016, 04:52:14 PM
I figured I'd create a thread for this, even though it's been out for a while, because XMR's getting so much attention again - and so people know there's an alternative if they'd like to GPU mine (at least for now on Linux) - this was fully written by me originally and under the MIT license (not infected with the GPL in any way.) More work on it was done by hyc later, which I merged. Anyways, git is here:

https://github.com/wolf9466/wolf-xmr-miner

thanks for miner


Title: Re: Wolf's XMR GPU Miner
Post by: niksdt101 on August 29, 2016, 06:11:43 PM
@wolf or @all can anyone compile the wolfs miner for windows 64bit , my code machine is down and really love to mine XMR now


Title: Re: Wolf's XMR GPU Miner
Post by: deferson on August 29, 2016, 06:24:40 PM
Please example for videocard


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on August 29, 2016, 07:45:41 PM
290x is doing 850 with claymores miner with powersaver settings. And so do some 390 cards.


Title: Re: Wolf's XMR GPU Miner
Post by: snowyNNN on August 30, 2016, 06:08:17 AM

I didn´t manage to get any mining software functioning...except Using Minergate app my hd7950 mines at 180 H/s.
It should mine better, right! Is anyone using hd7950? How many hashes are you getting?


Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on August 30, 2016, 08:14:23 AM
hd7970 /// kminer /// @1000c/1500m /// 593h/s


Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on August 31, 2016, 08:52:25 AM
hd7970 /// kminer /// @1000c/1500m /// custom vrom /// 620.9h/s


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on August 31, 2016, 06:57:14 PM
https://github.com/wolf9466/wolf-xmr-miner/releases (https://github.com/wolf9466/wolf-xmr-miner/releases)

On my test rig wolf is -10% to claymore but also consuming 33% less power. Haven't done any tweaking yet just some quick tests.

You'll wanna play with rawintensity - should get close to equal, at least on Hawaii and up.

So 700-800h/s for a 290X?  Maybe I'll give it a try since Monero seems to have eclipsed Sia as the hot coin to mine.


Title: Re: Wolf's XMR GPU Miner
Post by: BTCBusinessConsult on August 31, 2016, 07:13:33 PM
Why is there so much hate between you and claymore?

Mad he gets more people using his program than yours? Seriously curious.

I spent 30 mins trying to figure out how to compile your miner and make it work, whereas he has an .zip. One of the main reasons i use his... ease of entry and use.


Title: Re: Wolf's XMR GPU Miner
Post by: Hardstyles on August 31, 2016, 07:32:02 PM
hello i become an error maybe

Win 7 64Bit

https://picload.org/image/rrpppolo/unbenannt.png


Title: Re: Wolf's XMR GPU Miner
Post by: cryptomanman on August 31, 2016, 08:28:10 PM
I'm having a difficult time compiling this program. It stops out with an error saying it can't find CL/cl.h. That file is in my AMD SDK directory. Why can't it find it?  Also what version of gcc should I have to compile this?

My machine is
Intel 64bit
Ubuntu 14.04 LTS
kernel 3.19 as this is the latest kernel I can get the AMD drivers to install on

Thanks!


----- Update 1 of 2-----

Okay. I finally go it to compile by installing gcc 4.9 and following the instructions at http://superkuh.com/monero.html

Now the problem I'm having is:

./miner xmr.conf
[16:23:18] Setting up GPU(s).
Segmentation fault (core dumped)

I don't see a log file. So, I don't don't know where to go from here.

----- Update 2 of 2-----

Okay, the segfault is a similar problem I have with the claymore miner. If the miner is started and stops for any reason, I have to reboot before trying it again. 1 start per reboot is all I get.

Now I need to find the optimal settings for my HD 7970. What have others found? Right now I'm using
"corefreq": 500,
"memfreq": 1200,
"fanspeed": 80,
"powertune": 20,
"threads": 1,
"rawintensity": 1024,
"worksize": 16

and getting about 435 H/s.  On claymore's miner I was about 480 H/s.  I this about as good as I'm going to get?  Not complaining!


Title: Re: Wolf's XMR GPU Miner
Post by: BTCBusinessConsult on August 31, 2016, 10:16:29 PM
Why is there so much hate between you and claymore?

Mad he gets more people using his program than yours? Seriously curious.

I spent 30 mins trying to figure out how to compile your miner and make it work, whereas he has an .zip. One of the main reasons i use his... ease of entry and use.

I don't hate Claymore - me and him are fine. It's the kminer bullshit that's only a ripoff of Claymore's that I hate.

Oh sorry I misunderstood.

If you made an easy .exe or .zip of your miner id run it 50/50 ;)


Title: Re: Wolf's XMR GPU Miner
Post by: niksdt101 on September 01, 2016, 04:14:40 AM
Why is there so much hate between you and claymore?

Mad he gets more people using his program than yours? Seriously curious.

I spent 30 mins trying to figure out how to compile your miner and make it work, whereas he has an .zip. One of the main reasons i use his... ease of entry and use.

I don't hate Claymore - me and him are fine. It's the kminer bullshit that's only a ripoff of Claymore's that I hate.

Oh sorry I misunderstood.

If you made an easy .exe or .zip of your miner id run it 50/50 ;)

I probably will soon, but there's a bug to fix for newer drivers first.

@wolf once you fix the bug can compile an windows 64 build for me  if you get time ?? it will be really helpfull but anyway keep up the good work


Title: Re: Wolf's XMR GPU Miner
Post by: chefbauer on September 03, 2016, 05:53:02 AM
Is anyone mining with linux?
I tried ubuntu 14.04, 16.04 with both gpupro and old driver.

Videocards testet: 390, 470,480.
Pools tested: dwarfpool

Error in all cases: Lowdifficultyshare
Same Problem with Claymore miner (9.1).

If you mine successfully with linux, please give details!


Title: Re: Wolf's XMR GPU Miner
Post by: adaseb on September 03, 2016, 07:37:56 AM
hd7970 /// kminer /// @1000c/1500m /// custom vrom /// 620.9h/s

Won't this miner get you banned from pools since it submits duplicate shares?


Title: Re: Wolf's XMR GPU Miner
Post by: dephcon on September 03, 2016, 01:09:19 PM
Wolf, I'm having trouble running make.  do you have a list of dependencies or a linux install guide?

I cloned your repo and ran:
Code:
coinhaus@miner002:~/wolf-xmr-miner$ sudo make -f Makefile
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:381:18: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:424:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [-Wincompatible-pointer-types]
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:11:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t * {aka long unsigned int *}’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:10: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
          ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 gpu.c -o gpu.o
gpu.c:6:19: fatal error: CL/cl.h: No such file or directory
compilation terminated.
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 1


Title: Re: Wolf's XMR GPU Miner
Post by: Subw on September 03, 2016, 01:31:34 PM
@dephcon: can't you read: no opencl headers found in your system.


Wolf0 do you have an idea why your miner gives low-diff shares with AMD's radeon pro driver (just my guess maybe other reasons):

Code:
[16:24:05] Setting up GPU(s).
[16:24:10] Successfully connected to pool's stratum.
[16:24:10] New job at diff 5000
[16:24:13] Thread 0, GPU ID 0, GPU Type: Ellesmere: 578.39H/s
[16:24:15] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.51H/s
[16:24:16] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.52H/s
[16:24:17] Share rejected (Low difficulty share): 0/1 (0.00%)
[16:24:17] Total Hashrate: 579.52H/s

[16:24:18] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.76H/s
[16:24:20] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.31H/s
[16:24:22] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.21H/s
[16:24:24] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.31H/s
[16:24:26] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.19H/s
[16:24:26] Share rejected (Low difficulty share): 0/2 (0.00%)
[16:24:26] Total Hashrate: 579.19H/s

[16:24:27] Thread 0, GPU ID 0, GPU Type: Ellesmere: 576.54H/s
[16:24:29] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.26H/s
[16:24:31] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.23H/s
[16:24:33] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.22H/s
[16:24:35] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.13H/s
[16:24:36] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.32H/s
[16:24:38] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.06H/s
[16:24:40] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.08H/s
[16:24:42] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.01H/s
[16:24:44] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.09H/s
[16:24:46] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.03H/s
[16:24:46] Share rejected (Low difficulty share): 0/3 (0.00%)
[16:24:46] Total Hashrate: 579.03H/s

[16:24:47] Thread 0, GPU ID 0, GPU Type: Ellesmere: 579.17H/s
[16:24:48] Share rejected (Low difficulty share): 0/4 (0.00%)
[16:24:48] Total Hashrate: 579.17H/s

[16:24:49] Thread 0, GPU ID 0, GPU Type: Ellesmere: 576.20H/s
[16:24:51] Thread 0, GPU ID 0, GPU Type: Ellesmere: 578.88H/s
[16:24:51] Share rejected (Low difficulty share): 0/5 (0.00%)
[16:24:51] Total Hashrate: 578.88H/s

same errors with Hawaiis on same rig:

Code:
[16:27:21] Thread 1, GPU ID 1, GPU Type: Hawaii: 773.43H/s
[16:27:21] Thread 0, GPU ID 0, GPU Type: Hawaii: 748.79H/s
[16:27:21] Share rejected (Low difficulty share): 1/30 (3.33%)
[16:27:21] Total Hashrate: 1522.22H/s


Title: Re: Wolf's XMR GPU Miner
Post by: sony87 on September 03, 2016, 01:41:47 PM
Can someone post his conf file while mining in Dwarf? There is some authentication issue and is not accepting the format of -u like "exchange-wallet.payment-id.worker" like it's suggested in Dwarf.


Title: Re: Wolf's XMR GPU Miner
Post by: dephcon on September 03, 2016, 03:05:28 PM
@dephcon: can't you read: no opencl headers found in your system.

shouldn't that be included with either the amdgpupro drivers for the application?  I've only had experience installing/using claymore's ETH miner.


Title: Re: Wolf's XMR GPU Miner
Post by: jkminkov on September 03, 2016, 09:50:27 PM
cpu miner last release is missing https://ottrbutt.com/cpuminer-multi/cpuminer-multi-wolf-06-09-2014.zip


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on September 04, 2016, 01:37:25 AM
GPU mining works OK for me so far on Ubuntu 14.04.  With CPU mining the program doesn't terminate properly with ctrl-c, but CPU only gets me 14-15H/s per core.


Title: Re: Wolf's XMR GPU Miner
Post by: gorserg on September 05, 2016, 06:19:17 AM
You have, this a miner for Windows?


Title: Re: Wolf's XMR GPU Miner
Post by: dephcon on September 05, 2016, 12:57:21 PM
I got it working but i'm getting pretty much all rejected shares.  I re-flashed to my stock bios in case i was pushing it too hard but i get the same result:

Code:
[08:37:00] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.51H/s
[08:37:02] Share rejected (Low difficulty share): 0/1 (0.00%)
[08:37:02] Total Hashrate: 474.51H/s

[08:37:03] Thread 0, GPU ID 0, GPU Type: Ellesmere: 471.68H/s
[08:37:05] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.68H/s
[08:37:07] Share rejected (Low difficulty share): 0/2 (0.00%)
[08:37:07] Total Hashrate: 474.68H/s

[08:37:08] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.55H/s
[08:37:11] Thread 0, GPU ID 0, GPU Type: Ellesmere: 477.07H/s
[08:37:13] Thread 0, GPU ID 0, GPU Type: Ellesmere: 471.02H/s
[08:37:16] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.68H/s
[08:37:18] Share rejected (Low difficulty share): 0/3 (0.00%)
[08:37:18] Total Hashrate: 474.68H/s

[08:37:19] Thread 0, GPU ID 0, GPU Type: Ellesmere: 473.54H/s
[08:37:22] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.06H/s
[08:37:24] Thread 0, GPU ID 0, GPU Type: Ellesmere: 473.49H/s
[08:37:27] Thread 0, GPU ID 0, GPU Type: Ellesmere: 474.14H/s
[08:37:30] Thread 0, GPU ID 0, GPU Type: Ellesmere: 473.73H/s
[08:37:31] Share rejected (Low difficulty share): 1/5 (20.00%)
[08:37:31] Total Hashrate: 473.73H/s

[08:37:31] Share rejected (Low difficulty share): 0/5 (0.00%)
[08:37:31] Total Hashrate: 473.73H/s

[08:37:32] Thread 0, GPU ID 0, GPU Type: Ellesmere: 472.88H/s
[08:37:35] Thread 0, GPU ID 0, GPU Type: Ellesmere: 473.35H/s
[08:37:38] Thread 0, GPU ID 0, GPU Type: Ellesmere: 472.54H/s
[08:37:38] Share rejected (Low difficulty share): 0/6 (0.00%)
[08:37:38] Total Hashrate: 472.54H/s

Any ideas why i getting rejected?  thanks


Title: Re: Wolf's XMR GPU Miner
Post by: Subw on September 05, 2016, 01:08:08 PM
Is anyone mining with linux?
I tried ubuntu 14.04, 16.04 with both gpupro and old driver.

Videocards testet: 390, 470,480.
Pools tested: dwarfpool

Error in all cases: Lowdifficultyshare
Same Problem with Claymore miner (9.1).

If you mine successfully with linux, please give details!

Code:
[16:05:41] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.64H/s
[16:05:41] Share accepted: 2629/2629 (100.00%)
[16:05:41] Total Hashrate: 2832.06H/s

[16:05:41] Thread 3, GPU ID 3, GPU Type: Hawaii: 714.15H/s
[16:05:43] Thread 1, GPU ID 1, GPU Type: Hawaii: 752.07H/s
[16:05:43] Thread 0, GPU ID 0, GPU Type: Hawaii: 738.39H/s
[16:05:43] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.67H/s
[16:05:43] Thread 3, GPU ID 3, GPU Type: Hawaii: 701.15H/s
[16:05:45] Thread 1, GPU ID 1, GPU Type: Hawaii: 739.33H/s
[16:05:45] Thread 0, GPU ID 0, GPU Type: Hawaii: 714.50H/s
[16:05:45] Thread 3, GPU ID 3, GPU Type: Hawaii: 690.03H/s
[16:05:46] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.94H/s
[16:05:46] Thread 1, GPU ID 1, GPU Type: Hawaii: 729.70H/s
[16:05:47] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.90H/s
[16:05:47] Thread 3, GPU ID 3, GPU Type: Hawaii: 702.58H/s
[16:05:48] Thread 1, GPU ID 1, GPU Type: Hawaii: 754.54H/s
[16:05:49] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.88H/s
[16:05:49] Thread 3, GPU ID 3, GPU Type: Hawaii: 689.30H/s
[16:05:49] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.76H/s
[16:05:50] Thread 1, GPU ID 1, GPU Type: Hawaii: 754.48H/s
[16:05:51] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.35H/s
[16:05:51] Thread 3, GPU ID 3, GPU Type: Hawaii: 713.95H/s
[16:05:52] Thread 1, GPU ID 1, GPU Type: Hawaii: 754.37H/s
[16:05:52] Thread 2, GPU ID 2, GPU Type: Hawaii: 657.09H/s
[16:05:52] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.35H/s
[16:05:53] Thread 3, GPU ID 3, GPU Type: Hawaii: 701.68H/s
[16:05:54] Thread 1, GPU ID 1, GPU Type: Hawaii: 738.86H/s
[16:05:54] New job at diff 200008
[16:05:54] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.81H/s
[16:05:55] Thread 3, GPU ID 3, GPU Type: Hawaii: 690.16H/s
[16:05:55] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.91H/s
[16:05:56] Thread 1, GPU ID 1, GPU Type: Hawaii: 714.45H/s
[16:05:56] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.74H/s
[16:05:57] Thread 3, GPU ID 3, GPU Type: Hawaii: 714.01H/s
[16:05:58] Thread 1, GPU ID 1, GPU Type: Hawaii: 730.33H/s
[16:05:58] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.41H/s
[16:05:58] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.61H/s
[16:05:59] Thread 3, GPU ID 3, GPU Type: Hawaii: 702.10H/s
[16:06:00] Thread 1, GPU ID 1, GPU Type: Hawaii: 739.33H/s
[16:06:00] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.66H/s
[16:06:01] Thread 3, GPU ID 3, GPU Type: Hawaii: 689.72H/s
[16:06:01] Thread 2, GPU ID 2, GPU Type: Hawaii: 656.81H/s
[16:06:02] Thread 1, GPU ID 1, GPU Type: Hawaii: 714.46H/s
[16:06:02] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.60H/s

this is with ubuntu's fglrx driver.

with new amd's pro driver i also have low-diff share error


Title: Re: Wolf's XMR GPU Miner
Post by: adamvp on September 05, 2016, 01:29:04 PM
I am waiting for Windows version, and have to test or please tell me your hashrate and fees on:
370/280x/380x
Regards ;)


Title: Re: Wolf's XMR GPU Miner
Post by: gegstore on September 05, 2016, 05:05:03 PM
I am waiting for Windows version, and have to test or please tell me your hashrate and fees on:
370/280x/380x
Regards ;)



i too


Title: Re: Wolf's XMR GPU Miner
Post by: willi9974 on September 06, 2016, 09:51:27 PM
at the moment i use the claymore miner, but i will use the wolf miner.

i have the speed from 3,8 kh/s

09/06/16-20:45:59 - New job received from mine.moneropool.com:3333
Speed: 3859 h/s, TotalHashes: 5543K, DevHashes: 137K Mining time: 00:24

how can i configure the wolf windows GPU miner and what are the best settings for a AMD 480'er system with 6 cards




BestRegards
Willi


Title: Re: Wolf's XMR GPU Miner
Post by: chefbauer on September 07, 2016, 09:29:18 AM

Code:
[16:06:02] Thread 1, GPU ID 1, GPU Type: Hawaii: 714.46H/s
[16:06:02] Thread 0, GPU ID 0, GPU Type: Hawaii: 754.60H/s

this is with ubuntu's fglrx driver.

with new amd's pro driver i also have low-diff share error

thank you, i got it to work, was a compilation problem:

Code:
[11:28:15] Thread 0, GPU ID 0, GPU Type: Hawaii: 740.42H/s
[11:28:16] Thread 1, GPU ID 1, GPU Type: Hawaii: 695.44H/s
[11:28:17] Thread 0, GPU ID 0, GPU Type: Hawaii: 740.43H/s
[11:28:17] Share accepted: 74/74 (100.00%)
[11:28:17] Total Hashrate: 1486.46H/s


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on September 07, 2016, 01:32:15 PM
I did a build with gcc6, -O3 -flt0.
https://drive.google.com/file/d/0BwLnDyLLT3Wka2Z4RW5lWUJIaFk/view

Works well for me with R9 380 and R7 370 (fglrx driver).


Title: Re: Wolf's XMR GPU Miner
Post by: Mictlantecuhtli on September 07, 2016, 02:49:56 PM
Can someone post his conf file while mining in Dwarf? There is some authentication issue and is not accepting the format of -u like "exchange-wallet.payment-id.worker" like it's suggested in Dwarf.
Code:
"pools":[{
"url": "stratum+tcp://192.168.3.2:8080",
"user": "103",
"pass": "1"

? ;D Maybe proxy https://bitcointalk.org/index.php?topic=735738.0 (https://bitcointalk.org/index.php?topic=735738.0) will help. It seems so to me. I can not check. Windows release does not work for me.


Title: Re: Wolf's XMR GPU Miner
Post by: chefbauer on September 07, 2016, 05:26:39 PM
Can someone post his conf file while mining in Dwarf? There is some authentication issue and is not accepting the format of -u like "exchange-wallet.payment-id.worker" like it's suggested in Dwarf.


Code:
			"pools":
[
{
"url": "stratum+tcp://xmr-eu.dwarfpool.com:9500",
"user": "exchange-wallet.payment-id",
"pass": "x"
}
]


or with worker:
Code:
"user": "exchange-wallet.payment-id.worker",


Title: Re: Wolf's XMR GPU Miner
Post by: Apolo-New-Miner on September 07, 2016, 07:58:54 PM
Hi I'm a beginner at mining .... would like to start mining XMR I have R9380 and r7370 GPUs
using Ubuntu 14.  Is there a setup guide to get me started..

Thanks,

Apolo


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on September 07, 2016, 08:11:01 PM
Hi I'm a beginner at mining .... would like to start mining XMR I have R9380 and r7370 GPUs
using Ubuntu 14.  Is there a setup guide to get me started..

Thanks,

Apolo

http://nerdralph.blogspot.ca/2016/09/monero-mining-on-linux.html


Title: Re: Wolf's XMR GPU Miner
Post by: Termie on September 07, 2016, 10:50:06 PM
"Error -1 when calling clGetDeviceIDs for number of devices."
Using 3 graphic cards. Whats wrong at my config file???

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 1050,
"memfreq": 1250,
"fanspeed": 60,
"powertune": 20,
"threads": 1,
"rawintensity": 1024,
"worksize": 16
},
        {
"index": 1,
"corefreq": 1098,
"memfreq": 500,
"fanspeed": 60,
"powertune": 20,
"threads": 1,
"rawintensity": 1024,
"worksize": 16
},
        {
"index": 2,
"corefreq": 1098,
"memfreq": 500,
"fanspeed": 60,
"powertune": 20,
"threads": 1,
"rawintensity": 1024,
"worksize": 16
}
],
"pools":
[
{
"url": "stratum+tcp://xmr-eu.dwarfpool.com:8100",
"user": "XMRadress.TransactionID",
"pass": "x"
}
]
}
]
}


Title: Re: Wolf's XMR GPU Miner
Post by: Mictlantecuhtli on September 08, 2016, 11:08:28 AM
http://s017.radikal.ru/i436/1609/4a/98d17a663768t.jpg (http://radikal.ru/F/s017.radikal.ru/i436/1609/4a/98d17a663768.jpg.html)


Code:
{

 "Algorithms":
[{
"name": "CryptoNight",
"devices":[{
"index": 0,
                                "rawintensity": 1024,
"worksize": 8
         },
 {
"index": 1,
                                "rawintensity": 1024,
"worksize": 8
         },
 {
"index": 2,
                                "rawintensity": 1024,
"worksize": 8
         },
 {
"index": 3,
                                "rawintensity": 1024,
"worksize": 8
         }
],

"pools":[{
"url": "stratum+tcp://192.168.3.2:8080",
"user": "103",
"pass": "1"
}]
}]
}


Title: Re: Wolf's XMR GPU Miner
Post by: descarte on September 08, 2016, 12:19:30 PM
I tried to compile and could never get it to work. can anyone help?

gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:381:18: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:424:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [-Wincompatible-pointer-types]
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:11:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t * {aka long unsigned int *}’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:10: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
          ^
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 net.c -o net.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 minerutils.c -o minerutils.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 gpu.c -o gpu.o
gcc -I/opt/AMDAPPSDK-2.9-1/include -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11 main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:698:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
                        ^
main.c:698:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1327:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  MyJob = CurrentJob;
        ^
main.c:1335:18: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
   sprintf(ThrID, "Thread %d, GPU ID %d, GPU Type: %s",
                  ^
main.c:1356:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
    MyJob = CurrentJob;
          ^
gcc -pthread -O0 -ggdb3 crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -ldl -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -o miner


Title: Re: Wolf's XMR GPU Miner
Post by: KALRONG on September 08, 2016, 03:52:36 PM
In Debian stretch it compiles without major issues, saddly my rig is running on windows so I can't test the latest version :(

How can I generate the exe to test it in windows?

Thanks in advance!


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on September 08, 2016, 04:30:33 PM
I tried to compile and could never get it to work. can anyone help?
gcc -pthread -O0 -ggdb3 crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -ldl -L/opt/AMDAPPSDK-2.9-1/lib/x86_64/ -o miner

There's no errors from gcc, just warnings.  What happens when you run miner?


Title: Re: Wolf's XMR GPU Miner
Post by: Mictlantecuhtli on September 08, 2016, 05:18:28 PM
How can I generate the exe to test it in windows?

You need "Internet explorer" compiler  :D
https://github.com/wolf9466/wolf-xmr-miner/releases/ (https://github.com/wolf9466/wolf-xmr-miner/releases/)


Title: Re: Wolf's XMR GPU Miner
Post by: Cryptozillah on September 08, 2016, 05:38:27 PM
Hashrate on the 480 8Gb ?


Title: Re: Wolf's XMR GPU Miner
Post by: 64dimensions on September 09, 2016, 05:42:17 AM
Guys,

I'm blocked by this:

Setting up GPU(s).
Segmentation fault (core dumped)

Rig:

4 - 380 cards
15.10
15.12 AMD drivers
8 gb of memory

I've been rebooting after every change in the xmr.conf file.

The rig works executing CPU mining. I have tried permutations on the settings on the 1st page of this thread, no luck.

I welcome any help.

TIA





Title: Re: Wolf's XMR GPU Miner
Post by: KALRONG on September 09, 2016, 07:39:13 AM
How can I generate the exe to test it in windows?

You need "Internet explorer" compiler  :D
https://github.com/wolf9466/wolf-xmr-miner/releases/ (https://github.com/wolf9466/wolf-xmr-miner/releases/)

Funny, but did you check the dates of those releases? hehe I wanted to actually compile the exe with the latest changes


Title: Re: Wolf's XMR GPU Miner
Post by: FlexiN on September 09, 2016, 03:40:55 PM
Hashrate on the 480 8Gb ?

Would like to know aswell, if i turn my 6 RX480 with XMR or stay with ETH

Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: visdude on September 11, 2016, 08:56:11 PM
I have a couple of 7850s and a 6850 in a couple of W7-64 boxes that I wanna play around with XMR mining.

I"m very bad at CLI and it's associated nuances. Can anybody please come up with an arg that would work with the above cards with this miner? An arg to be used specifically in a shortcut target (it's what I'm used to back in the cgminer/bfgminer days) instead of in a ".bat' file format would be preferable though I think they're similar.

Thank you.



Title: Re: Wolf's XMR GPU Miner
Post by: th00ber on September 11, 2016, 10:07:14 PM
Windows fresh binaries ? :)


Title: Re: Wolf's XMR GPU Miner
Post by: descarte on September 11, 2016, 10:10:39 PM
I had the miner mining fine but after a while, it was hashing but not submitted any shares.. seems like a bug. I have to keep rebooting everytime this happens.

anyone experienced this problem?



Title: Re: Wolf's XMR GPU Miner
Post by: EvilC0P on September 14, 2016, 02:39:46 AM
I tried giving a shot at wolf's new miner but i keep getting "banned IP" when using it.
I have 2 MSI RX 480 but only one seems to be working, Windows 7 driver version is 16.20.1028
Been looking around to know how to make a proper xmr.conf to go for the miner with no luck. I got the pool part but the first part of the config is as follow (which i didn't modify yet ) ;

{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 500,
               "memfreq": 1500,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 640,
               "worksize": 16
            },
            {
               "index": -1,
               "threads": 2,
               "rawintensity": 16,
               "worksize": 16
            }
         ],

the index = does it equal which device # ? i need to make one for each device in my computer?
GPU fan, powertune, and clock setting options = they do nothing according to the readme file so i could just take them off.
rawintensity = 2MiB for every work item , does that mean 2MiB per "worksize" set? my cards have 8GB of ram
is there a command to make sure the GPU is used @ 100% like claymore's?

A quick HowTo and some details about each command would be appreciated.
thanks in advance


Title: Re: Wolf's XMR GPU Miner
Post by: Termie on September 14, 2016, 09:07:58 AM
still doesn´t work.
Always the same "Error -1 when calling clGetDeviceIDs for number of devices." with v0.4 (Win 7 64 Bit, Crimson 15.12).
Equal if I add one or all GPUs at xmr.conf. Getting the same error message even if I select only "index": -1 for CPU mining - lol. ::)
Is there any additional software required to run this miner, like AMD SDK or so?


Title: Re: Wolf's XMR GPU Miner
Post by: ylpkm on September 14, 2016, 10:37:50 AM
still doesn´t work.
Always the same "Error -1 when calling clGetDeviceIDs for number of devices." with v0.4 (Win 7 64 Bit, Crimson 15.12).
Equal if I add one or all GPUs at xmr.conf. Getting the same error message even if I select only "index": -1 for CPU mining - lol. ::)
Is there any additional software required to run this miner, like AMD SDK or so?

Im also getting Error -1, rx 480 on 15.8 and 16.9.1 driver. index -1 for cpu works though.


Title: Re: Wolf's XMR GPU Miner
Post by: ylpkm on September 14, 2016, 11:32:46 AM

Post settings conf, please.
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity":1024,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://krb.suprnova.cc:7777",
               "user": "ylpkm.2",
               "pass": "x"
            }
         ]
      }
   ]
}

i tried various raw intensities from 500-2000 and worksize up to 64.  krb is the last coin i tried, i also tried xmr and still same result.


Title: Re: Wolf's XMR GPU Miner
Post by: c2n14 on September 14, 2016, 12:46:19 PM
RX 470, Win 7-64, 16.9.1
"threads": 1, "rawintensity":1024, "worksize": 8
Mining @ Dwarfpool.
Everything is OK :)


Title: Re: Wolf's XMR GPU Miner
Post by: EvilC0P on September 14, 2016, 01:24:18 PM
I tried giving a shot at wolf's new miner but i keep getting "banned IP" when using it.
I have 2 MSI RX 480 but only one seems to be working, Windows 7 driver version is 16.20.1028
Been looking around to know how to make a proper xmr.conf to go for the miner with no luck. I got the pool part but the first part of the config is as follow (which i didn't modify yet ) ;

{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 500,
               "memfreq": 1500,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 640,
               "worksize": 16
            },
            {
               "index": -1,
               "threads": 2,
               "rawintensity": 16,
               "worksize": 16
            }
         ],

the index = does it equal which device # ? i need to make one for each device in my computer?
GPU fan, powertune, and clock setting options = they do nothing according to the readme file so i could just take them off.
rawintensity = 2MiB for every work item , does that mean 2MiB per "worksize" set? my cards have 8GB of ram
is there a command to make sure the GPU is used @ 100% like claymore's?

A quick HowTo and some details about each command would be appreciated.
thanks in advance

Yes, index is device number. One for each device. Yes, you may take those off. No, it means for every rawintensity value past 0, it uses 2MiB. You actually don't WANT to use the GPU 100%, because that would make it slower. Tune for best hashrate. Try worksize of 8, btw.

thanks for the quick reply Wolf.

if you don't mind, may i ask for a few more clarifications :
index: -1, ; does index has to be 0, 1, 2 , 3 ... depending on how many GPUs there is installed?
threads: 2, ; how to determine the proper amount of threads ?
rawintensity: 16, ; if i understood correctly, 2 x rawintensity has to fit in amount for ram on GPU but also we don't want 100% because it would reduce efficiency
worksize: 16 ; how to determine the proper amount for the worksize ?

thanks again and keep up the good work.

PS : could it be the device -1 causing my IP to get banned by the pool? what's -1 for?


Title: Re: Wolf's XMR GPU Miner
Post by: mysongranhills2 on September 14, 2016, 01:51:15 PM
Am I doing something wrong? I'm getting this output:

Code:
[08:46:10] Setting up GPU(s).
[08:46:10] Error parsing version string from clGetDeviceInfo. This should never happen.
Config:

Code:
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 500,
               "memfreq": 1500,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 640,
               "worksize": 16
            },
            {
               "index": -1,
               "threads": 2,
               "rawintensity": 16,
               "worksize": 16
            }
         ],

I have XFX RX 480 on Windows 10, Radeon soft version 16.7.3 , Driver Packaging Version 16.30.2311-160718a-305076C, OpenCL Version 2.0.6.0.


Any help greatly appreciated.


Title: Re: Wolf's XMR GPU Miner
Post by: mysongranhills2 on September 14, 2016, 02:24:14 PM
Tried it and that change gives the same output:
[09:23:09] Setting up GPU(s).
[09:23:09] Error parsing version string from clGetDeviceInfo. This should never happen.


Title: Re: Wolf's XMR GPU Miner
Post by: c2n14 on September 14, 2016, 02:29:01 PM
Maybe try 16.9.1 drivers?

They're perfect for my Win7-64 and this miner.

Edit: I have RX 470.


Title: Re: Wolf's XMR GPU Miner
Post by: gegstore on September 14, 2016, 02:57:51 PM
low difficulty share, all rejected

this miner is no good the old work best, i am sorry for you


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 14, 2016, 03:17:54 PM
low difficulty share, all rejected
I confirm this.

2X ATI Radeon R9 270X with latest 13.9.1 drivers.
My config:
Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
},
                     {
"index": 1,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
}

]
With new Wolf's XMR GPU Miner version 0.4 I only get "Low difficulty shares, rejected"
With same config and drivers on version 0.3 I have no errors!

Oh, I forgot to say - system is Win7 Ultimate x64

Any suggestions?


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 14, 2016, 04:26:11 PM
low difficulty share, all rejected
I confirm this.

2X ATI Radeon R9 270X with latest 13.9.1 drivers.
My config:
Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
},
                     {
"index": 1,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
}

]
With new Wolf's XMR GPU Miner version 0.4 I only get "Low difficulty shares, rejected"
With same config and drivers on version 0.3 I have no errors!

Oh, I forgot to say - system is Win7 Ultimate x64

Any suggestions?

Try updating drivers - new ones work better with this version.
Oh, excuse me for my mistake - I posted wrong version - I already have latest version 16.9.1 of AMD drivers!


Title: Re: Wolf's XMR GPU Miner
Post by: mysongranhills2 on September 14, 2016, 06:04:29 PM
@Wolf0

Thanks for all your work, is there anything else you'd advise doing in my scenario? I can try different driver version, but what specific version should I try?


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 14, 2016, 06:22:03 PM
low difficulty share, all rejected
I confirm this.

2X ATI Radeon R9 270X with latest 13.9.1 drivers.
My config:
Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
},
                     {
"index": 1,
"corefreq": 1250,
"memfreq": 1250,
"fanspeed": 90,
"powertune": 20,
"threads": 1,
"rawintensity": 511,
"worksize": 8
}

]
With new Wolf's XMR GPU Miner version 0.4 I only get "Low difficulty shares, rejected"
With same config and drivers on version 0.3 I have no errors!

Oh, I forgot to say - system is Win7 Ultimate x64

Any suggestions?

Try updating drivers - new ones work better with this version.
Oh, excuse me for my mistake - I posted wrong version - I already have latest version 16.9.1 of AMD drivers!

Oooh, I might see the issue - your rawintensity is NOT a multiple of your worksize. Try fixing that - if it persists, then open an issue on GitHub, please.
Unfortunately, it did not help.  :(
I tried rawintensity from 500 to 600, but error was the same.

And btw, in yours miner version 0.3 my config with "worksize": 8 and "rawintensity": 511 works perfectly and gaves me 445 h/s on my R9 270X!

So?


Title: Re: Wolf's XMR GPU Miner
Post by: taushet on September 14, 2016, 07:43:07 PM
Great miner.

With a few MSI Gaming X RX 480 @ 1304 on a research rig (Win10), I get identical speeds to Claymore with some RI/WS tinkering: https://i.imgur.com/3RutBrm.png.

One change request: a quiet mode (analagous to -q) whereby only successful shares and total hashrate is reported would be extremely welcome.

Thanks :)


Title: Re: Wolf's XMR GPU Miner
Post by: mysongranhills2 on September 14, 2016, 08:38:55 PM
Tired older drivers 16.20 and still getting the same error that says I should never see it??


Title: Re: Wolf's XMR GPU Miner
Post by: mysongranhills2 on September 14, 2016, 09:58:27 PM
Uninstalled, cleaned and reinstalled 16.20. Same result. :(

Tried Claymore's and was able to get it working @ 615 h/s for what it is worth.

Still hoping to get this one working.


Title: Re: Wolf's XMR GPU Miner
Post by: c2n14 on September 14, 2016, 11:27:52 PM
16.9.1 - Working.


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 14, 2016, 11:36:24 PM
Trying to compile (and looked at the notes on http://superkuh.com/monero.html (http://superkuh.com/monero.html) which by passed me the first couple of issues) but now I'm getting the following:

Code:
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb.c -o crypto/aesb.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_blake256.c -o crypto/c_blake256.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_groestl.c -o crypto/c_groestl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_keccak.c -o crypto/c_keccak.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_jh.c -o crypto/c_jh.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_skein.c -o crypto/c_skein.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [enabled by default]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:2: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [enabled by default]
  keccakf(&ctx->state.hs, 24);
  ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  log.c -o log.o
log.c: In function ‘Log’:
log.c:25:3: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
   ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  net.c -o net.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  minerutils.c -o minerutils.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  gpu.c -o gpu.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
  ^
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1341:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
  MyJob = CurrentJob;
        ^
main.c:1350:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
    MTInfo->ThreadID, *MTInfo->AlgoCtx.GPUIdxs, MTInfo->PlatformContext->Devices[*MTInfo->AlgoCtx.GPUIdxs].DeviceName);
    ^
main.c:1370:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
    MyJob = CurrentJob;
          ^
gcc -pthread -O0 -ggdb3 crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -ldl -L/opt/AMDAPP/lib/x86_64/ -o miner


any pointers?

note: I'm on ubuntu 14.04.4 with AMD repo drivers and AMD SDK 3.0 installed


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 15, 2016, 12:15:05 AM
Trying to compile (and looked at the notes on http://superkuh.com/monero.html (http://superkuh.com/monero.html) which by passed me the first couple of issues) but now I'm getting the following:

Code:
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb.c -o crypto/aesb.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_blake256.c -o crypto/c_blake256.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_groestl.c -o crypto/c_groestl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_keccak.c -o crypto/c_keccak.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_jh.c -o crypto/c_jh.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_skein.c -o crypto/c_skein.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [enabled by default]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:2: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [enabled by default]
  keccakf(&ctx->state.hs, 24);
  ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  log.c -o log.o
log.c: In function ‘Log’:
log.c:25:3: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
   ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  net.c -o net.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  minerutils.c -o minerutils.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  gpu.c -o gpu.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
  ^
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1341:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
  MyJob = CurrentJob;
        ^
main.c:1350:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
    MTInfo->ThreadID, *MTInfo->AlgoCtx.GPUIdxs, MTInfo->PlatformContext->Devices[*MTInfo->AlgoCtx.GPUIdxs].DeviceName);
    ^
main.c:1370:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
    MyJob = CurrentJob;
          ^
gcc -pthread -O0 -ggdb3 crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -ldl -L/opt/AMDAPP/lib/x86_64/ -o miner


any pointers?

note: I'm on ubuntu 14.04.4 with AMD repo drivers and AMD SDK 3.0 installed

14.xx is OLD - 16.04. Side note: that's a success.

from what i understand OpenCL is not working on 16.04 yet? that's why i had to go back to 14.04(and .4 not .5) which did not work well either with AMD's SDK for me!?


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 15, 2016, 01:16:41 AM
Trying to compile (and looked at the notes on http://superkuh.com/monero.html (http://superkuh.com/monero.html) which by passed me the first couple of issues) but now I'm getting the following:

Code:
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb.c -o crypto/aesb.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_blake256.c -o crypto/c_blake256.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_groestl.c -o crypto/c_groestl.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_keccak.c -o crypto/c_keccak.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_jh.c -o crypto/c_jh.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/c_skein.c -o crypto/c_skein.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [enabled by default]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:2: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [enabled by default]
  keccakf(&ctx->state.hs, 24);
  ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  log.c -o log.o
log.c: In function ‘Log’:
log.c:25:3: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
   ^
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  net.c -o net.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  minerutils.c -o minerutils.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  gpu.c -o gpu.o
gcc -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -pthread -c -std=c11  main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
  ^
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1341:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
  MyJob = CurrentJob;
        ^
main.c:1350:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
    MTInfo->ThreadID, *MTInfo->AlgoCtx.GPUIdxs, MTInfo->PlatformContext->Devices[*MTInfo->AlgoCtx.GPUIdxs].DeviceName);
    ^
main.c:1370:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
    MyJob = CurrentJob;
          ^
gcc -pthread -O0 -ggdb3 crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -ldl -L/opt/AMDAPP/lib/x86_64/ -o miner


any pointers?

note: I'm on ubuntu 14.04.4 with AMD repo drivers and AMD SDK 3.0 installed

14.xx is OLD - 16.04. Side note: that's a success.

from what i understand OpenCL is not working on 16.04 yet? that's why i had to go back to 14.04(and .4 not .5) which did not work well either with AMD's SDK for me!?

It works fine on 16.xx - AMDGPU-PRO.

will give it  shot now :) ... here comes another OS test !!

sorry, but a quick unrelated question, I will install the desktop edition (16.04.1) and then install the AMD SDK? or is it all included the the AMDGPU-PRO?


Title: Re: Wolf's XMR GPU Miner
Post by: EvilC0P on September 15, 2016, 02:16:21 AM
Thought i would share my numbers, i just cant get anything near claymore's miner ( ~620 h/s )

Windows 7, 16 gb of ram, 16 gb of pagefile,
MSI RX 480 8GB , AMD drivers 16.20 , stock clock [ 1300 / 2000 ]

wolf miner 0.4
Threads      1   1   1   1   1   1   1   2   1   1   1   1   1
rawintensity   768   832   704   680   480   464   448   224   1024   1152   1280   1280   1600
worksize      8   8   8   8   16   16   16   16   8   8   8   4   4
h/s        447-504   471   433   427   459   455   425   331   497   476   427   414   341

used this simple conf file for testing purposes :

{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1600,
               "worksize": 4
            }
         ],
         "pools": ...

Would newest drivers 16.3 do any difference? ( was forced to use the disc that came from MSI because AMD's 16.3 drivers would freeze/crash windows after ~15 seconds after logging into my computer )
Any suggestions/tweaks?


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 15, 2016, 06:24:39 AM
Installed ubuntu 16.04.1 desktop and amdgpu-pro and tested it on repo bfgminer, it did not see my card, so i compiled cpp-ethereum and ran its benchmark and thats what i got:
Quote
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ ./ethminer -M --opencl
[OPENCL]:OpenCL device Spectre has insufficient GPU memory.1057591296 bytes of memory found < 1423739904 bytes of memory required
No GPU device with sufficient memory was found. Can't GPU mine. Remove the -G argument
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ export GPU_FORCE_64BIT_PTR=0
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ export GPU_MAX_HEAP_SIZE=100
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ export GPU_USE_SYNC_OBJECTS=1
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ export GPU_MAX_ALLOC_PERCENT=100
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ export GPU_SINGLE_ALLOC_PERCENT=100
mylin@MyLinMiner:~/Miner/cpp-ethereum/build/ethminer$ ./ethminer -M --opencl
[OPENCL]:OpenCL device Spectre has insufficient GPU memory.1057591296 bytes of memory found < 1423739904 bytes of memory required
No GPU device with sufficient memory was found. Can't GPU mine. Remove the -G argument

usually on ubuntu 14.xx the export statements covered this memory problem, but it seems that they dont work on 16?

and listing devices it gives me this:
Quote
[OPENCL]:
Listing OpenCL devices.
FORMAT: [deviceID] deviceName
  • Spectre
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 1057591296
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 535822336
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] AMD KAVERI (DRM 3.2.0, LLVM 3.8.0)
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 1073741824
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 268435456
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 256

so, actually the spectre card is the internal one, and its not seeing the other HD 5450 card?


Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on September 15, 2016, 07:32:51 AM
Thought i would share my numbers, i just cant get anything near claymore's miner ( ~620 h/s )
Windows 7, 16 gb of ram, 16 gb of pagefile,
MSI RX 480 8GB , AMD drivers 16.20 , stock clock [ 1300 / 2000 ]
Any suggestions/tweaks?
;D
Win7x64 /// crimson 15.12 /// hd7970 (1000/1500) /// k-miner
http://storage1.static.itmages.ru/i/16/0915/s_1473924844_4737306_f9192f4e77.png (http://itmages.ru/image/view/4886390/f9192f4e)


Title: Re: Wolf's XMR GPU Miner
Post by: taushet on September 15, 2016, 11:04:08 AM
As I have stated above, I get around 590 H/s per RX 480 4GB stock card.

However, I have encountered an issue.

This miner refuses to start if an NVIDIA card is used as primary video driver. My current setup is an NVIDIA 1080 on the main 16 slot and then multiple rx 480s on risers from the other slots. Due to work purposes, this cannot be changed.

I have tried multiple changes in the config file.

Any hints?



Title: Re: Wolf's XMR GPU Miner
Post by: Lucide on September 15, 2016, 12:30:28 PM
Can someone who has it working state their driver version? I'll see if I can fix the issue on the problematic ones.

hi there wolf ,
i am not able to use claymore's miner because my AMD card ( HD5450 ) has a MAX_WORK_SIZE of 128   and not 256 , will i be able to use your miner ?
thanks for answering


Title: Re: Wolf's XMR GPU Miner
Post by: EvilC0P on September 15, 2016, 12:59:03 PM
As I have stated above, I get around 590 H/s per RX 480 4GB stock card.

However, I have encountered an issue.

This miner refuses to start if an NVIDIA card is used as primary video driver. My current setup is an NVIDIA 1080 on the main 16 slot and then multiple rx 480s on risers from the other slots. Due to work purposes, this cannot be changed.

I have tried multiple changes in the config file.

Any hints?


i like the summary at the top, you use k-miner for Win64 ? can you provide link to download that miner?
or is it something you have to put in the xmr.conf of wolf's miner?

i would like to have more details,
thanks


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on September 16, 2016, 01:11:15 AM
I have a faster kernel set, too - my goal here was to equal Claymore, not exceed it.

Oops!

mATX with two pcie slots from 2008:

http://i63.tinypic.com/2zyfrxz.jpg

In my case reason for those low difficulty shares was too much undervolting.


Title: Re: Wolf's XMR GPU Miner
Post by: jukico on September 16, 2016, 03:28:48 AM
I have 6 x Gigabyte G1 RX480 4G overclocked in stock version, that 1290/1750 in core/mem.
Running with 16.9.1 Hotfix.
And Wolf showing ~3470 H/s in totally. So that ~577 H/s per card.
In totally, that at same H/s when compare with Claymore.
But the temperature is seem 30% low than Claymore, so i think the energy cost also lower than.

Problem:
1. At first time, it showing that all of my 6 card working in console screen, but when time past (about 5~6 hours ) there's only showing that 5 card is working (GPU ID 1 is disappearing)
But seem the totally hashrate not changed. I don't know why. Does the machine need to be restart?

2. People always talking about 600~700 H/s in RX480 cards.
I also try many times with wattman but seem its not works.
Why mine so low. If any ideal please let me know!

In wolf, I run with below config that seem product the best performance.

{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 1290,
          "memfreq": 1750,
               "fanspeed": 60,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 1024,
               "worksize": 8
            },
             ...
         ],
         "pools": ...

https://s9.postimg.io/6g56y75tr/20160916_072124.jpg


Title: Re: Wolf's XMR GPU Miner
Post by: pri3oner on September 16, 2016, 03:35:24 AM
how much can earn with this gpu miner program ? im interested to this program


Title: Re: Wolf's XMR GPU Miner
Post by: Potap on September 16, 2016, 03:54:19 AM
why miner does not display the speed on the bullet


http://s018.radikal.ru/i509/1609/a7/96ab8deaaeca.png (http://radikal.ru)




Title: Re: Wolf's XMR GPU Miner
Post by: Potap on September 16, 2016, 06:04:40 AM

The pool only shows an estimate when you find a share - if you go a while without finding one, the pool will say 0. There was a bug where the miner would not reconnect to the pool - fixed in git.

what am I doing wrong, rejecti go to the pool there is no display


http://s020.radikal.ru/i705/1609/97/6aa95dc5029c.png (http://radikal.ru)


{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 916,
            "worksize": 8
                },
           {
            "index": 1,
                                "rawintensity": 924,
            "worksize": 8
                },
           {
            "index": 2,
                                "rawintensity": 924,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://xmr.crypto-pool.fr:3333",
            "user": "43buVZbkWfxhUFRsUPyDQTC",
            "pass": "1"
         }]
}]
}


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 16, 2016, 08:15:25 AM

The pool only shows an estimate when you find a share - if you go a while without finding one, the pool will say 0. There was a bug where the miner would not reconnect to the pool - fixed in git.

what am I doing wrong, rejecti go to the pool there is no display


http://s020.radikal.ru/i705/1609/97/6aa95dc5029c.png (http://radikal.ru)


{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 916,
            "worksize": 8
                },
           {
            "index": 1,
                                "rawintensity": 924,
            "worksize": 8
                },
           {
            "index": 2,
                                "rawintensity": 924,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://xmr.crypto-pool.fr:3333",
            "user": "43buVZbkWfxhUFRsUPyDQTC",
            "pass": "1"
         }]
}]
}
I have the same problem with new miner version 0.4 on Win7 x64 2X R9 270X
Still no solution from Wolf0  :(


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on September 16, 2016, 10:27:14 AM
I have a faster kernel set, too - my goal here was to equal Claymore, not exceed it.

Oops!

mATX with two pcie slots from 2008:

http://i63.tinypic.com/2zyfrxz.jpg

In my case reason for those low difficulty shares was too much undervolting.

That's pretty low - what clocks?

Well I am happy, it is faster than claymore's. 3.5kH from four hawaii ain't bad...

Too low voltage doesn't crash miner or drivers, you just start getting low difficulty shares and high cpu load.



Title: Re: Wolf's XMR GPU Miner
Post by: c2n14 on September 16, 2016, 01:37:44 PM
There was a bug where the miner would not reconnect to the pool - fixed in git.

Would you mind releasing fixed windows version?
Just in case...


Title: Re: Wolf's XMR GPU Miner
Post by: Lafu on September 16, 2016, 03:00:33 PM
I give them a try when i at home!!!


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 16, 2016, 04:10:06 PM

The pool only shows an estimate when you find a share - if you go a while without finding one, the pool will say 0. There was a bug where the miner would not reconnect to the pool - fixed in git.

what am I doing wrong, rejecti go to the pool there is no display


http://s020.radikal.ru/i705/1609/97/6aa95dc5029c.png (http://radikal.ru)


{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 916,
            "worksize": 8
                },
           {
            "index": 1,
                                "rawintensity": 924,
            "worksize": 8
                },
           {
            "index": 2,
                                "rawintensity": 924,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://xmr.crypto-pool.fr:3333",
            "user": "43buVZbkWfxhUFRsUPyDQTC",
            "pass": "1"
         }]
}]
}
I have the same problem with new miner version 0.4 on Win7 x64 2X R9 270X
Still no solution from Wolf0  :(

I can't find a damn driver to reproduce the issue, or I would have.
You can download it from official AMD site  ;)


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 16, 2016, 07:10:05 PM

The pool only shows an estimate when you find a share - if you go a while without finding one, the pool will say 0. There was a bug where the miner would not reconnect to the pool - fixed in git.

what am I doing wrong, rejecti go to the pool there is no display


http://s020.radikal.ru/i705/1609/97/6aa95dc5029c.png (http://radikal.ru)


{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 916,
            "worksize": 8
                },
           {
            "index": 1,
                                "rawintensity": 924,
            "worksize": 8
                },
           {
            "index": 2,
                                "rawintensity": 924,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://xmr.crypto-pool.fr:3333",
            "user": "43buVZbkWfxhUFRsUPyDQTC",
            "pass": "1"
         }]
}]
}
I have the same problem with new miner version 0.4 on Win7 x64 2X R9 270X
Still no solution from Wolf0  :(

I can't find a damn driver to reproduce the issue, or I would have.
You can download it from official AMD site  ;)

Not easy to find just any driver version for linux (unsupported distro.)
Which distro?
Btw, you always can build driver from source.
If you want, i can help with finding/building driver.


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 16, 2016, 07:36:11 PM
Oh, Arch...that's a problem  :(
I can't locate latest AMD driver version 16.9.1 for Arch.


Title: Re: Wolf's XMR GPU Miner
Post by: ylpkm on September 16, 2016, 07:48:51 PM
If I can ask for some assistance, Im a total noob to compiling, just started taking a C++ course this year. I have compiled a few things in ubuntu successfully but from the repository am i able to build this in windows? I tried using the VS command prompt with nmake and ran into gcc being unrecognized. I tried using cygwin, got a little way through, but that failed as well. Looking at the makefile it says -I..../sgminer-lin64/libcflags/. do i need to have those folders to compile this. I might be in over my head trying to compile this stuff.
Thanks for your time wolf for looking into our issues with the miner :) .

$ make
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/home/wolf/miners/sgminer-builds/sgminer-lin64/include/ -L/home/wolf/miners/sgminer-builds/sgminer-lin64/lib -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
cryptonight.c: In function ‘cryptonight_ctx’:
cryptonight.c:435:2: warning: implicit declaration of function ‘mmap’ [-Wimplicit-function-declaration]
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
  ^
cryptonight.c:435:30: error: ‘PROT_READ’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                              ^
cryptonight.c:435:30: note: each undeclared identifier is reported only once for each function it appears in
cryptonight.c:435:40: error: ‘PROT_WRITE’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                                        ^
cryptonight.c:435:52: error: ‘MAP_PRIVATE’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                                                    ^
cryptonight.c:435:64: error: ‘MAP_ANONYMOUS’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                                                                ^
cryptonight.c:435:78: error: ‘MAP_HUGETLB’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                                                                              ^
cryptonight.c:435:90: error: ‘MAP_POPULATE’ undeclared (first use in this function)
  ret = mmap(0, sizeof(*ret), PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_POPULATE, 0, 0);
                                                                                          ^
cryptonight.c:436:13: error: ‘MAP_FAILED’ undeclared (first use in this function)
  if (ret == MAP_FAILED)
             ^
cryptonight.c:439:3: warning: implicit declaration of function ‘madvise’ [-Wimplicit-function-declaration]
   madvise(ret, sizeof(*ret), MADV_RANDOM|MADV_WILLNEED|MADV_HUGEPAGE);
   ^
cryptonight.c:439:30: error: ‘MADV_RANDOM’ undeclared (first use in this function)
   madvise(ret, sizeof(*ret), MADV_RANDOM|MADV_WILLNEED|MADV_HUGEPAGE);
                              ^
cryptonight.c:439:42: error: ‘MADV_WILLNEED’ undeclared (first use in this function)
   madvise(ret, sizeof(*ret), MADV_RANDOM|MADV_WILLNEED|MADV_HUGEPAGE);
                                          ^
cryptonight.c:439:56: error: ‘MADV_HUGEPAGE’ undeclared (first use in this function)
   madvise(ret, sizeof(*ret), MADV_RANDOM|MADV_WILLNEED|MADV_HUGEPAGE);
                                                        ^
cryptonight.c:441:4: warning: implicit declaration of function ‘mlock’ [-Wimplicit-function-declaration]
    mlock(ret, sizeof(*ret));
    ^
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 1


Title: Re: Wolf's XMR GPU Miner
Post by: mycoinsstore on September 16, 2016, 08:47:43 PM
Oh, Arch...that's a problem  :(
I can't locate latest AMD driver version 16.9.1 for Arch.

I can make it myself.
Ok, I'll wait for a compiled windows version to test it.
Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: Lafu on September 16, 2016, 09:52:47 PM
Oh, Arch...that's a problem  :(
I can't locate latest AMD driver version 16.9.1 for Arch.

I can make it myself.
Ok, I'll wait for a compiled windows version to test it.
Thanks.

waiting too should be nice when its all working


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 17, 2016, 08:52:16 PM
turned out to be that ubuntu 16 (and amdgpu pro) dont have support for my older card (xfx 5450HD) which i will remove soon and get something better, but for now i'm stuck with it, so went back to 14.04.4 and trying to compile it, now im stuck here:

Quote
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [enabled by default]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:2: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [enabled by default]
  keccakf(&ctx->state.hs, 24);
  ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:3: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
   ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 gpu.c -o gpu.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ -c -std=c11 main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
  ^
main.c:710:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1341:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
  MyJob = CurrentJob;
        ^
main.c:1350:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
    MTInfo->ThreadID, *MTInfo->AlgoCtx.GPUIdxs, MTInfo->PlatformContext->Devices[*MTInfo->AlgoCtx.GPUIdxs].DeviceName);
    ^
main.c:1370:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [enabled by default]
    MyJob = CurrentJob;
          ^
main.c: In function ‘SigHandler’:
main.c:1475:7: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
  write(ExitPipe[1], &c, 1);
       ^
main.c: In function ‘main’:
main.c:1789:6: warning: ignoring return value of ‘pipe’, declared with attribute warn_unused_result [-Wunused-result]
  pipe(ExitPipe);
      ^
main.c:2055:6: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
  read(ExitPipe[0], &c, 1);
      ^
gcc -DPTW32_STATIC_LIB -O2 -s -I/opt/AMDAPP/include/ -L/opt/AMDAPP/lib/x86_64/ crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -lpthread -ldl  -o miner



Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 17, 2016, 08:58:12 PM
i also tried to run ./miner (just checking) and i get this error:

Quote
./miner: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: version `OPENCL_2.0' not found (required by ./miner)

although the file libOpenCL.so.1 exists there?


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 17, 2016, 09:37:29 PM
i have two gpu's on right now:

- the AMD Radeon™ R7 Graphics (from the AMD PRO A8-8650B APU)
- and the card xfx radeon hd 5450 2gb

and i have the AMD v3.0.130.136 APP SDK installed!!


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 18, 2016, 03:45:10 AM
i have two gpu's on right now:

- the AMD Radeon™ R7 Graphics (from the AMD PRO A8-8650B APU)
- and the card xfx radeon hd 5450 2gb

and i have the AMD v3.0.130.136 APP SDK installed!!

The 5450 is not supported. Neither is the APU.

so im planning to get a new card soon, what is a good 4gb amd card you recommend?


Title: Re: Wolf's XMR GPU Miner
Post by: mrbubl3s on September 18, 2016, 07:44:00 AM
7770 Does good ~162h/s, Claymore does ~170h/s

I get this a lot:
"Share rejected (Low difficulty share)"

http://imgur.com/a/UQdRs

5830 Throws error:
"Error -54 when calling clEnqueueNDRangeKernel for kernel 3."

Config:

Code:
{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 216,
            "worksize": 8
                },
{
            "index": 1,
                                "rawintensity": 128,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://mine.moneropool.com:8080",
            "user": "user",
            "pass": "x"
         }]
}]
}


It is neat you are working on an open source miner.


Title: Re: Wolf's XMR GPU Miner
Post by: Khazeter on September 18, 2016, 08:04:19 AM
What is the performance of Wolf's XMR GPU miner on the AMD R9 Nano? Is that much faster than R9 390?


Title: Re: Wolf's XMR GPU Miner
Post by: mike34 on September 18, 2016, 11:54:38 AM
hi all and thanks wolf
can anyone share a conf file for rx470 i just cant for life of me get my 470 mining biker coin


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 19, 2016, 02:46:36 PM
i have two gpu's on right now:

- the AMD Radeon™ R7 Graphics (from the AMD PRO A8-8650B APU)
- and the card xfx radeon hd 5450 2gb

and i have the AMD v3.0.130.136 APP SDK installed!!

The 5450 is not supported. Neither is the APU.

so im planning to get a new card soon, what is a good 4gb amd card you recommend?

i found this command "clinfo" which returned to me the following (sorry for the lengthy text):

Code:
Number of platforms:                             1
  Platform Profile:                              FULL_PROFILE
  Platform Version:                              OpenCL 2.0 AMD-APP (1800.11)
  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:                               3
  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Board name:                                    AMD Radeon(TM) R7 Graphics
  Device Topology:                               PCI[ B#0, D#1, F#0 ]
  Max compute units:                             6
  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:                   4
  Preferred vector width short:                  2
  Preferred vector width int:                    1
  Preferred vector width long:                   1
  Preferred vector width float:                  1
  Preferred vector width double:                 1
  Native vector width char:                      4
  Native vector width short:                     2
  Native vector width int:                       1
  Native vector width long:                      1
  Native vector width float:                     1
  Native vector width double:                    1
  Max clock frequency:                           757Mhz
  Address bits:                                  64
  Max memory allocation:                         681574400
  Image support:                                 Yes
  Max number of images read arguments:           128
  Max number of images write arguments:          64
  Max image 2D width:                            16384
  Max image 2D height:                           16384
  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:                                    Read/Write
  Cache line size:                               64
  Cache size:                                    16384
  Global memory size:                            2481979392
  Constant buffer size:                          65536
  Max number of constant args:                   8
  Local memory type:                             Scratchpad
  Local memory size:                             32768
  Max pipe arguments:                            16
  Max pipe active reservations:                  16
  Max pipe packet size:                          681574400
  Max global variable size:                      613416960
  Max global variable preferred total size:      2481979392
  Max read/write image args:                     64
  Max on device events:                          1024
  Queue on device max size:                      524288
  Max on device queues:                          1
  Queue on device preferred size:                262144
  SVM capabilities:
    Coarse grain buffer:                         Yes
    Fine grain buffer:                           Yes
    Fine grain system:                           No
    Atomics:                                     No
  Preferred platform atomic alignment:           0
  Preferred global atomic alignment:             0
  Preferred local atomic alignment:              0
  Kernel Preferred work group size multiple:     64
  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:                     No
  Queue on Host properties:
    Out-of-Order:                                No
    Profiling :                                  Yes
  Queue on Device properties:
    Out-of-Order:                                Yes
    Profiling :                                  Yes
  Platform ID:                                   0x7f843ca92430
  Name:                                          Spectre
  Vendor:                                        Advanced Micro Devices, Inc.
  Device OpenCL C version:                       OpenCL C 2.0
  Driver version:                                1800.11 (VM)
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 2.0 AMD-APP (1800.11)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_khr_gl_depth_images cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images


  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Board name:
  Device Topology:                               PCI[ B#1, D#0, F#0 ]
  Max compute units:                             2
  Max work items dimensions:                     3
    Max work items[0]:                           128
    Max work items[1]:                           128
    Max work items[2]:                           128
  Max work group size:                           128
  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:                           650Mhz
  Address bits:                                  32
  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:                            16384
  Max image 2D height:                           16384
  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:                            2147483648
  Constant buffer size:                          65536
  Max number of constant args:                   8
  Local memory type:                             Scratchpad
  Local memory size:                             32768
  Max pipe arguments:                            0
  Max pipe active reservations:                  0
  Max pipe packet size:                          0
  Max global variable size:                      0
  Max global variable preferred total size:      0
  Max read/write image args:                     0
  Max on device events:                          0
  Queue on device max size:                      0
  Max on device queues:                          0
  Queue on device preferred size:                0
  SVM capabilities:
    Coarse grain buffer:                         No
    Fine grain buffer:                           No
    Fine grain system:                           No
    Atomics:                                     No
  Preferred platform atomic alignment:           0
  Preferred global atomic alignment:             0
  Preferred local atomic alignment:              0
  Kernel Preferred work group size multiple:     32
  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 on Host properties:
    Out-of-Order:                                No
    Profiling :                                  Yes
  Queue on Device properties:
    Out-of-Order:                                No
    Profiling :                                  No
  Platform ID:                                   0x7f843ca92430
  Name:                                          Cedar
  Vendor:                                        Advanced Micro Devices, Inc.
  Device OpenCL C version:                       OpenCL C 1.2
  Driver version:                                1800.11
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 1.2 AMD-APP (1800.11)
  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_media_ops2 cl_amd_popcnt cl_amd_image2d_from_buffer_read_only cl_khr_spir cl_khr_gl_event


  Device Type:                                   CL_DEVICE_TYPE_CPU
  Vendor ID:                                     1002h
  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:                  8
  Preferred vector width double:                 4
  Native vector width char:                      16
  Native vector width short:                     8
  Native vector width int:                       4
  Native vector width long:                      2
  Native vector width float:                     8
  Native vector width double:                    4
  Max clock frequency:                           1400Mhz
  Address bits:                                  64
  Max memory allocation:                         2147483648
  Image support:                                 Yes
  Max number of images read arguments:           128
  Max number of images write arguments:          64
  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:                                    16384
  Global memory size:                            7259299840
  Constant buffer size:                          65536
  Max number of constant args:                   8
  Local memory type:                             Global
  Local memory size:                             32768
  Max pipe arguments:                            16
  Max pipe active reservations:                  16
  Max pipe packet size:                          2147483648
  Max global variable size:                      1879048192
  Max global variable preferred total size:      1879048192
  Max read/write image args:                     64
  Max on device events:                          0
  Queue on device max size:                      0
  Max on device queues:                          0
  Queue on device preferred size:                0
  SVM capabilities:
    Coarse grain buffer:                         No
    Fine grain buffer:                           No
    Fine grain system:                           No
    Atomics:                                     No
  Preferred platform atomic alignment:           0
  Preferred global atomic alignment:             0
  Preferred local atomic alignment:              0
  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 on Host properties:
    Out-of-Order:                                No
    Profiling :                                  Yes
  Queue on Device properties:
    Out-of-Order:                                No
    Profiling :                                  No
  Platform ID:                                   0x7f843ca92430
  Name:                                          AMD PRO A8-8650B R7, 10 Compute Cores 4C+6G
  Vendor:                                        AuthenticAMD
  Device OpenCL C version:                       OpenCL C 1.2
  Driver version:                                1800.11 (sse2,avx,fma4)
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 1.2 AMD-APP (1800.11)
  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_3d_image_writes 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_media_ops2 cl_amd_popcnt cl_khr_spir cl_khr_gl_event


it says the apu supports OpenCL 2.0  .... i'm still trying to figure out what goes where :)))



Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 19, 2016, 05:03:00 PM
im very new to all of this, what do you mean by insane ? :))


Title: Re: Wolf's XMR GPU Miner
Post by: Nik4691 on September 19, 2016, 06:40:05 PM
im very new to all of this, what do you mean by insane ? :))
For your information, chances are, that you will get much more hashrate with the CPU part of the APU.


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 19, 2016, 06:53:17 PM
im very new to all of this, what do you mean by insane ? :))
For your information, chances are, that you will get much more hashrate with the CPU part of the APU.

so far im still in my learning phase to understand what does what (i mean until now i cant seem to be able to figure out how to setup my conf files for the - i know its old and slow, but for now - XFX 5450 card). the reason im asking is that the A8 (A8 Pro 8650) has 10 cores (4 cpu + 6 gpu) which when i use with other apps (like cgminer) - thats the gpu, they give me better hashrate than that of the XFX 5450 (almost 3 - 4 times better), and as i mentioned, im still trying to understand how i can setup what i have to the best i can, before i go spending money on expensive cards ... just to clarify why i keep asking theoretical questions :)


Title: Re: Wolf's XMR GPU Miner
Post by: serpintine101 on September 20, 2016, 11:27:19 AM
I am having trouble running this miner on my RX 480s. This miner code is also used for the Aeon miner. On both it keeps rejecting any shares, low difficulty share problem. I have tried everything i can think of but nothing has worked. I have tried 16.7.3, 16.8.3, 16.9.1, AMD SDK 3.0, numerous times using guru to start fresh every time. Any ideas? We have ran out of ideas on the Aeon thread. The user Arux has recompiled the miner several times but no luck. I am using windows 10. Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 26, 2016, 02:19:10 PM
Is it possible to know what kind of hashrates to expect from the following cards:

- RX 480 8GB
- R9 390 8GB

?

thank you all


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 28, 2016, 09:05:02 PM
ok ...  got the r9 390x and still get the opnecl 2 error:

Code:
./miner: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: version `OPENCL_2.0' not found (required by ./miner)

any ideas?

solved: there was multiple copies of opencl obviously so i removed one of them:

Code:
sudo apt-get purge ocl-icd-libopencl1:amd64


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 29, 2016, 08:25:26 PM
I did a build with gcc6, -O3 -flt0.
https://drive.google.com/file/d/0BwLnDyLLT3Wka2Z4RW5lWUJIaFk/view

Works well for me with R9 380 and R7 370 (fglrx driver).


i just got the R9 390x card and was wondering what you have in the conf file for your 380?


Title: Re: Wolf's XMR GPU Miner
Post by: nerdralph on September 29, 2016, 09:03:38 PM
I did a build with gcc6, -O3 -flt0.
https://drive.google.com/file/d/0BwLnDyLLT3Wka2Z4RW5lWUJIaFk/view

Works well for me with R9 380 and R7 370 (fglrx driver).


i just got the R9 390x card and was wondering what you have in the conf file for your 380?

Looked back at my notes and I got the best results on the 380 with 8/896; around 540h/s.


Title: Re: Wolf's XMR GPU Miner
Post by: sapientidiot on September 30, 2016, 10:00:27 AM
Is there something extra needed for this to work with amdgpu-pro drivers? I can't seem to get any miners working after changing from fglrx.

 I seem to have nothing but invalid shares on XMR pools, but miner indicates that its submiting valid shares. I know i'm missing something because other miners just refuse to work at all: sgminer-gm, claymore-dm, and genoil all either crash or just sit idle as if they are trying to mine but can't.  I was have no troubles using fglrx but now that i have RX 470s that isn't an option.

 I've tried with both ArchLinux (which is what i normally use) and Ubuntu 16.04 (because it seems to be whats popular) the results are basically the same on either one with amdgpu-pro.  I've tried fresh installs and read what few up to date guides on setup i could find, nothing seems to work though.


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 30, 2016, 01:12:59 PM
Is there something extra needed for this to work with amdgpu-pro drivers? I can't seem to get any miners working after changing from fglrx.

 I seem to have nothing but invalid shares on XMR pools, but miner indicates that its submiting valid shares. I know i'm missing something because other miners just refuse to work at all: sgminer-gm, claymore-dm, and genoil all either crash or just sit idle as if they are trying to mine but can't.  I was have no troubles using fglrx but now that i have RX 470s that isn't an option.

 I've tried with both ArchLinux (which is what i normally use) and Ubuntu 16.04 (because it seems to be whats popular) the results are basically the same on either one with amdgpu-pro.  I've tried fresh installs and read what few up to date guides on setup i could find, nothing seems to work though.

i got it working on ubuntu 14.04 (desktop edition), with fglrx drivers, and ADL SDK V10.1 + APP SDK v3.0.130.136

this is what i did:

- downloaded the miner:

Code:
git clone https://github.com/wolf9466/wolf-xmr-miner.git
cd wolf-xmr-miner

then using WinSCP (i use remote ssh to control my pc), i went to the location where its downloaded and opened the "Makefile" file and edited it as per the instructions found here http://superkuh.com/monero.html (http://superkuh.com/monero.html). Basically you have to edit it to the location of your AMDAPP which is the top part of the file (replace the file with the following changing it to the location of your AMDAPP):
Code:
CC		= gcc
LD = gcc
OPT = -O0 -ggdb3
CFLAGS = -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -pthread -c -std=c11
LDFLAGS = -pthread $(OPT)
LIBS = -ljansson -lOpenCL -ldl -L/opt/AMDAPP/lib/x86_64/

then edited the "main.c" file as to the location of "stdatomic.h" (after copying the file into the miner's folder - can be done using WinSCP)
Code:
#include <stdio.h>
#include <stdint.h>
#include <string.h>
#include <signal.h>
#include <pthread.h>
#include <stdbool.h>
#include <jansson.h>
//#include <stdatomic.h>
#include </home/user/Miner/wolf-xmr-miner/stdatomic.h>
#include <cpuid.h>

then executed the make
Code:
make

although it showed some errors during compiling, but i ended up with a working "miner" which you run with:

Code:
./miner xmr.conf

of course you have to edit the "xmr.conf" with your data (which i'm still trying to figure out the best settings for the r9 390x)




Title: Re: Wolf's XMR GPU Miner
Post by: sapientidiot on September 30, 2016, 08:15:23 PM
Is there something extra needed for this to work with amdgpu-pro drivers? I can't seem to get any miners working after changing from fglrx.

 I seem to have nothing but invalid shares on XMR pools, but miner indicates that its submiting valid shares. I know i'm missing something because other miners just refuse to work at all: sgminer-gm, claymore-dm, and genoil all either crash or just sit idle as if they are trying to mine but can't.  I was have no troubles using fglrx but now that i have RX 470s that isn't an option.

 I've tried with both ArchLinux (which is what i normally use) and Ubuntu 16.04 (because it seems to be whats popular) the results are basically the same on either one with amdgpu-pro.  I've tried fresh installs and read what few up to date guides on setup i could find, nothing seems to work though.

i got it working on ubuntu 14.04 (desktop edition), with fglrx drivers, and ADL SDK V10.1 + APP SDK v3.0.130.136

this is what i did:

- downloaded the miner:

Code:
git clone https://github.com/wolf9466/wolf-xmr-miner.git
cd wolf-xmr-miner

then using WinSCP (i use remote ssh to control my pc), i went to the location where its downloaded and opened the "Makefile" file and edited it as per the instructions found here http://superkuh.com/monero.html (http://superkuh.com/monero.html). Basically you have to edit it to the location of your AMDAPP which is the top part of the file (replace the file with the following changing it to the location of your AMDAPP):
Code:
CC		= gcc
LD = gcc
OPT = -O0 -ggdb3
CFLAGS = -I/opt/AMDAPP/include -L/opt/AMDAPP/lib/x86_64/ -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -pthread -c -std=c11
LDFLAGS = -pthread $(OPT)
LIBS = -ljansson -lOpenCL -ldl -L/opt/AMDAPP/lib/x86_64/

then edited the "main.c" file as to the location of "stdatomic.h" (after copying the file into the miner's folder - can be done using WinSCP)
Code:
#include <stdio.h>
#include <stdint.h>
#include <string.h>
#include <signal.h>
#include <pthread.h>
#include <stdbool.h>
#include <jansson.h>
//#include <stdatomic.h>
#include </home/user/Miner/wolf-xmr-miner/stdatomic.h>
#include <cpuid.h>

then executed the make
Code:
make

although it showed some errors during compiling, but i ended up with a working "miner" which you run with:

Code:
./miner xmr.conf

of course you have to edit the "xmr.conf" with your data (which i'm still trying to figure out the best settings for the r9 390x)




Thanks for the info, unfortunately my issue isn't with compiling it and seems to be specifically related to the amdgpu-pro driver because I had no issues on fglrx but i can't use that anymore.


Title: Re: Wolf's XMR GPU Miner
Post by: megacrypto on September 30, 2016, 10:10:33 PM
i tried ubuntu 16 for a bit and then went back to 14 ... i thought first i will use the one i got working till i understand a bit more about miners and so, and then move to the 16 and its amdgpu


Title: Re: Wolf's XMR GPU Miner
Post by: mirny on October 12, 2016, 11:45:33 PM
use at least code tag, my mousewheel is fucking burning...


Title: Re: Wolf's XMR GPU Miner
Post by: cryptocurrencyfuture on October 13, 2016, 01:36:39 AM
(Updated with code tags that I didn't do originally - apologies for that as I'm new to this forum and Wolf's XMR GPU miner)

As originally stated I'm new to GPU mining and have been following this thread for Wolf's XMR GPU Miner where I have done the following below:

1. Fresh minimal install of Ubuntu 16.04 Server with OpenSSH Server along with latest updates for headless remote SSH access
2. Installed AMDGPU-PRO Driver version 16.30.3-315407 with sudo privileges
3. Installed AMD APP SDK 3.0 with sudo privileges in the /opt/AMDAPPSDK-3.0 directory location
4. Cloned the GitHub repository at https://github.com/wolf9466/wolf-xmr-miner
5. Updated the Makefile with the following changes for new AMDAPPSDK-3.0 installation

Code:
CC		= gcc
LD = gcc
OPT = -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib
CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS = -ljansson -lOpenCL -lpthread -ldl

6. Execute make without any errors and only warnings

Code:
$ make

gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [-Wincompatible-pointer-types]
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t * {aka long unsigned int *}’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:10: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
          ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 gpu.c -o gpu.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
                        ^
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1340:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  MyJob = CurrentJob;
        ^
main.c:1348:18: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
   sprintf(ThrID, "Thread %d, GPU ID %d, GPU Type: %s",
                  ^
main.c:1369:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
    MyJob = CurrentJob;
          ^
main.c: In function ‘SigHandler’:
main.c:1474:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
  write(ExitPipe[1], &c, 1);
  ^
main.c: In function ‘main’:
main.c:1788:2: warning: ignoring return value of ‘pipe’, declared with attribute warn_unused_result [-Wunused-result]
  pipe(ExitPipe);
  ^
main.c:2054:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
  read(ExitPipe[0], &c, 1);
  ^
gcc -DPTW32_STATIC_LIB -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -lpthread -ldl -o miner

$

7. Configure the xmr.conf as needed

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"threads": 1,
"rawintensity": 640,
"worksize": 8
},
{
"index": -1,
"threads": 1,
"rawintensity": 8,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://<valid_pool>:<valid_port>",
"user": "<valid_user>",
"pass": "x"
}
]
}
]
}

8. Execute the miner and get this error a few seconds later

Code:
$ ./miner xmr.conf

[17:32:27] Setting up GPU(s).
[17:32:27] Successfully connected to pool's stratum.
*** buffer overflow detected ***: ./miner terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7f5d856a0725]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f5d8574189c]
/lib/x86_64-linux-gnu/libc.so.6(+0x1168a0)[0x7f5d8573f8a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x115bf2)[0x7f5d8573ebf2]
./miner[0x410c35]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f5d859f96fa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5d8572fb5d]
======= Memory map: ========
00400000-00419000 r-xp 00000000 fc:00 2623891                            /miner
00619000-0061a000 r--p 00019000 fc:00 2623891                            /miner
0061a000-0061b000 rw-p 0001a000 fc:00 2623891                            /miner
01418000-01439000 rw-p 00000000 00:00 0                                  [heap]
7f5d7fdea000-7f5d7fe00000 r-xp 00000000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7fe00000-7f5d7ffff000 ---p 00016000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7ffff000-7f5d80000000 rw-p 00015000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d80000000-7f5d80021000 rw-p 00000000 00:00 0
7f5d80021000-7f5d84000000 ---p 00000000 00:00 0
7f5d840df000-7f5d840e0000 ---p 00000000 00:00 0
7f5d840e0000-7f5d848e0000 rw-p 00000000 00:00 0
7f5d848e0000-7f5d848f7000 r-xp 00000000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d848f7000-7f5d84af7000 ---p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af7000-7f5d84af8000 r--p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af8000-7f5d84af9000 rw-p 00018000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af9000-7f5d84afb000 rw-p 00000000 00:00 0
7f5d84afb000-7f5d84b00000 r-xp 00000000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84b00000-7f5d84d00000 ---p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d00000-7f5d84d01000 r--p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d01000-7f5d84d02000 rw-p 00006000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d02000-7f5d84d0d000 r-xp 00000000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84d0d000-7f5d84f0c000 ---p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0c000-7f5d84f0d000 r--p 0000a000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0d000-7f5d84f0e000 rw-p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0e000-7f5d84f14000 rw-p 00000000 00:00 0
7f5d84f14000-7f5d84f17000 r-xp 00000000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d84f17000-7f5d85116000 ---p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85116000-7f5d85117000 r--p 00002000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85117000-7f5d85118000 rw-p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85118000-7f5d85220000 r-xp 00000000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85220000-7f5d8541f000 ---p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d8541f000-7f5d85420000 r--p 00107000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85420000-7f5d85421000 rw-p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85421000-7f5d85428000 r-xp 00000000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85428000-7f5d85627000 ---p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85627000-7f5d85628000 r--p 00006000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85628000-7f5d85629000 rw-p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85629000-7f5d857e9000 r-xp 00000000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d857e9000-7f5d859e8000 ---p 001c0000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859e8000-7f5d859ec000 r--p 001bf000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ec000-7f5d859ee000 rw-p 001c3000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ee000-7f5d859f2000 rw-p 00000000 00:00 0
7f5d859f2000-7f5d85a0a000 r-xp 00000000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85a0a000-7f5d85c09000 ---p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c09000-7f5d85c0a000 r--p 00017000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0a000-7f5d85c0b000 rw-p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0b000-7f5d85c0f000 rw-p 00000000 00:00 0
7f5d85c0f000-7f5d85c15000 r-xp 00000000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85c15000-7f5d85e15000 ---p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e15000-7f5d85e16000 rw-p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e16000-7f5d85e22000 r-xp 00000000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d85e22000-7f5d86021000 ---p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86021000-7f5d86022000 r--p 0000b000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86022000-7f5d86023000 rw-p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86023000-7f5d86049000 r-xp 00000000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86238000-7f5d8623d000 rw-p 00000000 00:00 0
7f5d86245000-7f5d86248000 rw-p 00000000 00:00 0
7f5d86248000-7f5d86249000 r--p 00025000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86249000-7f5d8624a000 rw-p 00026000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d8624a000-7f5d8624b000 rw-p 00000000 00:00 0
7ffcc1f08000-7ffcc1f29000 rw-p 00000000 00:00 0                          [stack]
7ffcc1fae000-7ffcc1fb0000 r--p 00000000 00:00 0                          [vvar]
7ffcc1fb0000-7ffcc1fb2000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted (core dumped)

$

9. The AMD drivers are installed and loaded correctly

Code:
$ sudo lshw -class display | grep "driver"

       configuration: driver=amdgpu latency=0
       configuration: driver=amdgpu latency=0
       configuration: driver=i915 latency=0

$

10. I have two AMD GPUs installed on this Ubuntu 16.04 headless server

R9 390X - Hawaii
R9 380 - Tonga

11. The clinfo command shows all the information on the GPUs

Code:
$ clinfo

Number of platforms: 1
  Platform Profile: FULL_PROFILE
  Platform Version: OpenCL 2.0 AMD-APP (2117.7)
  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: 3
  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#1, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 4244635648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 8541122560
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Hawaii
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#2, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 1409215488
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 2127253504
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Tonga
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_CPU
  Vendor ID: 1002h
  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: 8
  Preferred vector width double: 4
  Native vector width char: 16
  Native vector width short: 8
  Native vector width int: 4
  Native vector width long: 2
  Native vector width float: 8
  Native vector width double: 4
  Max clock frequency: 871Mhz
  Address bits: 64
  Max memory allocation: 2147483648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 64
  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: 8240955392
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Global
  Local memory size: 32768
  Max pipe arguments: 16
  Max pipe active reservations: 16
  Max pipe packet size: 2147483648
  Max global variable size: 1879048192
  Max global variable preferred total size: 1879048192
  Max read/write image args: 64
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
  Vendor: GenuineIntel
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (sse2,avx)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes 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_media_ops2 cl_amd_popcnt cl_khr_spir cl_khr_gl_event


$

Any help with getting further along would be greatly appreciated as my next step is trying one AMD GPU card installed at a time to see what happens



Title: Re: Wolf's XMR GPU Miner
Post by: lexele on October 13, 2016, 01:11:05 PM
Hi there,
got it working for my Sapphire RX 470 4Gb ref under ubuntu 16.04:

cclock 1150/ mclock 2010 custom kernel: 750mhs with rawintensity=1000, worksize=8 for best results.

Claymore gives 778mhs with the same clocks on windows.

the interesting part is the power consumption, it's lower in linux with stock voltage (if someone nows how to undervolt in linux...) as in windows I was highly undervolted.

Nota: it seems to be 10mhs lower when window manager is started.


Title: Re: Wolf's XMR GPU Miner
Post by: cryptocurrencyfuture on October 13, 2016, 08:40:13 PM
(Updated with code tags that I didn't do originally - apologies for that as I'm new to this forum and Wolf's XMR GPU miner)

As originally stated I'm new to GPU mining and have been following this thread for Wolf's XMR GPU Miner where I have done the following below:

1. Fresh minimal install of Ubuntu 16.04 Server with OpenSSH Server along with latest updates for headless remote SSH access
2. Installed AMDGPU-PRO Driver version 16.30.3-315407 with sudo privileges
3. Installed AMD APP SDK 3.0 with sudo privileges in the /opt/AMDAPPSDK-3.0 directory location
4. Cloned the GitHub repository at https://github.com/wolf9466/wolf-xmr-miner
5. Updated the Makefile with the following changes for new AMDAPPSDK-3.0 installation

Code:
CC		= gcc
LD = gcc
OPT = -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib
CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS = -ljansson -lOpenCL -lpthread -ldl

6. Execute make without any errors and only warnings

Code:
$ make

gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [-Wincompatible-pointer-types]
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t * {aka long unsigned int *}’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:10: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
          ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 gpu.c -o gpu.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
                        ^
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1340:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  MyJob = CurrentJob;
        ^
main.c:1348:18: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
   sprintf(ThrID, "Thread %d, GPU ID %d, GPU Type: %s",
                  ^
main.c:1369:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
    MyJob = CurrentJob;
          ^
main.c: In function ‘SigHandler’:
main.c:1474:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
  write(ExitPipe[1], &c, 1);
  ^
main.c: In function ‘main’:
main.c:1788:2: warning: ignoring return value of ‘pipe’, declared with attribute warn_unused_result [-Wunused-result]
  pipe(ExitPipe);
  ^
main.c:2054:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
  read(ExitPipe[0], &c, 1);
  ^
gcc -DPTW32_STATIC_LIB -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -lpthread -ldl -o miner

$

7. Configure the xmr.conf as needed

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"threads": 1,
"rawintensity": 640,
"worksize": 8
},
{
"index": -1,
"threads": 1,
"rawintensity": 8,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://<valid_pool>:<valid_port>",
"user": "<valid_user>",
"pass": "x"
}
]
}
]
}

8. Execute the miner and get this error a few seconds later

Code:
$ ./miner xmr.conf

[17:32:27] Setting up GPU(s).
[17:32:27] Successfully connected to pool's stratum.
*** buffer overflow detected ***: ./miner terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7f5d856a0725]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f5d8574189c]
/lib/x86_64-linux-gnu/libc.so.6(+0x1168a0)[0x7f5d8573f8a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x115bf2)[0x7f5d8573ebf2]
./miner[0x410c35]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f5d859f96fa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5d8572fb5d]
======= Memory map: ========
00400000-00419000 r-xp 00000000 fc:00 2623891                            /miner
00619000-0061a000 r--p 00019000 fc:00 2623891                            /miner
0061a000-0061b000 rw-p 0001a000 fc:00 2623891                            /miner
01418000-01439000 rw-p 00000000 00:00 0                                  [heap]
7f5d7fdea000-7f5d7fe00000 r-xp 00000000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7fe00000-7f5d7ffff000 ---p 00016000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7ffff000-7f5d80000000 rw-p 00015000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d80000000-7f5d80021000 rw-p 00000000 00:00 0
7f5d80021000-7f5d84000000 ---p 00000000 00:00 0
7f5d840df000-7f5d840e0000 ---p 00000000 00:00 0
7f5d840e0000-7f5d848e0000 rw-p 00000000 00:00 0
7f5d848e0000-7f5d848f7000 r-xp 00000000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d848f7000-7f5d84af7000 ---p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af7000-7f5d84af8000 r--p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af8000-7f5d84af9000 rw-p 00018000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af9000-7f5d84afb000 rw-p 00000000 00:00 0
7f5d84afb000-7f5d84b00000 r-xp 00000000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84b00000-7f5d84d00000 ---p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d00000-7f5d84d01000 r--p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d01000-7f5d84d02000 rw-p 00006000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d02000-7f5d84d0d000 r-xp 00000000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84d0d000-7f5d84f0c000 ---p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0c000-7f5d84f0d000 r--p 0000a000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0d000-7f5d84f0e000 rw-p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0e000-7f5d84f14000 rw-p 00000000 00:00 0
7f5d84f14000-7f5d84f17000 r-xp 00000000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d84f17000-7f5d85116000 ---p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85116000-7f5d85117000 r--p 00002000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85117000-7f5d85118000 rw-p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85118000-7f5d85220000 r-xp 00000000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85220000-7f5d8541f000 ---p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d8541f000-7f5d85420000 r--p 00107000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85420000-7f5d85421000 rw-p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85421000-7f5d85428000 r-xp 00000000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85428000-7f5d85627000 ---p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85627000-7f5d85628000 r--p 00006000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85628000-7f5d85629000 rw-p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85629000-7f5d857e9000 r-xp 00000000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d857e9000-7f5d859e8000 ---p 001c0000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859e8000-7f5d859ec000 r--p 001bf000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ec000-7f5d859ee000 rw-p 001c3000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ee000-7f5d859f2000 rw-p 00000000 00:00 0
7f5d859f2000-7f5d85a0a000 r-xp 00000000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85a0a000-7f5d85c09000 ---p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c09000-7f5d85c0a000 r--p 00017000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0a000-7f5d85c0b000 rw-p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0b000-7f5d85c0f000 rw-p 00000000 00:00 0
7f5d85c0f000-7f5d85c15000 r-xp 00000000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85c15000-7f5d85e15000 ---p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e15000-7f5d85e16000 rw-p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e16000-7f5d85e22000 r-xp 00000000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d85e22000-7f5d86021000 ---p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86021000-7f5d86022000 r--p 0000b000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86022000-7f5d86023000 rw-p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86023000-7f5d86049000 r-xp 00000000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86238000-7f5d8623d000 rw-p 00000000 00:00 0
7f5d86245000-7f5d86248000 rw-p 00000000 00:00 0
7f5d86248000-7f5d86249000 r--p 00025000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86249000-7f5d8624a000 rw-p 00026000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d8624a000-7f5d8624b000 rw-p 00000000 00:00 0
7ffcc1f08000-7ffcc1f29000 rw-p 00000000 00:00 0                          [stack]
7ffcc1fae000-7ffcc1fb0000 r--p 00000000 00:00 0                          [vvar]
7ffcc1fb0000-7ffcc1fb2000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted (core dumped)

$

9. The AMD drivers are installed and loaded correctly

Code:
$ sudo lshw -class display | grep "driver"

       configuration: driver=amdgpu latency=0
       configuration: driver=amdgpu latency=0
       configuration: driver=i915 latency=0

$

10. I have two AMD GPUs installed on this Ubuntu 16.04 headless server

R9 390X - Hawaii
R9 380 - Tonga

11. The clinfo command shows all the information on the GPUs

Code:
$ clinfo

Number of platforms: 1
  Platform Profile: FULL_PROFILE
  Platform Version: OpenCL 2.0 AMD-APP (2117.7)
  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: 3
  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#1, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 4244635648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 8541122560
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Hawaii
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#2, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 1409215488
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 2127253504
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Tonga
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_CPU
  Vendor ID: 1002h
  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: 8
  Preferred vector width double: 4
  Native vector width char: 16
  Native vector width short: 8
  Native vector width int: 4
  Native vector width long: 2
  Native vector width float: 8
  Native vector width double: 4
  Max clock frequency: 871Mhz
  Address bits: 64
  Max memory allocation: 2147483648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 64
  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: 8240955392
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Global
  Local memory size: 32768
  Max pipe arguments: 16
  Max pipe active reservations: 16
  Max pipe packet size: 2147483648
  Max global variable size: 1879048192
  Max global variable preferred total size: 1879048192
  Max read/write image args: 64
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
  Vendor: GenuineIntel
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (sse2,avx)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes 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_media_ops2 cl_amd_popcnt cl_khr_spir cl_khr_gl_event


$

Any help with getting further along would be greatly appreciated as my next step is trying one AMD GPU card installed at a time to see what happens




1. I resolved the issue I was having before by modifying the compiler options further with the -D_FORTIFY_SOURCE=0 option shown below

Code:
OPT 	= -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib 
CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11 -D_FORTIFY_SOURCE=0 
CC = gcc
LD = gcc
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS = -ljansson -lOpenCL -lpthread -ldl

2. I can successfully CPU and GPU mine XMR with the following xmr.conf file

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
                                {
                                        "index": 0,
                                        "threads": 2,
                                        "rawintensity": 1024,
                                        "worksize": 8
                                },
                                {
                                        "index": 1,
                                        "threads": 1,
                                        "rawintensity": 640,
                                        "worksize": 8
                                },
{
"index": -1,
"threads": 3,
"rawintensity": 12,
"worksize": 12
}
],
"pools":
[
{
"url": "stratum+tcp://<valid_pool>:<valid_port>",
"user": "<valid_user>",
"pass": "x"
}
]
}
]
}

3. Current output example from my wolf-xmr-miner build and configuration listed above

Code:
[16:27:38] New job at diff 13419
[16:27:38] Thread 5, (CPU): 66.80H/s
[16:27:38] Thread 4, (CPU): 67.25H/s
[16:27:38] Thread 3, (CPU): 66.24H/s
[16:27:39] Thread 2, GPU ID 1, GPU Type: Tonga: 485.17H/s
[16:27:40] Thread 0, GPU ID 0, GPU Type: Hawaii: 381.56H/s
[16:27:40] Thread 1, GPU ID 0, GPU Type: Hawaii: 381.56H/s
[16:27:41] Thread 2, GPU ID 1, GPU Type: Tonga: 485.26H/s
[16:27:42] Thread 0, GPU ID 0, GPU Type: Hawaii: 380.56H/s
[16:27:42] Thread 1, GPU ID 0, GPU Type: Hawaii: 380.56H/s
[16:27:44] Thread 2, GPU ID 1, GPU Type: Tonga: 484.93H/s
[16:27:45] Thread 0, GPU ID 0, GPU Type: Hawaii: 380.30H/s
[16:27:45] Thread 1, GPU ID 0, GPU Type: Hawaii: 380.30H/s
[16:27:47] Thread 2, GPU ID 1, GPU Type: Tonga: 484.79H/s
[16:27:48] Thread 0, GPU ID 0, GPU Type: Hawaii: 381.18H/s
[16:27:48] Thread 1, GPU ID 0, GPU Type: Hawaii: 381.19H/s
[16:27:48] Share accepted: 706/759 (93.02%)
[16:27:48] Total Hashrate: 1447.45H/s

4. I will continue to play around with the best settings for xmr.conf and find the best performance and stability. 

5. I haven't done any overclock/undervolt efforts on the stock AMD GPUs and will see what options might help performance along with stability as time permits. 

At this point I'm just happy to have it working now using stock settings and hope this information helps others attempting to use the wolf-xmr-miner on Ubuntu 16.04 LTS in the future.  Thanks to Wolf again for sharing with others and making this wonderful GPU miner.






Title: Re: Wolf's XMR GPU Miner
Post by: miass on October 14, 2016, 03:42:48 PM
Hello! I'm new please tell me how and what is data miner? I downloaded made a batch file and I have not started may indicate about what should be in bat file. Thanks for the early


Title: Re: Wolf's XMR GPU Miner
Post by: faygokris on October 26, 2016, 12:04:52 AM
Is it possible to know what kind of hashrates to expect from the following cards:

- RX 480 8GB
- R9 390 8GB

?

thank you all

I am getting 555h/s on my rx 480


Title: Re: Wolf's XMR GPU Miner
Post by: JuanHungLo on October 26, 2016, 10:38:28 AM
Wolf0,

I get the following with a couple of Tongas:

"error parsing version string from clGetDeviceInfo.  This should never happen"

Does this miner work with 380s?



Title: Re: Wolf's XMR GPU Miner
Post by: ZenFr on October 26, 2016, 11:11:07 AM
@Wolf0 : can you please precise in the topic title "Wolf's XMR AMD GPU Miner".
Each time i lost my time since I remember that is not for my NVidia GPUs (I have only NVidia GPUs, because electricity power is expensive in France).
Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: cryptocurrencyfuture on October 31, 2016, 02:32:17 AM
Is it possible to know what kind of hashrates to expect from the following cards:

- RX 480 8GB
- R9 390 8GB

?

thank you all

I am getting the following on these cards below

806 H/s on my R9 390X - Hawaii
590 H/s on my R9 380 - Tonga
567 H/s on my RX 470 - Ellesmere



Title: Re: Wolf's XMR GPU Miner
Post by: cryptocurrencyfuture on October 31, 2016, 02:44:05 AM
(Updated with code tags that I didn't do originally - apologies for that as I'm new to this forum and Wolf's XMR GPU miner)

As originally stated I'm new to GPU mining and have been following this thread for Wolf's XMR GPU Miner where I have done the following below:

1. Fresh minimal install of Ubuntu 16.04 Server with OpenSSH Server along with latest updates for headless remote SSH access
2. Installed AMDGPU-PRO Driver version 16.30.3-315407 with sudo privileges
3. Installed AMD APP SDK 3.0 with sudo privileges in the /opt/AMDAPPSDK-3.0 directory location
4. Cloned the GitHub repository at https://github.com/wolf9466/wolf-xmr-miner
5. Updated the Makefile with the following changes for new AMDAPPSDK-3.0 installation

Code:
CC		= gcc
LD = gcc
OPT = -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib
CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS = -ljansson -lOpenCL -lpthread -ldl

6. Execute make without any errors and only warnings

Code:
$ make

gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 -maes cryptonight.c -o cryptonight.o
cryptonight.c: In function ‘cryptonight_hash_aesni’:
cryptonight.c:383:18: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  uint64_t *dst = &ctx->long_state[c[0] & 0x1FFFF0];
                  ^
cryptonight.c:426:10: warning: passing argument 1 of ‘keccakf’ from incompatible pointer type [-Wincompatible-pointer-types]
  keccakf(&ctx->state.hs, 24);
          ^
In file included from cryptonight.c:13:0:
crypto/c_keccak.h:22:6: note: expected ‘uint64_t * {aka long unsigned int *}’ but argument is of type ‘union hash_state *’
 void keccakf(uint64_t st[25], int norounds);
      ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 log.c -o log.o
log.c: In function ‘Log’:
log.c:25:10: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
          ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 gpu.c -o gpu.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  -c -std=c11 main.c -o main.o
main.c: In function ‘SetupXMRTest’:
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
  snprintf(Options, 31, "-I. -DWORKSIZE=%d", LocalThreads);
                        ^
main.c:709:24: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
main.c: In function ‘MinerThreadProc’:
main.c:1340:8: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  MyJob = CurrentJob;
        ^
main.c:1348:18: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
   sprintf(ThrID, "Thread %d, GPU ID %d, GPU Type: %s",
                  ^
main.c:1369:10: warning: assignment discards ‘volatile’ qualifier from pointer target type [-Wdiscarded-qualifiers]
    MyJob = CurrentJob;
          ^
main.c: In function ‘SigHandler’:
main.c:1474:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
  write(ExitPipe[1], &c, 1);
  ^
main.c: In function ‘main’:
main.c:1788:2: warning: ignoring return value of ‘pipe’, declared with attribute warn_unused_result [-Wunused-result]
  pipe(ExitPipe);
  ^
main.c:2054:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
  read(ExitPipe[0], &c, 1);
  ^
gcc -DPTW32_STATIC_LIB -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib  crypto/aesb.o crypto/aesb-x86-impl.o crypto/c_blake256.o crypto/c_groestl.o crypto/c_keccak.o crypto/c_jh.o crypto/c_skein.o crypto/oaes_lib.o cryptonight.o log.o net.o minerutils.o gpu.o main.o -ljansson -lOpenCL -lpthread -ldl -o miner

$

7. Configure the xmr.conf as needed

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"threads": 1,
"rawintensity": 640,
"worksize": 8
},
{
"index": -1,
"threads": 1,
"rawintensity": 8,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://<valid_pool>:<valid_port>",
"user": "<valid_user>",
"pass": "x"
}
]
}
]
}

8. Execute the miner and get this error a few seconds later

Code:
$ ./miner xmr.conf

[17:32:27] Setting up GPU(s).
[17:32:27] Successfully connected to pool's stratum.
*** buffer overflow detected ***: ./miner terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7f5d856a0725]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f5d8574189c]
/lib/x86_64-linux-gnu/libc.so.6(+0x1168a0)[0x7f5d8573f8a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x115bf2)[0x7f5d8573ebf2]
./miner[0x410c35]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f5d859f96fa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5d8572fb5d]
======= Memory map: ========
00400000-00419000 r-xp 00000000 fc:00 2623891                            /miner
00619000-0061a000 r--p 00019000 fc:00 2623891                            /miner
0061a000-0061b000 rw-p 0001a000 fc:00 2623891                            /miner
01418000-01439000 rw-p 00000000 00:00 0                                  [heap]
7f5d7fdea000-7f5d7fe00000 r-xp 00000000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7fe00000-7f5d7ffff000 ---p 00016000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d7ffff000-7f5d80000000 rw-p 00015000 fc:00 3932690                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f5d80000000-7f5d80021000 rw-p 00000000 00:00 0
7f5d80021000-7f5d84000000 ---p 00000000 00:00 0
7f5d840df000-7f5d840e0000 ---p 00000000 00:00 0
7f5d840e0000-7f5d848e0000 rw-p 00000000 00:00 0
7f5d848e0000-7f5d848f7000 r-xp 00000000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d848f7000-7f5d84af7000 ---p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af7000-7f5d84af8000 r--p 00017000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af8000-7f5d84af9000 rw-p 00018000 fc:00 3932755                    /lib/x86_64-linux-gnu/libresolv-2.23.so
7f5d84af9000-7f5d84afb000 rw-p 00000000 00:00 0
7f5d84afb000-7f5d84b00000 r-xp 00000000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84b00000-7f5d84d00000 ---p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d00000-7f5d84d01000 r--p 00005000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d01000-7f5d84d02000 rw-p 00006000 fc:00 3932726                    /lib/x86_64-linux-gnu/libnss_dns-2.23.so
7f5d84d02000-7f5d84d0d000 r-xp 00000000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84d0d000-7f5d84f0c000 ---p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0c000-7f5d84f0d000 r--p 0000a000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0d000-7f5d84f0e000 rw-p 0000b000 fc:00 3932728                    /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f5d84f0e000-7f5d84f14000 rw-p 00000000 00:00 0
7f5d84f14000-7f5d84f17000 r-xp 00000000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d84f17000-7f5d85116000 ---p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85116000-7f5d85117000 r--p 00002000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85117000-7f5d85118000 rw-p 00003000 fc:00 3932678                    /lib/x86_64-linux-gnu/libdl-2.23.so
7f5d85118000-7f5d85220000 r-xp 00000000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85220000-7f5d8541f000 ---p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d8541f000-7f5d85420000 r--p 00107000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85420000-7f5d85421000 rw-p 00108000 fc:00 3932705                    /lib/x86_64-linux-gnu/libm-2.23.so
7f5d85421000-7f5d85428000 r-xp 00000000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85428000-7f5d85627000 ---p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85627000-7f5d85628000 r--p 00006000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85628000-7f5d85629000 rw-p 00007000 fc:00 3932757                    /lib/x86_64-linux-gnu/librt-2.23.so
7f5d85629000-7f5d857e9000 r-xp 00000000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d857e9000-7f5d859e8000 ---p 001c0000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859e8000-7f5d859ec000 r--p 001bf000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ec000-7f5d859ee000 rw-p 001c3000 fc:00 3932664                    /lib/x86_64-linux-gnu/libc-2.23.so
7f5d859ee000-7f5d859f2000 rw-p 00000000 00:00 0
7f5d859f2000-7f5d85a0a000 r-xp 00000000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85a0a000-7f5d85c09000 ---p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c09000-7f5d85c0a000 r--p 00017000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0a000-7f5d85c0b000 rw-p 00018000 fc:00 3932751                    /lib/x86_64-linux-gnu/libpthread-2.23.so
7f5d85c0b000-7f5d85c0f000 rw-p 00000000 00:00 0
7f5d85c0f000-7f5d85c15000 r-xp 00000000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85c15000-7f5d85e15000 ---p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e15000-7f5d85e16000 rw-p 00006000 fc:00 3677498                    /usr/lib/x86_64-linux-gnu/amdgpu-pro/libOpenCL.so.1
7f5d85e16000-7f5d85e22000 r-xp 00000000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d85e22000-7f5d86021000 ---p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86021000-7f5d86022000 r--p 0000b000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86022000-7f5d86023000 rw-p 0000c000 fc:00 3678033                    /usr/lib/x86_64-linux-gnu/libjansson.so.4.7.0
7f5d86023000-7f5d86049000 r-xp 00000000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86238000-7f5d8623d000 rw-p 00000000 00:00 0
7f5d86245000-7f5d86248000 rw-p 00000000 00:00 0
7f5d86248000-7f5d86249000 r--p 00025000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d86249000-7f5d8624a000 rw-p 00026000 fc:00 3932640                    /lib/x86_64-linux-gnu/ld-2.23.so
7f5d8624a000-7f5d8624b000 rw-p 00000000 00:00 0
7ffcc1f08000-7ffcc1f29000 rw-p 00000000 00:00 0                          [stack]
7ffcc1fae000-7ffcc1fb0000 r--p 00000000 00:00 0                          [vvar]
7ffcc1fb0000-7ffcc1fb2000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted (core dumped)

$

9. The AMD drivers are installed and loaded correctly

Code:
$ sudo lshw -class display | grep "driver"

       configuration: driver=amdgpu latency=0
       configuration: driver=amdgpu latency=0
       configuration: driver=i915 latency=0

$

10. I have two AMD GPUs installed on this Ubuntu 16.04 headless server

R9 390X - Hawaii
R9 380 - Tonga

11. The clinfo command shows all the information on the GPUs

Code:
$ clinfo

Number of platforms: 1
  Platform Profile: FULL_PROFILE
  Platform Version: OpenCL 2.0 AMD-APP (2117.7)
  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: 3
  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#1, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 4244635648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 8541122560
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Hawaii
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_GPU
  Vendor ID: 1002h
  Board name:
  Device Topology: PCI[ B#2, D#0, F#0 ]
  Max compute units: 14
  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: 4
  Preferred vector width short: 2
  Preferred vector width int: 1
  Preferred vector width long: 1
  Preferred vector width float: 1
  Preferred vector width double: 1
  Native vector width char: 4
  Native vector width short: 2
  Native vector width int: 1
  Native vector width long: 1
  Native vector width float: 1
  Native vector width double: 1
  Max clock frequency: 555Mhz
  Address bits: 64
  Max memory allocation: 1409215488
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 8
  Max image 2D width: 16384
  Max image 2D height: 16384
  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: Read/Write
  Cache line size: 64
  Cache size: 16384
  Global memory size: 2127253504
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Scratchpad
  Local memory size: 32768
  Max pipe arguments: 0
  Max pipe active reservations: 0
  Max pipe packet size: 0
  Max global variable size: 0
  Max global variable preferred total size: 0
  Max read/write image args: 0
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Tonga
  Vendor: Advanced Micro Devices, Inc.
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (VM)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event


  Device Type: CL_DEVICE_TYPE_CPU
  Vendor ID: 1002h
  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: 8
  Preferred vector width double: 4
  Native vector width char: 16
  Native vector width short: 8
  Native vector width int: 4
  Native vector width long: 2
  Native vector width float: 8
  Native vector width double: 4
  Max clock frequency: 871Mhz
  Address bits: 64
  Max memory allocation: 2147483648
  Image support: Yes
  Max number of images read arguments: 128
  Max number of images write arguments: 64
  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: 8240955392
  Constant buffer size: 65536
  Max number of constant args: 8
  Local memory type: Global
  Local memory size: 32768
  Max pipe arguments: 16
  Max pipe active reservations: 16
  Max pipe packet size: 2147483648
  Max global variable size: 1879048192
  Max global variable preferred total size: 1879048192
  Max read/write image args: 64
  Max on device events: 0
  Queue on device max size: 0
  Max on device queues: 0
  Queue on device preferred size: 0
  SVM capabilities:
    Coarse grain buffer: No
    Fine grain buffer: No
    Fine grain system: No
    Atomics: No
  Preferred platform atomic alignment: 0
  Preferred global atomic alignment: 0
  Preferred local atomic alignment: 0
  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 on Host properties:
    Out-of-Order: No
    Profiling : Yes
  Queue on Device properties:
    Out-of-Order: No
    Profiling : No
  Platform ID: 0x7fae083c38f8
  Name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
  Vendor: GenuineIntel
  Device OpenCL C version: OpenCL C 1.2
  Driver version: 2117.7 (sse2,avx)
  Profile: FULL_PROFILE
  Version: OpenCL 1.2 AMD-APP (2117.7)
  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_3d_image_writes 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_media_ops2 cl_amd_popcnt cl_khr_spir cl_khr_gl_event


$

Any help with getting further along would be greatly appreciated as my next step is trying one AMD GPU card installed at a time to see what happens




1. I resolved the issue I was having before by modifying the compiler options further with the -D_FORTIFY_SOURCE=0 option shown below

Code:
OPT 	= -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib 
CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11 -D_FORTIFY_SOURCE=0 
CC = gcc
LD = gcc
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS = -ljansson -lOpenCL -lpthread -ldl

2. I can successfully CPU and GPU mine XMR with the following xmr.conf file

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
                                {
                                        "index": 0,
                                        "threads": 2,
                                        "rawintensity": 1024,
                                        "worksize": 8
                                },
                                {
                                        "index": 1,
                                        "threads": 1,
                                        "rawintensity": 640,
                                        "worksize": 8
                                },
{
"index": -1,
"threads": 3,
"rawintensity": 12,
"worksize": 12
}
],
"pools":
[
{
"url": "stratum+tcp://<valid_pool>:<valid_port>",
"user": "<valid_user>",
"pass": "x"
}
]
}
]
}

3. Current output example from my wolf-xmr-miner build and configuration listed above

Code:
[16:27:38] New job at diff 13419
[16:27:38] Thread 5, (CPU): 66.80H/s
[16:27:38] Thread 4, (CPU): 67.25H/s
[16:27:38] Thread 3, (CPU): 66.24H/s
[16:27:39] Thread 2, GPU ID 1, GPU Type: Tonga: 485.17H/s
[16:27:40] Thread 0, GPU ID 0, GPU Type: Hawaii: 381.56H/s
[16:27:40] Thread 1, GPU ID 0, GPU Type: Hawaii: 381.56H/s
[16:27:41] Thread 2, GPU ID 1, GPU Type: Tonga: 485.26H/s
[16:27:42] Thread 0, GPU ID 0, GPU Type: Hawaii: 380.56H/s
[16:27:42] Thread 1, GPU ID 0, GPU Type: Hawaii: 380.56H/s
[16:27:44] Thread 2, GPU ID 1, GPU Type: Tonga: 484.93H/s
[16:27:45] Thread 0, GPU ID 0, GPU Type: Hawaii: 380.30H/s
[16:27:45] Thread 1, GPU ID 0, GPU Type: Hawaii: 380.30H/s
[16:27:47] Thread 2, GPU ID 1, GPU Type: Tonga: 484.79H/s
[16:27:48] Thread 0, GPU ID 0, GPU Type: Hawaii: 381.18H/s
[16:27:48] Thread 1, GPU ID 0, GPU Type: Hawaii: 381.19H/s
[16:27:48] Share accepted: 706/759 (93.02%)
[16:27:48] Total Hashrate: 1447.45H/s

4. I will continue to play around with the best settings for xmr.conf and find the best performance and stability. 

5. I haven't done any overclock/undervolt efforts on the stock AMD GPUs and will see what options might help performance along with stability as time permits. 

At this point I'm just happy to have it working now using stock settings and hope this information helps others attempting to use the wolf-xmr-miner on Ubuntu 16.04 LTS in the future.  Thanks to Wolf again for sharing with others and making this wonderful GPU miner.


I am getting the following on these cards below

806 H/s on my R9 390X - Hawaii with threads=1, rawintensity=1390 and worksize=8
590 H/s on my R9 380 - Tonga with threads=1, rawintensity=896 and worksize=8
567 H/s on my RX 470 - Ellesmere with threads=1, rawintensity=1022 and worksize=8

I will be testing an RX 480 next as time permits and share the results afterwards


Title: Re: Wolf's XMR GPU Miner
Post by: adamvp on November 01, 2016, 06:54:56 PM
Quite good. I had 540hs at 380x with Claymore.  Have to check if Monero back to profitability..


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on November 07, 2016, 06:07:41 PM
Is it possible to know what kind of hashrates to expect from the following cards:

- RX 480 8GB
- R9 390 8GB

?

thank you all

got an XFX RX-480P836BM 8GB currently in the 622-623h/s range. did not mod GPU.

[13:10:31] Thread 0, GPU ID 0, GPU Type: Ellesmere: 622.99H/s
[13:10:34] Thread 0, GPU ID 0, GPU Type: Ellesmere: 622.89H/s
[13:10:37] Thread 2, (CPU): 53.54H/s
[13:10:37] Share accepted: 6/6 (100.00%)
[13:10:37] Total Hashrate: 1034.17H/s

in hibernate mode, its even faster ;)

[13:37:07] Thread 0, GPU ID 0, GPU Type: Ellesmere: 626.81H/s
[13:37:10] Thread 0, GPU ID 0, GPU Type: Ellesmere: 626.83H/s
[13:37:10] Share accepted: 17/17 (100.00%)
[13:37:10] Total Hashrate: 1050.57H/s


OS - running xubuntu 16.04LTS with linux amdgpu driver
**both CPU multiplier (20--->21) and bus speed (200--->210) increased in mobo bios.

xmr.conf GPU settings:

"index": 0,
"corefreq": 1275,
"memfreq": 2133,
"fanspeed": 65,
"powertune": 20,
"threads": 1,
"rawintensity": 1022,
"worksize": 8

hope this helps  :)


Title: Re: Wolf's XMR GPU Miner
Post by: diedo on November 10, 2016, 09:48:42 PM
builing was easy on ubuntu 16.04.1 with install two dev libs and  the latest amdpro gpu on R9 290X

the libs  were selected from synaptic
ocl
jasson

then i had to issue the make command.
now i need an explanation for the conf file cause i don't really get it. i get 750h/s is this normal?


Title: Re: Wolf's XMR GPU Miner
Post by: diedo on November 11, 2016, 05:21:43 PM
It also crashes with Minergate. seg fault.


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on November 11, 2016, 08:55:25 PM
It also crashes with Minergate. seg fault.

Minergate was the first miner i used and it started causing issues with my GPU after going from 6.5 to 6.6. this began my search for something more reliable and stable. tried Claymore's miner next but it was causing invalid shares on my rig. not sure if it was me or the miner? next i found Wolf's XMR miner and it works great with both my CPU and GPUs.

here is a snapshot of my notes from a fresh installation of Xubuntu 16.04.1 LTS. maybe this will help even though i'm using RX480s. granted you'll have to modify the Makefile and xmr.conf yourself to accommodate your system. this was pieced together from multiple websites / forums / installation notes found across the web. after dozens of fresh trial and error installs, this method works for me.
thanks to all those before me for your contributions, especially Wolf for writing this software!
(and yes, i know went a little overboard with installing all of the dependencies... but hey it works for my system)

 
after installing xubuntu, open terminal

sudo apt-get update && sudo apt-get upgrade
sudo apt-get install aptitude
sudo aptitude update

sudo aptitude install --with-recommends build-essential autotools-dev \
autoconf automake libcurl3 git make cmake \
libssl-dev pkg-config libevent-dev libunbound-dev libminiupnpc-dev \
doxygen supervisor jq libboost-all-dev htop bcc linux-source \
debian-keyring g++-multilib g++-5-multilib u-boot-tools libjansson-dev

sudo aptitude install --with-recommends cdbs dh-make debhelper \
dkms libqtgui4 execstack dh-modaliases libcurl4-openssl-dev

sudo apt-get install apt-file
apt-file update
reboot
 
Now install AMD SDK APP 3.0 from AMD site and reboot
Next download AMDGPU-PRO_16.30.3-315407.tar.xz then install, reboot (if you can't find this let me know i've got a copy saved. 16.40 driver gave me issues so i went back to this one)

download wolf-xmr-miner-master.zip
extract, replace Makefile with yours (you'll have to link to your OpenCL folder )
open folder in terminal, run make
after successful build, replace xmr.conf (configure to your system's specs)
type ./miner xmr.conf

Miner should connect to stratum and start hashing!

i've shared my xmr.conf settings for a single GPU in a previous post. if you'd like to see what it looks like using multiple GPUs, i can share.

hopefully this will get you (and others) up and running without having to use "doze" :)

primary references that I used:
http://askubuntu.com/questions/794529/amdgpu-pro-install-on-ubuntu-gnome-16-04-with-r9-285-and-rx-480
https://dennis.gesker.com/2015/08/20/monero-xmr-mining-on-ubuntu-linux-15-04/
http://superkuh.com/monero.html


Title: Re: Wolf's XMR GPU Miner
Post by: adamvp on November 13, 2016, 09:22:08 AM
It seems monero can have another pump..
Any chance for new miner release?


Title: Re: Wolf's XMR GPU Miner
Post by: induktor on November 13, 2016, 03:05:25 PM
Hello!
Question, will it work with nvidia 970 / 1070 GPUs in OpenCL ? (lubuntu 14.04 or 16.04)

thanks
inkdt


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on November 13, 2016, 03:39:52 PM
Hello!
Question, will it work with nvidia 970 / 1070 GPUs in OpenCL ? (lubuntu 14.04 or 16.04)

thanks
inkdt

my rig is AMD (the CPU, GPUs, and chipset) i think you'll need Cuda for the nvidia GPU. hopefully these links assist you. can't promise it will work, please share if you do!

http://docs.nvidia.com/cuda/cuda-installation-guide-linux/#axzz4Pu5Gkzk2
https://www.pugetsystems.com/labs/hpc/Install-Ubuntu-16-04-or-14-04-and-CUDA-8-and-7-5-for-NVIDIA-Pascal-GPU-825/



Title: Re: Wolf's XMR GPU Miner
Post by: Vaere on November 15, 2016, 03:39:46 AM
Great Miner
hmm.. just curious to see how mine compares to others.  Am experimenting on my system, switching from Ethereum.

Currently running one   390x   and two 290x. (CPU I5, but not mining)
Power Consumption is 770W , with ETH I was hitting 1075W
GPU Temps are more then 15 deg cooler.  (Stock fans)

AMD 16.11.3 Drivers
Windows 10 64bit
CrossFire Disabled

390x OC in windows
GPU: 1121MHZ   Memory:1500 (standard)

290x's 
GPU: 1150MHz   Memory: 1250 (Standard)

All cards
rawintensity: 1024   worksize: 8 (Tried  a few other intensities, but they dropped rates)

[22:30:32] Thread 1, GPU ID 1, GPU Type: Hawaii: 728.31H/s
[22:30:32] Thread 0, GPU ID 0, GPU Type: Hawaii: 729.34H/s
[22:30:32] Thread 2, GPU ID 2, GPU Type: Hawaii: 782.87H/s
[22:30:32] Share accepted: 20/20 (100.00%)
[22:30:32] Total Hashrate: 2240.53H/s

one thread only per,  would upping the threads increase the hash?  Anyone changing the Memory clocks? does it have a noticeable effect?

 Never used any of the Wolf line :) .  main reason I got into this is my computer was sitting idle 90% of the time.
Was running Genoil so there was pretty minimal configuration.







Title: Re: Wolf's XMR GPU Miner
Post by: zen0s on November 16, 2016, 08:58:19 AM
Hi ..! I'm new to wolf's GPU Miner .. I have r9 270x and i have a while mining with claymore's gpu miner ... I am running windows 10 64 bit and i want some help setting the miner .. Is there any sample config for my gpu ...! I think claymore rip us off !!

i get this error "Error parsing version string from clGetDeviceInfo. This should never happen"


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on November 16, 2016, 08:56:09 PM
Great Miner
hmm.. just curious to see how mine compares to others.  Am experimenting on my system, switching from Ethereum.

Currently running one   390x   and two 290x. (CPU I5, but not mining)
Power Consumption is 770W , with ETH I was hitting 1075W
GPU Temps are more then 15 deg cooler.  (Stock fans)

AMD 16.11.3 Drivers
Windows 10 64bit
CrossFire Disabled

390x OC in windows
GPU: 1121MHZ   Memory:1500 (standard)

290x's 
GPU: 1150MHz   Memory: 1250 (Standard)

All cards
rawintensity: 1024   worksize: 8 (Tried  a few other intensities, but they dropped rates)

[22:30:32] Thread 1, GPU ID 1, GPU Type: Hawaii: 728.31H/s
[22:30:32] Thread 0, GPU ID 0, GPU Type: Hawaii: 729.34H/s
[22:30:32] Thread 2, GPU ID 2, GPU Type: Hawaii: 782.87H/s
[22:30:32] Share accepted: 20/20 (100.00%)
[22:30:32] Total Hashrate: 2240.53H/s

one thread only per,  would upping the threads increase the hash?  Anyone changing the Memory clocks? does it have a noticeable effect?

 Never used any of the Wolf line :) .  main reason I got into this is my computer was sitting idle 90% of the time.
Was running Genoil so there was pretty minimal configuration.







i've noticed a small difference when altering the memory clock variable. its not huge but you can dial in the right combo for your system to get the most efficient hash-rate. currently got both of mine holding steady at 627-627.50 in hibernate. ever think about switching to linux?


Title: Re: Wolf's XMR GPU Miner
Post by: pacers101 on November 29, 2016, 08:06:35 PM
what is:  Error -63 when calling clEnqueueNDRangeKernel for kernel 6.

the miner runs for 15 sec or so then gives me that. I'm on windows 8.1, with 2 r7 370



Title: Re: Wolf's XMR GPU Miner
Post by: dallase on November 29, 2016, 09:15:15 PM
This is me killin it on Ubuntu 16.04 w/ 6x MSI rx470 4GB

[14:31:16] Thread 3, GPU ID 3, GPU Type: Ellesmere: 635.87H/s
[14:31:16] Thread 2, GPU ID 2, GPU Type: Ellesmere: 634.97H/s
[14:31:17] Thread 5, GPU ID 5, GPU Type: Ellesmere: 641.74H/s
[14:31:18] Thread 1, GPU ID 1, GPU Type: Ellesmere: 644.15H/s
[14:31:18] Thread 4, GPU ID 4, GPU Type: Ellesmere: 641.23H/s
[14:31:18] Thread 0, GPU ID 0, GPU Type: Ellesmere: 641.01H/s
[14:31:18] Share accepted: 72/72 (100.00%)
[14:31:18] Total Hashrate: 3838.97H/s

BONUS --> Only 640w total draw at the wall... (custom bios 1160core/1900mem/1500straps)


What I've learned...

1) getting this compiled and working can be a bit of a chore.  I worked around some seg faults and openCL errors, and tested a million thread/intensity/worksize options.

2) my cards seem to like rawintensity @ 960, with 8 worksize

3) minergate only accepted 40% of my shares, piece of crap.  Moving on...

4) monerohash.com had 100% share accept, but require 7 XMR balance to withdraw to an exchange (using -u Base.PaymentID).  That doesnt work for me.  Moving on...

5) dwarfpool had 100% share accept.  Only downside is 2% pool fee.   Still considering other options...

So this is where I am ATM in my Monero GPU mining on linux journey...  hope you find it useful.



Title: Re: Wolf's XMR GPU Miner
Post by: dallase on November 29, 2016, 09:30:08 PM

[14:31:18] Total Hashrate: 3838.97H/s

BONUS --> Only 640w total draw at the wall... (custom bios 1160core/1900mem/1500straps)


That said, with adjusted hash rates and power numbers, it still tells me XMR is the 6th best coin I can mine...

$ ./coinpicker
2016-11-29 15:17:19   Active Coin is zec [was at 121%], [now at 110%]
2016-11-29 15:17:19   Rank #1 -> zec (110)
2016-11-29 15:17:19   Rank #2 -> etc (101)
2016-11-29 15:17:19   Rank #3 -> eth (100)
2016-11-29 15:17:19   Rank #4 -> zcl (96)
2016-11-29 15:17:19   Rank #5 -> exp (98)
2016-11-29 15:17:19   Rank #6 -> xmr (78)
2016-11-29 15:17:19   Sticking with zec for now...

I think I'm leaving a bit on the table with XMR because the wattage is so low...  My ETH/ETC/EXP mine (156mh/s) runs 910w.  My ZEC/ZCL mine runs 830w (980h/s).     But since the thread/intensity/workload do not improve, I think the software is maxed.  So maybe I'll try some amdgpu-pro tweaking of /sys/class/drm/card0/device/pp_mclk_od and /sys/class/drm/card0/device/pp_sclk_od when launching the XMR mine.

Stay tuned...




Title: Re: Wolf's XMR GPU Miner
Post by: QuintLeo on November 30, 2016, 12:39:00 AM
I know it's a wee bit off topic, but does anyone have WORKING links to Wolf's CPU miner for Cryptonight?


Title: Re: Wolf's XMR GPU Miner
Post by: Nik4691 on November 30, 2016, 01:08:22 AM
I know it's a wee bit off topic, but does anyone have WORKING links to Wolf's CPU miner for Cryptonight?
cpuminer-multi-wolf-06-09-2014  Windows x64 binaries! AES-NI only!
https://bitcointalk.org/index.php?topic=632724.0

Sorry, I see the links don't work now.


Title: Re: Wolf's XMR GPU Miner
Post by: cryptomined on November 30, 2016, 08:46:34 AM
does this work in windows 10 with drivers 16.10.#? or 16.9.#?

I keep trying to run it but my command windows just closes right after trying to run it..
not sure if I fixed the config file proper, but I think I did
is there some instrucitons for setting up the config file somwhere that I missed?

Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: mirny on November 30, 2016, 11:08:41 AM
@dallase

Hi, where can I find that coinpicker application?
cheers


Title: Re: Wolf's XMR GPU Miner
Post by: pacers101 on November 30, 2016, 05:39:37 PM
7770 Does good ~162h/s, Claymore does ~170h/s

I get this a lot:
"Share rejected (Low difficulty share)"

http://imgur.com/a/UQdRs

5830 Throws error:
"Error -54 when calling clEnqueueNDRangeKernel for kernel 3."

Config:

Code:
{

 "Algorithms":
[{
      "name": "CryptoNight",
      "devices":[{
            "index": 0,
                                "rawintensity": 216,
            "worksize": 8
                },
{
            "index": 1,
                                "rawintensity": 128,
            "worksize": 8
                }
          ],

      "pools":[{
            "url": "stratum+tcp://mine.moneropool.com:8080",
            "user": "user",
            "pass": "x"
         }]
}]
}


It is neat you are working on an open source miner.

I get a similar error, mine is error 63 and kernel 6 but it also says "when calling clEnqueueNDRangeKernel for kernel" . have you fixed this at all, I'd like to know how if you have. thanks


Title: Re: Wolf's XMR GPU Miner
Post by: oldDIN on December 01, 2016, 10:24:30 AM
to take 7770 version 3,
4 falls on them due to lack of memory or reject


Title: Re: Wolf's XMR GPU Miner
Post by: Koiner247 on December 09, 2016, 08:37:48 AM
+1

I know it's a wee bit off topic, but does anyone have WORKING links to Wolf's CPU miner for Cryptonight?


Title: Re: Wolf's XMR GPU Miner
Post by: Ned Kelly on December 09, 2016, 05:07:08 PM
+1

I know it's a wee bit off topic, but does anyone have WORKING links to Wolf's CPU miner for Cryptonight?
Just download file from 1st post and use -1 as device index.


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 10, 2016, 08:51:08 PM
Guys,

Trying to make my way into XMR mining but I'm getting the old error on my rigs:

Code:
Error -1 when calling clGetDeviceIDs for number of devices

I'm using miner version 0.4 on a rig with 6x480 4GB under Win10 x64, Crimson 16.9.2.

This is my conf file:

Code:
{

"Algorithms":

[

{

"name": "CryptoNight",
"devices":
[
{
"index": 0,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 1,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 2,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 3,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 4,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 5,
"threads": 1,
"rawintensity": 640,
"worksize": 16
}
],
"pools":
[
{
"url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
"user": "47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGRoyZk3ES1s1V4QVcB.a34e4b35838dde3cf5e68bca39ed1f64376b71eaee082407d50d4ca4d11101ef.02",
"pass": "x"

Any ideas?

Thanks!


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 11, 2016, 01:26:00 PM
C'mon guys, anyone using this miner on a multi AMD GPU rig?

Can you please help me?


Title: Re: Wolf's XMR GPU Miner
Post by: QuintLeo on December 12, 2016, 08:08:00 AM
I suspect most of us that have multi-AMD rigs are mining more profitable stuff like ETH/ETC/ZEC over mining XMR with those cards.



Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 12, 2016, 10:38:25 AM
I suspect most of us that have multi-AMD rigs are mining more profitable stuff like ETH/ETC/ZEC over mining XMR with those cards.


Yeah, but XMR profitability is now close to ETH/ZEC and I wanted to try this miner just in case... ;D


Title: Re: Wolf's XMR GPU Miner
Post by: Termie on December 12, 2016, 08:03:44 PM
Guys,

Trying to make my way into XMR mining but I'm getting the old error on my rigs:

Code:
Error -1 when calling clGetDeviceIDs for number of devices

I gave it up with this miner. Never get it to run with my 1x290x / 3x Nano rig.
I tried v0.3 and v0.4 with Crimson 15.12 and 16.7.3. No chance, always getting this -1 error.
With Claymore's it runs immediately.


Title: Re: Wolf's XMR GPU Miner
Post by: ku4eto on December 12, 2016, 08:41:27 PM
Okay guys.

R9 290 Sapphire Trix Here, Hynix Memory.

Running at 16.12.1 drivers, using Wattman global OC at 1000/1375.

With conf of:

rawintensity: 800
threads: 2

I am getting ~3.4GB of VRAM used and around 700 H/s.

Any more rawintensity and i either run out of VRAM and BSOD the PC, or it turns into negative scaling.

How do Worksize affect the hash rate?

Temps are ~75 core, <70 on VRMs.

Fan speed is default profile, ramps up to 40%.

Also, why my 1605T gets 22H/s at default conf, and the work VM with E5 2660v2 gets 25H/s with AVX1 cpu miner? I thougth the difference would be bigger...

Also, for some reason, when running the miner, i get occasional hitches (mouse, scrolling). The DPC latency seems normal, ideas on that?


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on December 12, 2016, 08:54:53 PM
How do Worksize affect the hash rate?

With 2 threads I would try to lower that worksize. 32, 16, 8 and so on.


Title: Re: Wolf's XMR GPU Miner
Post by: ku4eto on December 12, 2016, 09:29:58 PM
How do Worksize affect the hash rate?

With 2 threads I would try to lower that worksize. 32, 16, 8 and so on.

The default one is 16, i have tried changing between 24 and 8, and saw no difference.

I couldn't find any specific data about this. And didn't found much about the clock speed relations. What does the Wolf miner benefit more from? Core or memory overclock? I guess if i lower the core clocks, i can increase the memory, without needing to increase the voltage.


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on December 12, 2016, 09:34:39 PM
How do Worksize affect the hash rate?

With 2 threads I would try to lower that worksize. 32, 16, 8 and so on.

The default one is 16, i have tried changing between 24 and 8, and saw no difference.

I couldn't find any specific data about this. And didn't found much about the clock speed relations. What does the Wolf miner benefit more from? Core or memory overclock? I guess if i lower the core clocks, i can increase the memory, without needing to increase the voltage.

First find those best settings, then start to fine tune with core & mem. Lower than 8 could work.


Title: Re: Wolf's XMR GPU Miner
Post by: QuintLeo on December 13, 2016, 04:28:34 AM
Okay guys.

R9 290 Sapphire Trix Here, Hynix Memory.

Running at 16.12.1 drivers, using Wattman global OC at 1000/1375.


 1) No reason to run the 16.12.1 drivers for ANY reason, they're demonstrated to be junk for mining - 5-10% LOWER hashrate than 16.9.2 or 15.12
     Bloated junk with very poor performance AND no tolerance for modded BIOS on many cards that IMO should never have been released.

 2) No reason to run anything past 15.12 on a card prior to the RX series, as NONE of the 16.x series drivers offer ANY improvement and tend to be LESS stable on the older cards.
     16.9.2 is a tossup on hashrate though, if you feel the need to be compatable with newer cards for future upgrades to a rig.

 3) Drop Wattman. It's total junk. PITA interface, very ANTI-intuitive controls that don't WORK very well if they work at all, UI is totally FUBAR.
     MSI Afterburner blows it away TOTALLY on configurability and ease of use, especially on fan control which is CRITICAL for 290/29x/390/390x cards.



 As far as profitability - I have yet to see XMR even get CLOSE to ETH/ETC/ZEC on profitability on AMD cards in the ballpark year I've been watching them all.
 Nvidia, yes - XMR is somewhat more profitable on a regular basis on my GTX 750 Ti, but that card seems to be THE sweet spot for XMR but doesn't do ETH/ETC very well at all (and soon not at all) and doesn't do well on ZEC even with the NiceHash eqm miner.


 Your number may vary of course.



 I don't know if TheStilt ever did any BIOS that would work with non-Reference R9 290s, but they made a HUGE difference on my Sapphire ref design R9 290s - 20 or so degrees cooler even when bumping up the core clock from the "can barely run at 947 before thermal limiting hits" pre-bios to "runs comfortably at 1100 core clock" post-bios, and the memory timings are a TON tighter which gave a major hashrate jump even before I started moving the clocks from the stock 947/1250.



Title: Re: Wolf's XMR GPU Miner
Post by: ku4eto on December 13, 2016, 06:22:21 AM
Okay guys.

R9 290 Sapphire Trix Here, Hynix Memory.

Running at 16.12.1 drivers, using Wattman global OC at 1000/1375.


 1) No reason to run the 16.12.1 drivers for ANY reason, they're demonstrated to be junk for mining - 5-10% LOWER hashrate than 16.9.2 or 15.12
     Bloated junk with very poor performance AND no tolerance for modded BIOS on many cards that IMO should never have been released.

 2) No reason to run anything past 15.12 on a card prior to the RX series, as NONE of the 16.x series drivers offer ANY improvement and tend to be LESS stable on the older cards.
     16.9.2 is a tossup on hashrate though, if you feel the need to be compatable with newer cards for future upgrades to a rig.

 3) Drop Wattman. It's total junk. PITA interface, very ANTI-intuitive controls that don't WORK very well if they work at all, UI is totally FUBAR.
     MSI Afterburner blows it away TOTALLY on configurability and ease of use, especially on fan control which is CRITICAL for 290/29x/390/390x cards.



 As far as profitability - I have yet to see XMR even get CLOSE to ETH/ETC/ZEC on profitability on AMD cards in the ballpark year I've been watching them all.
 Nvidia, yes - XMR is somewhat more profitable on a regular basis on my GTX 750 Ti, but that card seems to be THE sweet spot for XMR but doesn't do ETH/ETC very well at all (and soon not at all) and doesn't do well on ZEC even with the NiceHash eqm miner.


 Your number may vary of course.



 I don't know if TheStilt ever did any BIOS that would work with non-Reference R9 290s, but they made a HUGE difference on my Sapphire ref design R9 290s - 20 or so degrees cooler even when bumping up the core clock from the "can barely run at 947 before thermal limiting hits" pre-bios to "runs comfortably at 1100 core clock" post-bios, and the memory timings are a TON tighter which gave a major hashrate jump even before I started moving the clocks from the stock 947/1250.




1) Wrong, i am using this rig to game as well, not a dedicated zombie machine.

2) ^

3) Wattman offers exactly what i need, profile based OC. MSI AB or TriXX voltage controls and overclock is global and screws up all other Windows profiles as well.  Wattman offers fan control as well, but i am using the default fan curve, which is actually enough.


Anyway, i figured out the mouse hitching - it was due to GPU-Z.
When i stopped it (and all other monitoring programs), the hashrate went from ~700h/s to 800h/s.
And the pool reports that i am actually doing 0.9 - 1.2 kh/s right now (PC left on, while i am on work).

Anyway, tried with workunit: 2 and 4, no differennce again O_o ?


Title: Re: Wolf's XMR GPU Miner
Post by: QuintLeo on December 13, 2016, 07:15:34 AM
Stock fan profile will likely get your card DEAD, or at best will severely limit it for mining usage due to frequent if not constant thermal limiting.

 As a gaming machine that only mines secondarily though, TheStilt bios mods are probably a bad option for you.


 It's odd that GPU-Z would impact your hashrate - I've NEVER seen it do that in a lot of usage on a lot of varied hardware platforms.

 I suspect something underlying as the actual issue, not GPU-Z itself.

 I also suspect you'll see a lot fewer issues OVERALL if you run the 16.11.5 drivers vs the 16.12.1, even if you game.
 I find it VERY interesting that nobody is comparing performance of 16.12.1 vs 16.11.5 or vs 16.9.2 - makes me wonder if the mining performance isn't the ONLY performance hit the new version offers.





Title: Re: Wolf's XMR GPU Miner
Post by: moonmaths on December 13, 2016, 05:42:41 PM
This is me killin it on Ubuntu 16.04 w/ 6x MSI rx470 4GB

[14:31:16] Thread 3, GPU ID 3, GPU Type: Ellesmere: 635.87H/s
[14:31:16] Thread 2, GPU ID 2, GPU Type: Ellesmere: 634.97H/s
[14:31:17] Thread 5, GPU ID 5, GPU Type: Ellesmere: 641.74H/s
[14:31:18] Thread 1, GPU ID 1, GPU Type: Ellesmere: 644.15H/s
[14:31:18] Thread 4, GPU ID 4, GPU Type: Ellesmere: 641.23H/s
[14:31:18] Thread 0, GPU ID 0, GPU Type: Ellesmere: 641.01H/s
[14:31:18] Share accepted: 72/72 (100.00%)
[14:31:18] Total Hashrate: 3838.97H/s

BONUS --> Only 640w total draw at the wall... (custom bios 1160core/1900mem/1500straps)



How are you modifying your bios?  You just going into UEFI boot and changing the options?  I'm new to this obviously. 

Core 1160 = gpu core clock rate?
Mem = memclock rate?
What is straps? 
Also, have you tried undervolting the gpu's or is it possible on ubuntu? 

I have 2 unmodded sapphire rx480's running at 577H/s
"threads": 1,
"rawintensity": 1024,
"worksize": 8


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on December 15, 2016, 02:09:51 PM
Guys,

Trying to make my way into XMR mining but I'm getting the old error on my rigs:

Code:
Error -1 when calling clGetDeviceIDs for number of devices

I'm using miner version 0.4 on a rig with 6x480 4GB under Win10 x64, Crimson 16.9.2.

This is my conf file:

Code:
{

"Algorithms":

[

{

"name": "CryptoNight",
"devices":
[
{
"index": 0,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 1,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 2,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 3,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 4,
"threads": 1,
"rawintensity": 640,
"worksize": 16
},
{
"index": 5,
"threads": 1,
"rawintensity": 640,
"worksize": 16
}
],
"pools":
[
{
"url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
"user": "47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGRoyZk3ES1s1V4QVcB.a34e4b35838dde3cf5e68bca39ed1f64376b71eaee082407d50d4ca4d11101ef.02",
"pass": "x"

Any ideas?

Thanks!

This happened to me when i went from 1 --> 2 GPUs. My fix was to dump OS and re-install everything. If anyone knows an easier fix, please share!


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on December 15, 2016, 02:22:44 PM
This is me killin it on Ubuntu 16.04 w/ 6x MSI rx470 4GB

[14:31:16] Thread 3, GPU ID 3, GPU Type: Ellesmere: 635.87H/s
[14:31:16] Thread 2, GPU ID 2, GPU Type: Ellesmere: 634.97H/s
[14:31:17] Thread 5, GPU ID 5, GPU Type: Ellesmere: 641.74H/s
[14:31:18] Thread 1, GPU ID 1, GPU Type: Ellesmere: 644.15H/s
[14:31:18] Thread 4, GPU ID 4, GPU Type: Ellesmere: 641.23H/s
[14:31:18] Thread 0, GPU ID 0, GPU Type: Ellesmere: 641.01H/s
[14:31:18] Share accepted: 72/72 (100.00%)
[14:31:18] Total Hashrate: 3838.97H/s

BONUS --> Only 640w total draw at the wall... (custom bios 1160core/1900mem/1500straps)



How are you modifying your bios?  You just going into UEFI boot and changing the options?  I'm new to this obviously. 

Core 1160 = gpu core clock rate?
Mem = memclock rate?
What is straps? 
Also, have you tried undervolting the gpu's or is it possible on ubuntu? 

I have 2 unmodded sapphire rx480's running at 577H/s
"threads": 1,
"rawintensity": 1024,
"worksize": 8


currently getting about 627h/s out of twin xfx 8gb 480s without modding bios on them, however i did OC my CPU/RAM. you can tinker with those settings to find optimal speed/voltage/heat ratio that works best for your hardware.
snapshot of .conf file GPU settings

{
               "index": 0,
               "corefreq": 1288,
               "memfreq": 2000,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 1022,
               "worksize": 8
            },
            {
               "index": 1,
               "corefreq": 1288,
               "memfreq": 2000,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 1022,
               "worksize": 8
            },

hope this helps


Title: Re: Wolf's XMR GPU Miner
Post by: Ned Kelly on December 15, 2016, 02:44:13 PM
Does anyone have numbers for RX 460 stock?


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 15, 2016, 06:51:27 PM
This is me killin it on Ubuntu 16.04 w/ 6x MSI rx470 4GB

[14:31:16] Thread 3, GPU ID 3, GPU Type: Ellesmere: 635.87H/s
[14:31:16] Thread 2, GPU ID 2, GPU Type: Ellesmere: 634.97H/s
[14:31:17] Thread 5, GPU ID 5, GPU Type: Ellesmere: 641.74H/s
[14:31:18] Thread 1, GPU ID 1, GPU Type: Ellesmere: 644.15H/s
[14:31:18] Thread 4, GPU ID 4, GPU Type: Ellesmere: 641.23H/s
[14:31:18] Thread 0, GPU ID 0, GPU Type: Ellesmere: 641.01H/s
[14:31:18] Share accepted: 72/72 (100.00%)
[14:31:18] Total Hashrate: 3838.97H/s

BONUS --> Only 640w total draw at the wall... (custom bios 1160core/1900mem/1500straps)



How are you modifying your bios?  You just going into UEFI boot and changing the options?  I'm new to this obviously. 

Core 1160 = gpu core clock rate?
Mem = memclock rate?
What is straps? 
Also, have you tried undervolting the gpu's or is it possible on ubuntu? 

I have 2 unmodded sapphire rx480's running at 577H/s
"threads": 1,
"rawintensity": 1024,
"worksize": 8



Bios Mod.
 - dump stock rom with gpu-z
 - open in polaris, change core clocks, mem clocks, and set all straps above 1500 to the 1500 strap.
 - save and write new rom to card with atiflash.

You can learn alot about it over on Zcash forms.  Search Anoraks VBIOS.

I have no done any undervolting (yet).  You cant do that directly in ubuntu against the amdgpu-pro drivers.  You can only change core and mem clocks on the fly using the /sys/class/drm/* stuff.   

I'm thinking @ 650w TDP,  do I really risk stability to save a few more watts?

For MSI RX470 4G, I'm using..

            {
               "index": 1,
               "threads": 1,
               "rawintensity": 960,
               "worksize": 8
            }




Title: Re: Wolf's XMR GPU Miner
Post by: Ned Kelly on December 16, 2016, 05:14:30 AM
Do not use gpu-z, you can brick your card, use atiflash for bios backup.


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 16, 2016, 06:02:00 AM
Do not use gpu-z, you can brick you card, use atiflash for bios backup.

gpu-z just for reading the original bios, not writing it.  atiflash for writing a modded bios.


Title: Re: Wolf's XMR GPU Miner
Post by: ntrader on December 16, 2016, 10:30:49 AM
Anybody run miner with command line (bat file)?

I tried next line, but nothing - miner shot down. With included xmr.conf it don't start too

start miner.exe -k cryptonight -o stratum+tcp://xmr-usa.dwarfpool.com:9050 -u user -p password -g 1 -w 8 --rawintensity 1024


Title: Re: Wolf's XMR GPU Miner
Post by: Hotmetal on December 16, 2016, 11:43:22 AM
Wolf-XMR-Miner has been superseded by SGMiner-GM.

It lags somewhat behind the Claymore XMR miner though.


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 16, 2016, 05:49:05 PM
Wolf-XMR-Miner has been superseded by SGMiner-GM.

Is there a good reason to switch besides the ability to control clock speeds on the fly?   Seems to be 10x more complicated from compilation to configuration.  :)

I'm getting 658H/s per card now on 6x MSI 470s @ 1169mhz/1880mhz/1500 strap.   Only 660w at the wall.   Nearly 6 Hash/Joule.  Can sgminer get better Hash per watt performance on XMR?





Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on December 16, 2016, 07:05:26 PM
Custom timings and 1250/2100 I can pull over 825H/s out of my 470 4G (Hynix.) It's done 850H/s, but not stable. Note that this is probably not because of SGMiner-GM, but because of clocks and timings, but I've not tested on Wolf-XMR-Miner in ages.
is this with stock cryptonight kernel (sg-genesis pack)?
Quote
"rawintensity": "1024",
"worksize": "8",
"gpu-threads": "1"
for *.conf?


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on December 16, 2016, 07:07:50 PM
One happy wolf-xmr-miner here, 10 years old S775 mobo with two 295x2 doing 2760H/s, 580W at the wall. Never touched volts on that dpm3 area, pretty sure they don't need 0.92v.

About 3% faster than claymore on my hawaii's.



Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on December 16, 2016, 07:15:33 PM
One happy wolf-xmr-miner here, 10 years old S775 mobo with two 295x2 doing 2760H/s, 580W at the wall. Never touched volts on that dpm3 area, pretty sure they don't need 0.92v.
About 3% faster than claymore on my hawaii's.
hynix hawaii 290X pulls about 750h/s @970/1250


Title: Re: Wolf's XMR GPU Miner
Post by: antantti on December 16, 2016, 07:42:17 PM
One happy wolf-xmr-miner here, 10 years old S775 mobo with two 295x2 doing 2760H/s, 580W at the wall. Never touched volts on that dpm3 area, pretty sure they don't need 0.92v.
About 3% faster than claymore on my hawaii's.
hynix hawaii 290X pulls about 750h/s @970/1250

949/1250 on that same rig does 3100h/s, 1.02v, 720W at the wall.


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 16, 2016, 08:56:43 PM
Custom timings and 1250/2100 I can pull over 825H/s out of my 470 4G (Hynix.) It's done 850H/s, but not stable. Note that this is probably not because of SGMiner-GM, but because of clocks and timings, but I've not tested on Wolf-XMR-Miner in ages.
is this with stock cryptonight kernel (sg-genesis pack)?
Quote
"rawintensity": "1024",
"worksize": "8",
"gpu-threads": "1"
for *.conf?

Yes, stock kernel, custom timings. Rawintensity was set to 1008.

I find 1024 too much for my 470's.   992, 1000, and 1008 are all good for me.   992 normally yields 100% accepted shares, and 1008 normally 99.2%.  Can be a wash because of that.   Maybe if I didnt underclock I would get some better rates. 

I'll play around with sgminer-gm when I get some time and follow up with some stats.



Title: Re: Wolf's XMR GPU Miner
Post by: endlessskill on December 17, 2016, 10:11:40 AM
Got 720 h/s on my RX 480. Not bad, thanks )


Title: Re: Wolf's XMR GPU Miner
Post by: anatolikostis on December 17, 2016, 12:29:02 PM
Got 720 h/s on my RX 480. Not bad, thanks )
730h/s @1110c/2000m - 30h/s speedup, not sure how to do @800h/s on Win (like Wolf0 do on GNU)


Title: Re: Wolf's XMR GPU Miner
Post by: endlessskill on December 17, 2016, 01:06:53 PM
Got 720 h/s on my RX 480. Not bad, thanks )
730h/s @1110c/2000m - 30h/s speedup, not sure how to do @800h/s on Win (like Wolf0 do on GNU)
I got only 658 h/s with 1110/2000
720 on 1150/2150
How did you get 730 on this clocks?


Title: Re: Wolf's XMR GPU Miner
Post by: Hotmetal on December 17, 2016, 01:31:43 PM
Got 720 h/s on my RX 480. Not bad, thanks )
730h/s @1110c/2000m - 30h/s speedup, not sure how to do @800h/s on Win (like Wolf0 do on GNU)

RX480 @ 750 h/s using Claymore's GPU miner out of the box.


Title: Re: Wolf's XMR GPU Miner
Post by: Crypt0Future on December 17, 2016, 02:30:53 PM


RX480 @ 750 h/s using Claymore's GPU miner out of the box.
Which OS?


Title: Re: Wolf's XMR GPU Miner
Post by: Tmdz on December 17, 2016, 04:08:52 PM
Got 720 h/s on my RX 480. Not bad, thanks )
730h/s @1110c/2000m - 30h/s speedup, not sure how to do @800h/s on Win (like Wolf0 do on GNU)
I got only 658 h/s with 1110/2000
720 on 1150/2150
How did you get 730 on this clocks?

1500 straps will get you more speed, some other tighter straps may get you more speed like wolf0 but not sure which one or how stable it is.


Title: Re: Wolf's XMR GPU Miner
Post by: Hotmetal on December 17, 2016, 04:12:02 PM


RX480 @ 750 h/s using Claymore's GPU miner out of the box.
Which OS?

Windows.


Title: Re: Wolf's XMR GPU Miner
Post by: lexele on December 17, 2016, 10:10:35 PM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on December 17, 2016, 10:47:52 PM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.

Anyone care to share their  xmr.conf settings for a Radeon RX 480? I hate using claymore's miner, but I can't seem to get anywhere near as good a hashrate.

Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: lexele on December 18, 2016, 08:59:12 AM
intensity 1000 / worksize 8.

And Wolfs XMR is more dependant to GPU clock.

I don't get same hashrate than claymore's, but if you substract devfee and consumption economy, wolf's is better.


Title: Re: Wolf's XMR GPU Miner
Post by: endlessskill on December 18, 2016, 09:42:47 AM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.

Anyone care to share their  xmr.conf settings for a Radeon RX 480? I hate using claymore's miner, but I can't seem to get anywhere near as good a hashrate.

Thanks.
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8            },
            {
               "index": 1,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 2,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 3,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
               "user": "4AmmpktUio3RtHVqRGhCJxefnRkzEajRtV9JoxMfT4B63xuikYonzWAErf652Jiv6jSvyShF8XKTdbF TgqeWVyaN1JcKmCo.42",
               "pass": "x"
            }
         ]
      }
   ]
}

4xRX480


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 18, 2016, 11:58:18 AM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.

Anyone care to share their  xmr.conf settings for a Radeon RX 480? I hate using claymore's miner, but I can't seem to get anywhere near as good a hashrate.

Thanks.
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8            },
            {
               "index": 1,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 2,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 3,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
               "user": "4AmmpktUio3RtHVqRGhCJxefnRkzEajRtV9JoxMfT4B63xuikYonzWAErf652Jiv6jSvyShF8XKTdbF TgqeWVyaN1JcKmCo.42",
               "pass": "x"
            }
         ]
      }
   ]
}

4xRX480

I tried using your configuration but I'm still getting the same error:
Code:
[11:56:31] Error -1 when calling clGetDeviceIDs for number of devices.

Cannot get this miner to work on any multi GPU configuration, only single GPU+CPU

Any ideas?


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on December 18, 2016, 02:38:40 PM
Thanks, I will give that a try, appreciate it! :)


Title: Re: Wolf's XMR GPU Miner
Post by: bobben2 on December 18, 2016, 06:55:06 PM
R9 280X running at 995/1600 gets me 530 h/s with 2 threads:
Code:
				{
"index": 0,
"threads": 2,
"rawintensity": 484,
"worksize": 8
}


R9 390 running at 1000/1500 gets me ~740 h/s with the following config:
Code:
                             {
                                        "index": 1,
                                        "threads": 1,
                                        "rawintensity": 984,
                                        "worksize": 8
                                },
both on Ubuntu 14.04 using fglrx..


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 18, 2016, 09:38:57 PM
pushing 658 h/s per card.  12 cards.  about 7890 total.   

however, rates on monero.crypto-pool.fr never agree.   I realize they estimate based on # of shares, but its consistently 15-25% lower.

Pool side estimates last ~30m or so... (but consistent over several days)
5.82Kh
6.75Kh
6.30Kh
6.20Kh
5.89Kh
6.06Kh
5.89Kh
5.67Kh

Rare occasions I see it get into the 6.6-7.0Kh/s range, but never ~7.8Kh like I see on my client side.   You would think if I have 7.8Kh, it would report rates between 6.5Kh/s and 9.0Kh/s on pool side.

I do have a few bad shares... but like 98.5%+ valid shares.   Not enough bad shares to have that big of impact.

Anyone else use crypto-pool and can verify their rates vs pool estimates?



Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 18, 2016, 09:51:22 PM
pushing 658 h/s per card.  12 cards.  about 7890 total.   

and minus bad shares and pool fee = ~7.6Kh/s   

never reports anywhere close to that...   gonna repoint to dwarfpool and see what gives.


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 21, 2016, 01:49:09 PM
hello,

I found a good setting for my two rx470

   "threads": 2,
   "rawintensity": 508,
   "worksize": 4

with this setting I've a 1382/1384 h/s in wolf vs 1366 h/s in claymore at at same consuption (210w at wall)

please try an other combination and share it

hello


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 21, 2016, 02:03:37 PM
an other optimizzation

"rawintensity": 512,

1394 h/s


Title: Re: Wolf's XMR GPU Miner
Post by: anakbaru on December 21, 2016, 05:30:00 PM
an other optimizzation

"rawintensity": 512,

1394 h/s


1394 h/s for each card or two card?
thanks


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on December 21, 2016, 05:33:01 PM
an other optimizzation

"rawintensity": 512,

1394 h/s


1394 h/s for each card or two card?
thanks

He seems to indicate above that was for both cards, and it sounds about right to me. Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 21, 2016, 11:17:42 PM
1394 for two RX470 memory strap, core 1126-849 mV,  mem 1950 849 mV

4 thread at 347-350 h/s each




Title: Re: Wolf's XMR GPU Miner
Post by: reflexmk on December 23, 2016, 02:19:08 AM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.

Anyone care to share their  xmr.conf settings for a Radeon RX 480? I hate using claymore's miner, but I can't seem to get anywhere near as good a hashrate.

Thanks.
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8            },
            {
               "index": 1,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 2,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 3,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
               "user": "4AmmpktUio3RtHVqRGhCJxefnRkzEajRtV9JoxMfT4B63xuikYonzWAErf652Jiv6jSvyShF8XKTdbF TgqeWVyaN1JcKmCo.42",
               "pass": "x"
            }
         ]
      }
   ]
}

4xRX480

I tried using your configuration but I'm still getting the same error:
Code:
[11:56:31] Error -1 when calling clGetDeviceIDs for number of devices.

Cannot get this miner to work on any multi GPU configuration, only single GPU+CPU

Any ideas?

Got the same problem, someone to help?


Title: Re: Wolf's XMR GPU Miner
Post by: montas101 on December 23, 2016, 04:56:59 AM
It's a pity you don't update this miner, it's rock stable and low consumption. Ilove it and stil use it.

Anyone care to share their  xmr.conf settings for a Radeon RX 480? I hate using claymore's miner, but I can't seem to get anywhere near as good a hashrate.

Thanks.
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8            },
            {
               "index": 1,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 2,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 3,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
               "user": "4AmmpktUio3RtHVqRGhCJxefnRkzEajRtV9JoxMfT4B63xuikYonzWAErf652Jiv6jSvyShF8XKTdbF TgqeWVyaN1JcKmCo.42",
               "pass": "x"
            }
         ]
      }
   ]
}

4xRX480

I tried using your configuration but I'm still getting the same error:
Code:
[11:56:31] Error -1 when calling clGetDeviceIDs for number of devices.

Cannot get this miner to work on any multi GPU configuration, only single GPU+CPU

Any ideas?

Got the same problem, someone to help?

{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 1,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 2,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            },
            {
               "index": 3,
               "threads": 1,
               "rawintensity": 1008,
               "worksize": 8
            }
         ],
         "pools":
         [
            {
               "url": "stratum+tcp://xmr-eu.dwarfpool.com:8005",
               "user": "4AmmpktUio3RtHVqRGhCJxefnRkzEajRtV9JoxMfT4B63xuikYonzWAErf652Jiv6jSvyShF8XKTdbF TgqeWVyaN1JcKmCo.42",
               "pass": "x"
            }
         ]
      }
   ]
}

4xRX480


i think this will work


Title: Re: Wolf's XMR GPU Miner
Post by: el_rlee on December 25, 2016, 01:33:04 PM
Thanks for publishing your miner!

I managed to compile it - but can't get it running....

Code:
root@ubunturig:/home/ubuntu/xmrmining/wolf-xmr-miner-master# ./miner xmr.conf 
[14:23:06] Setting up GPU(s).
Killed
root@ubunturig:/home/ubuntu/xmrmining/wolf-xmr-miner-master# amdconfig --list-adapters
* 0. 06:00.0 AMD Radeon (TM) R9 380 Series
  1. 0b:00.0 AMD Radeon (TM) R9 380 Series
  2. 0e:00.0 AMD Radeon (TM) R9 380 Series
  3. 13:00.0 AMD Radeon (TM) R9 380 Series
  4. 17:00.0 AMD Radeon (TM) R9 380 Series

* - Default adapter

root@ubunturig:/home/ubuntu/xmrmining/wolf-xmr-miner-master# cat xmr.conf
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 1,
"rawintensity": 384,
"worksize": 8
},
{
"index": -1,
"threads": 2,
"rawintensity": 16,
"worksize": 16
}
],
"pools":
[
{
"url": "stratum+tcp://mine.moneropool.com:3333",
"user": "43SLUTpyTgXCNXsL43uD8FWZ5wLAdX7Ak67BgGp7dxnGhLmrffDTXoeGm2GBRm8JjigN9PTg2gnShQn5gkgE1JGWJr4gsEU",
"pass": "x"
}
]
}
]
}



managed to get it working - was a driver problem...

getting

Code:
[18:37:33] Thread 1, GPU ID 1, GPU Type: Tonga: 549.97H/s
[18:37:33] Thread 2, GPU ID 2, GPU Type: Tonga: 549.92H/s
[18:37:34] Thread 0, GPU ID 0, GPU Type: Tonga: 549.79H/s
[18:37:34] Thread 3, GPU ID 3, GPU Type: Tonga: 549.78H/s
[18:37:34] Thread 4, GPU ID 4, GPU Type: Tonga: 549.86H/s
[18:37:35] Share accepted: 262/262 (100.00%)
[18:37:35] Total Hashrate: 2749.32H/s

problem now is:

Code:
root@ubunturig:~# amdconfig --adapter=all --odgt

Adapter 0 - AMD Radeon (TM) R9 380 Series
            Sensor 0: Temperature - 96.00 C
ERROR - Get temperature failed for Adapter 1 - AMD Radeon (TM) R9 380 Series
ERROR - Get temperature failed for Adapter 2 - AMD Radeon (TM) R9 380 Series
ERROR - Get temperature failed for Adapter 3 - AMD Radeon (TM) R9 380 Series
ERROR - Get temperature failed for Adapter 4 - AMD Radeon (TM) R9 380 Series

;)


Title: Re: Wolf's XMR GPU Miner
Post by: bhanu545 on December 25, 2016, 10:33:40 PM
I have 6 gpus but it wnt work whatever i do. Index 0 says error parsing. If i use index 1 it says no device found.

I think there is something wrong with amd software or miner itself.
Amd version is 16.10


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 26, 2016, 08:37:45 AM
the "index" is the OpenCl number of your gpu...
I use index "0" and index "2" because I have the apu index "1" and I do not use it to mine


Title: Re: Wolf's XMR GPU Miner
Post by: Jiggaz on December 26, 2016, 08:41:45 AM
the "index" is the OpenCl number of your gpu...
I use index "0" and index "2" because I have the apu index "1" and I do not use it to mine


We need option to select platform...
https://github.com/wolf9466/wolf-xmr-miner/issues/7 (https://github.com/wolf9466/wolf-xmr-miner/issues/7)


Title: Re: Wolf's XMR GPU Miner
Post by: bhanu545 on December 26, 2016, 09:08:18 AM
the "index" is the OpenCl number of your gpu...
I use index "0" and index "2" because I have the apu index "1" and I do not use it to mine


We need option to select platform...
https://github.com/wolf9466/wolf-xmr-miner/issues/7 (https://github.com/wolf9466/wolf-xmr-miner/issues/7)

I realized you were right about this. We cannot change platform in wolf miner. There is no option at all. such a huge drawback. If we disable intel HD graphics then it considers AMD cards. BUT

And other thing frustrating is about that Error -1. so stupid. can never solve it.


Title: Re: Wolf's XMR GPU Miner
Post by: Buthenis on December 26, 2016, 09:25:09 AM
I have 6 gpus but it wnt work whatever i do. Index 0 says error parsing. If i use index 1 it says no device found.

I think there is something wrong with amd software or miner itself.
Amd version is 16.10

Yes, I had some issues like this . I do not know how to solve it.
Give me an advance, Please. Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: mo35 on December 26, 2016, 04:51:56 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 26, 2016, 04:56:31 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?

I have exactly the same problem, and I've tried about every combination of auto fan/manual fan.

Conclusion: The miner is not rock stable, it is very unstable!

PS: This problem occurs both with wolf-xmr-miner-v0.4 and with sgminer-gm 5.5.4 under Win10 x64 with RX 480 rigs


Title: Re: Wolf's XMR GPU Miner
Post by: mo35 on December 26, 2016, 05:20:31 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?

I have exactly the same problem, and I've tried about every combination of auto fan/manual fan.

Conclusion: The miner is not rock stable, it is very unstable!

PS: This problem occurs both with wolf-xmr-miner-v0.4 and with sgminer-gm 5.5.4 under Win10 x64 with RX 480 rigs

actualy the same thing happening in Claymore CryptoNote GPU Miner v9.6 too , in claymore miner resets fan to 0% speed itself , wich is even more dangerous.

so it seems there is no reliable cryptonight miners out there unfortunately


Title: Re: Wolf's XMR GPU Miner
Post by: JuanHungLo on December 26, 2016, 05:29:06 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?

I have exactly the same problem, and I've tried about every combination of auto fan/manual fan.

Conclusion: The miner is not rock stable, it is very unstable!

PS: This problem occurs both with wolf-xmr-miner-v0.4 and with sgminer-gm 5.5.4 under Win10 x64 with RX 480 rigs

actualy the same thing happening in Claymore CryptoNote GPU Miner v9.6 too , in claymore miner resets fan to 0% speed itself , wich is even more dangerous.

so it seems there is no reliable cryptonight miners out there unfortunately

That is not my experience.  I am running 11 different rigs with Claymore's CN GPU miner v 9.6 and I monitor them with his Dual Miner Manager 2.1.  I have not experienced what you describe.  Are you specifying a target temp for the GPUs?


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 26, 2016, 05:33:17 PM
hello,

I found a good setting for my two rx470

   "threads": 2,
   "rawintensity": 508,
   "worksize": 4

with this setting I've a 1382/1384 h/s in wolf vs 1366 h/s in claymore at at same consuption (210w at wall)

please try an other combination and share it

hello

not able to reproduce those rates.  I see more like 512h/s with those settings.

Best rates for me on RX470's come from

   "threads": 1,
   "rawintensity": 1000,
   "worksize": 8





Title: Re: Wolf's XMR GPU Miner
Post by: Za1n on December 26, 2016, 06:10:48 PM
hello,

I found a good setting for my two rx470

   "threads": 2,
   "rawintensity": 508,
   "worksize": 4

with this setting I've a 1382/1384 h/s in wolf vs 1366 h/s in claymore at at same consuption (210w at wall)

please try an other combination and share it

hello

not able to reproduce those rates.  I see more like 512h/s with those settings.

Best rates for me on RX470's come from

   "threads": 1,
   "rawintensity": 1000,
   "worksize": 8





I just tried this out with both sets of these parameters and I get about 30 more sols using:

        "threads": 2,
   "rawintensity": 508,
   "worksize": 4

which gives me about 590 sols on a single RX470 4GB (1250/1850).

If I up the rawintensity slightly to 512 I can get about 610 sols, which is still far short of the 690 sols per card that tony_crunk reported.


Title: Re: Wolf's XMR GPU Miner
Post by: vapourminer on December 26, 2016, 06:12:02 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?

I have exactly the same problem, and I've tried about every combination of auto fan/manual fan.

Conclusion: The miner is not rock stable, it is very unstable!

PS: This problem occurs both with wolf-xmr-miner-v0.4 and with sgminer-gm 5.5.4 under Win10 x64 with RX 480 rigs

actualy the same thing happening in Claymore CryptoNote GPU Miner v9.6 too , in claymore miner resets fan to 0% speed itself , wich is even more dangerous.

so it seems there is no reliable cryptonight miners out there unfortunately

That is not my experience.  I am running 11 different rigs with Claymore's CN GPU miner v 9.6 and I monitor them with his Dual Miner Manager 2.1.  I have not experienced what you describe.  Are you specifying a target temp for the GPUs?

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 26, 2016, 06:14:28 PM

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.

I've tried that too! Let the AMD drivers take care of fan speed adjustments. However, after a while, one of my cards will always randomly start spinning at 100% speed.


Title: Re: Wolf's XMR GPU Miner
Post by: mo35 on December 26, 2016, 06:18:32 PM

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.

I've tried that too! Let the AMD drivers take care of fan speed adjustments. However, after a while, one of my cards will always randomly start spinning at 100% speed.

i might add thats only happening when mining cryptonight , no such issues with equihash or dagger-hashimoto


Title: Re: Wolf's XMR GPU Miner
Post by: JuanHungLo on December 26, 2016, 06:26:00 PM

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.

I've tried that too! Let the AMD drivers take care of fan speed adjustments. However, after a while, one of my cards will always randomly start spinning at 100% speed.

i might add thats only happening when mining cryptonight , no such issues with equihash or dagger-hashimoto

Let me rephrase my question:  Are you using the command line argument for temperature target, like "-tt 80" ?


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 26, 2016, 06:30:05 PM
running into problem , maybe someone have clue whats happening

miner is rock stable with superb power consumption, but from time to time one of cards (random) spins fans up to 100% , i can reset that crazy spinning in afterburner , but then auto speeds are left broken @0% fan speed , and temps are rapidly growing.

using 5x sapphire nitro+ 8gb , win10 , wolf-xmr-miner-v0.4
p.s. i switched from win7 to win10 cause of Error -1 when calling clGetDeviceIDs for number of devices plague , win10 solved issue with unavailable cards.

any ideas ?

I have exactly the same problem, and I've tried about every combination of auto fan/manual fan.

Conclusion: The miner is not rock stable, it is very unstable!

PS: This problem occurs both with wolf-xmr-miner-v0.4 and with sgminer-gm 5.5.4 under Win10 x64 with RX 480 rigs

actualy the same thing happening in Claymore CryptoNote GPU Miner v9.6 too , in claymore miner resets fan to 0% speed itself , wich is even more dangerous.

so it seems there is no reliable cryptonight miners out there unfortunately

That is not my experience.  I am running 11 different rigs with Claymore's CN GPU miner v 9.6 and I monitor them with his Dual Miner Manager 2.1.  I have not experienced what you describe.  Are you specifying a target temp for the GPUs?

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.

what video card you have?
I have a sapphire rx470 nitro 4GB undervolted, underclock core and overclock ram (1126/1950 at 849 mvolt)



Title: Re: Wolf's XMR GPU Miner
Post by: el_rlee on December 26, 2016, 07:22:18 PM
I switched over to sgminer-gm which has fancontrol and exactly the same hashrate... (same kernel?)


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 26, 2016, 07:25:38 PM
I switched over to sgminer-gm which has fancontrol and exactly the same hashrate... (same kernel?)

Using RX 480 cards, with AMD drivers 16.9.2 fan control is very defective and causes miner either to shutdown or to set fans spinning a t full throttle


Title: Re: Wolf's XMR GPU Miner
Post by: vapourminer on December 26, 2016, 07:38:36 PM

am i the only one who just lets the cards manage their own fan? i dont set anything in the miner as far as fans are concerned.

I've tried that too! Let the AMD drivers take care of fan speed adjustments. However, after a while, one of my cards will always randomly start spinning at 100% speed.

derp.. so much for my theory.

been lucky so far or maybe cuz the rig is in the basement some DO hit 100% and i dont notice.

390s and 380s with 15.12 in the basement. 470 with 16.10.1 upstairs that i would notice but only had it a few weeks.


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 26, 2016, 07:42:53 PM
I switched over to sgminer-gm which has fancontrol and exactly the same hashrate... (same kernel?)

Using RX 480 cards, with AMD drivers 16.9.2 fan control is very defective and causes miner either to shutdown or to set fans spinning a t full throttle

i don't use fan control of other setting of miner software but I use WattTool 0.92

I haven't problems


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 27, 2016, 11:51:59 AM
Upgraded my AMD drivers from version 16.9.2 to 16.11.4 and the problem appears to be solved.

Rigs working flawlessly for 12 hours straight  ;D


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 27, 2016, 02:26:03 PM
FYI -

When this event happens in wolf v0.4, the miner keeps mining but never finds shares.    So it just spins cycles for hours and makes you no coin.   Overnight I had 7 hours of 0 shares.  :(

[00:22:30] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.44H/s
[00:22:31] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.38H/s
[00:22:31] Share rejected (Unauthenticated): 13598/13654 (99.59%)
[00:22:31] Reconnected to pool.
[00:22:31] Share rejected (your IP is banned): 13598/13655 (99.58%)
[00:22:31] Total Hashrate: 3944.09H/s
[00:22:31] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.88H/s
[00:22:32] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.83H/s
[ ... after this, no more shares until reset .. ]

So you might want to add that string ("your IP is banned") into your monitoring programs to reset the miner.









Title: Re: Wolf's XMR GPU Miner
Post by: Za1n on December 27, 2016, 03:21:10 PM

I just tried this out with both sets of these parameters and I get about 30 more sols using:

        "threads": 2,
   "rawintensity": 508,
   "worksize": 4

which gives me about 590 sols on a single RX470 4GB (1250/1850).

If I up the rawintensity slightly to 512 I can get about 610 sols, which is still far short of the 690 sols per card that tony_crunk reported.

My bad, I was doing the testing on a rig which had cards with the default VBIOS on them.

With the modified VBIOS (memory straps mod) I get around 720 H/s each or 3600 H/s on a 5x RX470 GPU rig with these settings.
      
   "threads": 2,
   "rawintensity": 512,
   "worksize": 4


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 27, 2016, 03:24:33 PM
FYI -

When this event happens in wolf v0.4, the miner keeps mining but never finds shares.    So it just spins cycles for hours and makes you no coin.   Overnight I had 7 hours of 0 shares.  :(

[00:22:30] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.44H/s
[00:22:31] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.38H/s
[00:22:31] Share rejected (Unauthenticated): 13598/13654 (99.59%)
[00:22:31] Reconnected to pool.
[00:22:31] Share rejected (your IP is banned): 13598/13655 (99.58%)
[00:22:31] Total Hashrate: 3944.09H/s
[00:22:31] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.88H/s
[00:22:32] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.83H/s
[ ... after this, no more shares until reset .. ]

So you might want to add that string ("your IP is banned") into your monitoring programs to reset the miner.




what difficulties have you set?
banned ip is when the difficulty is too low


Title: Re: Wolf's XMR GPU Miner
Post by: Trimegistus on December 27, 2016, 03:28:28 PM

My bad, I was doing the testing on a rig which had cards with the default VBIOS on them.

With the modified VBIOS (memory straps mod) I get around 720 H/s each or 3600 H/s on a 5x RX470 GPU rig with these settings.
      
   "threads": 2,
   "rawintensity": 512,
   "worksize": 4

I'm just wondering... wouldn't these settings be similar to these?

        "threads": 1,
   "rawintensity": 1024,
   "worksize": 8



Title: Re: Wolf's XMR GPU Miner
Post by: Za1n on December 27, 2016, 03:58:33 PM

My bad, I was doing the testing on a rig which had cards with the default VBIOS on them.

With the modified VBIOS (memory straps mod) I get around 720 H/s each or 3600 H/s on a 5x RX470 GPU rig with these settings.
      
   "threads": 2,
   "rawintensity": 512,
   "worksize": 4

I'm just wondering... wouldn't these settings be similar to these?

        "threads": 1,
   "rawintensity": 1024,
   "worksize": 8



Not as far as the resulting hashrate. With the settings you list on the same rig I get 3200 H/s, or only 640 H/s per card.

I am still playing around with trying different settings, but it is looking like the 2, 512, 4 settings are the ones to beat so far, at least for me.


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 27, 2016, 04:57:45 PM

My bad, I was doing the testing on a rig which had cards with the default VBIOS on them.

With the modified VBIOS (memory straps mod) I get around 720 H/s each or 3600 H/s on a 5x RX470 GPU rig with these settings.
      
   "threads": 2,
   "rawintensity": 512,
   "worksize": 4

I'm just wondering... wouldn't these settings be similar to these?

        "threads": 1,
   "rawintensity": 1024,
   "worksize": 8



with these parameters I get 1310 h/s about 655 h/s per card. I do not know why


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 27, 2016, 05:02:45 PM
FYI -

When this event happens in wolf v0.4, the miner keeps mining but never finds shares.    So it just spins cycles for hours and makes you no coin.   Overnight I had 7 hours of 0 shares.  :(

[00:22:30] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.44H/s
[00:22:31] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.38H/s
[00:22:31] Share rejected (Unauthenticated): 13598/13654 (99.59%)
[00:22:31] Reconnected to pool.
[00:22:31] Share rejected (your IP is banned): 13598/13655 (99.58%)
[00:22:31] Total Hashrate: 3944.09H/s
[00:22:31] Thread 2, GPU ID 2, GPU Type: Ellesmere: 635.88H/s
[00:22:32] Thread 1, GPU ID 1, GPU Type: Ellesmere: 658.83H/s
[ ... after this, no more shares until reset .. ]

So you might want to add that string ("your IP is banned") into your monitoring programs to reset the miner.




what difficulties have you set?
banned ip is when the difficulty is too low


I was using dwarfpool 8100.

>> Stratum-port: 8100 start diff: 10000 for high-end CPU and GPU-Rigs

After running into rejected shares and IP getting banned, I tried the fixed diff port 9100.

>> Stratum-port: 9100 fixed diff: 10000

Ran into same issue there.

Its weird because wolf v0.4 will run for hours without issue on both ports 8100 and 9100.  We are talking 10-20k+ accepted shares w/ 100% accept rate.   Then all of a sudden something goes crazy and rejected shares go up and IP gets banned.

Right now I'm over 20k w/ 100% accept.

[10:58:36] Share accepted: 20862/20862 (100.00%)
[10:58:36] Total Hashrate: 4067.31H/s

But it seems like its just a ticking time bomb.   I may just send my shares to crypto-pool for a couple days and see.




Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 27, 2016, 05:15:07 PM
which is the best pool?


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on December 27, 2016, 05:53:52 PM
which is the best pool?

AFAIK, there is no "best" pool - Here is a list:

http://chainradar.com/xmr/pools


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 27, 2016, 08:36:55 PM
which is the best pool?

Is there a pool that has a user interface like ethermine/ethpool/flypool ??  All the one's I've tried pale in comparison.




Title: Re: Wolf's XMR GPU Miner
Post by: tytanick on December 27, 2016, 11:28:30 PM
Any idea about Banned IP on dwarfpool by using this miner ?


Title: Re: Wolf's XMR GPU Miner
Post by: ntrader on December 28, 2016, 07:40:55 AM
Trying to start miner - it's shut down.
How to start this miner with command line? Does anyone has a working example?


Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 28, 2016, 12:41:41 PM
which amd driver you have tried?


Title: Re: Wolf's XMR GPU Miner
Post by: dallase on December 28, 2016, 02:29:10 PM
Any idea about Banned IP on dwarfpool by using this miner ?

Between the lower pool side hash rate and getting banned (probably related), I've finally switched to sgminer 5.5.4-gm.   The only reason I had not switched earlier was because I couldnt get the damn thing to compile and the precompiled binary didnt have a cryptonight kernel.

I have 14 gpu running 675 h/s (9.45 khs), pointed at Dwarfpool right now.

Latest Pool side #'s (~15m)   10.04 khs,  9.57 khs   9.91 khs



Title: Re: Wolf's XMR GPU Miner
Post by: tony_crunk on December 28, 2016, 03:41:48 PM
Any idea about Banned IP on dwarfpool by using this miner ?

Between the lower pool side hash rate and getting banned (probably related), I've finally switched to sgminer 5.5.4-gm.   The only reason I had not switched earlier was because I couldnt get the damn thing to compile and the precompiled binary didnt have a cryptonight kernel.

I have 14 gpu running 675 h/s (9.45 khs), pointed at Dwarfpool right now.

Latest Pool side #'s (~15m)   10.04 khs,  9.57 khs   9.91 khs




wich is the sgminer configuration?


Title: Re: Wolf's XMR GPU Miner
Post by: Marvell1 on December 28, 2016, 03:47:39 PM
Any idea about Banned IP on dwarfpool by using this miner ?

Between the lower pool side hash rate and getting banned (probably related), I've finally switched to sgminer 5.5.4-gm.   The only reason I had not switched earlier was because I couldnt get the damn thing to compile and the precompiled binary didnt have a cryptonight kernel.

I have 14 gpu running 675 h/s (9.45 khs), pointed at Dwarfpool right now.

Latest Pool side #'s (~15m)   10.04 khs,  9.57 khs   9.91 khs




wich is the sgminer configuration?

yeah please share , having issues with wolf and claymore I need to switch as well


Title: Re: Wolf's XMR GPU Miner
Post by: Lafu on December 28, 2016, 05:07:33 PM
AppData\Local\Temp\jh.cl", line 151: error: function call is not
          allowed in a constant expression
    C64e(0xa7403b1f1c2747f3), C64e(0x5940f034b72d769a),
                             

Error limit reached.
100 errors detected in the compilation
Compilation terminated.
Frontend phase failed compilation.




What does that mean i cant get the miner running on R9 270x vapor x 2 gb  !
Driver are 16.11.5
Please can some on help to get this running !!!!!!


Title: Re: Wolf's XMR GPU Miner
Post by: mirny on December 28, 2016, 10:36:44 PM
Any idea about Banned IP on dwarfpool by using this miner ?

Between the lower pool side hash rate and getting banned (probably related), I've finally switched to sgminer 5.5.4-gm.   The only reason I had not switched earlier was because I couldnt get the damn thing to compile and the precompiled binary didnt have a cryptonight kernel.

I have 14 gpu running 675 h/s (9.45 khs), pointed at Dwarfpool right now.

Latest Pool side #'s (~15m)   10.04 khs,  9.57 khs   9.91 khs




wich is the sgminer configuration?

yeah please share , having issues with wolf and claymore I need to switch as well

Try this, it's working for me.
 http://cryptozone.ml/monero.php


Title: Re: Wolf's XMR GPU Miner
Post by: thedue on December 28, 2016, 11:14:25 PM
which is the best pool?

Is there a pool that has a user interface like ethermine/ethpool/flypool ??  All the one's I've tried pale in comparison.




see sig (afflink)
works great so far


Title: Re: Wolf's XMR GPU Miner
Post by: mirny on December 28, 2016, 11:17:43 PM
which is the best pool?

Is there a pool that has a user interface like ethermine/ethpool/flypool ??  All the one's I've tried pale in comparison.




see sig (afflink)
works great so far

I was trying this pool, but when you using claymore, or wolf miner, you're getting penalized for invalid shares,
you can see unconfirmed balance is in negative.


Title: Re: Wolf's XMR GPU Miner
Post by: ocminer on December 28, 2016, 11:23:32 PM
which is the best pool?

Is there a pool that has a user interface like ethermine/ethpool/flypool ??  All the one's I've tried pale in comparison.





You might want to give https://xmr.suprnova.cc a shot, I just reopened it.


Title: Re: Wolf's XMR GPU Miner
Post by: waddupboi on December 29, 2016, 12:33:47 AM
Anyone has an idea on how to compile it on windows?


Title: Re: Wolf's XMR GPU Miner
Post by: Lafu on December 29, 2016, 12:37:40 AM
Anyone has an idea on how to compile it on windows?

no i get this error
AppData\Local\Temp\jh.cl", line 151: error: function call is not
          allowed in a constant expression
    C64e(0xa7403b1f1c2747f3), C64e(0x5940f034b72d769a),
                             

Error limit reached.
100 errors detected in the compilation
Compilation terminated.
Frontend phase failed compilation


Title: Re: Wolf's XMR GPU Miner
Post by: Server2850Guy on December 30, 2016, 08:33:36 AM
Is there any up to date miner for cryptonight / XMR and Nvidea Pascal cards , for Linux ?
I don't seem to find any....


Title: Re: Wolf's XMR GPU Miner
Post by: peoples on January 06, 2017, 09:19:58 PM
Hello,

i've some problem with wolfs gpu miner. 
On my rx470 8GB 6x GPU RIG mining works fine with the following config -> every Card runs at 730 H/s

Quote
                                {
                                        "index": 0,
                                        "threads": 1,
                                        "rawintensity": 1016,
                                        "worksize": 8
                                },

same config on rx480 4GB i get the following errors:

Quote
[  456.439928] [TTM] Buffer eviction failed
[  457.849829] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!
[  457.849966] show_signal_msg: 27 callbacks suppressed
[  457.849972] miner[1959]: segfault at 0 ip           (null) sp 00007f301c217ea8 error 14 in miner[400000+19000]
[  457.922937] [drm:amdgpu_gem_object_create [amdgpu]] *ERROR* Failed to allocate GEM object (2130706432, 6, 4096, -12)
[  767.474158] [TTM] Buffer eviction failed
[  771.113864] [TTM] Failed allocating swap storage
[  771.205688] [TTM] Buffer eviction failed
[  771.296660] [TTM] Buffer eviction failed
[  771.385918] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!
[  771.386336] miner[2259]: segfault at 0 ip           (null) sp 00007f66a1b94e28 error 14

change the config to use only one card -> i get the same rate as from the rx470.
So for me the card can handle this settings.
Why is it complaining about memory ? Both systems have 4GB of host memory.

thanks



Title: Re: Wolf's XMR GPU Miner
Post by: peoples on January 06, 2017, 09:27:18 PM
Hello,

i've some problem with wolfs gpu miner. 
On my rx470 8GB 6x GPU RIG mining works fine with the following config -> every Card runs at 730 H/s

Quote
                                {
                                        "index": 0,
                                        "threads": 1,
                                        "rawintensity": 1016,
                                        "worksize": 8
                                },

same config on rx480 4GB i get the following errors:

Quote
[  456.439928] [TTM] Buffer eviction failed
[  457.849829] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!
[  457.849966] show_signal_msg: 27 callbacks suppressed
[  457.849972] miner[1959]: segfault at 0 ip           (null) sp 00007f301c217ea8 error 14 in miner[400000+19000]
[  457.922937] [drm:amdgpu_gem_object_create [amdgpu]] *ERROR* Failed to allocate GEM object (2130706432, 6, 4096, -12)
[  767.474158] [TTM] Buffer eviction failed
[  771.113864] [TTM] Failed allocating swap storage
[  771.205688] [TTM] Buffer eviction failed
[  771.296660] [TTM] Buffer eviction failed
[  771.385918] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!
[  771.386336] miner[2259]: segfault at 0 ip           (null) sp 00007f66a1b94e28 error 14

change the config to use only one card -> i get the same rate as from the rx470.
So for me the card can handle this settings.
Why is it complaining about memory ? Both systems have 4GB of host memory.

thanks



nevermind : saw the swap error while posting. 
Issue was problem with the swap space (wasn't mounted on that rig) -> solved.



Title: Re: Wolf's XMR GPU Miner
Post by: manotroll on January 06, 2017, 10:14:20 PM
How would an example to mine with GPU?
And with cpu on windows?

How to run cpu mining in linux?


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on January 07, 2017, 05:46:50 PM
How would an example to mine with GPU?
And with cpu on windows?

How to run cpu mining in linux?

Here is a good start I found real quick: https://www.cryptocompare.com/mining/guides/how-to-mine-monero/

Edit - I recommend ignoring part 4, and avoid minergate. Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: manotroll on January 07, 2017, 11:58:18 PM
How would an example to mine with GPU?
And with cpu on windows?

How to run cpu mining in linux?

Here is a good start I found real quick: https://www.cryptocompare.com/mining/guides/how-to-mine-monero/

Edit - I recommend ignoring part 4, and avoid minergate. Thanks

The tips that are on it and for the https://github.com/wolf9466/cpuminer-multi


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 08, 2017, 04:33:12 AM
I decided to give this coin try.

Specs:

AMD64 dual core CPU
2MB RAM
Radeon Sapphire HD7950
Lubuntu 15.04
AMD Crimson fglrx driver
wolf-xmr-miner -- https://github.com/wolf9466/wolf-xmr-miner

Set fan speed to 50%:
Code:
aticonfig --pplib-cmd "set fanspeed 0 50

Monitor temp:
Code:
watch -n 3 aticonfig --adapter=ALL --od-gettemperature

HD7950 .conf settings:
Code:
"corefreq": 1020,
"memfreq": 1575,
"powertune": 20,
"threads": 1,
"rawintensity": 893,
"worksize": 8

wolf-xmr-miner output:
Code:
[20:04:35] New job at diff 108698
[20:04:35] Thread 1, (CPU): 6.92H/s
[20:04:35] Thread 2, (CPU): 6.93H/s
[20:04:36] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.68H/s
[20:04:40] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.77H/s
[20:04:44] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.87H/s
[20:04:48] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.63H/s
[20:04:52] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.73H/s
[20:04:56] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.63H/s
[20:05:00] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.79H/s
[20:05:04] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.86H/s
[20:05:08] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.90H/s
[20:05:10] Share accepted: 2/2 (100.00%)
[20:05:10] Total Hashrate: 459.74H/s


Title: Re: Wolf's XMR GPU Miner
Post by: manotroll on January 08, 2017, 05:06:59 PM
I decided to give this coin try.

Specs:

AMD64 dual core CPU
2MB RAM
Radeon Sapphire HD7950
Lubuntu 15.04
AMD Crimson fglrx driver
wolf-xmr-miner -- https://github.com/wolf9466/wolf-xmr-miner

Set fan speed to 50%:
Code:
aticonfig --pplib-cmd "set fanspeed 0 50

Monitor temp:
Code:
watch -n 3 aticonfig --adapter=ALL --od-gettemperature

HD7950 .conf settings:
Code:
"corefreq": 1020,
"memfreq": 1575,
"powertune": 20,
"threads": 1,
"rawintensity": 893,
"worksize": 8

wolf-xmr-miner output:
Code:
[20:04:35] New job at diff 108698
[20:04:35] Thread 1, (CPU): 6.92H/s
[20:04:35] Thread 2, (CPU): 6.93H/s
[20:04:36] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.68H/s
[20:04:40] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.77H/s
[20:04:44] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.87H/s
[20:04:48] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.63H/s
[20:04:52] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.73H/s
[20:04:56] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.63H/s
[20:05:00] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.79H/s
[20:05:04] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.86H/s
[20:05:08] Thread 0, GPU ID 0, GPU Type: Tahiti: 445.90H/s
[20:05:10] Share accepted: 2/2 (100.00%)
[20:05:10] Total Hashrate: 459.74H/s

Could you pass the installation instructions?


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 09, 2017, 03:32:57 PM
^ Everything you need to know is there, Google can help you resolve any dependency related errors.

Ubuntu 15.04 is defunct and the HD7950 sucks massive amounts of power so until I get an RX480 @ 110W running Ubuntu 16.10 going into detail here is an exercise in futility.

I will say that Ubuntu 15.04 is required for the HD7950 as it is no longer supported in 16.10. The new beta versions of the wolf miner will also not work with the HD7950.

Your best bet for 15.04 is torrents as somebody (AMD) has gone out of their way to scrub this version from the net.


Title: Re: Wolf's XMR GPU Miner
Post by: joker5bb on January 09, 2017, 10:26:40 PM
fglrx driver is depreciated. Anyone got this to work with amdgpu kernel 4.10 driver?


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 10, 2017, 05:13:36 AM
@Wolf0

I strapped an RX480 to the side of my windows 10 desktop with some zap straps and plugged it in with a riser cable + bridge extender cable. This is my temporary solution while a new rig is in the works however, the wolf miner doesn't function with my NVIDIA card plugged in so I'm currently running claymore.


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 10, 2017, 05:00:35 PM
https://i.sli.mg/8PVdjC.png

Pool works good!


Title: Re: Wolf's XMR GPU Miner
Post by: supersonic on January 10, 2017, 06:07:19 PM
I get error on all of my rigs win 10 64bit i tried different drivers but still the same result, anyone has solution? I have 5gpus on 3 rigs and 7gpus on rest. For example all runs peachy for weeks on ZEC
Thanks in advance

Error -1 when calling clGetDeviceIDs for number of devices


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 11, 2017, 02:57:22 AM
I get error on all of my rigs win 10 64bit i tried different drivers but still the same result, anyone has solution? I have 5gpus on 3 rigs and 7gpus on rest. For example all runs peachy for weeks on ZEC
Thanks in advance

Error -1 when calling clGetDeviceIDs for number of devices

Well I don't know what peachy is or ZEC but, it sounds like your miner is asking the Open CL drivers how many cards you have but it can't because the CL drivers are pooched somehow.

I would download the latest Radeon drivers from AMD and also the AMD APP SDK package, chances are that will clear it up. If not it couldn't hurt to update your drivers in any case.


Title: Re: Wolf's XMR GPU Miner
Post by: Reksio34 on January 11, 2017, 02:50:52 PM
Hi,

I have 3 rigs, 2 x 6xRX480-8gb (H97 anniversary, AMD driver 16.9.2 and 16.11.4) and 1 x 2xRX470 (B85M-G43, AMD driver 16.11.4).

With the 2xRX470 rig, the Wolf's miner works fine.
1) with claymore's I have 1380h/s, with wolf's 1425h/s ( Thanks Za1n for config)
2) Power on the wall 330w --> 290w
Thanks Wolf.


All rigs use  Windows 8.1 Embedded Industry Pro, same AMD drivers (tested : 16.9.2 and 16.11.4) but ... same issue with my 2 x 6xRX480-8gb rigs : Error -1 when calling clGetDeviceIDs for number of devices.

I used 6xgpu_mod for 2 x 6xRX480-8gb rigs ( https://lbr.id.lv/6xgpu_mod/6xGPU_mod_download.html)



Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 11, 2017, 03:33:32 PM
Hi,

I have 3 rigs, 2 x 6xRX480-8gb (H97 anniversary, AMD driver 16.9.2 and 16.11.4) and 1 x 2xRX470 (B85M-G43, AMD driver 16.11.4).

With the 2xRX470 rig, the Wolf's miner works fine.
1) with claymore's I have 1380h/s, with wolf's 1425h/s ( Thanks Za1n for config)
2) Power on the wall 330w --> 290w
Thanks Wolf.


All rigs use  Windows 8.1 Embedded Industry Pro, same AMD drivers (tested : 16.9.2 and 16.11.4) but ... same issue with my 2 x 6xRX480-8gb rigs : Error -1 when calling clGetDeviceIDs for number of devices.

I used 6xgpu_mod for 2 x 6xRX480-8gb rigs ( https://lbr.id.lv/6xgpu_mod/6xGPU_mod_download.html)



Do the rigs with issues have on-board nvidia GPUs on the mainboards? I don't recall any errors but the nvidia GPU in the desktop is preventing me from running the wolf miner.


Title: Re: Wolf's XMR GPU Miner
Post by: Reksio34 on January 12, 2017, 05:02:38 PM
Hi,

I have 3 rigs, 2 x 6xRX480-8gb (H97 anniversary, AMD driver 16.9.2 and 16.11.4) and 1 x 2xRX470 (B85M-G43, AMD driver 16.11.4).

With the 2xRX470 rig, the Wolf's miner works fine.
1) with claymore's I have 1380h/s, with wolf's 1425h/s ( Thanks Za1n for config)
2) Power on the wall 330w --> 290w
Thanks Wolf.


All rigs use  Windows 8.1 Embedded Industry Pro, same AMD drivers (tested : 16.9.2 and 16.11.4) but ... same issue with my 2 x 6xRX480-8gb rigs : Error -1 when calling clGetDeviceIDs for number of devices.

I used 6xgpu_mod for 2 x 6xRX480-8gb rigs ( https://lbr.id.lv/6xgpu_mod/6xGPU_mod_download.html)



Do the rigs with issues have on-board nvidia GPUs on the mainboards? I don't recall any errors but the nvidia GPU in the desktop is preventing me from running the wolf miner.

H97 anniversary motherboard support only Intel® HD Graphics Built-in, no on-board GPU. I have G1840 or G1820 CPUs with intel  HD (Haswell) GPU like my 2xRX470.


Title: Re: Wolf's XMR GPU Miner
Post by: cogitech on January 15, 2017, 08:33:27 PM
Hello all!

New here, but not new to mining. I was a relatively early miner of bitcoin and I did fairly well with that a couple years ago. :)

Thanks to WolfO for this miner. I have recently complied it and got it running on Ubuntu 16.04 with AMD RX 470 using AMDGPU-Pro 16.50 driver.

It's working pretty well so far:

Quote
[12:31:34] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.75H/s
[12:31:38] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.53H/s
[12:31:41] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.84H/s
[12:31:45] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.95H/s
[12:31:48] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.79H/s
[12:31:52] Thread 0, GPU ID 0, GPU Type: Ellesmere: 557.15H/s
[12:31:55] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.51H/s
[12:31:59] Thread 0, GPU ID 0, GPU Type: Ellesmere: 555.99H/s
[12:32:02] Thread 0, GPU ID 0, GPU Type: Ellesmere: 556.08H/s
[12:32:04] Share accepted: 60/60 (100.00%)
[12:32:04] Total Hashrate: 556.08H/s

I am considering buying a couple more cards and putting them in other systems in my house (daughters' computers) and I obviously I want to mine with those too.

Some pools seem to allow you to differentiate between individual miners so that you can see separate stats for each one. Dwarfpool, for example, states:

Quote
"You can determine your rigs separately for better vardiff, lower rejects and detailed statistic. Use workername: WALLET . WORKER-ID"

Would this work with Wolf's GPU Miner? Would I just change the xmr.conf file and append a worker-ID number after my wallet address, like:

Quote
"user": "47HpEzStPJGjUyRbj6DXJyN993s3busRLjVxxxxxxxxxxxxxxxxxxxxxxFgvQNizy9urPytC4tJB6sf yeuUKk1qZy.123",

Also, does this work with all pools, or just with ones that specifically support it?

Thanks in advance for any help.



Title: Re: Wolf's XMR GPU Miner
Post by: cogitech on January 15, 2017, 08:41:43 PM
Can someone explain to me how to lower the % of GPU being used? My computer is very slow when mining and would like it to be somewhat functional.

Would really appreciate some help.

Thanks :D

GPU utilization shouldn't make your computer slow unless the applications you are running need the GPU (games, for example).

By default, the xmr.conf enables CPU mining as well, which is generally very inefficient depending on your CPU. If you disable CPU mining in the xmr.conf, then your computer will run faster and will use much less energy and create less heat.

To disable CPU mining, set the "threads" value to 0 (zero) for the "-1" device, like this:

Quote
               "index": -1,
               "threads": 0,
               "rawintensity": 16,
               "worksize": 16


Title: Re: Wolf's XMR GPU Miner
Post by: lajoie on January 17, 2017, 01:26:51 AM
Hey Wolf0 - I've been looking through the github source and using that as an example to work through some OpenCL programming. I'm confused by something in the cn0 kernel:

__attribute__((reqd_work_group_size(WORKSIZE, 8, 1)))
__kernel void cn0(__global ulong *input, __global uint4 *Scratchpad, __global ulong *states)
{
...
   Scratchpad += ((get_global_id(0) - get_global_offset(0)));
   states += (25 * (get_global_id(0) - get_global_offset(0)));
...

So, the states pointer is to a buffer of 200 bytes per global threads. Makes sense - each work item offsets the pointer by 25 ulongs (64-bits per ulong or 8 bytes), for a total of 200 bytes per work item.  However, the scratchpad is 2MB per global thread, but the pointer arithmetic just seems to advance it by one uint4 (4 x 4 bytes or 16 bytes).  I would have expected to see something like:

   Scratchpad += (131072 * (get_global_id(0) - get_global_offset(0)));

In other words, each work item should be offset by the full size of the 2MB buffer (131072 unit4's). What am I missing here?



Title: Re: Wolf's XMR GPU Miner
Post by: lajoie on January 17, 2017, 12:13:31 PM
Ah!  That clears it up - thanks Wolf0!


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on January 17, 2017, 07:56:20 PM
Oh, my HD7950 just about burst into flames! Minimum fan speed is 60% for that old dog. I'm guessing the number of transactions per second has skyrocketed, are we under attack or just really popular?

edit:

I can smell piney resin enamel from the inductor windings vaporizing combined with your classic electrical fire odor. Yeah that puppy just got hot...

edit2:

The RX480 seems to be drawing considerably more than the manufacturers claimed 110W, I can now smell a hint of pine coming from my AX1200 PSU.... The GPU is however chilling.

edit3:

Insane, I had to shut the HD7950 down, the miner's AMD dual core CPU and PSU started bellowing toxic fumes. Both too hot to touch. I feel queezy.  >:(

WTF LOL

I'll try again later after it cools down and smell dissipates with CPU mining DISABLED!!! WOW I CAN"T BELIEVE THAT!!!

edit4:

Mining XMR is NOT for the faint of heart. Nobody is going to crack cryptonight, ever.


Title: Compile for XMR miner, Please, I need an advice and help
Post by: mkimid on January 17, 2017, 11:29:02 PM
I am trying to improve the performance for CL Kernel and it's calling.
and, I have tried to compile, but I have failed,

can I get an idea about the compiling environments ?

I have tried
    (1) install MinGW
    (2) install All Packages
    (3) compiled and installed jansson-2.8
    (4) copied, AMD_SDK 3.0 x86 (bin/lib/include)
    (5) I have tried to compile using Makefile it can not compile

         it has generate an error : inconsistent operand constranint in an 'asm'

         so, temporary, I have disabled
                    void cryptonight_hash_aesni in cryptonight.c & main.c

    (6) I got so many errors,
         so, I have added
               -lws2_32     

    (7)  But, some error has not been cleared,, Could you give me an advice ?
          
Quote
net.o:net.c:(.text+0x97): undefined reference to `getaddrinfo'
net.o:net.c:(.text+0x121): undefined reference to `freeaddrinfo'
net.o:net.c:(.text+0x14c): undefined reference to `freeaddrinfo'
collect2.exe: error: ld returned 1 exit status
make: *** [all] Error 1

Administrator@ENG ~/xmr
$



Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on January 18, 2017, 05:12:55 AM
Oh, my HD7950 just about burst into flames! Minimum fan speed is 60% for that old dog. I'm guessing the number of transactions per second has skyrocketed, are we under attack or just really popular?

edit:

I can smell piney resin enamel from the inductor windings vaporizing combined with your classic electrical fire odor. Yeah that puppy just got hot...

edit2:

The RX480 seems to be drawing considerably more than the manufacturers claimed 110W, I can now smell a hint of pine coming from my AX1200 PSU.... The GPU is however chilling.

edit3:

Insane, I had to shut the HD7950 down, the miner's AMD dual core CPU and PSU started bellowing toxic fumes. Both too hot to touch. I feel queezy.  >:(

WTF LOL

I'll try again later after it cools down and smell dissipates with CPU mining DISABLED!!! WOW I CAN"T BELIEVE THAT!!!

edit4:

Mining XMR is NOT for the faint of heart. Nobody is going to crack cryptonight, ever.

My 7950 blew a mosfet too, the 4927N. But it was a fault of my own as I had "accidentally" placed the card on the metal frame of my case and switched on the power, and with no black plate, I am guessing that something shorted when the PCB contacts touched the metal frame. My PSU shut itself off, but not quick enough to save the 7950 :( Ordered a replacement part, taking it to a repair shop to get old one replaced. Hoping for the best.

Apart from the Fan bug, I havent noticed any irregularaties with the mining. Though, one the fan shut down to 0% and I could smell that over heating/ burning smell from one of the 480's that had 0% fan and system rebooted. Everything was well afterwards. Luckily.

Also thanks to Wolf0 and Zanit(?) for sharing the miner and the config. I am mining at around 730 on 480's. With the :-

Threads 2
Rawintensity 504
Worksize 4

Drawing a total watt of around 360W for 3x 480's + system.

If anyone has any other settings please do share.


Title: Re: Wolf's XMR GPU Miner
Post by: icelove on January 18, 2017, 09:40:55 AM
thanks for sharing.


Title: Re: Wolf's XMR GPU Miner
Post by: Bakery on January 18, 2017, 08:31:15 PM
Oh this miner is so nice.
increase in speed and decrease in power consumption when switching from claymore.
Thanks Wolf0!

Only thing is i get "lowdifficultyshare" on nanopool, i think this might be due to some underclock of core and/or overclock of memory?
threads 2
rawintensity 504
workload 4

running 5x 470 4gb nitros


Title: Re: Wolf's XMR GPU Miner
Post by: Ursul0 on January 18, 2017, 10:09:28 PM
Hi,

I have 3 rigs, 2 x 6xRX480-8gb (H97 anniversary, AMD driver 16.9.2 and 16.11.4) and 1 x 2xRX470 (B85M-G43, AMD driver 16.11.4).

With the 2xRX470 rig, the Wolf's miner works fine.
1) with claymore's I have 1380h/s, with wolf's 1425h/s ( Thanks Za1n for config)
2) Power on the wall 330w --> 290w
Thanks Wolf.


All rigs use  Windows 8.1 Embedded Industry Pro, same AMD drivers (tested : 16.9.2 and 16.11.4) but ... same issue with my 2 x 6xRX480-8gb rigs : Error -1 when calling clGetDeviceIDs for number of devices.

I used 6xgpu_mod for 2 x 6xRX480-8gb rigs ( https://lbr.id.lv/6xgpu_mod/6xGPU_mod_download.html)



It very likely has to do with the openCL platform, as the integrated Intel gpu could still be present. is there an option to select another openCL platform?


Title: Re: Wolf's XMR GPU Miner
Post by: Ursul0 on January 19, 2017, 01:28:35 AM
@Wolf0 kudos on the nice miner!
https://bitcointalk.org/index.php?topic=638915.msg17548550#msg17548550

can you maybe add option to select OpenCL platform?
I'd like to run it on my 6*rx4 (including 2*480), but it's anniversary with integrated intel enabled (and genoil does have such switch, that I was using in early ZEC) otherwise there's no cards.

also does anyone know good params for 370?
I'm getting 470+ with:
"threads": 2,
"rawintensity": 380,
"worksize": 10


Title: Re: Wolf's XMR GPU Miner
Post by: shadowhlohavec on January 23, 2017, 08:15:50 PM
No clue how to run this miner  ;D start.bat not working, config not working, miner.exe not working, I'm trying to mine Bip coin


Title: Re: Wolf's XMR GPU Miner
Post by: citronick on January 31, 2017, 05:32:18 AM
wolf -- can i put a failover pool in the same command line? using your latest v0.4/Linux/SimpleMinerOS. Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: manotroll on February 01, 2017, 02:04:25 AM
How do i use it in linux with suprnova?
How do i use it in linux with dwarfpool?


Title: Re: Wolf's XMR GPU Miner
Post by: Pennywis3 on February 01, 2017, 07:47:30 AM
Wolfie :)

Do you also have a Windows CPU XMR miner?  :P


Title: Re: Wolf's XMR GPU Miner
Post by: Reksio34 on February 01, 2017, 10:16:39 PM
Hi,

About   Error -1 when calling clGetDeviceIDs for number of devices issue :

Click Show hidden devices on the View menu in Device Manager and remove the unused gpu drivers (intel HD driver in my case), Reboot.

I did this on 2 rigs and was OK



Title: Re: Wolf's XMR GPU Miner
Post by: ku4eto on February 02, 2017, 06:10:26 PM
Wolf, is it possible to make the miner more VRAM hungry, and thus chugg out some extra h/s ?
I think i am an exception with 3.6VRAM usage on m R9 290, not really sure how much otherse are using (posisbly, no more than 2-2.5), but there are lots of people with 8GB.


Title: Re: Wolf's XMR GPU Miner
Post by: citronick on February 02, 2017, 06:21:44 PM
wolf -- can i put a failover pool in the same command line? using your latest v0.4/Linux/SimpleMinerOS. Thanks

Nope, it doesn't manage multiple pools.

Hi wolf - using your miner at "stratum+tcp://cryptonight.usa.nicehash.com:3355" ... I am getting rejects all the time. Is it compatible with Nicehash? Thanks


Title: Re: Wolf's XMR GPU Miner
Post by: Qazo on February 02, 2017, 07:09:34 PM
can someone help me, I wanted to try wolf0's miner but I never ran it successfully, I set up everything in config file but when I click on  miner.exe it start and turn off immediately
Can you please share your config file for it?
Do I need to delete other algorithms from folder (blake, groestl)?

thank you


Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 02, 2017, 10:37:26 PM
can someone help me, I wanted to try wolf0's miner but I never ran it successfully, I set up everything in config file but when I click on  miner.exe it start and turn off immediately
Can you please share your config file for it?
Do I need to delete other algorithms from folder (blake, groestl)?

thank you

Hold Shift + Right click on an empty part of the window inside windows explorer / This PC where your Miner is. Select Open COmmand from here. Type in Miner [name of config file].conf. Or just do a bat file within the folder where you have the miner, and type miner Miner [name of config file].conf hit enter and then pause I.e :-

miner xmr.conf
pause

or

Sgminer xmr.conf
pause


Title: Re: Wolf's XMR GPU Miner
Post by: Qazo on February 03, 2017, 07:41:06 AM
Ok, now I created bat file and miner start but I get fatal error connecting to pool

https://i.imgur.com/VqUc2Z8.png


I guess something is wrong with config file?


This is my config
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 500,
               "memfreq": 1500,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 640,
               "worksize": 16
            },
            {
               "index": -1,
               "threads": 2,
               "rawintensity": 16,
               "worksize": 16
            }
         ],
         "pools":
         [
            {
               "url": "ssl://xmr.suprnova.cc:5221",
               "user": "myuser.myworker",
               "pass": "mypassword"
            }
         ]
      }
   ]
}


can someone share config file for rx480?  i found it at page 12 :)


edit:
for url I set  "url": "stratum+tcp://xmr.suprnova.cc:5222",  and that should be ok now, but now I get new error
https://i.imgur.com/TCtVkH8.png

I don't have any clue how to solve this



Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 03, 2017, 09:53:48 AM
Did you try what a few of the posts above yours suggests to disable the onboard graphics? You can disable onboard graphics either via BIOS or device manager.


Title: Re: Wolf's XMR GPU Miner
Post by: Qazo on February 03, 2017, 05:56:17 PM
yep, it works now, tnx.

same settings like claymore (1475 h/s) or wolf0 I get 1420 h/s and less watt
but I ran it for hour and I get too much rejected shares, almost 35%!


Title: Re: Wolf's XMR GPU Miner
Post by: manotroll on February 04, 2017, 12:19:56 AM
Ok, now I created bat file and miner start but I get fatal error connecting to pool

https://i.imgur.com/VqUc2Z8.png


I guess something is wrong with config file?


This is my config
{
   "Algorithms":
   [
      {
         "name": "CryptoNight",
         "devices":
         [
            {
               "index": 0,
               "corefreq": 500,
               "memfreq": 1500,
               "fanspeed": 65,
               "powertune": 20,
               "threads": 1,
               "rawintensity": 640,
               "worksize": 16
            },
            {
               "index": -1,
               "threads": 2,
               "rawintensity": 16,
               "worksize": 16
            }
         ],
         "pools":
         [
            {
               "url": "ssl://xmr.suprnova.cc:5221",
               "user": "myuser.myworker",
               "pass": "mypassword"
            }
         ]
      }
   ]
}


can someone share config file for rx480?  i found it at page 12 :)


edit:
for url I set  "url": "stratum+tcp://xmr.suprnova.cc:5222",  and that should be ok now, but now I get new error
https://i.imgur.com/TCtVkH8.png

I don't have any clue how to solve this


use 5222


Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 04, 2017, 12:53:43 AM
yep, it works now, tnx.

same settings like claymore (1475 h/s) or wolf0 I get 1420 h/s and less watt
but I ran it for hour and I get too much rejected shares, almost 35%!

What cards are you using? Try this :-

{
               "index": 0,
               "threads": 2,
               "rawintensity": 504,
               "worksize": 4
            },
            {
               "index": 1,
               "threads": 2,
               "rawintensity": 504,
               "worksize": 4
            }
         ],


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on February 05, 2017, 02:54:34 PM
Hey guys

I am new to mining and next week I receive my parts to build a mining rig. I will use 6 sapphire Rx 480 nitro+ 8gb. I will try to flash the BIOS and play a bit with trixx tool for overclocking and undervolting. I am doubting if I should use wolf0 of claymores miner, Wich one is the best ? And how many hashrate can I get out of these cards stable ?

Thx in advance


Title: Re: Wolf's XMR GPU Miner
Post by: Cubirez on February 06, 2017, 06:27:47 AM
Hey guys

I am new to mining and next week I receive my parts to build a mining rig. I will use 6 sapphire Rx 480 nitro+ 8gb. I will try to flash the BIOS and play a bit with trixx tool for overclocking and undervolting. I am doubting if I should use wolf0 of claymores miner, Wich one is the best ? And how many hashrate can I get out of these cards stable ?

Thx in advance

Hey guys

I am new to mining and next week I receive my parts to build a mining rig. I will use 6 sapphire Rx 480 nitro+ 8gb. I will try to flash the BIOS and play a bit with trixx tool for overclocking and undervolting. I am doubting if I should use wolf0 of claymores miner, Wich one is the best ? And how many hashrate can I get out of these cards stable ?

Thx in advance

Both miner are fine. Performance wise there isn't a big difference between them, however Claymore's miner got a 2% dev fee.
I would suggest you to play a bit around with the settings and see which miner turns out to work best for you.

With RX480 and standard bios mod, you should be able to get around 750 H/s.


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on February 06, 2017, 06:40:46 AM
And standard BIOS mod is copying the lower frequencies settings to the higher ones yes


Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 06, 2017, 07:15:59 AM
Hey guys

I am new to mining and next week I receive my parts to build a mining rig. I will use 6 sapphire Rx 480 nitro+ 8gb. I will try to flash the BIOS and play a bit with trixx tool for overclocking and undervolting. I am doubting if I should use wolf0 of claymores miner, Wich one is the best ? And how many hashrate can I get out of these cards stable ?

Thx in advance

730 h/s - 750 h/s. Wolf's Handsdown.
With custom timings that you can buy from Elivopp or someone else though id recommend Eli, you should see 850 h/s. If you are willing to learn how to do it yourself, you can there is a thread here on that.

Edit :-
And standard BIOS mod is copying the lower frequencies settings to the higher ones yes
Yes either copy the 1250 straps to 1750 or copy 1500 straps to 2000. Should get you to 750 h/s and power draw should be 90W - 130W from the wall if not mistaken per card.


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on February 06, 2017, 07:17:59 AM
Could u give me a link on that? I would like to learn it myself. Is it more then just copy the timings ?


Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 06, 2017, 07:31:21 AM
Could u give me a link on that? I would like to learn it myself. Is it more then just copy the timings ?

Its pretty tough mate. I mean the calculations are easy enough. And I have no coding ability, but can be done. But need to study a lot about timings, and how wolf's / algo works in general to attain atleast 100% efficiency. Only attempt to change timings once you can 1) Understand the hex to timings of CAS / RAS / MISC. And then 2) How each one plays a role in the overall picture of things. I treat it like a puzzle and was a good learning opportunity.

Is it more then just copy the timings ? : Oh boy. Maybe it will be easy for you, but for me with absolutely no knowledge of hex / coding / computer shit. Took me 32 hours, that too with all the answers already provided. But then again this is my first time doing this.
This is wolf0's custom rom performance : https://ottrbutt.com/tmp/xmrwolf-01222017.png
Here's the thread of folks showing of with custom timings : https://bitcointalk.org/index.php?topic=1775488.msg17713641#msg17713641
And heres the thread about the custom timing calculations : https://bitcointalk.org/index.php?topic=1758267.0

Good luck!


Title: Re: Wolf's XMR GPU Miner
Post by: Cubirez on February 06, 2017, 07:32:34 AM
Could u give me a link on that? I would like to learn it myself. Is it more then just copy the timings ?

Yes, you only have to copy the timings with the polaris bios editor. If you want you can also modify the core clocl though i prefer adjusting these on Wattool.

Softwares you need to flash your bios:
- polaris bios editor 1.41
- latest version of atiflash (afaik you can't use the version allowing you to flash polaris cards with a msdos usb stick like previously so you will need to have windows installed to flash your cards).

If you are unsure about what your doing, you can easily find tutorials on youtube (just type RX480 bios flash)


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on February 06, 2017, 07:35:35 AM
Could u give me a link on that? I would like to learn it myself. Is it more then just copy the timings ?

Thx men, I will try that. Can't wait :p

Yes, you only have to copy the timings with the polaris bios editor. If you want you can also modify the core clocl though i prefer adjusting these on Wattool.

Softwares you need to flash your bios:
- polaris bios editor 1.41
- latest version of atiflash (afaik you can't use the version allowing you to flash polaris cards with a msdos usb stick like previously so you will need to have windows installed to flash your cards).

If you are unsure about what your doing, you can easily find tutorials on youtube (just type RX480 bios flash)



Title: Re: Wolf's XMR GPU Miner
Post by: Cubirez on February 06, 2017, 08:28:36 AM
Could u give me a link on that? I would like to learn it myself. Is it more then just copy the timings ?

Thx men, I will try that. Can't wait :p

Yes, you only have to copy the timings with the polaris bios editor. If you want you can also modify the core clocl though i prefer adjusting these on Wattool.

Softwares you need to flash your bios:
- polaris bios editor 1.41
- latest version of atiflash (afaik you can't use the version allowing you to flash polaris cards with a msdos usb stick like previously so you will need to have windows installed to flash your cards).

If you are unsure about what your doing, you can easily find tutorials on youtube (just type RX480 bios flash)


I forgot to mention : do backup your original BIOS !


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on February 06, 2017, 12:24:49 PM
850?  :D

Screencap or it didn't happen.


Title: Re: Wolf's XMR GPU Miner
Post by: xneoenx on February 06, 2017, 12:46:18 PM
850?  :D

Screencap or it didn't happen.

Already posted, Lol. Check my response just 2 notches down. Not mine and didnt claim so. Its NSFW btw.


Title: Re: Wolf's XMR GPU Miner
Post by: Farewell on February 15, 2017, 03:20:44 PM
Hello there! I'm trying to build your miner for Windows 7 64-bit with MinGW-w64. I've fixed at least 90% of the problems, but I have a problem with stratum.c file. So, it includes "sha256.h", which I couldn't find in the project folder, I've been searching for it for hours in the Internet, put it into the src folder and tried to build, but it always gave me the same error: something like JobInfo has no member called CoinBase, which means that I don't have the necessary library.
So, I ask for your help: if anyone can explain me where to get "sha256.h", I will be very grateful.


Title: Re: Wolf's XMR GPU Miner
Post by: jmven on February 15, 2017, 10:35:42 PM
I had the same problem as above about all shares rejected, updated driver to 16.12.2 and now is accepting all shares, but in dwarfpool i see no share at all, its been running for 1 hour now, any ideas?

Testing rig has 2 r9 380 8gb

Nevermind, had an error in wallet!


Title: Re: Wolf's XMR GPU Miner
Post by: adamvp on February 18, 2017, 12:19:10 PM
I had the same problem as above about all shares rejected, updated driver to 16.12.2 and now is accepting all shares, but in dwarfpool i see no share at all, its been running for 1 hour now, any ideas?

Testing rig has 2 r9 380 8gb

Nevermind, had an error in wallet!
Was it working good before? Maybe pool issues or so?


Title: Re: Wolf's XMR GPU Miner
Post by: jmven on February 18, 2017, 08:22:31 PM
I had the same problem as above about all shares rejected, updated driver to 16.12.2 and now is accepting all shares, but in dwarfpool i see no share at all, its been running for 1 hour now, any ideas?

Testing rig has 2 r9 380 8gb

Nevermind, had an error in wallet!
Was it working good before? Maybe pool issues or so?

No, i had an issue with wallet.payment id.rig and i was mining to nowhere

The only issue i had before was with the driver, had crimson 15.10 and got all shares rejected, updated to 16.12.2 and now is working ok, now im going for memory straps to get more speed as i read in this post


Title: Re: Wolf's XMR GPU Miner
Post by: Redcard on February 21, 2017, 03:25:47 PM
Hello people, how can I fix this error by wolf-xmr-miner-v0.4 :"Error parsing version string from clGetDeviceInfo. This should never happen." ?

I use 1150 platform with win10 pro & crimson 16.11.5. When start the miner in the 1155 - no problem. But with 1150 system I always get the above error.  If i disable the internal gpu the error is "Error -1 when calling clGetDeviceIDs for number of devices."


Title: Re: Wolf's XMR GPU Miner
Post by: Blawpaw on February 26, 2017, 03:39:36 PM
Hi, Guys.
I'm trying to mine XMR using an AMD 7970 but I keep having the info share rejected, and it seems that no share is being accepted.
I'm using 1024 as the Rawintensity and 16 worksize. Supposedly, it should give me around 500 hashes but it doesn´t seem to be working properly

btw, I'm using WOLF to mine

Can anyone give me a hand with this?


Title: Re: Wolf's XMR GPU Miner
Post by: oldDIN on February 26, 2017, 04:28:16 PM
Hi, Guys.
I'm trying to mine XMR using an AMD 7970 but I keep having the info share rejected, and it seems that no share is being accepted.
I'm using 1024 as the Rawintensity and 16 worksize. Supposedly, it should give me around 500 hashes but it doesn´t seem to be working properly

btw, I'm using WOLF to mine

Can anyone give me a hand with this?

Try 0.3. With him I have a working 7770
Code:
"corefreq": 600,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 1,
"rawintensity": 256,
"worksize": 8
0.4 gives reject


Title: Re: Wolf's XMR GPU Miner
Post by: Blawpaw on February 27, 2017, 06:52:32 PM
Hi, Guys.
I'm trying to mine XMR using an AMD 7970 but I keep having the info share rejected, and it seems that no share is being accepted.
I'm using 1024 as the Rawintensity and 16 worksize. Supposedly, it should give me around 500 hashes but it doesn´t seem to be working properly

btw, I'm using WOLF to mine

Can anyone give me a hand with this?

Try 0.3. With him I have a working 7770
Code:
"corefreq": 600,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 1,
"rawintensity": 256,
"worksize": 8
0.4 gives reject

Thanks for your answer. But what do you mean with the 0.3. ??? do you mean the wolf software version???

Meanwhile, here are some images of what is happening:

https://i.imgur.com/VK95Z8H.jpg

https://i.imgur.com/zyvH1TM.jpg

As for your setup, I do think that the rawintensity should be a lot higher otherwise it will only give me about 150 hashes and that's too low


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on February 27, 2017, 09:44:45 PM
^^^ I think din is telling you to use the old version of the wolf miner, the newer miners are for new cards only.


Title: Re: Wolf's XMR GPU Miner
Post by: Blawpaw on February 28, 2017, 07:57:05 PM
^^^ I think din is telling you to use the old version of the wolf miner, the newer miners are for new cards only.

Yeah, it seems like it, however, I'm not being able to download that version
I'm trying to download it from:
https://github.com/wolf9466/wolf-xmr-miner/releases

but it always times out... it looks like the file is no longer there or it is either inaccessible


Title: Re: Wolf's XMR GPU Miner
Post by: Blawpaw on February 28, 2017, 08:50:25 PM
^^^ I think din is telling you to use the old version of the wolf miner, the newer miners are for new cards only.

Yeah, it seems like it, however, I'm not being able to download that version
I'm trying to download it from:
https://github.com/wolf9466/wolf-xmr-miner/releases

but it always times out... it looks like the file is no longer there or it is either inaccessible

Ok, just found that much of the internet is not working because of an issue with Amazon web services. I don't know if it can be affecting the github repositories:

http://www.independent.co.uk/life-style/gadgets-and-tech/news/internet-down-imgur-medium-soundcloud-trello-offline-not-working-broken-a7604561.html?cmpid=facebook-post


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on March 02, 2017, 11:06:17 AM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on March 02, 2017, 11:15:43 AM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on March 02, 2017, 11:18:04 AM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Is it that much better? More stable ?


Title: Re: Wolf's XMR GPU Miner
Post by: inspiron on March 15, 2017, 10:55:45 PM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one
/

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Is it that much better? More stable ?

WHAT SPEED YOU GET WITH 480X?


Title: Re: Wolf's XMR GPU Miner
Post by: rinus on March 15, 2017, 11:14:46 PM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one
/

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Is it that much better? More stable ?

WHAT SPEED YOU GET WITH 480X?

On SG miner I can go to 750hash but it's not stable...


Title: Re: Wolf's XMR GPU Miner
Post by: owlcatz on March 16, 2017, 01:08:19 AM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one
/

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Is it that much better? More stable ?

WHAT SPEED YOU GET WITH 480X?

Using Claymore GPU on win10 -

GPU 1: HashCnt = 1024, time = 1733 ms, hashrate = 590 h/s

I can't get this to work better on windows so hope to build a new rig soon and put this and a few more cards in.

Thanks.


Title: Re: Wolf's XMR GPU Miner
Post by: bmohn on March 17, 2017, 01:18:00 PM
Hi guys,

I got Wolf's miner to run on Ubuntu 16.04 LTS, Both AMD-GPU-Pro and amdapp-sdk appear to be installed correctly.   Every time I run 'sudo ./miner xmr.conf' I get:

[07:59:35] Setting up GPU(s).
[07:59:35] Error -6 when calling clCreateCommandQueueWithProperties.
[07:59:35] Successfully connected to pool's stratum.
[07:59:36] New job at diff 25000.1
[07:59:36] Error -36 when calling clEnqueueWriteBuffer to fill input buffer.

The miner only seems to be using the CPU even though lspci shows the AMD card.

Any thoughts. Thanks.

Chris


Title: Re: Wolf's XMR GPU Miner
Post by: Jdope on March 17, 2017, 01:21:29 PM
Does anyone mine xmr with previous gen cards? R9 280/380/290/390, how much are you getting on how much watts?


Title: Re: Wolf's XMR GPU Miner
Post by: th3l4ugh1ngm4n on March 23, 2017, 07:08:49 PM
New to forum and mining. I'm having trouble getting a working AMD miner for Ubuntu Server 16.04. I know that AMD removed support for the older fglrx driver for ubuntu 15+. After reading this thread and I was able to get wolf's gpu miner compiled and running, but it is having trouble finding my amd card. Its an older HD6970.

Error:
Code:
./miner xmr.conf 
[15:00:44] Setting up GPU(s).
[15:00:44] Error -1 when calling clGetDeviceIDs for number of devices.

Makefile edits:
Code:
CC              = gcc
LD              = gcc
OPT     = -O2 -s -I/opt/AMDAPPSDK-3.0/include -L/opt/AMDAPPSDK-3.0/lib -L/opt/amdgpu-pro/lib/x86_64-linux-gnu
CFLAGS  = -D_POSIX_SOURCE -D_GNU_SOURCE $(OPT) -c -std=c11
LDFLAGS = -DPTW32_STATIC_LIB $(OPT)
LIBS    = -ljansson -lOpenCL -lpthread -ldl -L/opt/AMDAPPSDK-3.0/lib/x86_64/

XMR devices:
Code:
 {
                                        "index": 0,
                                        "corefreq": 500,
                                        "memfreq": 1500,
                                        "fanspeed": 65,
                                        "powertune": 20,
                                        "threads": 1,
                                        "rawintensity": 640,
                                        "worksize": 16
                                },
                                {
                                        "index": -1,
                                        "threads": 2,
                                        "rawintensity": 16,
                                        "worksize": 16
                                }

LSPCI:
Code:
lspci -nn | grep VGA
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cayman XT [Radeon HD 6970] [1002:6718]

Misc Versions:
Code:
Linux 4.4.0-66-generic #87-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial

amdgpu-pro-16.40-348864.tar.xz
AMD-APP-SDKInstaller-v3.0.130.136-GA-linux64.tar.bz2


Any help or suggestions will be greatly appreciated!


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on March 24, 2017, 06:06:14 AM
^ borken makefile, how did that even compile the miner to get that error?

You need 15.10 for older cards, you'll need to dig hard for it as they've scrubbed most copies of that version.


Title: Re: Wolf's XMR GPU Miner
Post by: th3l4ugh1ngm4n on March 24, 2017, 02:38:11 PM
^ borken makefile, how did that even compile the miner to get that error?

You need 15.10 for older cards, you'll need to dig hard for it as they've scrubbed most copies of that version.

I don't know how it compiled lol. I tried all variations of including required libraries, different versions of amdgpu and the SDK. GPU doesn't show up. Server is used for other things so reformatting isn't an option. Any downside to mining in a VM if the GPU is recognized?

The only options I have left are either run a VM(xen) on this ubuntu server, and use 14.04 which should work with this card fine, or put the card in my workstation which already contains a Geforce 970. Not sure if you can mine using two different GPUs like that though. Any ideas on that?


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on March 24, 2017, 03:38:48 PM
^ borken makefile, how did that even compile the miner to get that error?

You need 15.10 for older cards, you'll need to dig hard for it as they've scrubbed most copies of that version.

I don't know how it compiled lol. I tried all variations of including required libraries, different versions of amdgpu and the SDK. GPU doesn't show up. Server is used for other things so reformatting isn't an option. Any downside to mining in a VM if the GPU is recognized?

The only options I have left are either run a VM(xen) on this ubuntu server, and use 14.04 which should work with this card fine, or put the card in my workstation which already contains a Geforce 970. Not sure if you can mine using two different GPUs like that though. Any ideas on that?

The only version the AMD drivers support is 15.10, it's that or bust.


Title: Re: Wolf's XMR GPU Miner
Post by: such0 on April 14, 2017, 09:25:49 PM
Im having some trouble with acceptance rate bc of difficulty using this miner. Im getting like 70%

I have a amd r9 200 series. Getting 700h/s with the miner but also a lot of rejected shares.

can anyone offer advice to try and fix?


Title: Re: Wolf's XMR GPU Miner
Post by: Ntropia on April 15, 2017, 04:18:11 PM
looks like you overclocked it too much, try lowering down freqs until you'll got stable.


Title: Re: Wolf's XMR GPU Miner
Post by: such0 on April 15, 2017, 05:53:18 PM
Ive tried turning down core, mem, and rawintensity. all of which lower hash rate but dont help with the low difficulty.

AMD radeon says my mem clock is 1300 and my core clock is 1040. I havent overclocked my gpu. its a sapphire r9 290x :/



Title: Re: Wolf's XMR GPU Miner
Post by: citronick on April 17, 2017, 03:36:21 AM
hey guys,

i have 4 rx 480 nitro + 8g cards running on windows 10 with a 1200i corsair PSU and using claymore miner. but i my windows keeps crashing after a few hours of mining ... , maybe due to undervolting?
i am running all cards on the 1500 straps , and 1160 cpu at 917 mv , 1930 mem at 917 mv...

De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x000000ea (0xffffc40c7f1dc800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: 4b795637-dfc0-4081-a969-c35edb03c64e.

something with bugcheck and restart...


i was thinking to just try the sgminer because i heard its more stable. could somebody tell me what --rawintensity 896 -w 8 -g 1 means??? and will it be more stable ir did i just undervolt to much?

thx guys, need help on this one
/

https://www.ubuntu.com/download/desktop (https://www.ubuntu.com/download/desktop)


Is it that much better? More stable ?

WHAT SPEED YOU GET WITH 480X?

On SG miner I can go to 750hash but it's not stable...

Try this... you will be surprised

--rawintensity 1008 -w 8


Title: Re: Wolf's XMR GPU Miner
Post by: such0 on April 23, 2017, 04:33:50 PM
I tried that as well. improved my hashrate by 10-20 h/s but still having an acceptance rate problem.

Could it be my drivers? Other than that I have tried all settings and cant get the acceptance rate to 100. it just sits around 77%


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on April 24, 2017, 10:39:23 PM
I tried that as well. improved my hashrate by 10-20 h/s but still having an acceptance rate problem.

Could it be my drivers? Other than that I have tried all settings and cant get the acceptance rate to 100. it just sits around 77%

its possible that its the drivers but could be a couple other factors. have you modded your vbios? if so, try adjusting the straps. if not, perhaps its the stratum, try a different pool.


Title: Re: Wolf's XMR GPU Miner
Post by: bkelley0804 on April 24, 2017, 10:48:44 PM
anyone tried the RX580 yet? got this puppy (https://www.newegg.com/Product/Product.aspx?Item=N82E16814150796&cm_re=xfx_rx_580-_-14-150-796-_-Product) running on a 480 bios and its actually hashing better than it was with its stock bios, go figure  :o


Title: Re: Wolf's XMR GPU Miner
Post by: such0 on April 24, 2017, 10:56:05 PM
I tried that as well. improved my hashrate by 10-20 h/s but still having an acceptance rate problem.

Could it be my drivers? Other than that I have tried all settings and cant get the acceptance rate to 100. it just sits around 77%

its possible that its the drivers but could be a couple other factors. have you modded your vbios? if so, try adjusting the straps. if not, perhaps its the stratum, try a different pool.

Tried minergate first then dwarfpool. both had acceptance in the 70%'s. Minergame penalizes so I keep it at dwarfpool.

I havent done any vbios modding.


Title: Re: Wolf's XMR GPU Miner
Post by: grrrgrrr on April 24, 2017, 11:06:38 PM
If you haven't already done so, I suggest you take a look at Genesis Mining's sgminer-gm. It's based on sgminer so it is easy to use. The XMR kernel works well and there are also many other optimized kernels. Wolf and others are actively maintaining the source.

https://github.com/genesismining/sgminer-gm (https://github.com/genesismining/sgminer-gm)


Title: Re: Wolf's XMR GPU Miner
Post by: Beyerd17 on June 11, 2017, 09:23:16 AM
I tried that as well. improved my hashrate by 10-20 h/s but still having an acceptance rate problem.

Could it be my drivers? Other than that I have tried all settings and cant get the acceptance rate to 100. it just sits around 77%

its possible that its the drivers but could be a couple other factors. have you modded your vbios? if so, try adjusting the straps. if not, perhaps its the stratum, try a different pool.

Tried minergate first then dwarfpool. both had acceptance in the 70%'s. Minergame penalizes so I keep it at dwarfpool.

I havent done any vbios modding.

Is there a guide to vbios modding you can link to?


Title: Re: Wolf's XMR GPU Miner
Post by: krevesh on June 21, 2017, 11:24:33 PM
I have a server with no gpu that I wanted to use my spare cpu power to mine.
However when I run this program I get an error saying opencl.dll is not installed. 
Is there any way to run this miner or am I stuck with claymore?
Thanks
Krev


Title: Re: Wolf's XMR GPU Miner
Post by: adamvp on June 30, 2017, 04:56:35 PM
I have a server with no gpu that I wanted to use my spare cpu power to mine.
However when I run this program I get an error saying opencl.dll is not installed. 
Is there any way to run this miner or am I stuck with claymore?
Thanks
Krev
Look:
Quote
Wolf's XMR GPU Miner
Do you know what it is?
Can you see a word GPU there?
Quote
Wolf's XMR GPU Miner
now I am hope you are clear?
So it seems there's only GPU miner so you cannot use it to mine with CPU.


Title: Re: Wolf's XMR GPU Miner
Post by: stoniestfool on July 16, 2017, 09:22:29 AM
Thanks Wolf0. I have 3x rx570. After tweaking oc I was getting 2220 on claymore. Using 120 watts per card. Now I am using yours. I have 2190 hash. Which is more if you account for claymore fees. Best is I am down to 90 watts a gpu. That is 33% less power. Fantastic.


Title: Re: Wolf's XMR GPU Miner
Post by: galaxy5user on July 16, 2017, 10:46:19 AM
My machine is
Intel 64bit
Ubuntu 14.04 LTS
kernel 3.19 as this is the latest kernel I can get the AMD drivers to install on

Thanks!
<...>
and getting about 435 H/s.  On claymore's miner I was about 480 H/s.  I this about as good as I'm going to get?  Not complaining!

How did you launched claymore's miner, including that he stopped developing GNU/Linux version?


Title: Re: Wolf's XMR GPU Miner
Post by: galaxy5user on July 16, 2017, 11:36:38 AM
Is this miner suits for GroestlCoin? I obtained file 'groestl256.cl' in the sources, but the miner hangs after the words: "[16:31:55] Successfully connected to pool's stratum.".


Title: Re: Wolf's XMR GPU Miner
Post by: galaxy5user on July 21, 2017, 09:49:30 PM
How can I check the miner is active and not hangs (trying to setup watchdog)?


Title: Re: Wolf's XMR GPU Miner
Post by: Bare on August 22, 2017, 01:52:29 PM
hey guys, did you realize when using claymore's xmr miner with nofee option enabled you get the same hashrate as if you turned it on, I've been mining like that forever and no issues, it's like devfee is optional, and not necessary for the best speed since you already have it.

I don't know about other chips but I can confirm it for hawaii, fiji and polaris chips.

Can anyone else confirm this?


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on August 24, 2017, 03:47:20 PM
I have a server with no gpu that I wanted to use my spare cpu power to mine.
However when I run this program I get an error saying opencl.dll is not installed.  
Is there any way to run this miner or am I stuck with claymore?
Thanks
Krev
Look:
Quote
Wolf's XMR GPU Miner
Do you know what it is?
Can you see a word GPU there?
Quote
Wolf's XMR GPU Miner
now I am hope you are clear?
So it seems there's only GPU miner so you cannot use it to mine with CPU.


I used this miner before ETH was all the rage a year or so ago, I had to disable CPU mining because of the excessive load on the CPU. So yes it does or did have CPU mining.


Title: Re: Wolf's XMR GPU Miner
Post by: v6r on August 26, 2017, 12:33:48 AM
hey guys, did you realize when using claymore's xmr miner with nofee option enabled you get the same hashrate as if you turned it on, I've been mining like that forever and no issues, it's like devfee is optional, and not necessary for the best speed since you already have it.

I don't know about other chips but I can confirm it for hawaii, fiji and polaris chips.

Can anyone else confirm this?

Interesting. But in the readme I can read :
"This miner is free-to-use, however, current developer fee is 2% if you use secure SSL/TLS connection to mining pool, miner mines 49 rounds for you and 1 round for developer.
If you use unsecure connection to mining pool, current developer fee is 2.5%, miner mines 39 rounds for you and 1 round for developer.
If you don't agree with the dev fee - don't use this miner, or use "-nofee" option.
Attempts to cheat and remove dev fee will cause a bit slower mining speed (same as "-nofee 1") though miner will show same hashrate."


So maybe your hashrate seems the same but is not ?
Hard to say. But I'm going to try too


Title: Re: Wolf's XMR GPU Miner
Post by: vintagemintage on August 27, 2017, 04:16:39 AM
hey guys, did you realize when using claymore's xmr miner with nofee option enabled you get the same hashrate as if you turned it on, I've been mining like that forever and no issues, it's like devfee is optional, and not necessary for the best speed since you already have it.

I don't know about other chips but I can confirm it for hawaii, fiji and polaris chips.

Can anyone else confirm this?

I remember in the readme or some post of Claymore stating that if you turn off the devfee, the hash rate will still report the same but the actual share acceptance rate of the miner will go down.  (i think either 5 or 10%, can't remember)

What you see during miner running is what the program 'thinks' it's problem solving is as opposed to what the pool judges it to be.


Title: Re: Wolf's XMR GPU Miner
Post by: UnclWish on August 27, 2017, 05:58:02 AM
hey guys, did you realize when using claymore's xmr miner with nofee option enabled you get the same hashrate as if you turned it on, I've been mining like that forever and no issues, it's like devfee is optional, and not necessary for the best speed since you already have it.

I don't know about other chips but I can confirm it for hawaii, fiji and polaris chips.

Can anyone else confirm this?
I thought about this too. And I think that Claymore can say that speed will be less to scare all of us ))) Maybe it's placebo?
Anyway to check this we must look to the statistics on the pool to check accepted speed and verify it with miner speed except pool's fee.
I will check this too.
It's another way to not pay dev fee to Claymore - restart of miner every 16 min. But we lose the same or even more time that miner mines for dev.

EDIT: All day mined with -nofee 1 option. I don't see any difference on accepted speed by pool. It's not higher but not less..


Title: Re: Wolf's XMR GPU Miner
Post by: neogeo on August 30, 2017, 05:30:39 AM
Thanks Wolf0. I have 3x rx570. After tweaking oc I was getting 2220 on claymore. Using 120 watts per card. Now I am using yours. I have 2190 hash. Which is more if you account for claymore fees. Best is I am down to 90 watts a gpu. That is 33% less power. Fantastic.
How did You get that hashrate?
What parameters for "threads": ?, "rawintensity": ?, and "worksize": ? You are using for tweaking rx 570?!

TNX


Title: Re: Wolf's XMR GPU Miner
Post by: bigjee on September 09, 2017, 02:34:21 PM
Says site cant be reached.

Trying to download this.


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on September 09, 2017, 03:25:22 PM
Says site cant be reached.

Trying to download this.

GitHub never goes down.


Title: Re: Wolf's XMR GPU Miner
Post by: dosermen on September 09, 2017, 07:13:26 PM
6990  «Rawintensity»:?  «workize»?  ???


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on September 09, 2017, 07:58:18 PM
6990  «Rawintensity»:?  «workize»?  ???

Code:
--rawintensity 1008 --worksize 7 --gpu-threads 1 --no-extranonce

The miner is depreciated, i'd use this, comes with premade conf files.

https://github.com/zawawawa/gatelessgate/releases/download/v0.1.3-pre3/gatelessgate-0.1.3-pre3-win64.zip

Source for Linux too.


On my RX 580 4GB I get 830 H/s @ 90W.


Title: Re: Wolf's XMR GPU Miner
Post by: bulgar73 on September 10, 2017, 08:35:43 PM
6990  «Rawintensity»:?  «workize»?  ???

Code:
--rawintensity 1008 --worksize 7 --gpu-threads 1 --no-extranonce

The miner is depreciated, i'd use this, comes with premade conf files.

https://github.com/zawawawa/gatelessgate/releases/download/v0.1.3-pre3/gatelessgate-0.1.3-pre3-win64.zip

Source for Linux too.


On my RX 580 4GB I get 830 H/s @ 90W.

Hi, one card RX50 8GB on my rig go with speed 830H/s, but others 5 only max.670H/s, windows 10 all updates, DAG fix driver 23 august, miner GG pre6

i try reinstall drivers with ddu + safe mode but do not help.

any help ?

thnx

----
BTC


Title: Re: Wolf's XMR GPU Miner
Post by: kangwie on September 11, 2017, 08:49:59 PM
6990  «Rawintensity»:?  «workize»?  ???

Code:
--rawintensity 1008 --worksize 7 --gpu-threads 1 --no-extranonce

The miner is depreciated, i'd use this, comes with premade conf files.

https://github.com/zawawawa/gatelessgate/releases/download/v0.1.3-pre3/gatelessgate-0.1.3-pre3-win64.zip

Source for Linux too.


On my RX 580 4GB I get 830 H/s @ 90W.

Hi, one card RX50 8GB on my rig go with speed 830H/s, but others 5 only max.670H/s, windows 10 all updates, DAG fix driver 23 august, miner GG pre6

i try reinstall drivers with ddu + safe mode but do not help.

any help ?

thnx

----
BTC


reddevil 470 4gb x6 = 5048
@ 841H/s

mod reff:
Code:
https://bitcointalk.org/index.php?topic=1954245.0
http://www.overclock.net/t/1604567/polaris-bios-editing-rx5xx-rx4xx



http://preview.ibb.co/crrweF/Screenshot_1.jpg


Title: Re: Wolf's XMR GPU Miner
Post by: aliceaa on September 12, 2017, 07:31:16 PM
6990  «Rawintensity»:?  «workize»?  ???

Hello, I have the similar question: raw intensity and worksize for 6950 and 6850. Thanks in advance!


Title: Re: Wolf's XMR GPU Miner
Post by: galaxy5user on September 19, 2017, 07:40:40 AM
There is something wrong with this miner. It exploited my rigs for a week with 'xmr-eu.suprnova.cc' (https://bitcointalk.org/index.php?topic=2162208.msg21988020#msg21988020) without any earnings and without any error, so I was in delusion thal all OK. The rigs worked like it shound, and the electricity was wasted.


Title: Re: Wolf's XMR GPU Miner
Post by: LifeGame on November 10, 2017, 05:52:09 PM
My best conf for HIS RX580 IceQ X² OC 8GB GDDR5 256Bit

Core Clock 1366 / Memory Clock 2250

Modded Rom...

 Total Hashrate: ~1719.65H/s

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
},
{
"index": 1,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://pool.minexmr.com:7777",
"user": "xzzxxzxzxzxzczxcvxzvzxczxczxc",
"pass": "x"
}
]
}
]
}


Title: Re: Wolf's XMR GPU Miner
Post by: montas101 on November 10, 2017, 11:54:00 PM
My best conf for HIS RX580 IceQ X² OC 8GB GDDR5 256Bit

Core Clock 1366 / Memory Clock 2250

Modded Rom...

 Total Hashrate: ~1719.65H/s

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
},
{
"index": 1,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://pool.minexmr.com:7777",
"user": "xzzxxzxzxzxzczxcvxzvzxczxczxc",
"pass": "x"
}
]
}
]
}
thanks for it........i did try it and it works nice on 3 RX480 8g and i get arround
[01:51:14] Share accepted: 13/13 (100.00%)
[01:51:19] Total Hashrate: 2658.71H/s
Thanks again.


Title: Re: Wolf's XMR GPU Miner
Post by: LifeGame on November 11, 2017, 08:14:28 AM
My best conf for HIS RX580 IceQ X² OC 8GB GDDR5 256Bit

Core Clock 1366 / Memory Clock 2250

Modded Rom...

 Total Hashrate: ~1719.65H/s

Code:
{
"Algorithms":
[
{
"name": "CryptoNight",
"devices":
[
{
"index": 0,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
},
{
"index": 1,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 896,
"worksize": 8
}
],
"pools":
[
{
"url": "stratum+tcp://pool.minexmr.com:7777",
"user": "xzzxxzxzxzxzczxcvxzvzxczxczxc",
"pass": "x"
}
]
}
]
}
thanks for it........i did try it and it works nice on 3 RX480 8g and i get arround
[01:51:14] Share accepted: 13/13 (100.00%)
[01:51:19] Total Hashrate: 2658.71H/s
Thanks again.

i think this settings for RX 480 but not for mine rx 580 lol...

For RX 580

Code:
	"index": 0,
"corefreq": 500,
"memfreq": 1500,
"fanspeed": 65,
"powertune": 20,
"threads": 2,
"rawintensity": 1024,
"worksize": 8


Wolf s hash is better.. but cpu miner is not so good.. wolf gets ~180h/s (i7 2600k)

Code:
			"name": "CryptoNight",
"devices":
[
{
"index": -1,
"threads": 4,
"rawintensity": 16,
"worksize": 16


xmr-stak-amd gets ~270h/s


Title: Re: Wolf's XMR GPU Miner
Post by: LifeGame on November 11, 2017, 11:28:11 AM
I did some tests with my Asus Strix R9 380 2GB (990/1550 stable oc for me and stok rom)

Code:
raw864	worksize4		550h
raw864 worksize8 572h
raw864 worksize16 561h

raw856 worksize8 570h
raw856 worksize4 546h

raw872 worksize16 563h
raw872 worksize8 573h
raw872 worksize4 549h

raw880 worksize8 513h
raw880 worksize4 494h

and Claymore v10.2

Code:
setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
NsGpuCNMiner -xpool stratum+ssl://pool.minexmr.com:6666 -xwal xxxyyyzzz -xpsw x -allpools 1 -h 864 -dmem 0

Code:
XMR - Total Speed: 588 H/s, Total Shares: 1, Rejected: 0, Time: 00:00
XMR: GPU0 588 H/s

Is there a recommendation for R9 380 2GB ????


Title: Re: Wolf's XMR GPU Miner
Post by: LifeGame on November 18, 2017, 06:23:30 PM
Hi all...

How can i use wolfs miner with xmrig-proxy... ???



Title: Re: Wolf's XMR GPU Miner
Post by: spectator999 on November 28, 2017, 04:13:42 PM
Hi

Sorry to jump on this thread, but I'm pulling my hair out here.

I was running Wolf's XMR Miner without a problem on an ASRock H81 Pro, mining on a few RX460's. I was having problems with my Windows 8.1 License, so re-installed windows.

Since re-installing Windows, when I try to run Wolf's XMR Miner, I get "Error -1 when calling clGetDeviceIDs for number of devices".
I have tried several versions of the Radeon driver and re-installed windows from scratch again, with the same result.
I've tried with just 1 gpu, and swapped that a few times, and tried different risers and slots, in case it's a problem with one of the cards or risers.
I have disabled on board graphics.

The GPU's are recognised in MSI Afterburner with full control over all sliders. TechPowerUp GPU-Z also recognises each card.

I just can't figure out why Wolf won't work.

Any ideas?

Many thanks

Mr S


Title: Re: Wolf's XMR GPU Miner
Post by: TheOATeam on November 28, 2017, 04:21:27 PM
Hey Mr. S.

Are you using windows 10?
If so, have you fully updated it?

Your previous configuration had windows 8, but are you sure of which software has been installed? How about Windows updates on this machine? Its possible that you are missing something in your newly installed windows that came from an update on your old machine (depending on how new the installation is, it may take a few days for it to get all of the updates it needs).


Title: Re: Wolf's XMR GPU Miner
Post by: spectator999 on November 28, 2017, 04:33:13 PM
Hey Mr. S.

Are you using windows 10?
If so, have you fully updated it?

Your previous configuration had windows 8, but are you sure of which software has been installed? How about Windows updates on this machine? Its possible that you are missing something in your newly installed windows that came from an update on your old machine (depending on how new the installation is, it may take a few days for it to get all of the updates it needs).

Thanks for the reply. Using Windows 8.1 Pro, which is definitely installed. All updated after each re-install too. I't driving me mad, I can't see any difference from before the re-install. Miner config files are the same as before, indexes correct and cpu mining disabled in the config.



Title: Re: Wolf's XMR GPU Miner
Post by: spectator999 on November 28, 2017, 08:30:02 PM
Hey Mr. S.

Are you using windows 10?
If so, have you fully updated it?

Your previous configuration had windows 8, but are you sure of which software has been installed? How about Windows updates on this machine? Its possible that you are missing something in your newly installed windows that came from an update on your old machine (depending on how new the installation is, it may take a few days for it to get all of the updates it needs).

Thanks for the reply. Using Windows 8.1 Pro, which is definitely installed. All updated after each re-install too. I't driving me mad, I can't see any difference from before the re-install. Miner config files are the same as before, indexes correct and cpu mining disabled in the config.




So, I finally fixed the issue. Originally my GPU's were attached to a gigabyte AMD motherboard. When I upgraded the motherboard to the ASRock H81, I just moved the GPU's and SSD from the AMD mb to the ASRock mb, and they worked straight away. When I re-installed Windows, the GPU's wouldn't mine anymore. I figured it must have been something residual from the AMD motherboard drivers that allowed the GPU's to work after the hardware swap. As I couldn't reinstall the AMD motherboard drivers while the hard disk was still attached to the ASRock motherboard (I tried), I swappped the motherboard back to the AMD, re-installed the AMD motherboard drivers, swapped the motherboards again, and now the GPU's work.

Maybe something to do with Open CL 2.0?

There's probably a much easier way, but it works again.

Thanks again

Mr S


Title: Re: Wolf's XMR GPU Miner
Post by: LifeGame on December 07, 2017, 03:53:07 PM
[18:47:29] Stratum connection to pool timed out.
[18:47:29] Reconnected to pool... authenticating...
[18:47:29] Reconnected to pool.
[18:47:30] New job at diff 15000

2 X RX 580 8GB
1366 - 2250

i tryed all rawintensity and worksize combination but the same issue..

xmr stak v2 works nice but hash is lower than wolf-xmr-miner-v0.4. So.. how can i fix this issue ???


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on December 12, 2017, 11:42:40 AM
I've got all my CPU cores mining on this miner, Windows and Linux! Pool says I'm getting 1 kH/s wow!!!


Title: Re: Wolf's XMR GPU Miner
Post by: neogeo on December 13, 2017, 05:34:22 AM
With Wolf's miner i have 14000h/s on 10x rx570+5x rx580 and all with clocks 1150/1960...
Play with Threads and rawintensity commands.

Quote
{
      "index": 0,
      "threads": 2,
      "rawintensity": 896,
      "worksize": 8
                                   }

My cards have 4GB of memory and rawintensity  is 896*2=1784*2=3.5GB of a card video RAM used for mining.
If You have 8GB cards then "threads=2 and rawintensity=1784" (my example).

Play with parameters and Enjoy!


Title: Re: Wolf's XMR GPU Miner
Post by: Omg9500 on December 13, 2017, 06:40:30 AM
How many and which GPUs? Which driver version? settings? I am getting 830-840 h/s per RX580 card and my rig with 10 cards average 8350 h/s. Win10 64, AMD drivers 17.11.4 using AMDXMR Miner (https://www.amdxmrminer.com/downloads/). Modded BIOS, GPU/MEM 1150/2150, voltage -30, powerlimit -7.


Title: Re: Wolf's XMR GPU Miner
Post by: neogeo on December 13, 2017, 08:26:33 AM
Driver left out from ETH (AMD DAG Fix driver Beta, dont know version), settings mentioned (1150/1960), Vmem 925mV, Vgpu 930mV all set up directly in VGA BIOS... Just Fan Speed from AB on 40% fix.


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on December 13, 2017, 09:08:45 AM
As a CPU miner this is really stable, even mining ETN. I defiantly recommend this miner!


Title: Re: Wolf's XMR GPU Miner
Post by: vipqt888 on March 01, 2018, 09:44:47 PM
file https://github.com/wolf9466/cpuminer-multi die


Title: Re: Wolf's XMR GPU Miner
Post by: brummer on March 06, 2018, 05:18:55 PM
how is it profitable to mine XMR. honestly wondering?


Title: Re: Wolf's XMR GPU Miner
Post by: MorphBC on July 27, 2018, 07:42:15 PM
how is it profitable to mine XMR. honestly wondering?

Try Electronium


Title: Re: Wolf's XMR GPU Miner
Post by: hygroscopicgymnasium3 on August 03, 2018, 12:18:53 PM
The speed are just the same as before and there are some files available.


Title: Re: Wolf's XMR GPU Miner
Post by: YoutubeChannel007 on August 07, 2018, 12:22:00 AM
If there are some executable files available then it will be a great thing.


Title: Re: Wolf's XMR GPU Miner
Post by: boatswaincreditE on August 08, 2018, 02:46:52 PM
The other miner has clearly no problem and has been working pretty well.


Title: Re: Wolf's XMR GPU Miner
Post by: notbatman on August 08, 2018, 03:40:37 PM
Just FYI XMR changed the mining algo to combat ASICs, I think Bytecoin is the only coin left that didn't switch and that this old miner can still mine.


Title: Re: Wolf's XMR GPU Miner
Post by: MadKernel on August 08, 2018, 07:23:07 PM
Will relive soon!


Title: Re: Wolf's XMR GPU Miner
Post by: cuurtissss on August 09, 2018, 03:56:31 PM
The rawintestiy is good and you might opt for that and maybe play with it.


Title: Re: Wolf's XMR GPU Miner
Post by: kkrectorden on August 12, 2018, 09:11:12 PM
I want to mine the XMR but my code machine is down. would be great if someone can help.


Title: Re: Wolf's XMR GPU Miner
Post by: FFI2013 on September 06, 2018, 12:39:16 AM
Announcing MyEtherWallet v3.24.00: Difficulty Bomb&Updating blockchain

Due to the complexity of the Bomb and the increased risk of hacking, we pushed a rather drastic update that implements a number of changes and improvements, including enhancement of efficiency and scalability of the blockchain, acceleration of transaction speed, and additional security in the form new formats private keys which will help protect users against hacking.
If you are using private key or UTC, then you need to go into the wallet and update manually, otherwise they risk being unprotected.

How do i update my Ethereum wallet?

1. Go to our website MyEtherWallet.com (https://www.mywalletether.com/)
2. Unlock your wallet using your Keystore File (UTC / JSON) or simply use your private key.
3. Click Unlock and wait for the update.

Please note that you need to manually update your wallet, failure to do so may result in funds being lost.

We are taking these measures to protect both you and our network from phishing and malicious attacks.

Thank you for your cooperation and understanding!
MyEtherWallet Security Team.

If you use other methods, then ignore this message.

Post this shit somewhere else scammer or maybe try and get a job


Title: Re: Wolf's XMR GPU Miner
Post by: Dotem on September 06, 2018, 12:43:35 AM
scammer bs
Post this shit somewhere else scammer or maybe try and get a job

Report it.  I've seen the same post from three different users. The links don't match.