nicehash / excavator

NiceHash's proprietary low-level CUDA miner
https://www.nicehash.com
53 stars 19 forks source link

1.6.8c API device.get output error #310

Closed EvgeniyKorepov closed 3 years ago

EvgeniyKorepov commented 3 years ago

Method device.get (and devices.get) returns error JSON in section gpu_memory_timings: Duplicate key 'DELAY0'

"timings": {
                "RC": 51,
                "RFC": 138,
                "RAS": 32,
                "RP": 19,
                "CL": 17,
                "WL": 7,
                "RD_RCD": 21,
                "WR_RCD": 15,
                "RPRE": 0,
                "WPRE": 0,
                "CDLR": 7,
                "WR": 20,
                "W2R_BUS": 5,
                "R2W_BUS": 5,
                "PDEX": 10,
                "PDEN2PDEX": 10,
                "FAW": 20,
                "AOND": 0,
                "CCDL": 2,
                "CCDS": 2,
                "REFRESH_LO": 2,
                "REFRESH": 6,
                "RRD": 6,
                "DELAY0": 44,
                "ADR_MIN": 2,
                "WRCRC": 10,
                "OFFSET0": 39,
                "DELAY0_MSB": 0,
                "OFFSET1": 7,
                "OFFSET2": 4,
                "DELAY0": 7,
                "DS_GDDR5": 0,
                "R2P": 1,
                "RDCRC": 1,
                "T22_RFCSBA": 257,
                "T22_RFCSBR": 64
            }

"DELAY0": 44 and "DELAY0": 7

Perhaps because of this, the setting of timings does not work via config:

[[2021-03-21 11:44:00.902427] [thread=0x00001a88] [info]]
    device #0 | No timings set, skipping

via API: http://192.168.0.10:38080/api?command={"id":999,"method":"device.set.memory.timings","params": ["GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9","MT0=16","MT1=4"]}

{"id":999,"error":"Failed to set memory timings."}

(device GTX 1080)

nicehashdev commented 3 years ago

Please, update to latest Excavator that you can get in this package: https://github.com/nicehash/NiceHashQuickMiner/releases/download/v0.4.2.1_RC/NiceHash_QuickMiner_v0.4.2.1_RC.zip

EvgeniyKorepov commented 3 years ago

v1.6.8d - Same. And API error and the setting of timings does not work

nicehashdev commented 3 years ago

Will be fixed in next ver.

nicehashdev commented 3 years ago

Should be fixed in latest 1.6.9a that comes with NHQM. Check it out.

EvgeniyKorepov commented 3 years ago

Output json correct

"timings": {
                "RC": 51,
                "RFC": 138,
                "RAS": 32,
                "RP": 19,
                "CL": 17,
                "WL": 7,
                "RD_RCD": 21,
                "WR_RCD": 15,
                "RPRE": 0,
                "WPRE": 0,
                "CDLR": 7,
                "WR": 20,
                "W2R_BUS": 5,
                "R2W_BUS": 5,
                "PDEX": 10,
                "PDEN2PDEX": 10,
                "FAW": 20,
                "AOND": 0,
                "CCDL": 2,
                "CCDS": 2,
                "REFRESH_LO": 2,
                "REFRESH": 6,
                "RRD": 6,
                "DELAY0": 44,
                "ADR_MIN": 2,
                "WRCRC": 10,
                "OFFSET0": 39,
                "DELAY0_MSB": 0,
                "OFFSET1": 7,
                "OFFSET2": 4,
                "DELAY01": 7
            }

But timings are not set:

[[2021-03-24 10:14:25.473963] [thread=0x0000047c] [info]]
    core | Initialized!
[[2021-03-24 10:14:25.475961] [thread=0x00001e0c] [info]]
    device #0 | No timings set, skipping
[[2021-03-24 10:14:25.475961] [thread=0x00001e0c] [trace]]
    Response: {"id":1,"error":"Failed to set memory timings."}

my config:

[
    {"time":0,"commands":[
        {"id":1,"method":"subscribe","params":["nhmp-ssl.eu-west.nicehash.com:443","382bkNMNYWRvWKMQ4K25XMraJcybRf8qsv$0--928brG09lOAQsoIRDSPWg"]}
    ]},
    {"time":1,"commands":[
        {"id":1,"method":"algorithm.add","params":["daggerhashimoto"]}
    ]},
    {"time":2,"commands":[
        {"id":3,"method":"worker.add","params":["daggerhashimoto","GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9"]}
    ]},
    {"time":1,"commands":[
        {"id":1,"method":"device.set.oc_profile","params":["GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9","0","650","135"]},
        {"id":1,"method":"workers.reset","params":["0"]}
    ]},
    {"time":15,"loop":10,"commands":[
        {"id":1,"method":"worker.print.efficiencies","params":[]},
        {"id":1,"method":"algorithm.print.speeds","params":[]},
        {"id":1,"method":"worker.reset","params":["0"]}
    ]},

    {"event":"on_quit","commands":[
        {"id":1,"method":"device.set.oc_profile","params":["GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9","0","0","160"]}
    ]}
]
EvgeniyKorepov commented 3 years ago

My mistake, this is not right: {"id":999,"method":"device.set.memory.timings","params": ["GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9","__MT0=16","__MT1=4"]}

That's right:: {"id": 1,"method":"device.set.memory.timings","params": ["GPU-39d6e841-c9d6-3807-ecf4-fa8cc8814be9","FAW=16","RRD=4"]}

GTX 1080 : core | Device #0-0 speed: 31.40 MH/s power: 131.26 W efficiency: 239.26 kH/J

nicehashdev commented 3 years ago

Yes, this was changed. Good :) Looks like issue solved then.