Topic: WildRig Multi 0.35.1 beta 2 multi-algo miner for AMD & NVIDIA - page 14. (Read 92082 times)

Where is API documentation?

Hi! I wanted to ask if an upgrade was in the works for RDNA2 Cards? I tried mining with 2 Rx6700Xt's but they are not recognized.
EDIT: for Zano specifically.

Unfortunately my card does not support bristol ridge. So I can't play mining some coins.

Hi!
Why doesn't your miner work in solo?
I'm trying to mine one coin that is not on the pool, but neither AMD or NVIDIA do not work.
There are no errors at all.
Miner just shows statistics with 0 hash and that's it.

Is amd 6800 supported? Looking to min vprogpow algo anf looks like this mine4 is only one for amd cards

i have a proble when i use this in windows10 nvidia gtx1070
the program will print: Unwanted module "C:\Program Files (x86)\Sangfor\SSL\ClientComponent\SangforNspX64.dll"...
why is that?anyone can help me !!!!!!!!!
thx alot!!!!!!!!!!!!!!!!!

* VERSIONS: WildRig/0.28.3 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015                                                       * CPU:      Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz                                                                    * ALGO:     phi5                                                                                                        * POOL #1:  stratum.aikapool.com:7980                                                                                   * COMMANDS: hashrate, statistics, pause, resume                                                                        [00:13:32] donation: 2%                                                                                                 [00:13:32] send-stale: no                                                                                               [00:13:32] watchdog: disabled                                                                                           [00:13:32] temp limits: 60C..85C                                                                                        Unwanted module "C:\Program Files (x86)\Sangfor\SSL\ClientComponent\SangforNspX64.dll"...

Any plans to support the new RX 6000 series any time soon?

For mining Kyan with x11d, it just won't connect with multi-gpu rigs. Just get "timeout" from the pool (mecrypto.club in this instance). And it's really finicky about even getting it to work with individual GPUs, setting the threads to 2 and intensity to 22x128 works on, for instance, an RX5600s and RX5700s, but no combination will hash with RX580 8GB cards.

RX480 4GB cards load any intensity/opencl setting.

start.bash:

#!/bin/bash
#export GPU_FORCE_64BIT_PTR=1
#export GPU_MAX_ALLOC_PERCENT=100
#export GPU_SINGLE_ALLOC_PERCENT=100
#export GPU_MAX_HEAP_SIZE=100
#export GPU_USE_SYNC_OBJECTS=1

# opencl-launch 22x128 with two threads worked; 24x256 didn't
screen -dmS wildrig ./wildrig-multi --algo x11k --opencl-threads 2 --opencl-launch 22x128 --opencl-device 0 --strategy 1 \
-o stratum+tcp://na.mecrypto.club:9484 -u (my_kyan_wallet) -w x -p Annabelle75_$(hostname)_gpu

(mecrypto.club reads the password field as the worker name, hence the juxtaposition)

________________________

Produces:
[09:50:08] AMD Navi(gfx1010) not fully optimized yet for chosen algorithm
[09:50:08] GPU #0: AMD Radeon RX 5600 XT [busID: 3] [arch: gfx1010]
[09:50:08] threads: 2, intensity: 22, worksize: 128/256, cu: 36, mem: 6128Mb
[09:50:11] use pool na.mecrypto.club:9484 149.248.58.224
[09:50:11] Stratum set raw difficulty to 0.0160

But intensity of 22x256, anything_x_256 and it won't hash.

Any ideas would be most welcome, and thanks!

Hi, so far this new gpu's are not supported.

Hello there!

I'm having an issue with my AMD GPU, i have a 6900XT and when i try to use this miner i get:

architecture "gfx1030" not supported

 

Any advice ?


Thanks so much for the effort !!

Hi, you need to use port 3333. Encrypted protocol is not supported by wildrig.

Hi. I have an issue with the miner. It doesn't seem to work

I'm using hiveos. The extra arguments are

--opencl-threads 2
--opencl-launch auto
--opencl-device 1,2

* ALGO: kawpow
* POOL #1: stratum-ravencoin.flypool.org:3443
* API PORT: 60060
* COMMANDS: hashrate, statistics, pause, resume
[20:58:32] Failed to obtain all required AMD file pointers
[20:58:32] AMD hardware monitoring disabled
[20:58:32] donation: 1%
[20:58:32] send-stale: no
[20:58:32] watchdog: disabled
[20:58:32] initializing GPUs...
[20:58:32] GPU #1: Radeon RX 570 Series [busID: 3] [arch: ellesmere]
[20:58:32] threads: 2, intensity: 23, worksize: 0/256, cu: 32, mem: 4081Mb
[20:58:32] GPU #1: Radeon RX 570 Series [busID: 4] [arch: ellesmere]
[20:58:32] threads: 2, intensity: 23, worksize: 0/256, cu: 32, mem: 4081Mb
[20:59:32] Uptime: 0 days 00:00:59
[20:59:32] GPU #1[T:0C F:0%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[20:59:32] GPU #2[T:0C F:0%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[20:59:32] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s

Might be, only have this GPU in this system, so device reset might not be usable, but could work for multi-gpu system.
I know driver reset are finicky and best avoided on RX VEGA though, bad recovery rate. Risk of instability causing crashes if you try to many times. Not the best auto-recovery in general.

I just expect this to be a feature of the code, I've noted and seen unexpected oddities from code structures when I was messing with that stuff years back. Simple changes could have drastic behaviour changes, even though it should make no difference.
I expect that maybe some resource is not released and kept reserved for the application upon closing. just a guess but worth to try and check.

This one is really odd. Did you try to reset(disable-enable device in Windows) Vega after wildrig session? When cryptonight was popular, people were doing so to get "fresh" hashrate, so maybe something similar happens here. Wildrig do nothing itself to modify anything related to gpu.

Thanks for the information.
This bug, known behaviour makes you not want to use the particular algorithm on this GPU. [RX VEGA 64]
To large a loss of hashrate.
_____________________________

I've noted another oddity when exiting and running WildRig application, the hashrate decreases if you exit WildRig and run another application.
You need a system reboot to restore performance after having had WildRig running.
Seems to lower gpu performance if you exit and want to run another application.

Noticed when I ran another mining software when I wasn't getting the usual hashrate and investigated.
If I don't run WildRig performance is normal, but as soon as I've had it run, performance is lowered afterwards. Can't find the cause other than the application doesn't exit/close properly? Keeps hogging system resources?
Known issue?

For example ethash has a decrease from 43mh/s down to 36mh/s after using WildRig. Doesn't occur if I don't run the application. (system reboot restores performance)
Any suggestions, comments on this behaviour?

WildRig itself also has decreasing performance for each exit/close and new start. But not as noticeable at first, until you only run it once per system start where you get the best performance. If you close the application it's for me recommended to restart the system if I want to run another algorithm, otherwise I can't get the best results from it.

Hi, unfortunately this is known issue for Vega gpu's(something to do with broken OpenCL compiler in drivers, and this need some tricks in code to make drivers provide correct binary). So far only kernel 1 works fine, but with lower hashrate. And this issue in my TODO list.

Well, I'm not a Linux guy, sorry, can't help here. But I believe it should be the same way as running any other app at start, but maybe with some scenario like "run terminal and execute app in it". Try to google something like this.

@andrucrypt, Hello. Please advise how to autostart the miner on ubuntu 18 boot? Tried creating a new service but the miner does not start unlike other miners. All I have is a miner start script in my task manager though mining will not start. Manual start is fine.

Getting some trouble using the kowpow algorithm on a RX VEGA 64.

On occasion of variance, the [kernel 2 compiled for gfx901] results in corrupt shares afterwards untill it does a new kernel compile.

It's seemingly random at the moment and I've tried voltage, clock adjustment on the gpu/vmem to help, keeps happening on stock or changed variables.



Any knowledge on why it does a bad [kernel 2 compiled]?

hi, I will take a look, but can't promise anything.

@andrucrypt, hi, any plans for Vertcoin hardfork and algo changing?