--pass=m=solo

[eltech35]

Can't solo mine using password "m=solo"

Tried --pass=m=solo --pass="m=solo" --pass='m=solo' --pass=m=solo same with -p always switched by -p x at runtime (looking with ps aux)

[rplant8]

-p m=solo

[eltech35]

tried that but "ps aux" tells me it's still replaced by -p x

[rplant8]

Are you running it through a script? You need to fix it in the script itself.

[eltech35]

yep, made a script, modified the script with -p m=solo, same issue, even running it direct from command line and ps aux from another term session, ps aux tells me it uses -p x Given my hashrate 22Khs, perhaps no point to solo mine but still... super weird.

[rplant8]

show sh file

[eltech35]

cat avian.sh ./cpuminer-ryzen -a minotaurx -o stratum+tcps://stratum-eu.rplant.xyz:17068 -u RSFSaAp4m4atajNRJV7WpJb5fCZxMqTJfM.m2051 -p m=solo --threads=30 --api-bind 127.0.0.1:4069

(./cpuminer-ryzen -V

built on Oct 6 2021 with GCC 9.3.0 features: x86_64 SSE2 AVX AVX2 XOP

libcurl/7.75.0 OpenSSL/1.1.1j zlib/1.2.11 c-ares/1.17.0 jansson/2.13.1 ) Ryzen 9 5950x

[rplant8]

the script is correct. look for where -p x comes from it looks like you're running a different script

[eltech35]

Very weird

Le 8 janv. 2022 à 16:49, rplant8 @.***> a écrit :

the script is correct. look for where -p x comes from it looks like you're running a different script

was more thinking to a bug in interpreting the m=solo due to unexpected special character = in the password field. Could affect only the cpuminer-ryzen version ?

[rplant8]

It's not a bug in the miner, you're calling it incorrectly somewhere

[eltech35]

After 24h, pool side, rig is showed with correct hashrate and immature/balance/shares to 0, so i came to the conclusion it is actually solo mining. Have to deduct when you "ps aux" from command line, the password p x showed in the process line is here to obfuscate the password...simply.

Would be cool if pool.rplant.xyz could implement an "S" or "SOLO" in Workers tab for workers detected mining solo.

Thanks for your help @rplant8