SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 47.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: BoozyTalking on September 15, 2020, 12:42:54 AM

Hi, Doktor. I change my miner algorithmes combination,
so i can't now provide you log for randomepic+randomsfx combination,
but i can provide you log for another problem.
Randomepic+yescryptr16, after 7-8 hours of working miner can no more
allocate large pages and start to use RAM:

Windows 10, ryzen 5 3600, 32 mb, 8GB RAM

RAM usage growing from 80MB after start miner to 900MB after 8 hours miner working.

Yes, that's something i got aware later, that's because on every algo switch it free's and re-allocates scratchpads. I will try to make it preserve previous allocations, after that the hugep issue should dissapear.

I can only reproduce the mem leak with Verushash (one i knew about before releasing) , tried combinations of multiple algorithms (epic+randomx, randomx+yespower2b, randomx+cryptonight etc..)on 3 different systems and have no mem leaks, and it sends shares normally even after days of running...

BoozyTalking

newbie

Activity: 315

Merit: 0

Hi, Doktor. I change my miner algorithmes combination,
so i can't now provide you log for randomepic+randomsfx combination,
but i can provide you log for another problem.
Randomepic+yescryptr16, after 7-8 hours of working miner can no more
allocate large pages and start to use RAM:

Code:

[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 4][H]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 0][H]
[2020-09-15 06:03:56] VM created [CPU worker 4]
[2020-09-15 06:03:56] VM created [CPU worker 0]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 8][H]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] VM created [CPU worker 8]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 3][H]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 5][H]
[2020-09-15 06:03:56] VM created [CPU worker 3]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] VM created [CPU worker 5]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 2][H]
[2020-09-15 06:03:56] VM created [CPU worker 2]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 7][H]
[2020-09-15 06:03:56] VM created [CPU worker 7]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 9][H]
[2020-09-15 06:03:56] VM created [CPU worker 9]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 6][H]
[2020-09-15 06:03:56] VM created [CPU worker 6]
[2020-09-15 06:03:56] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:03:56] Allocated scratchpad [CPU worker 1][H]
[2020-09-15 06:03:56] VM created [CPU worker 1]
[2020-09-15 06:04:10] json_receive[0][976]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",965134],["randomx",526057490],["progpow",1027014628278]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[606060,607060,[175,33,78,33,79,232,120,22,110,99,38,251,209,76,152,224,239,210,255,141,83,7,36,78,184,88,55,30,214,3,106,212]]],"height":606841,"job_id":0,"pre_pow":"00060000000000094279000000005f602f2d024805e150b0382a34daa840de89814221930f128addb39db2a6b55e7daee88bf1f70dbe867af51568fa137c5a6faa6cd4498581233d51e6f951a803323ba7f0530506e60eb0d4b670ac9238d7fd902b759bcaddf20069fec8ee35339efdf501d12861f8be4b13478e59259a669dd0a00c6843ee812552528ecaafef52b733d9e6f5c408b558e2ee37aa2e84334b828b39ff84508d13ff88e5d7053e3abb62253e646f2e6b789a76dfabbb811718a38540950f8c6a01f943c7faa578d9934a3b00000000001ca18c000000000013c70300000000000000040000000000002509e8010000005bd59257a0020000d5ba68aef7b2030495aef2c91e5d94fb8c820c","xn":"e8d7"}}
[2020-09-15 06:04:10] New job received [0], block height 606841[0]
[2020-09-15 06:04:15] json_receive[1][636]: {"id":null,"method":"mining.notify","params":["d001","f0439892b2a82271a5d928fdedb4de3ccc4e82b701e0d873d9459e1f95903fee","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d024c6204322f605f08fabe6d6d00000000000000000000000000000000000000000000000000000000000000000100000000000000","0f706f6f6c2e72706c616e742e78797a00000000020000000000000000266a24aa21a9ed9715576a2168c2cb1d2816eaa99d6d33a5b90a8823d3ab3507fa61858843d7a0d0e6ff02000000001976a91488d5378e77ed4b8c0d9c1ccf2ccfcdebfe49497288ac00000000",["9c7cbd9e71d60b4a426fe249f498e21583e131de9b23188c14997bd82b272d8e"],"20000000","1d12ddb5","5f602f32",true]}
[2020-09-15 06:04:15] New job received [d001], block height 25164[1]
[2020-09-15 06:04:20] json_receive[0][976]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"progpow","block_difficulty":[["cuckoo",965134],["randomx",532477335],["progpow",1027014628278]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[606060,607060,[175,33,78,33,79,232,120,22,110,99,38,251,209,76,152,224,239,210,255,141,83,7,36,78,184,88,55,30,214,3,106,212]]],"height":606842,"job_id":0,"pre_pow":"0006000000000009427a000000005f602f370c9b29077e6c40d7b780d237f153f7b730523ed4d5dc395a5cc82a06601ab96d49799212fadd0a6ab37d54d624cf31201c684901da44e8386402da296248e7fddc7d827c1b995b63c5511d5ba888a90c1a7b30467c3ff6f51ba5a04ee96bad6bcbc3498aaea73c617f76c3d28bd774b2070742defdf848960f6f98b87935ab8e146f73fc94105b2749e8a3317c37d132f1b68f236c5b5d9745ec39ad8da7668b3e646f2e6b789a76dfabbb811718a38540950f8c6a01f943c7faa578d9934a3b00000000001ca18f000000000013c70700000000000000040000000000002509ec010000005bd5a111ae020000d5ba886bed49030495afe1e7f5f14afb8d2e78","xn":"e8d7"}}
[2020-09-15 06:04:20] New job ignored [0], block height 606842[0]
[2020-09-15 06:04:20] Redirecting jobs from algorithm 1 to algorithm 0 workers
[2020-09-15 06:04:27] json_receive[0][976]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",965134],["randomx",532477335],["progpow",1020063000974]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[606060,607060,[175,33,78,33,79,232,120,22,110,99,38,251,209,76,152,224,239,210,255,141,83,7,36,78,184,88,55,30,214,3,106,212]]],"height":606843,"job_id":0,"pre_pow":"0006000000000009427b000000005f602f3ef730291be058ec41d2e28240debb0dc55b0eac830aa0337438d5438e64fc9ea2c8e84c7557fa82e31e2135f4d39f21ac60b97ea0ac2a681a8ad66154d70b97aa1da2cf9908d192738c3b825a3788c3ed3948384690c573e164b42f36d3a5e49d2159746c9c90f5b0bceffd91a10f9408ccdec2c5c4a42445a88be3888170598ca76f1566c97f09f371c36704e6bb1af0f8a6073bdd0eddbe8a6b41be621a91af3e646f2e6b789a76dfabbb811718a38540950f8c6a01f943c7faa578d9934a3b00000000001ca190000000000013c70800000000000000040000000000002509f0010000005bd5afcbbc020000d5baa828e2e0030495b0cf68741ad8fb71e3f5","xn":"e8d7"}}
[2020-09-15 06:04:27] New job received [0], block height 606843[0]
[2020-09-15 06:04:27] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 0][H]
[2020-09-15 06:04:27] VM created [CPU worker 0]
[2020-09-15 06:04:27] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 5][H]
[2020-09-15 06:04:27] VM created [CPU worker 5]
[2020-09-15 06:04:27] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 2][H]
[2020-09-15 06:04:27] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:04:27] VM created [CPU worker 2]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 8][H]
[2020-09-15 06:04:27] VM created [CPU worker 8]
[2020-09-15 06:04:27] Allocated 2048 kB in large-page memory[0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 1][H]
[2020-09-15 06:04:27] VM created [CPU worker 1]
[2020-09-15 06:04:27] Not enough free pages to allocate 2048 kB in large-page memory. Restarting the computer could help.[0]
[2020-09-15 06:04:27] Not enough free pages to allocate 2048 kB in large-page memory. Restarting the computer could help.[0]
[2020-09-15 06:04:27] Not enough free pages to allocate 2048 kB in large-page memory. Restarting the computer could help.[0]
[2020-09-15 06:04:27] Allocated memory [2048 kB][0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 3]
[2020-09-15 06:04:27] Allocated memory [2048 kB][0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 7]
[2020-09-15 06:04:27] VM created [CPU worker 3]
[2020-09-15 06:04:27] Allocated memory [2048 kB][0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 9]
[2020-09-15 06:04:27] VM created [CPU worker 7]
[2020-09-15 06:04:27] VM created [CPU worker 9]
[2020-09-15 06:04:27] Not enough free pages to allocate 2048 kB in large-page memory. Restarting the computer could help.[0]
[2020-09-15 06:04:27] Not enough free pages to allocate 2048 kB in large-page memory. Restarting the computer could help.[0]
[2020-09-15 06:04:27] Allocated memory [2048 kB][0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 4]
[2020-09-15 06:04:27] Allocated memory [2048 kB][0]
[2020-09-15 06:04:27] Allocated scratchpad [CPU worker 6]
[2020-09-15 06:04:27] VM created [CPU worker 4]
[2020-09-15 06:04:27] VM created [CPU worker 6]
[2020-09-15 06:04:31] json_send[0][246]: {"id":"134","jsonrpc":"2.0","method":"submit","params":{"height":606843,"job_id":0,"nonce":16778050706889414937,"pow":{"RandomX":[0,0,31,111,29,90,105,128,217,143,138,20,158,222,6,200,230,159,236,19,247,164,106,117,174,42,60,50,185,118,17,127]}}}
[2020-09-15 06:04:31] json_receive[0][73]: {"id":"134","jsonrpc":"2.0","method":"submit","result":"ok","error":null}
[2020-09-15 06:04:31] CPU result accepted [397ms][0]
[2020-09-15 06:04:55] json_receive[0][976]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",965134],["randomx",535737544],["progpow",1020063000974]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[606060,607060,[175,33,78,33,79,232,120,22,110,99,38,251,209,76,152,224,239,210,255,141,83,7,36,78,184,88,55,30,214,3,106,212]]],"height":606844,"job_id":0,"pre_pow":"0006000000000009427c000000005f602f59c01e92d5da62579bc10f8889e2914f5a98344b296b2ec6cb2264e7b060af91763adab790749a521738d2015eba70029dac252da5f66481d0aecaa8f37fcaeac8210f7639b1e55ed0baafc9b8dec062dfffaeace4bbc854bb42be5f4304d8e4465c0f1b36646a0827f329896c7739f708011c6bc2ccc8e4a1f9587515234de7b6d82863ab2aa00315c58bc1f0cd8dfc73db5c4f40cc7667dbf31d7414368739ae3e646f2e6b789a76dfabbb811718a38540950f8c6a01f943c7faa578d9934a3b00000000001ca192000000000013c70a00000000000000040000000000002509f4010000005bd5be85ca020000d5bac81797a8030495b1bce8f24466fb8e3eca","xn":"e8d7"}}
[2020-09-15 06:04:55] New job received [0], block height 606844[0]
[2020-09-15 06:05:10] json_receive[1][636]: {"id":null,"method":"mining.notify","params":["d002","f0439892b2a82271a5d928fdedb4de3ccc4e82b701e0d873d9459e1f95903fee","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d024c6204692f605f08fabe6d6d00000000000000000000000000000000000000000000000000000000000000000100000000000000","0f706f6f6c2e72706c616e742e78797a00000000020000000000000000266a24aa21a9ed9715576a2168c2cb1d2816eaa99d6d33a5b90a8823d3ab3507fa61858843d7a0d0e6ff02000000001976a91488d5378e77ed4b8c0d9c1ccf2ccfcdebfe49497288ac00000000",["9c7cbd9e71d60b4a426fe249f498e21583e131de9b23188c14997bd82b272d8e"],"20000000","1d12ddb5","5f602f69",true]}
[2020-09-15 06:05:10] New job received [d002], block height 25164[1]
[2020-09-15 06:05:24] json_receive[0][976]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",965134],["randomx",535737544],["progpow",1020063000974]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[606060,607060,[175,33,78,33,79,232,120,22,110,99,38,251,209,76,152,224,239,210,255,141,83,7,36,78,184,88,55,30,214,3,106,212]]],"height":606844,"job_id":1,"pre_pow":"0006000000000009427c000000005f602f77c01e92d5da62579bc10f8889e2914f5a98344b296b2ec6cb2264e7b060af91763adab790749a521738d2015eba70029dac252da5f66481d0aecaa8f37fcaeac8210f7639b1e55ed0baafc9b8dec062dfffaeace4bbc854bb42be5f4304d8e4465c0f1b36646a0827f329896c7739f708011c6bc2ccc8e4a1f9587515234de7b62f47d27b66cd7b41dc0db4b987bc9424de699c9110e176c0834a255bcd0ccb6c3e646f2e6b789a76dfabbb811718a38540950f8c6a01f943c7faa578d9934a3b00000000001ca192000000000013c70a00000000000000040000000000002509f4010000005bd5be85ca020000d5bac81797a8030495b1bce8f24466fb8e3eca","xn":"e8d7"}}
[2020-09-15 06:05:24] New job received [1], block height 606844[0]

Windows 10, ryzen 5 3600, 32 mb, 8GB RAM

RAM usage growing from 80MB after start miner to 900MB after 8 hours miner working.

BoozyTalking

newbie

Activity: 315

Merit: 0

Yes, crash is fixed.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: BoozyTalking on September 14, 2020, 12:53:22 AM

Hi, Doktor! I found some strange bug - after 5-8 hours of miner work
miner stop generate shares, but continue to load processor.
Looks like some kind of dev fee bug.
Next time i will try to provide a screenshot.
Algos: randomepic+randomsfx.

And looks like there is some memory leaks, coz miner start with using ~72 MB RAM,
and after few hours it take around 500 MB RAM.

I would like an extended log, a screenshot isn't too helpful. Please enable logging and add --extended-log flag.
Did i manage to fix the previous miner crash issue?

BoozyTalking

newbie

Activity: 315

Merit: 0

Hi, Doktor! I found some strange bug - after 5-8 hours of miner work
miner stop generate shares, but continue to load processor.
Looks like some kind of dev fee bug.
Next time i will try to provide a screenshot.
Algos: randomepic+randomsfx.

And looks like there is some memory leaks, coz miner start with using ~72 MB RAM,
and after few hours it take around 500 MB RAM.

BoozyTalking

newbie

Activity: 315

Merit: 0

Tellor can be mined for now only if you have 1000 tellor with deployed node. Can't be mined on pool right now, until tellor v.2. Google it.

Doktor, more then 12 hours without errors.

Btw on nvidia yescryptr16 gpu make much more hashes then cpu.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: antminerguruguy on September 09, 2020, 10:39:01 PM

Well why did you disable tellor so I cant gpu mine it, its even in your list am I know stupid enough to mine tellor?

it's not disabled.
But looks like tellorpool.org is dead.

antminerguruguy

newbie

Activity: 328

Merit: 0

Well why did you disable tellor so I cant gpu mine it, its even in your list am I know stupid enough to mine tellor?

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: antminerguruguy on September 09, 2020, 01:38:24 PM

I was wondering if anyone could help me configure SRB miner I am using Awesome Miner and it only cpu mines it never uses the GPU's I have 7 AMD GPUS 4/480 2/570 1/470 they are all 8 gb virtual memory is set to 16000 mb but I do have 32 Gb ram.... should I bump that up is that why it crashes sometimes?

As well how do I tell it to GPU mine with all the gpus I configured it and it just cpu mines I tried all the other dialogs with no luck.

Maybe someone that has done this with these cards and yescryptr16 could tell me how to I want to mine goldcash with it.

Hi, yescryptr16 isn't gpu mineable, that's why you can't mine it with GPU's

antminerguruguy

newbie

Activity: 328

Merit: 0

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: BoozyTalking on September 09, 2020, 05:45:53 AM

Then why miner must reconnect if it just need to be ignored (progpow/cuckoo)? Don't it just have to wait for RX job?
Ver. 0.4.7 don't have this problem.

Works same in v 0.4.7 btw. It is no difference for you if it reconnects or waits because it wouldnt mine RX anyways

But i will see what i can do.

BoozyTalking

newbie

Activity: 315

Merit: 0

Quote from: doktor83 on September 09, 2020, 05:29:27 AM

Quote from: BoozyTalking on September 09, 2020, 04:47:09 AM

Hi.

Quote

+ Added algorithm 'argon2id_chukwa'
+ Added algorithm 'argon2d_dynamic'

Is it for cpu only? If so then why? There is already exist gpu miners for these algo.
Better add progpow and nimiq.

And thank you for new version, i testing it right now.

Also:

Quote

Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect.

Don't you think better is to store first value of difficulty (when miner first connect to pool) and then miner receive Invalid difficulty - just use stored value instead of spent time for reconnecting? Or maybe add cmd line option for default difficalty?

Code:

[2020-09-09 12:59:49] PARSE error: Invalid difficulty received[0]
[2020-09-09 12:59:49] Redirecting jobs from algorithm 1 to algorithm 0 workers [a]
[2020-09-09 12:59:49] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:03] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:03] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:03] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:15] CPU result accepted [335ms][1]
[2020-09-09 13:00:18] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:18] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:18] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:22] CPU result accepted [488ms][1]
[2020-09-09 13:00:32] New job received [d630], block height 116005[1]
[2020-09-09 13:00:33] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:33] Difficulty 240000.00000000[0]

Too much reconnects.

Invalid difficulty is received when a progpow job is received, so why would i 'store first value of difficulty and use stored value', when it wont be mined at all ? It's not RX. Also you cant just cant use any diff you want when you want it, vardiff doesn't work that way.

Then why miner must reconnect if it just need to be ignored (progpow/cuckoo)? Don't it just have to wait for RX job?
Ver. 0.4.7 don't have this problem.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: BoozyTalking on September 09, 2020, 04:47:09 AM

Hi.

Quote

+ Added algorithm 'argon2id_chukwa'
+ Added algorithm 'argon2d_dynamic'

Is it for cpu only? If so then why? There is already exist gpu miners for these algo.
Better add progpow and nimiq.

And thank you for new version, i testing it right now.

Also:

Quote

Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect.

Don't you think better is to store first value of difficulty (when miner first connect to pool) and then miner receive Invalid difficulty - just use stored value instead of spent time for reconnecting? Or maybe add cmd line option for default difficalty?

Code:

[2020-09-09 12:59:49] PARSE error: Invalid difficulty received[0]
[2020-09-09 12:59:49] Redirecting jobs from algorithm 1 to algorithm 0 workers [a]
[2020-09-09 12:59:49] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:03] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:03] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:03] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:15] CPU result accepted [335ms][1]
[2020-09-09 13:00:18] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:18] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:18] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:22] CPU result accepted [488ms][1]
[2020-09-09 13:00:32] New job received [d630], block height 116005[1]
[2020-09-09 13:00:33] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:33] Difficulty 240000.00000000[0]

Too much reconnects.

Invalid difficulty is received when a progpow job is received, so why would i 'store first value of difficulty and use stored value', when it wont be mined at all ? It's not RX. Also you cant just cant use any diff you want when you want it, vardiff doesn't work that way.

BoozyTalking

newbie

Activity: 315

Merit: 0

And maybe more informative would be print algo name instead of algo (or just add algo name) number:

Code:

[2020-09-09 12:54:21] CPU result accepted [161ms][0] - [randomepic]

BoozyTalking

newbie

Activity: 315

Merit: 0

Hi.

Quote

+ Added algorithm 'argon2id_chukwa'
+ Added algorithm 'argon2d_dynamic'

Is it for cpu only? If so then why? There is already exist gpu miners for these algo.
Better add progpow and nimiq.

And thank you for new version, i testing it right now.

Also:

Quote

Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect.

Don't you think better is to store first value of difficulty (when miner first connect to pool) and then miner receive Invalid difficulty - just use stored value instead of spent time for reconnecting? Or maybe add cmd line option for default difficalty?

Code:

[2020-09-09 12:59:49] PARSE error: Invalid difficulty received[0]
[2020-09-09 12:59:49] Redirecting jobs from algorithm 1 to algorithm 0 workers [a]
[2020-09-09 12:59:49] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:03] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:03] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:03] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:15] CPU result accepted [335ms][1]
[2020-09-09 13:00:18] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:18] PARSE error: Invalid difficulty received[0]
[2020-09-09 13:00:18] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]
[2020-09-09 13:00:22] CPU result accepted [488ms][1]
[2020-09-09 13:00:32] New job received [d630], block height 116005[1]
[2020-09-09 13:00:33] Connected to epic.icemining.ca:4000[0]
[2020-09-09 13:00:33] Difficulty 240000.00000000[0]

Too much reconnects.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: BoozyTalking on September 09, 2020, 02:29:49 AM

Hi, Doktor. Your last cmd line option for exceptions help with miner crushes, but after 8-10 hours of mining miner just stop mining,
program continue to work, accept works from pools, but not generate hashes.

Try the latest 0.5.1 release, also without the cmd line option for exceptions, let's see if i managed to fix it.

doktor83

hero member

Activity: 2548

Merit: 626

V0.5.1

+ Added algorithm 'argon2id_chukwa'
+ Added algorithm 'argon2d_dynamic'
+ Added parameter '--miner-priority' to set priority of main miner process
+ Renamed '--cpu-priority' to '--cpu-threads-priority'
+ Faster hashrate refresh interval for CPU workers
+ Fixed (probably) crash when mining with 'randomepic' algorithm
+ Bug fixes

BoozyTalking

newbie

Activity: 315

Merit: 0

Hi, Doktor. Your last cmd line option for exceptions help with miner crushes, but after 8-10 hours of mining miner just stop mining,
program continue to work, accept works from pools, but not generate hashes.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: alucard20724 on September 08, 2020, 05:56:47 PM

Quote from: doktor83 on September 07, 2020, 01:49:59 AM

Quote from: alucard20724 on September 07, 2020, 12:12:35 AM

Quote from: doktor83 on September 06, 2020, 11:04:36 PM

Quote from: alucard20724 on September 06, 2020, 07:01:49 PM

Quote from: doktor83 on September 06, 2020, 07:43:20 AM

V0.5.0

You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful

I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back? it's just the "!" is non-standard and not used in any other miners... that i know of. the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated.
That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc..
Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others..

Hopefully software that uses SRB will adapt to the new format.

Never got an answer on whether you support all algos on Navi now.

Maybe you could try it ?

I compiled all algorithms except MTP for Navi, but i did not test because i dont have a card. You could try and report back.

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: doktor83 on September 07, 2020, 01:49:59 AM

Quote from: alucard20724 on September 07, 2020, 12:12:35 AM

Quote from: doktor83 on September 06, 2020, 11:04:36 PM

Quote from: alucard20724 on September 06, 2020, 07:01:49 PM

Quote from: doktor83 on September 06, 2020, 07:43:20 AM

V0.5.0

You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful

I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back? it's just the "!" is non-standard and not used in any other miners... that i know of. the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated.
That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc..
Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others..

Hopefully software that uses SRB will adapt to the new format.

Never got an answer on whether you support all algos on Navi now.

Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 47. (Read 44750 times)