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

ma smaraju me na discordu ti za to i ne znas 

pa nemres na svaku primjedbu reagirat micanjem neceg iz statistike minera. covjel ne napisao 3 posta do sada i to je tebe jako uzrujalo

Nista, vraticu onako kao sto je bilo u 174, s tim da necu prikazati da li je share stale ili ne, posto vidim da stale shareovi uzrujavaju ljude  

Thanks for 1.7.5. Worker statistic works great! STALE and DUPLICATE shares stopped coming, but pool hashrate lower than the LOUD-miner, despite the fact that SRB shows a large local hashrate.
I think there is still something to work on. In the meantime, I prefer LOUD-miner.

I have a program that has all the listed CN-Algos you support that it switches between. Within that program I have it call the config file with my threads/intensity/etc and my pools... When that program launches say, CN8, it creates its own batch file on the fly.

za doktor83

V 1.7.4

http://www.anyg.rs/174.jpg


v 1.7.5

http://www.anyg.rs/175.jpg


levo u konzoli je pool log

http://www.anyg.rs/rig1.jpg

posalji mi jedino .srb fajl za vega 64 ili mogu da ti dam pristup nekom od rigova i pristup pool-u pa proveri, u sustini 1.7.4 radi extra jedini problem worker

Driver 18.6.1

nemoj da gledas verziju 1.7.6, sve je isto kao 1.7.5

try with --disablegpuwatchdog (disable gpu crash detection watchdog) in start.bat

Does anyone know how to disable miner restart?

If any GPU crashes, miner automatically will restart itself, this makes it hard to catch problems with GPUs when tuning settings.

I would like to know to disable restart and just have miner close itself or exit out when one of the GPUs crash.

Thanks in advance.

jedino drajveri ako nisu u redu, koristim Win10-64Bit-Radeon-Software-Adrenalin-Edition-18.6.1-June13, do sada radilo na svemu, "alternativni" miner za webchain radi bez problema, srb V8 takodje radi extra
proveri kako se ponasa na oficijalnom pool-u pool.webchain.network:3333


http://www.anyg.rs/rig.jpg

rig-1, rig-2  5x rx470 miner prijavljuje oko 4kh po rig-u
rig-0,rig-3,rig-4 5x rx570 miner prijavljuje oko 5kh po rig-u
rig-5,rig-6,rig-7,rig8  8x vega64 miner prijavljuje oko 16.5kh po rig-u
rig 9 4x vega 64 miner prijavljuje oko 8kh po rig-u
rig10 7x rx580 miner prijavljuje oko 6.7kh

ne promalazi i ne salje share, testirao sam na vise pulova, dok 1.7.4 sem worker-a i stale share nema zamerke, stale share moze da se podesi na pool-u da ne kida miner, nego samo da odbije share, u sustini, treba samo json da se promeni
za login: json_send: {"id":1,"jsonrpc": "2.0","method":"login","worker":"SRB","params":{"login":"","pass":"x","agent":"SRBMiner Cryptonight AMD GPU miner/1.7.5"}}
za send share: json_send: {"id":1,"jsonrpc":"2.0","method":"submit","worker":"SRB","params":{"id":"0","job_id":"e676425e98f96eca13f840ca257ea73e","nonce":"0e0200a0bd010000","result":"0000405e8de648cb84562234d61b39c1771edaa54759030c819a58dd87f23fda"}}

Hi Dok,

This time was the gpu 8, but sometimes is gpu1, when appear in log.
And sometimes , i dont have nothing in log, and all the system is freeeze.
Yes only for my vega rig and for version superior to 1.7.0.
I tested and work for days this version   -> here my log of 3 days for example:  https://justpaste.it/7qdkn

This problem occur only in my vega rig in my rx580 is all good. I have 2 indivudual pcs, and last version with only one vega seems to work good until today. Probably in multi-vega-gpu have some kind of problem in last version.  

Thanks

It looks to me that GPU8 killed/restarted the video driver, that's why all the others stopped hashing.
Interesting that users report this only on Vegas.

I will check what changed after 1.7.0 that could cause this.
Are you sure 1.7.0 still works ok for you ?
Can you test it a day or two ?

Also im curious, can you try out --gpuwatchdogdisablemode on 1.7.5 ?

Describe 'not ok'

Same problem here. exactly. Sometimes some card have 0 hash/s or all together. And now one have a strange pump in hashes. Tried to lower clocks an d increase all mv and intensity and same problem.

Check this dok:

[2018-12-30 14:32:17] hashrate: GPU0: 1752 H/s [T:54c][BUS:29]
[2018-12-30 14:32:17] hashrate: GPU1: 1774 H/s [T:54c][BUS:32]
[2018-12-30 14:32:17] hashrate: GPU2: 1778 H/s [T:54c][BUS:26]
[2018-12-30 14:32:17] hashrate: GPU3: 1770 H/s [T:47c][BUS:12]
[2018-12-30 14:32:17] hashrate: GPU4: 1734 H/s [T:54c][BUS:3]
[2018-12-30 14:32:17] hashrate: GPU5: 1769 H/s [T:54c][BUS:6]
[2018-12-30 14:32:17] hashrate: GPU6: 1766 H/s [T:54c][BUS:18]
[2018-12-30 14:32:17] hashrate: GPU7: 1770 H/s [T:55c][BUS:23]
[2018-12-30 14:32:17] hashrate: GPU8: 1949 H/s [T:53c][BUS:9]
[2018-12-30 14:32:17] hashrate: Total: 16062 H/s
[2018-12-30 14:32:28] miner_result: Sending user result to pool
[2018-12-30 14:32:28] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"662863462746484","job_id":"426769207075645","nonce":"4ebd8e63","result":"13f2f7ccdf1fed3ae46fece860886d864388a6177e2bf998136e9537d4070000"}}
[2018-12-30 14:32:28] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-12-30 14:32:28] miner_result: Pool accepted result 0x000007D4
[2018-12-30 14:33:04] miner_result: Sending user result to pool
[2018-12-30 14:33:04] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"662863462746484","job_id":"426769207075645","nonce":"b1dd398e","result":"5d5e2db0b56fb9057dbc809eb1fdca6253d5c8bc37e7d1b2ead7d1204a050000"}}
[2018-12-30 14:33:04] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-12-30 14:33:04] miner_result: Pool accepted result 0x0000054A
[2018-12-30 14:34:17] hashrate: GPU0: 1751 H/s [T:55c][BUS:29]
[2018-12-30 14:34:17] hashrate: GPU1: 1774 H/s [T:55c][BUS:32]
[2018-12-30 14:34:17] hashrate: GPU2: 1778 H/s [T:54c][BUS:26]
[2018-12-30 14:34:17] hashrate: GPU3: 1770 H/s [T:47c][BUS:12]
[2018-12-30 14:34:17] hashrate: GPU4: 1734 H/s [T:55c][BUS:3]
[2018-12-30 14:34:17] hashrate: GPU5: 1768 H/s [T:54c][BUS:6]
[2018-12-30 14:34:17] hashrate: GPU6: 1766 H/s [T:54c][BUS:18]
[2018-12-30 14:34:17] hashrate: GPU7: 1770 H/s [T:54c][BUS:23]
[2018-12-30 14:34:17] hashrate: GPU8: 1092 H/s [T:54c][BUS:9]
[2018-12-30 14:34:17] hashrate: Total: 15203 H/s
[2018-12-30 14:34:27] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0505f3aea3e10597f109ce1b467661284633cfba9922cbdfea25ea1acce6a87ec8b63146a386bf0 000000053294ec0c8d92887bd6f6d4e4cf9686a31ebab0e8327c9521d0886fb007c51490b","job_id":"309129661896354","target":"2f0b0000"}}
[2018-12-30 14:35:12] watchdog: GPU0 [BUS: 29] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU1 [BUS: 32] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU2 [BUS: 26] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU3 [BUS: 12] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU4 [BUS: 3] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU6 [BUS: 18] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU7 [BUS: 23] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU8 [BUS: 9] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU0 [BUS: 29] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU1 [BUS: 32] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU2 [BUS: 26] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU3 [BUS: 12] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU4 [BUS: 3] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU6 [BUS: 18] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU7 [BUS: 23] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU8 [BUS: 9] hashing speed is 0 H/S
[2018-12-30 14:35:34] Starting reboot script reboot-windows.bat...

Sometimes when restart its ok, but when freezes i have to locally restart the rig..

In v 1.7.0 its ok.

Dok see what i highlight in bold in the log. Its strange.
Gpu 8 jump to 1949 h/S, almost impossible in my vega 64 mining bittube.

Regards

tried srbminer 1.7.5 webchain on  
rx470 work ok
rx570 work ok
rx580 work ok
vega 64 not ok

tried srbminer 1.7.4 webchain on  
rx470 work ok (pool reject stale, no worker id)
rx570 work ok (pool reject stale, no worker id)
rx580 work ok (pool reject stale, no worker id)
vega 64 work ok (pool reject stale, no worker id)

Right, webchain implementation screwed the benchmarking..
Will be fixed.

We know, basically was a cpu coin. But there pool is ok, not restarting gpus or rig.