Setting up Baikal BK X with Awesome Miner

[Cryptostevo]

I have some Baikal BK X units I am setting up through awesome miner. When I input the mining pool information directly onto the miner's dashboard (under the Miner tab through IP address) the miner works great and mining pools accept the shares. When I input that same data through awesome miner and tell the same Baikal BK X to mine to that mining pool, it has an 85%+ shares rejected rate. Tried adding /#xnsub, tried removing and adding the stratum+tcp:// at the beginning and still get the same result. After I restart and it goes back to the mining pools I saved on the Baikal's dashboard it starts working again just fine, so there is something that awesome miner is doing to the pool URL, or other programming that is making the pools then reject the shares. The pools I am using in awesome miner are:

Nicehash:
stratum+tcp://quark.usa.nicehash.com:3345
stratum+tcp://qubit.usa.nicehash.com:3344
stratum+tcp://nist5.usa.nicehash.com:3340
stratum+tcp://x11gost.usa.nicehash.com:3359

Mining Pool Hub:
stratum+tcp://hub.miningpoolhub.com:12007
stratum+tcp://hub.miningpoolhub.com:12014
stratum+tcp://hub.miningpoolhub.com:12015
stratum+tcp://hub.miningpoolhub.com:12005
stratum+tcp://hub.miningpoolhub.com:12016

Also using Zpool

Any help is appreciated!

[1713899890]

1713899890

[1713899890]

1713899890

[1713899890]

1713899890

[1713899890]

1713899890

[1713899890]

1713899890

[1713899890]

1713899890

[TheRealCashen]

Code:

{
    "api-port": "4028",
    "api-allow": "W:127.0.0.1,W:192.168.0.0/16",
    "baikal-fan": "50",
    "pools": [
                {	"algo": "quark",	"user": "BTC ADRESS",	"pass": "d=64",	"extranonce": "true",	"priority": "1",	"url": "stratum+tcp://quark.usa.nicehash.com:3345"	},
		{	"algo": "qubit",	"user": "BTC ADRESS",	"pass": "d=64",	"extranonce": "true",	"priority": "1",	"url": "stratum+tcp://qubit.usa.nicehash.com:3344"	},
		{	"algo": "nist5",	"user": "BTC ADRESS",	"pass": "d=64",	"extranonce": "true",	"priority": "1",	"url": "stratum+tcp://nist5.usa.nicehash.com:3340"	},
		{	"algo": "x11gost",	"user": "BTC ADRESS",	"pass": "d=64",	"extranonce": "true",	"priority": "1",	"url": "stratum+tcp://x11gost.usa.nicehash.com:3359"	}
    ]
}

[Cryptostevo]

Thanks!

When I edit the mining pools in the IP dashboard they work just fine. When I add a mining pool into Awesome Miner and then change the mining pool for the Baikal BK X via awesomeminer the mining pool info seems to all be correct, but the BK X then processes the wrong algorithm.

For example for quark zpool mining pool when initiated through awesomeminer, the BK X processes X11 instead. I can't figure out how to change or fix it.

[brian717]

Have you tried adding the pools that awesome miner uses in the web interface first? It seems to work if the pool URL entered via the web interface matches what awesome miner is setting exactly.

[TheRealCashen]

You cannot force a pool using AM, at least I could never figure it out.

If you want AM to switch pools / algos I found they have to be on the machine already.

Easiest way to way to edit file is used notepad++ and then use th Baikal Monitor to "change pool" and select the miner file.

[Cryptostevo]

Thanks!
So I went back to the Baikal IP dashboard, deleted all the mining pools, and added the pools I wanted. They work fine on the Baikal unit. Then I went to awesome miner and added the same info on there. When I try to re-prioritize the pools in AM, it works (kind of), then the miner will process the new pool BUT with the incorrect algorithm. For example I made a Nist5 pool the top priority, the miner switched to that pool, and then starting mining on that pool, but was mining as if it was a Quark algo.