Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 243. (Read 237247 times)

Added a link in TIPS section on first page

Thanks for the tool 

np.

my 6*vega56 nitro+ GPUz not work with any version srbminer(i not try with cast or xmrstack). i try HWinfo but not work with srbminer. when i start  gpuz+miner = BLOCK.

gpuz and hwinfo work fine solo.

3*vega56 powercolor gpuz work finwe with all version srbminer

@livada please don't overquote too much, it's hard to read...
I have two rigs: 8xVega64 and 4xVega56, both dig CNv7 with weeks of stable uptime. I interrupt it only for miner updates. I guess running GPU-Z makes problems, not the miner itself.

I've made it recently
https://bitcointalksearch.org/topic/clayconn-using-srbminer-rigs-with-claymores-manager-4324950
Somebody please report if you like it. It will not format your drive, I promise )

version is last SRBMiner-CN-V1-5-8

watchdog disabled.

mine rwork 10 hour before this
work in 06:13:26
and not see any work 1 hour ? hmmm
no bad shaer not any stats 1 hour
and in 07:25 miner go conect on devpool. hmmmmm
work and go back to mine and dont again any stats 1,5 hour.

if pool not work miner must say  any?

FILE .srb. I have -srb 30 file in srbminer directori and this is not good. i dotn wont see this in my work directory. last version have 1 file now i see 30 .srb file.  in this folder i have 30.bat file. 50 .config filer . 50 pool file. and all .srb file is GARBAGE for me in this folder

Other miners have their own pools, where they do the devfee mining, but it would be too much to maintain those pools + work on the miner + work my 8-16h time job.
I have an idea how will i manage this without making own pools.

Regarding the stability thing, are you sure its related only to 1.5.8 ? There really isn't anything 'new' in that version that could cause GPU-Z crashing.

If some of you have older versions working better than the latest, i willl re-compile them all with the new devfee pool for heavy, and re-upload to mega.

Thanks for your support guys 

Version of miner?

From 1.5.5.1 there is a job_timeout parameter set to default of 15 minutes.
When no new job is received for 15 minutes it reconnects to your pool.

On your screenshot miner is not stuck AFTER the devfee, but BEFORE, there was a big pause before the devfee, which to admit looks interesting because miner did not freeze.
Logs of this would be interesting to see.

Also those file are not garbage, they are cached files, meant to speed up the compile process.

From the logs i can see that this isn't probably related to devfee-user pool switching, because after the devfee finished, you got jobs and accepted results from your pool, so the switchback was successful.

[2018-06-03 03:09:20] switch_pool: Disconnected from devfee pool, now mining for user
[2018-06-03 03:10:26] hashrate: GPU0: 964 H/S [BUS:5]
[2018-06-03 03:10:26] hashrate: GPU1: 1013 H/S [BUS:6]
[2018-06-03 03:10:26] hashrate: GPU2: 1017 H/S [BUS:2]
[2018-06-03 03:10:26] hashrate: GPU3: 964 H/S [BUS:4]
[2018-06-03 03:10:26] hashrate: GPU4: 952 H/S [BUS:1]
[2018-06-03 03:10:26] hashrate: Total: 4910 H/S
[2018-06-03 03:10:59] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"010193e4ccd805375fd1190a992e2b57929b47ae079a998a31bc7e1c11111a5a43e932b87519c20 0000000e510944a66dda1a13a8c31101b4cd678c25c109320e76a7936b82ff0fc10938201","job_id":"436392239714041","target":"d96f0000"}}
[2018-06-03 03:10:59] pool_have_job: Pool sent a new job (ID: 436392239714041)
[2018-06-03 03:11:09] miner_result: Sending user result to pool
[2018-06-03 03:11:09] json_send: {"method":"submit","params":{"id":"316536043444648","job_id":"436392239714041","nonce":"964033b3","result":"23e46068b4c15131a3d638b862f4988b4f810f82aa7b46a2d4cf0a91360b0000"},"id":1}
[2018-06-03 03:11:09] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-06-03 03:11:09] miner_result: Pool accepted result 0x00000B36


also there are new jobs/accepted shares after this before the fun begins :

[2018-06-03 03:31:29] json_receive: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Unauthenticated"}}
[2018-06-03 03:31:29] miner_result: You are not authenticated to the pool
[2018-06-03 03:31:29] miner_result: Pool rejected result 0x00003690 (unauthenticated)
[2018-06-03 03:31:29] miner_result: Network error
[2018-06-03 03:31:29] miner_result: Network error

The 0 hashing speed in this case is normal, because the GPU's are not working on any job.
This looks like some kind of pool problem to me.

good solution.

Tonight miner block after devfee.. Computer work  but miner not. This is SS in 9:00 AM

https://image.prntscr.com/image/PLv-MTFATcK75lt_0_1E3g.jpg

ovo gore je super ideja jer eto nakon dizanja gpu-a je miner zapeo na toj prvoj kartici i to je bilo to. sat i pol nije radio samo je trosio struju.

i neznam sto je ovo jer toga prije niakd nije bilo i samo mi puni smecem komp:

https://image.prntscr.com/image/JaPFaoMLRkKfAi7L0_uWrw.jpg

Your proposal seems good. This is immune to any changes as the user will select the correct algo, however, for any given algo, the program must detect type of mined coin so it can provide the correct wallet address.

Btw, I lost stability. it crashed while I was firing up GPU-Z. I really don't have the time to dig this one up. Will see if the crash is related to GPU-Z fire up. Or maybe the faster setting began to push a GPU over the edge but the logs are not good enough to see what GPU stalled. Claymore logs revealed the GPU that hung pretty well even before a violent crash.

Edit: Brief look, system seems to work ok if I don't fire up GPU-Z, (working for 10 mins) but I lose a total of 800-1000 mH/s unfortunately, on 13 cards. Some run full speed and some run 100 mh/s slower.

finally i have got logs:

https://thumb.ibb.co/eTtANd/Screenshot_at_03_03_31_24.png
https://thumb.ibb.co/mu0qNd/Screenshot_at_03_03_32_40.png

LOGS - http://www.filedropper.com/log_9
 

Can you make the miner's API compatible with Claymore Remote Manager (Ethman)?

@doktor83 you could program devfee like Claymore did in his miners: he uses the same pool and coin as user set in config file, just changes a wallet for a while. At first user cannot cheat with devfee just banning your pool. Also there's no need to reload data to GPUs while changing pool and/or coin for devfee, so it should switch faster.

PS CNv7 became several hashes faster on Vegas with 1.5.8. Thanks for that

hello. what is your vega setup? i have 2 x vega 64 with samsung mem but my hash low- (1360-1410 h/s)
i use hellm register mod. 200w power down.
http://www.overclock.net/forum/67-amd-ati/1633446-preliminary-view-amd-vega-bios-26.html#post_26297003

vega 64 setup
p7 1430 - 1000mv
mem p3 1080 - 950mv

{ "id" : 3, "intensity" : 58, "worksize" : 8, "threads" : 2},

That is nice, i only changed a few unrolls in cl in previous version that boosted my 580 8g only about 0.2-0.3%, looks like vegas like that even more 

i forgot... now i turned it on

ADD  biger  HR

i test this: and this versio¸n  give 1,7% more HR for identical  setup adn identical power use.

1.53 vs 1.5.8 SRBminer
Vega 56/64bios -samsung mem
https://image.prntscr.com/image/LZ9-vXiESPiEgd4O9THbDg.jpg
https://image.prntscr.com/image/i4P8BLN5Sc_0va2jRPU06g.jpg

Vega 56 nitro+ /64bios -hynix mem
https://image.prntscr.com/image/xQUEF6YFTPmYWDEiQVQTkQ.jpg
https://image.prntscr.com/image/0_aGo4CGSdewHMGUlvRvnQ.jpg

GOOD JOB DOC

Version 1.5.6. Windows 1803 with 18.5.2 (18.5.1 same thing). Miner didn't release all video memory on closing miner. I use GPU-Z to see vmemory usage. On each RX 580 card after closing miner still exists used vmemory. And with every launch free amount of vmemory decreases. I don't know how, but after many-many launches, during mining GPU-Z shows 15-16Gb of used video memory on each card. But they have only 8Gb of it...
Pagefile usage grows with that too...

Thats definitely something wrong with SRB miner on last Windows version with last AMD drivers...
And still miner detects RX 580 cards as R9 200 series. I have 3rd connected card - R9 270X. Maybe thats the cause of wrong detection of 580?

i switch directly   .
thx.

Done.

Yup I was on 1.5.x earlier.