SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[Mashy81]

Hello,

I am looking for config for 7 RX580, currently I am getting "warning: Too many compute errors"
thx

Lower clocks

[sharix80]

Hello,

I am looking for config for 7 RX580, currently I am getting "warning: Too many compute errors"
thx

What algorithm do you use? When using the webchain, there are always a lot of mistakes and rejected shares.

[ganzocrypt]

I tried to reduce cc to 1150 mc 1950, got same errors
I am mining uplex algo.

also with another miner, clocks are ok at 1200 and 1950 with Vcc 940/900 with 800 Watts, getting around 21kh/s

so I wanted to test this miner to see if I can get more.

Strange thing is that one of the RX580 is a  4 Gb card, other 6 are 8Gb, and it's getting 3.3kh/s while the others are around 10% less.

[Kgonla]

I tried to reduce cc to 1150 mc 1950, got same errors
I am mining uplex algo.

also with another miner, clocks are ok at 1200 and 1950 with Vcc 940/900 with 800 Watts, getting around 21kh/s

so I wanted to test this miner to see if I can get more.

Strange thing is that one of the RX580 is a  4 Gb card, other 6 are 8Gb, and it's getting 3.3kh/s while the others are around 10% less.

I have something like you with V8.
I was using 1.7.0 working fine, after switching to 1.7.4-5 my RX 580 4GB is giving about 12 H/s more than before but full of compute errors.
The 8GB 580 are same hash rate & I think they work fine but not tested carefully.

Try to disable the 4GB card pressing the number where it is placed, if compute errors disappear it is a miner problem.
I don't know if 1.7.0 have the uplex algo, if it have try with this version.

Also I have better H/s with 4GB than with 8GB but it is a very old miner problem, I think is better optimized for 4GB cards.

[vgeorgiev]

DOC How to change UPX Intensity?

[Bllacky]

Feedback on
V. 1.7.5

Now it finally works when I have mix of 270X and 280X video cards.
Hashrates are very good for normal V8 algo:
280X 450 H/s
270X 345 H/s
290 530H/s

I do not OC.
I also sometimes get lots of STALE shares.

Good job!

[doktor83]

I tried to reduce cc to 1150 mc 1950, got same errors
I am mining uplex algo.

also with another miner, clocks are ok at 1200 and 1950 with Vcc 940/900 with 800 Watts, getting around 21kh/s

so I wanted to test this miner to see if I can get more.

Strange thing is that one of the RX580 is a  4 Gb card, other 6 are 8Gb, and it's getting 3.3kh/s while the others are around 10% less.

I have something like you with V8.
I was using 1.7.0 working fine, after switching to 1.7.4-5 my RX 580 4GB is giving about 12 H/s more than before but full of compute errors.
The 8GB 580 are same hash rate & I think they work fine but not tested carefully.

Try to disable the 4GB card pressing the number where it is placed, if compute errors disappear it is a miner problem.
I don't know if 1.7.0 have the uplex algo, if it have try with this version.

Also I have better H/s with 4GB than with 8GB but it is a very old miner problem, I think is better optimized for 4GB cards.

Just tested UPX on :
470 4g
570 4g
580 4g

Driver 18.6.1

Ran it for 30 minutes, no compute errors.


Also 3.3khs is low for 580 4gb, it should do 3.7khs without any crazy overclocking.

[doktor83]

Feedback on
V. 1.7.5

Now it finally works when I have mix of 270X and 280X video cards.
Hashrates are very good for normal V8 algo:
280X 450 H/s
270X 345 H/s
290 530H/s

I do not OC.
I also sometimes get lots of STALE shares.

Good job!

Awesome, thanks for reporting.
Also stales shown in miner are not a problem because those are accepted shares.
Its just more a 'cosmetical thing'.

[Turkish88]

who test webchain algo ?
What are the best intensity and worksize for Radeon RX550 series gpu ?

[lsHaKeRl]

Recommended drivers:
Adrenalin 18.6.1

Hello doctor!

First of all, I would like to express a big thank you for your effort and work on SRB Miner!
It's going really well, I've been working for a long time with SRB Miner and my Vega64 graphics cards, currently 12 pieces in number.

My question currently is, still working or is recommended at most the ADRENALIN driver 18.6.1 to use.

What about the newer drivers? Do these work? Or do you continue to work only on 18.6.1? Should we try it for ourselves?

The 2nd thing:

What bothers me a bit or is upset that with SRB 1.7.0 the power consumption of Vega64 cards was about ~ 185 watts per card!

With SRB 1.7.5. The consumption per card increased approximately to 203 watts / card. Could you perhaps also consider this or perhaps mention it in the information?

Because it brings nothing if graphics cards make 10-30 H / s more, but the power consumption increases every time!
This is not an optimization!

Personally, I am very surprised that nobody here talks about electricity consumption or reports or writes about it, because it´s a big thing for everyones MONEY!.

Here are the current values of my RIG with Vega64 to version 1.7.5 on V8(GRAFTCOIN) .:

[2019-01-04 19:09:05] GPU0 :    2073 H/s [T: 32c, RPM: 2410, CC: 1408 MHz, MC: 1100 MHz][BUS:28]
[2019-01-04 19:09:05] GPU1 :    2076 H/s [T: 30c, RPM: 2289, CC: 1408 MHz, MC: 1100 MHz][BUS:19]
[2019-01-04 19:09:05] GPU2 :    2076 H/s [T: 27c, RPM: 2380, CC: 1408 MHz, MC: 1100 MHz][BUS:37]
[2019-01-04 19:09:05] GPU3 :    2071 H/s [T: 35c, RPM: 3573, CC: 1408 MHz, MC: 1100 MHz][BUS:34]
[2019-01-04 19:09:05] GPU4 :    2069 H/s [T: 39c, RPM: 3677, CC: 1408 MHz, MC: 1100 MHz][BUS:9]
[2019-01-04 19:09:05] GPU5 :    2077 H/s [T: 32c, RPM: 2377, CC: 1408 MHz, MC: 1100 MHz][BUS:13]
[2019-01-04 19:09:05] GPU6 :    2072 H/s [T: 32c, RPM: 3536, CC: 1408 MHz, MC: 1100 MHz][BUS:31]
[2019-01-04 19:09:05] GPU7 :    2079 H/s [T: 34c, RPM: 2349, CC: 1408 MHz, MC: 1100 MHz][BUS:16]
[2019-01-04 19:09:05] GPU8 :    2069 H/s [T: 39c, RPM: 3603, CC: 1408 MHz, MC: 1100 MHz][BUS:25]
[2019-01-04 19:09:05] GPU9 :    2076 H/s [T: 34c, RPM: 2336, CC: 1408 MHz, MC: 1100 MHz][BUS:40]
[2019-01-04 19:09:05] GPU10:    2072 H/s [T: 32c, RPM: 2375, CC: 1408 MHz, MC: 1100 MHz][BUS:22]
[2019-01-04 19:09:05] GPU11:    2074 H/s [T: 25c, RPM: 2337, CC: 1408 MHz, MC: 1100 MHz][BUS:5]

[2019-01-04 19:09:05] Total:    24884 H/s

it runs stable!



best regards & big thanks!  
Patrick

[abg00]

who test webchain algo ?
What are the best intensity and worksize for Radeon RX550 series gpu ?

read two previous page. webchain work very poor

2 gb and 4 gb different setings

[doktor83]

V1.7.6
- New tuning parameter 'thread_delay', can be used in cmd (--cgputhreaddelay), config, gpu_conf
- Even faster kernel compilation
- Added HTML statistics page, can be accessed if API is enabled via /stats
- Added 3 new API parameters: --apirigrestarturl, --apirigshutdownurl, --apiminerrestarturl
- Added share 'trip' time from miner->pool->miner on share sending
- Added SSL in interactive configurator
- Removed --runbenchmark, --benchmarkduration parameters
- Fixed algo benchmarking
- Webchain sending stale shares again
- Startup monitor now restarts whole machine on fail, instead of miner
- Fixed a bug with shutdown temperature and false ADL temperature reporting


+ Oh, a new parameter that can impact your hashing speed : thread_delay (or --cgputhreaddelay in start.bat)
It's value goes from 1-1000. It is used only when 2 or more threads are used per SAME GPU.
Simply said, this value controls the timing between thread starting on the same gpu.
The default is 319, this is something i found acceptable across multiple gpu platforms.

+ Added a GUI statistics page, where you can see basic info about your mining session.

First you must enable API, by using the --apienable parameter in start.bat
Set your rig (computer) name with --apirigname myrigname also in start.bat

After you have started the miner, you can access the stats page in your browser :
http://127.0.0.1:21555/stats

There are also three other parameters that can help you to restart miner, reboot or shutdown your machine remotely :

--apirigrestarturl
This should be a unique string, which accessed in browser results in a computer restart. Miner needs to have admin privileges.

--apirigshutdownurl
This should be a unique string, which accessed in browser results in a computer shutdown. Miner needs to have admin privileges.

--apiminerrestarturl
This should be a unique string, which accessed in browser restart SRBMiner.



Example start.bat:
SRBMiner-CN.exe --config Config\config-normalv8.txt --pools Pools\pools-normalv8.txt --apienable --apirigrestarturl 12345fff --apirigshutdownurl 54321fff --apiminerrestarturl restart_my_srb

Visiting this url restarts your machine:
http://127.0.0.1:21555/12345fff

Visiting this url turns off your machine:
http://127.0.0.1:21555/54321fff

Visiting this url restarts SRBMiner:
http://127.0.0.1:21555/restart_my_srb


Of course if you are going to 'open' this HTTP interface to the world, you better use complex urls so nobody can guess them easilly and turn off your rig Smiley

+ Now showing time in ms for shares. This is the time needed for:

- your miner sent the share to the pool
- pool accepted the share, did some validation and returned a result
- your miner accepted the result

+ Removed the benchmarking per algo, there is the --benchmarkalgos parameter which benches all you got in algos.txt

[abg00]

V1.7.6
- Webchain sending stale shares again

+ Now showing time in ms for shares. This is the time needed for:

test webchain now. speed better. lot of stale shares but lot of good shares too. excellent info time for shares

[sharix80]

Incredible! The webchain algorithm works. But LOUD Miner work perfectly.
Please, kill this algorithm in SRB miner!

[abg00]

1.7.6
key O P dont work. dont swich to next pool on webchain algo. other algo work

[doktor83]

1.7.6
key O P dont work. dont swich to next pool on webchain algo. other algo work

those keys have nothing to do with the used algo. Capslock was on maybe?

[twotwosix]

What hashrate you have with webchain?

[doktor83]

What hashrate you have with webchain?

it should be a little lower than v7

[abg00]

What hashrate you have with webchain?

it should be a little lower than v7

strange rate on webchain. one rig work fine with rate 80-85% from local.
but if add 1-2 rig have lot of rejected duplicate share and rate 40-60%

[2019-01-06 15:11:54] Pool accepted result 0xC80AD1CD [121ms]
[2019-01-06 15:11:54] Pool sent a new job (ID: 96e16412aab5c1865246e58fd67b6cdc)
[2019-01-06 15:11:56] Pool accepted result 0xD4AEDD68 [92ms][ S]
[2019-01-06 15:11:58] Pool sent a new job (ID: 2825b66be399a209ae1f10f5bf4ef5fb)
[2019-01-06 15:12:01] Pool rejected result 0x64858290 (duplicate share)
[2019-01-06 15:12:11] Pool difficulty: 20000
[2019-01-06 15:12:11] Pool sent a new job (ID: f4b8fcf6c5cec6a16d8d1ea973e90ece)
[2019-01-06 15:12:17] Pool sent a new job (ID: 06ca85cfb801ec7bd6ca43e63a1be417)
[2019-01-06 15:12:25] Pool rejected result 0x98A210FA (high rate of invalid shares)
[2019-01-06 15:12:34] Pool difficulty: 20000
[2019-01-06 15:12:34] Pool sent a new job (ID: 06ca85cfb801ec7bd6ca43e63a1be417)
[2019-01-06 15:12:39] Pool sent a new job (ID: 8c6b120b42492e89f9f546388378ec2b)

[doktor83]

What hashrate you have with webchain?

it should be a little lower than v7

strange rate on webchain. one rig work fine with rate 80-85% from local.
but if add 1-2 rig have lot of rejected duplicate share and rate 40-60%

[2019-01-06 15:11:54] Pool accepted result 0xC80AD1CD [121ms]
[2019-01-06 15:11:54] Pool sent a new job (ID: 96e16412aab5c1865246e58fd67b6cdc)
[2019-01-06 15:11:56] Pool accepted result 0xD4AEDD68 [92ms][ S]
[2019-01-06 15:11:58] Pool sent a new job (ID: 2825b66be399a209ae1f10f5bf4ef5fb)
[2019-01-06 15:12:01] Pool rejected result 0x64858290 (duplicate share)
[2019-01-06 15:12:11] Pool difficulty: 20000
[2019-01-06 15:12:11] Pool sent a new job (ID: f4b8fcf6c5cec6a16d8d1ea973e90ece)
[2019-01-06 15:12:17] Pool sent a new job (ID: 06ca85cfb801ec7bd6ca43e63a1be417)
[2019-01-06 15:12:25] Pool rejected result 0x98A210FA (high rate of invalid shares)
[2019-01-06 15:12:34] Pool difficulty: 20000
[2019-01-06 15:12:34] Pool sent a new job (ID: 06ca85cfb801ec7bd6ca43e63a1be417)
[2019-01-06 15:12:39] Pool sent a new job (ID: 8c6b120b42492e89f9f546388378ec2b)

you can thank that to the super-duper webchain protocol.
now i don't know why i added it at all, people only have problems and think its miner related.