Quote from: sahbibenayed on December 29, 2018, 11:12:52 AM

Quote from: hobocoe on December 28, 2018, 04:49:22 PM

Quote from: sahbibenayed on December 28, 2018, 03:28:05 PM

Implemented dual mining (Ethash/Blake2s) for some AMD GPUs (RX580/570/560/480/470/460 and Vega). Use the new -dpool, -dwal, -dpass, -dworker, and -dcoin options to set the Blake2s pool. You can set the secondary coin mining intensity with the -sci option. For more information see the Readme.txt file. Note that the devfee when using dual mining is 0.9% on the ethash coin (there is no devfee on the secondary coin).

==>
Dual mining not working
I try everything but Nada

Chances are its a driver conflict. I just recently went through the last 15 or so driver releases trying to get a vega 56 working, and I also used some drivers on 470's and 480. From driver to driver the dual mining quits working. like for me the newest beta driver doesnt dual mine but the current stable does. mess with different drivers to get the dual mining working

I m using msos with Phoenix client (linux) :
my config :
-eworker RigRayan
-epool etc-eu1.nanopool.org:19999
-ewal 0x**.**
-epsw x
-dcoin blake2s
-dpool xvg.blake2s.com:8888
-dwal **
-dpass c=XVG
-proto (AUTO)
-clgreen 1
-mode 0
-tstop 85
-tt 60
-fanmin 50
-fanmax 100

any help please because with the same config it works on Claymore

ahh ya on my MSOS rigs I'm having the same issue and I think it has to do with the current stable build having an older driver. There was talk on their discord about implementing the newest stable linux driver that was just released, but they are worried about stability. Once enough feedback comes in from the community about its stability I think they were going to update the driver. and that may fix it. Ive even gone into the files and manually changed the config file to use dual mining and I can get it to initiate but it never hashes anything, much like my tests on windows that dual mining works driver by driver. Give it some time and Im sure it work, but for now they are actively "blocking" the dual mining info from being passed into the config file when you enter it on the web interface.