Good Morning,
i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.
The GPU ID for the 580 is 3 and i put this in the start.bat
SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....
Thank you
Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 172. (Read 237261 times)
August 13, 2018, 02:26:45 AM
August 13, 2018, 12:43:26 AM
Hi doktor,
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
Tell him which driver you using.
and which algo is it
August 12, 2018, 11:26:18 PM
Hi doktor,
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
Tell him which driver you using.
August 12, 2018, 11:22:43 PM
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
that doubling trick doesn't work for me, but I have 7920-7925 h/s without it on 4 vega56 (ref or noname idk, it was OEM and the only sign on it is RADEON), cc 1450-1470, mc 925-935 (found exact stable maximum for each card).I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
BTW, if you have only RADEON written on your vegas, you have ref cards
My non ref card (hynix memory) runs stable at 1775 with higher consumption
My 3 ref cards (samsung memory) go over 2000h/s with CC:1407 / MC:941 but run too hot so I lower the frequencies during the summer
August 12, 2018, 07:41:32 PM
Hi doktor,
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
I was using version 1.6.3 in my vega 56,
using the 1.6.6 i got less 30 hs
Using same settings,
On other rigs with rx 580 and vega 64 got the same hashes.
Just reporting
August 12, 2018, 06:30:37 PM
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
...Doc?reboot script is the one you add in config.txt, so yes, add it in every config.
That is handy because maybe your heavy algo clock settings in overdriventool are not the same as for v7, so on every algo start it will run the appropriate batch file.
Let's see how the rigs behave overnight!
EDIT: still also possible to set a logfile?
EDIT 2: Should "fast" and "stellitev4" be using the same clocks and settings generally as "normalv7" (on Vega and RX 570's)?
I normally run the same clocks and settings. I only change mine for heavy and lite
August 12, 2018, 06:11:14 PM
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
...Doc?reboot script is the one you add in config.txt, so yes, add it in every config.
That is handy because maybe your heavy algo clock settings in overdriventool are not the same as for v7, so on every algo start it will run the appropriate batch file.
Let's see how the rigs behave overnight!
EDIT: still also possible to set a logfile?
EDIT 2: Should "fast" and "stellitev4" be using the same clocks and settings generally as "normalv7" (on Vega and RX 570's)?
August 12, 2018, 05:14:29 PM
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
...Doc?reboot script is the one you add in config.txt, so yes, add it in every config.
That is handy because maybe your heavy algo clock settings in overdriventool are not the same as for v7, so on every algo start it will run the appropriate batch file.
August 12, 2018, 03:27:06 PM
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
...Doc? August 12, 2018, 01:31:08 PM
The trick is working on "v7" algos, on heavy, tube, haven nope 
August 12, 2018, 12:56:31 PM
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
that doubling trick doesn't work for me, but I have 7920-7925 h/s without it on 4 vega56 (ref or noname idk, it was OEM and the only sign on it is RADEON), cc 1450-1470, mc 925-935 (found exact stable maximum for each card).I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
BTW, if you have only RADEON written on your vegas, you have ref cards
My non ref card (hynix memory) runs stable at 1775 with higher consumption
My 3 ref cards (samsung memory) go over 2000h/s with CC:1407 / MC:941 but run too hot so I lower the frequencies during the summer
August 12, 2018, 11:25:30 AM
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
that doubling trick doesn't work for me, but I have 7920-7925 h/s without it on 4 vega56 (ref or noname idk, it was OEM and the only sign on it is RADEON), cc 1450-1470, mc 925-935 (found exact stable maximum for each card). I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
August 12, 2018, 10:03:39 AM
Haha,
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.
just remove duplicatedgpuid and see. i thinhk driver up HR. duplicated gpuid not work for me.
HR is identical or smaller with this otpion for me.
3*referal vega56 with 64 bios(1-2-4card) + 1 vega64LE(stock bios)(3card)=700W from the wall(tube) and 720W(xtl)
ver 1.6.4 + driver 1.8.34 standard option without --enableduplicategpuid
algo: tube and stellite
https://image.prntscr.com/image/_QihwWeLTQiGRpgtx9N3nQ.jpg
https://image.prntscr.com/image/lZW72vYJQAi33QmK1kotGA.jpg
stellite and v7 go up 20HR per card if use 1.6.1 driver but tube not work with HBC mem,.
August 12, 2018, 09:51:34 AM
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
August 12, 2018, 08:28:05 AM
Anyone experience increased HR with v1.6.6 over v1.6.5 using Vega64s (without the trick)?
August 12, 2018, 08:10:39 AM
Haha,
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s and now I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.
August 12, 2018, 06:13:57 AM
August 12, 2018, 06:03:00 AM
Me
August 12, 2018, 05:51:57 AM
Extra 21H/s per Vega 56 when using Doc's new trick
Now my Vega 56's do 2049H/s per card.
Anyone getting better results with reference Vega 56's?
Now my Vega 56's do 2049H/s per card.
Anyone getting better results with reference Vega 56's?
August 12, 2018, 04:59:43 AM
Jump to: