search

miniZ-miner / miniZ

37 stars 1 forks source link

progpowz algo not detected, miniZ tries to mine kawpow #26

Open PSLLSP opened 1 year ago

PSLLSP commented 1 year ago

miniZ 2.2c, Linux

MiningRigRenatls connects to progpowz at Zergpool. miniZ detects it as MEWC and starts to mine kawpow, and it crashes after a few seconds. Another exmaple that autodectection doesn't work.

./miniZ --par=progpowz --smart-pers --server=eu-de01.miningrigrentals.com:3344 --user droidMiner.295700 --pass=miniZ --ocX --show-pers
************ miniZ v2.2c ************
[INFO   ] ProgPoW does not need --ocX
Number of miniZ CUDA>=[.] using driver CUDA[11.40] devices found: 1
Driver:         470.18
Algo:           EQ[progpowz] [smart-pers]
Pool#0:         user[droidMiner.295700]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[MEWC]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 1.00%
[ERROR  ] Invalid job params rvn[5]
miniZ<progpowz>[00:0:00.0: 1860]: Selecting GPU#0[0] ASUS GeForce GTX 750 Ti
[INFO   ] GPU[00]: Generating DAG #0 [1023+15=1039MB]
[ 0d 0h 0m30s] 0>GTX 750 Ti ` 100% [72°C/48%]  0.00(0.00)H/s  36( 35.6)W clk=1176MHz mclk=2700MHz H/W=0.000 [MEWC]
[ 0d 0h 0m40s] 0>GTX 750 Ti ` 100% [71°C/48%]  0.00(0.00)H/s  35( 35.4)W clk=1176MHz mclk=2700MHz H/W=0.000 [MEWC]
[INFO   ] GPU[00]: Generated DAG in 21.51 s
[ERROR  ] GPU[00]: Cannot launch program 0: 27,256,70F81B4E
[FATAL  ] GPU[00] CUDA API error 400 from <progpow>, line 919 - check your OC settings.
[INFO   ] QUIT miniZ
Segmentation fault (core dumped)

I tried to force miniZ to ZANO with --pers ZANO but this doesn't help:

************ miniZ v2.2c ************
[INFO   ] ProgPoW does not need --ocX
Number of miniZ CUDA>=[.] using driver CUDA[11.40] devices found: 1
Driver:         470.18
Algo:           EQ[progpowz] [smart-pers]
Pool#0:         user[droidMiner.295700]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[ZANO]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 1.00%
[ 0d 0h 0m30s] [ZANO]
[ 0d 0h 0m40s] [ZANO]
[FATAL  ] No devices selected, exiting...
[INFO   ] QUIT miniZ

T-Rex or WildRig-multi miners could be used to verified that MRR configuration is correct and ZANO coin can be mined...

miniZ-miner commented 1 year ago

Hi PSLLSP, thanks for the message. If you add --worker WorkerName to your command line it should work well. miniZ is not recognizing the entire 'droidMiner.295700' as username (breaks at the '.', as user.worker). But if you use the option--worker it will work fine. We'll try to make the miner a bit more 'inteligent' for the next release. Let us know if this helps. Cheers

PSLLSP commented 1 year ago

droidMiner.295700 is username, it cannot be split to two parts. 295700 in this case is not rigname... MRR uses password field for rigname (WorkerName); password could be "x" too...

When I use --worker it doesn't work, I still see that miniZ tries to mine RVN (or kawpow). I tried this:

$ ./miniZ --par=progpowz --smart-pers --server=eu-de01.miningrigrentals.com:3344 --user droidMiner --worker=295700 --pass=miniZ --ocX --show-pers

************ miniZ v2.2c ************
[INFO   ] ProgPoW does not need --ocX
Number of miniZ CUDA>=[.] using driver CUDA[11.40] devices found: 1
Driver:         470.18
Algo:           EQ[progpowz] [smart-pers]
Pool#0:         user[droidMiner.295700]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[MEWC]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 1.00%
[ERROR  ] Invalid job params rvn[5]
miniZ<progpowz>[00:0:00.0: 1594]: Selecting GPU#0[0] ASUS GeForce GTX 750 Ti
[INFO   ] GPU[00]: Generating DAG #0 [1023+15=1039MB]
[ 0d 0h 0m30s] 0>GTX 750 Ti ` 100% [NA°C/NA%]  0.00(0.00)H/s   0(  0.0)W clk=0MHz mclk=0MHz H/W=-nan [MEWC]
[ 0d 0h 0m40s] 0>GTX 750 Ti ` 100% [70°C/47%]  0.00(0.00)H/s  31( 31.3)W clk=1176MHz mclk=2700MHz H/W=0.000 [MEWC]
[ERROR  ] Invalid job params rvn[5]
...

When I keep username as "droidMiner.295700" and workername as "MINIZ", it doesn't work:

$ ./miniZ --par=progpowz --smart-pers --server=eu-de01.miningrigrentals.com:3344 --user droidMiner.295700 --worker=MINIZ --pass=miniZ --ocX --show-pers

************ miniZ v2.2c ************
[INFO   ] ProgPoW does not need --ocX
Number of miniZ CUDA>=[.] using driver CUDA[11.40] devices found: 1
Driver:         470.18
Algo:           EQ[progpowz] [smart-pers]
Pool#0:         user[droidMiner.295700.MINIZ]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[MEWC]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 1.00%
[ 0d 0h 0m30s] [MEWC]
[ 0d 0h 0m40s] [MEWC]
[FATAL  ] No devices selected, exiting...
[INFO   ] QUIT miniZ

I assume that --worker parameter is not an issue, it is not needed. I use miniZ to mine in MRR and it is not problem with other coins (like kawpow) that is documented in other issue.

There could be compatibility issue, that miniZ is not compatible with MRR for propowz algo. I already found that I cannot use miniZ to mine RTH in MRR because it is not compatible, I have to use bzminer (and only this one...) to mine RTH in MRR, because only bzminer was tested with MRR and MRR pool was tuned for this miner...

Run with --protocol-dump:

$ ./miniZ --par=progpowz --smart-pers --server=eu-de01.miningrigrentals.com:3344 --user droidMiner.295700 --pass=miniZ --ocX --show-pers --protocol-dump

************ miniZ v2.2c ************
[INFO   ] ProgPoW does not need --ocX
Number of miniZ CUDA>=[.] using driver CUDA[11.40] devices found: 1
Driver:         470.18
Algo:           EQ[progpowz] [smart-pers]
Pool#0:         user[droidMiner.295700]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[MEWC]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 1.00%
[TRACE  ] <<00:18:01 [eu-de01.miningrigrentals.com] RECONNECT[0]!
[TRACE  ] >>00:18:01 [eu-de01.miningrigrentals.com] {"id":1,"method":"mining.subscribe","params":["miniZ/2.2c", null,"eu-de01.miningrigrentals.com","3344"]}

[TRACE  ] <<00:18:01 [eu-de01.miningrigrentals.com] {"jsonrpc":"2.0","id":1,"result":true}
[TRACE  ] >>00:18:01 [eu-de01.miningrigrentals.com] {"id":2,"method":"mining.authorize","params":["droidMiner.295700","miniZ"]}

[TRACE  ] <<00:18:02 [eu-de01.miningrigrentals.com] {"jsonrpc":"2.0","result":true,"id":2}
[TRACE  ] >>00:18:02 [eu-de01.miningrigrentals.com] {"id":3,"method":"mining.extranonce.subscribe","params":[]}

[TRACE  ] <<00:18:02 [eu-de01.miningrigrentals.com] {"jsonrpc":"2.0","id":3,"result":true}
[ 0d 0h 0m30s] [MEWC]
[ 0d 0h 0m40s] [MEWC]
[FATAL  ] No devices selected, exiting...
[INFO   ] QUIT miniZ
[INFO   ] Monitor exited.

I cannot see any information in the "protocol" that algo is progpowz, so miniZ has to guess algo and it fails. Well, algo progpowz was passed as parameter to miniZ, there is no need to guess it...

miniZ-miner commented 1 year ago

Hi PSLLSP, You need add--worker WorkerName to your command line, and still need to use --par progpowz --pers zano.

The following should work ok: ./miniZ --server=eu-de01.miningrigrentals.com:3344 --user droidMiner.295700 --worker WorkerName --pass=miniZ --par=progpowz --pers zano --show-pers

We just cleaned a bit the command line - progPoW does not need --ocX, and --smart-pers doesn't work in this particular case.

We'll try to make it easier to use, in MRR in the next release. Let us know if this helps. Cheers

PSLLSP commented 1 year ago

I confirm that your configuration with "useless" --worker parameter works. It is strange, this is the first algo that requires --worker parameter to mine in MRR; miniZ can mine other algo without it...