Author

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

newbie
Activity: 7
Merit: 0
INFO - TEST VEGA 56 PowerColor

3*Vega56 flashed to 64
Crimson-ReLive-Beta-Blockchain driver
SRBminer 1.4.9
GPU - 1442/1437/1407mhz 905-907mv
MEM - 1095/1100mhz 900mv

Cryptonight V7(monero)
"intensity" : 120  HR=6000 - 560W
https://image.prntscr.com/image/rK5kLVCPQQS89xDEIYhHgQ.jpg

Cryptonight lite(aeon)
"intensity" : 235  HR=12900 - 570W
https://image.prntscr.com/image/23TkvCkvRMCvC9p2YhxiCQ.jpg

Cryptonight liteV7(trtl)
"intensity" : 235  HR=12900 - 570W
https://image.prntscr.com/image/Xb6WiZ1EQaS5UMmWq3KHuw.jpg

Cryptonight ultraheavy-lightv3(ipbc)
"intensity" : 239  HR=11100 - 550W
https://image.prntscr.com/image/PeiajoLsTJO3Zwc1ZX8f8A.jpg

Cryptonight heavy(sumo)
"intensity" : 56  HR=4550 - 530W
https://image.prntscr.com/image/2xW89wB8SxaZeSWX1n6zjQ.jpg

Cryptonight artocache(arto)
"intensity" : 118  HR=5400 - 550W
https://image.prntscr.com/image/AopDRnW8R0m9EDnqyB8-aw.jpg
thanks for info
hero member
Activity: 2548
Merit: 626
can overdrivenext be used to change voltage? i didn't see that in the readme, so wasn't sure. thanks!

Currently no, only gpu temperature and fan speeds.
full member
Activity: 294
Merit: 104
V1.5.2
- Added support for ADL Overdrive5, in gpu_conf add 'adl_type' = 1 for OverdriveNext , 2 for Overdrive5, if not set default is 1 (OverdriveNext)
- Parameter 'restart_devices_on_startup' now only restarts Vega GPU'S, cause others don't need restarting to get max performance
- Disable/enable GPU while mining now happens almost instantly
- Added '--gpureorder' parameter (use in bat)  to order devices by BUSID like GPU-Z does
- Added '--listdevicesreordered' that lists devices in BUSID order, for usage with '--gpureorder' parameter

+ If your GPU temperature or fan speed isn't displayed when pressing 'h' , try adding 'adl_type' : 2 in gpu_conf :

"gpu_conf" :
[
   { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "adl_type" : 2}
]


Also you can try type 2 if 'target_fan_speed' isn't working for you with the default OverdriveN.
Basically :
Type 1 : Use OverdriveN (mostly for newer cards)
Type 2 : Use Overdrive5 (mostly for older cards)


+ If you want to order your GPU's like in GPU-Z or OverdriveNTool, put parameter --gpureorder in .bat like :

FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING
%EXE% --config config.txt --pools pools.txt --gpureorder
TIMEOUT /T 15 /NOBREAK

When setting up 'gpu_conf' in config but want to use the BUSID ordering, first list devices with --listdevicesreordered parameter to get the reordered gpu id's :

SRBMiner-CN.exe --listdevicesreordered

+ The 'restart_devices_on_startup' parameter now looks only for Vega GPU'S, and disables/enables only those before mining.

can overdrivenext be used to change voltage? i didn't see that in the readme, so wasn't sure. thanks!
hero member
Activity: 2548
Merit: 626
V1.5.2
- Added support for ADL Overdrive5, in gpu_conf add 'adl_type' = 1 for OverdriveNext , 2 for Overdrive5, if not set default is 1 (OverdriveNext)
- Parameter 'restart_devices_on_startup' now only restarts Vega GPU'S, cause others don't need restarting to get max performance
- Disable/enable GPU while mining now happens almost instantly
- Added '--gpureorder' parameter (use in bat)  to order devices by BUSID like GPU-Z does
- Added '--listdevicesreordered' that lists devices in BUSID order, for usage with '--gpureorder' parameter

+ If your GPU temperature or fan speed isn't displayed when pressing 'h' , try adding 'adl_type' : 2 in gpu_conf :

"gpu_conf" :
[
   { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "adl_type" : 2}
]


Also you can try type 2 if 'target_fan_speed' isn't working for you with the default OverdriveN.
Basically :
Type 1 : Use OverdriveN (mostly for newer cards)
Type 2 : Use Overdrive5 (mostly for older cards)


+ If you want to order your GPU's like in GPU-Z or OverdriveNTool, put parameter --gpureorder in .bat like :

FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING
%EXE% --config config.txt --pools pools.txt --gpureorder
TIMEOUT /T 15 /NOBREAK

When setting up 'gpu_conf' in config but want to use the BUSID ordering, first list devices with --listdevicesreordered parameter to get the reordered gpu id's :

SRBMiner-CN.exe --listdevicesreordered

+ The 'restart_devices_on_startup' parameter now looks only for Vega GPU'S, and disables/enables only those before mining.
jr. member
Activity: 176
Merit: 2
...
also, anyone able to get 750h/s+ on RX 580 4GB models?
my 8GB models do 1000h/s+ SOMETIMES but cant get 4GB any higher.

I get 1040 h/s on my armor rx 580 hynix 8 gb I=55 and 720 h/s only on my nitro+ rx 480 elpida 4 gb I=29.5, I tried different timing straps on the 480, but it didn't change much

One strange thing is that the reported hashrate change each time I restart the miner
(most of the time, it's one time good, with 1040 h/s on the rx-580 and one time "bad" with 930 h/s on the same rx-580... and it makes comparison difficult)

I got that exact problem, my rx 480 4gb is always stuck at 730h/s but my 2 rx 580 8gb are crazy, miner starts with both doing 950h/s or first 850h/s and second 1050h/s. I am always restarting im till second gives 1050h/S and then the first one seing tv shows or sometimes from nowere will go to 950-990h/S. The values are very unstable.

rednoW already explain in cast xmr thread and that explanation more make sense for me.
below are explanation from rednoW:
Quote
In case of normal v7 vega with 16gb becomes compute bounded. Vega 8gb is memory size bounded with heavy.
It is just like with polaris 8gb and v7. You can set intensity to use all 8gb ram but due to lack of compute units it cannot handle it. But with heavy Polaris 8gb uses all its memory and has the same hashrate as with v7

so basically my understanding for CN-V7 is compute bounded in RX 580 8 GB because even if you set higher intensity it will not increase hash rate. while for CN-Heavy is memory bounded in RX 580 4 GB because CN-Heavy used more memory than CN-V7.
full member
Activity: 294
Merit: 104
I just moved over from Claymore (ethash) to try my hand at a few Heavy coins, and I'm glad I did after two days so far. I couldn't get any of the other miners to work with my AMD system except SRBMiner. I'm running 8x RX570/580 4GB at around 750 h/s and 1 RX580 8GB at around 1100 h/s. I have one RX570 that I could not get to work with SRBMiner (errors) so I have it still going after Ethereum with Claymore.

Question for the group - I didn't really know that Cryptonight Heavy was good for AMD cards, versus seemingly all the non-Ethash algos being good for Nvidia. Are there any other new algorithms that are better for AMD cards than Nvidia?
newbie
Activity: 24
Merit: 0
...
also, anyone able to get 750h/s+ on RX 580 4GB models?
my 8GB models do 1000h/s+ SOMETIMES but cant get 4GB any higher.

I get 1040 h/s on my armor rx 580 hynix 8 gb I=55 and 720 h/s only on my nitro+ rx 480 elpida 4 gb I=29.5, I tried different timing straps on the 480, but it didn't change much

One strange thing is that the reported hashrate change each time I restart the miner
(most of the time, it's one time good, with 1040 h/s on the rx-580 and one time "bad" with 930 h/s on the same rx-580... and it makes comparison difficult)

I got that exact problem, my rx 480 4gb is always stuck at 730h/s but my 2 rx 580 8gb are crazy, miner starts with both doing 950h/s or first 850h/s and second 1050h/s. I am always restarting im till second gives 1050h/S and then the first one seing tv shows or sometimes from nowere will go to 950-990h/S. The values are very unstable.
jr. member
Activity: 176
Merit: 2
I don't know how you guys do it.
My Vega 56's (Reference models) with Vega 56 BIOS runs 2010H/s on Normal V7 but on Heavy I am not able to get more than 1350H/s.

I have even now tried Vega 56 @ 1437/1100 907mV -30 power target on 56 intensity but no luck still only get 1350H/s per card.

My normal clocks on NormalV7 are: 1475/1100 @ 915 and 900



set intensity 60 worksize 8 run miner, then close miner set intensity 56 worksize 8 and run miner again, you should able to get more than 1500 h/s.
hero member
Activity: 2548
Merit: 626
I don't know how you guys do it.
My Vega 56's (Reference models) with Vega 56 BIOS runs 2010H/s on Normal V7 but on Heavy I am not able to get more than 1350H/s.

I have even now tried Vega 56 @ 1437/1100 907mV -30 power target on 56 intensity but no luck still only get 1350H/s per card.

My normal clocks on NormalV7 are: 1475/1100 @ 915 and 900

The miner isn't stable for vega 56/blockchain drivers, I noticed that on some testing I could get 1430+ average and then afterwards dropped to 1300+ that's after tweaking config files for intensity and worksize as well as some restarts/driver resets/hbcc memory toggles. Castxmr on the other hand will work just alright after a restart and driver reset. Now I'm mining 1430+ average(p6 1212/875,p7 1407/875, p3 95/875).

or just drop the blockchain drivers and use 18.3.4 where you don't need to disable/enable devices for better hashrate.
jr. member
Activity: 113
Merit: 1
I don't know how you guys do it.
My Vega 56's (Reference models) with Vega 56 BIOS runs 2010H/s on Normal V7 but on Heavy I am not able to get more than 1350H/s.

I have even now tried Vega 56 @ 1437/1100 907mV -30 power target on 56 intensity but no luck still only get 1350H/s per card.

My normal clocks on NormalV7 are: 1475/1100 @ 915 and 900

The miner isn't stable for vega 56/blockchain drivers, I noticed that on some testing I could get 1430+ average and then afterwards dropped to 1300+ that's after tweaking config files for intensity and worksize as well as some restarts/driver resets/hbcc memory toggles. Castxmr on the other hand will work just alright after a restart and driver reset. Now I'm mining 1430+ average(p6 1212/875,p7 1407/875, p3 950/875).
jr. member
Activity: 230
Merit: 1
I don't know how you guys do it.
My Vega 56's (Reference models) with Vega 56 BIOS runs 2010H/s on Normal V7 but on Heavy I am not able to get more than 1350H/s.

I have even now tried Vega 56 @ 1437/1100 907mV -30 power target on 56 intensity but no luck still only get 1350H/s per card.

My normal clocks on NormalV7 are: 1475/1100 @ 915 and 900

sr. member
Activity: 1484
Merit: 253
hi

found why my rig 580 doesn t love srb :auto intensity was 100 or 118....works great at 53.

why auto intensity is so high??
For normal cryptonight v7 100-118 is best. For CN heavy it's need half of CN V7 intensity.
jr. member
Activity: 158
Merit: 5
Mining ETN at nanopool with RX580 8GB , intensity 60 on each card 890h/s! Is there anyway I can further tweak it or that's the maximum? Do you guys have some BIOS mods for RX580 Sapphire Nitro+ Special Edition's with Micron memory for cryptonight algorithm? I am currently mining it with my ETH, which may be causing this not optimal speed.

MSI Armor RX580 8GB - Micron, using one click patch timings in Polaris Bios Editor.

Getting 1010 h/s using:
Intensity: 51, threads: double (Constrained by the Virtual Mem Size, out of space on SSD, could be higher)
1160 cclock / 880 vcore
2220 mclock / 880 vmem

Double threads are very important, it increases occupancy. Make sure you have sufficient vmem space, check out vmem usage using HWINFO, make sure there's at least 10% free vmem left during mining.

Microns are good, I like'em. One click patch timings in Polaris is very good for ETH mining (31-32 Mh/s) and it's possible that there may be timings that will take one to the moon at 2100 mclock catered for Cryptonight, but I don't want to play with BIOS everytime, it's really stressful because I'm afraid of bricking cards, so not going to touch'em for now.

Also, you need to close gpu-z or hwinfo during mining, it slows down the mining slightly but the losses would accumulate over time.


I modify strap from Polaris bios editor one click timings with cclock 1240 and mclock 2150 CN-V7 got 1010 h/s and CN-Heavy got 1080 h/s.
if you like to try I will post my strap here. with your card which can set mclock 2220 most likely can reach CN-Heavy 1100 h/s.

Thanks! I don't want to flash anymore as every time I do it I get shivers down my spine Cheesy

But here's one thing about flashing, two of my cards failed flash... Bios write failed multiple times, gpu's no longer listed as AMD, bios read was not even working. Then I continued a few hours of operation with other gpu's, reading about fixing bricked cards, and then they literally fixed themselves, with the original bios. I don't think MSI Armor has dual bios so I don't know how that happened. You guys have any ideas??


Maybe if I increase the Core clocks to 1240 it'd do 1050-1100 but it gets too hot and I have to crank up vcore so I think I struck a nice balance here, will try those after I get the hardware cost covered lol Cheesy
newbie
Activity: 66
Merit: 0
i try alloy coin... and i get 0 h/s
rx470 4gb and rx580 4gb
newbie
Activity: 35
Merit: 0
So my Vega 56 @ 1437/1100 907mV -30 power target on 56 intensity gets 1530 h/s on CN-Heavy, whereas my Vega 64 with the same settings gets 1380 h/s. I need to raise intensity to 60 to get 1450 h/s on the Vega 64 - but something is not right. Maybe a higher core clock is required on the Vega 64?
member
Activity: 176
Merit: 10
hi

found why my rig 580 doesn t love srb :auto intensity was 100 or 118....works great at 53.

why auto intensity is so high??
jr. member
Activity: 176
Merit: 2
Mining ETN at nanopool with RX580 8GB , intensity 60 on each card 890h/s! Is there anyway I can further tweak it or that's the maximum? Do you guys have some BIOS mods for RX580 Sapphire Nitro+ Special Edition's with Micron memory for cryptonight algorithm? I am currently mining it with my ETH, which may be causing this not optimal speed.

MSI Armor RX580 8GB - Micron, using one click patch timings in Polaris Bios Editor.

Getting 1010 h/s using:
Intensity: 51, threads: double (Constrained by the Virtual Mem Size, out of space on SSD, could be higher)
1160 cclock / 880 vcore
2220 mclock / 880 vmem

Double threads are very important, it increases occupancy. Make sure you have sufficient vmem space, check out vmem usage using HWINFO, make sure there's at least 10% free vmem left during mining.

Microns are good, I like'em. One click patch timings in Polaris is very good for ETH mining (31-32 Mh/s) and it's possible that there may be timings that will take one to the moon at 2100 mclock catered for Cryptonight, but I don't want to play with BIOS everytime, it's really stressful because I'm afraid of bricking cards, so not going to touch'em for now.

Also, you need to close gpu-z or hwinfo during mining, it slows down the mining slightly but the losses would accumulate over time.


I modify strap from Polaris bios editor one click timings with cclock 1240 and mclock 2150 CN-V7 got 1010 h/s and CN-Heavy got 1080 h/s.
if you like to try I will post my strap here. with your card which can set mclock 2220 most likely can reach CN-Heavy 1100 h/s.
jr. member
Activity: 158
Merit: 5
Mining ETN at nanopool with RX580 8GB , intensity 60 on each card 890h/s! Is there anyway I can further tweak it or that's the maximum? Do you guys have some BIOS mods for RX580 Sapphire Nitro+ Special Edition's with Micron memory for cryptonight algorithm? I am currently mining it with my ETH, which may be causing this not optimal speed.

MSI Armor RX580 8GB - Micron, using one click patch timings in Polaris Bios Editor.

Getting 1010 h/s using:
Intensity: 51, threads: double (Constrained by the Virtual Mem Size, out of space on SSD, could be higher)
1160 cclock / 880 vcore
2220 mclock / 880 vmem

Double threads are very important, it increases occupancy. Make sure you have sufficient vmem space, check out vmem usage using HWINFO, make sure there's at least 10% free vmem left during mining.

Microns are good, I like'em. One click patch timings in Polaris is very good for ETH mining (31-32 Mh/s) and it's possible that there may be timings that will take one to the moon at 2100 mclock catered for Cryptonight, but I don't want to play with BIOS everytime, it's really stressful because I'm afraid of bricking cards, so not going to touch'em for now.

Also, you need to close gpu-z or hwinfo during mining, it slows down the mining slightly but the losses would accumulate over time.
member
Activity: 140
Merit: 20
all time run this miner my rig is hug

what i can do about that ??

i test this miner in 4 rigs at stock bios and also rigs stop !!!!

newbie
Activity: 118
Merit: 0
Great miner!
A+++ for RX580. This is my 8 x RX580 8gb rig - Nitro+ and Pulse GPU's, 8 kh/s, consumption 880w on CN-Heavy.
https://prnt.sc/jf2j12

Vega 64 hashrate is lower than cast-xmr.

Thanks!

What memory and what memory straps?
Jump to: