AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly - page 48.

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: plox99 on April 18, 2019, 12:33:03 PM

Quote from: rednoW on April 18, 2019, 12:25:47 PM

Quote from: kerney666 on April 18, 2019, 11:42:02 AM

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). It’s the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

Nice, from 1.75 to 2.03 kh/s increase for cn/r from 0.4.3 to 0.4.4. vega56 hynix 1200/940@775mv (gpu-z shown clocks and voltage) Same timings

How about power? How many watts?

I don't know, 98watt gpu power in gpu-z. The same as trtl with 0.4.3
config 16*16 doesn't work for my vegas64 and 19.4.1 drivers. 14*14 config is ok and I'm getting 2.33kh/s (1300/1090@825mv 120 watt gpu-z )

rdome

newbie

Activity: 15

Merit: 0

this is comedy, 56 flashed to 64,
11/12 runs 2250
and one vega runs guesh what 2660 (insane stabilized at 2700h/s wtf, but this one card only) everithing is the same Wink

Samsung memory gpu 1408/ mem 1100 on 900mv

plox99

newbie

Activity: 9

Merit: 0

Quote from: rednoW on April 18, 2019, 12:25:47 PM

Quote from: kerney666 on April 18, 2019, 11:42:02 AM

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). It’s the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

Nice, from 1.75 to 2.03 kh/s increase for cn/r from 0.4.3 to 0.4.4. vega56 hynix 1200/940@775mv (gpu-z shown clocks and voltage) Same timings

How about power? How many watts?

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: kerney666 on April 18, 2019, 11:42:02 AM

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). It’s the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

Nice, from 1.75 to 2.03 kh/s increase for cn/r from 0.4.3 to 0.4.4. vega56 hynix 1200/940@775mv (gpu-z shown clocks and voltage) Same timings

kerney666

member

Activity: 658

Merit: 86

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). It’s the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

misterkit

newbie

Activity: 47

Merit: 0

Quote from: rednoW on April 18, 2019, 10:54:26 AM

Quote from: misterkit on April 18, 2019, 10:50:12 AM

Ok - what am I doing wrong?

WinAmdTweak.exe -i 0 --current

gives the settings for all GPU's instead of just the first one.

I also tried:
WinAMDTweak.exe -i 0 --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600

and instead of applying it to the first one it did it to all GPU's. I dont think the -i flag works in this usage.

facepalm

--i 0
DOUBLE!!!

Ha good eyes. I'll try it

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: misterkit on April 18, 2019, 10:50:12 AM

Ok - what am I doing wrong?

WinAmdTweak.exe -i 0 --current

gives the settings for all GPU's instead of just the first one.

I also tried:
WinAMDTweak.exe -i 0 --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600

and instead of applying it to the first one it did it to all GPU's. I dont think the -i flag works in this usage.

facepalm

--i 0
DOUBLE!!!

misterkit

newbie

Activity: 47

Merit: 0

Ok - what am I doing wrong?

WinAmdTweak.exe -i 0 --current

gives the settings for all GPU's instead of just the first one.

I also tried:
WinAMDTweak.exe -i 0 --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600

and instead of applying it to the first one it did it to all GPU's. I dont think the -i flag works in this usage.

N2DCRYPT

jr. member

Activity: 148

Merit: 5

@Eliovp,

I've a Radeon Pro Duo Polaris that I'm messing around with on your tool; the gpu is recognized just fine, with all the parameters, but the settings won't stick. For example, if I try to bring down the CL value from default 24 to 22 using --CL 22, I get the "successfully applied new CL settings" to both gpus, but when I check the settings again using --current CL is still at 24. Any ideas why the settings aren't sticking?

Thanks!

Edit: I run amdmemtweak after I've already put the mining load on the GPU (PhoenixMiner). I'm using ROCm on Linux.

misterkit

newbie

Activity: 47

Merit: 0

ok I was able to get around this....

I created a batch file with the commands that I wanted. The batch file has this:

WinAMDTweak.exe -i 0 --current > i0.current.txt

Then I ran the CMD prompt as admin (instead of running the batch file as admin) and it generated the file for me.

misterkit

newbie

Activity: 47

Merit: 0

I'd like to get the starting/current values before applying any changes so seeing the output of --current is important. I've tried a few of the settings posted in this thread and the rig dumps shortly thereafter so I wanted to take a more methodical approach.

On my win 10/AMD 19.4.2/Team Read on Vega 56 I am getting 2.048 kh/s.... so I am unsure how much farther I can push it using this tool.

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: misterkit on April 18, 2019, 08:08:26 AM

Quote from: JuanHungLo on April 18, 2019, 07:53:59 AM

Quote from: Mashy81 on April 18, 2019, 05:20:33 AM

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that. Doesnt make a difference. You can see the command opening a new window and values being printed to it but quickly closing....

It doesn't matter, the timings are still being applied.
Make sure you start your overclocking, then the miner, and whilst the miner is running, apply tweaked timings.
You'll see the hashrate go up immediately.

misterkit

newbie

Activity: 47

Merit: 0

I'm running on win 10...

wei0339

newbie

Activity: 12

Merit: 1

Quote from: misterkit on April 18, 2019, 08:08:26 AM

Quote from: JuanHungLo on April 18, 2019, 07:53:59 AM

Quote from: Mashy81 on April 18, 2019, 05:20:33 AM

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that. Doesnt make a difference. You can see the command opening a new window and values being printed to it but quickly closing....

OS:win 10
DRIVE: 18.5.2 & 18.6.1
GPU: VEGA 56*6 & vega56*7
run "WinAMDTweak.exe --i", Open a new window and close it in less than 1 second.
run "WinAMDTweak.exe --help > a.txt" , There is "a.txt" file size 0k.

OS:WIN7
DRIVE: only nvidia drive
GPU:GTX 970 & 1060
run "WinAMDTweak.exe --i", Display the text "No AMD display devices have been found!"
run "WinAMDTweak.exe --help > a.txt" , There is "a.txt" file size 3k.

OS:WIN7
DRIVE: 18.5.1
GPU:R7 200 Series
run "WinAMDTweak.exe --i", No text displayed‧
run "WinAMDTweak.exe --help > a.txt" , There is "a.txt" file size 3k.

Guess may be executed under win10 seems to have problems.

When there is free time, try vega56*6 to install v19.4.1 driver.

misterkit

newbie

Activity: 47

Merit: 0

Quote from: JuanHungLo on April 18, 2019, 07:53:59 AM

Quote from: Mashy81 on April 18, 2019, 05:20:33 AM

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that. Doesnt make a difference. You can see the command opening a new window and values being printed to it but quickly closing....

JuanHungLo

hero member

Activity: 935

Merit: 1001

I don't always drink...

Quote from: Mashy81 on April 18, 2019, 05:20:33 AM

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

misterkit

newbie

Activity: 47

Merit: 0

Quote from: Mashy81 on April 18, 2019, 05:20:33 AM

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Same issue here. I tried directing the output to a file and the file is empty. It appears that the WinAmdTweak.exe will open a NEW window instead of printing to the same current one. The new window opens, prints the results, and then quickly closes.

mingdao

newbie

Activity: 15

Merit: 0

Guys, any suggestions for Vega FE for 18.6.1/CnR on TeamRed?
I am efficiency focussed, running custom Wattman profile with -25 PL, core between P6 1353/890 - P7 1407/890, mem 1100/880.
Everything I try gives me instacrash.
Thanks.

Mashy81

jr. member

Activity: 225

Merit: 1

Quote from: iRonNuke on April 18, 2019, 05:13:10 AM

Quote from: Mashy81 on April 18, 2019, 05:08:46 AM

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

mingdao

newbie

Activity: 15

Merit: 0

Quote from: N2DCRYPT on April 16, 2019, 08:59:35 PM

Well that's fun... Vega FE's can crack the 2800 H/s threshold on CN-Heavy Algos Cheesy

https://i.imgur.com/IUZtjAL.jpg

Which drivers and settings are you using?

Topic: AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly - page 48. (Read 58906 times)