Pages:
Author

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

member
Activity: 340
Merit: 29
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.

Double-check you enumerate your GPUs correctly. I know it sounds like a silly suggestion, but you know... been there, done that.

If the onboard GPU is anything AMD, it gets listed too (usually GPU0).  

I hear ya, made plenty of stupid mistakes myself. But yeah, TRM miner shows the bus number and changes I make to the other GPUs do take effect. I’m wondering if it’s because I’m using CLI and the - -i parameter and it’s not reading the last GPU in the parameter setting?

You don't happen to start TRM with a -d in config?

No, but I’m going to do some further tests tomorrow with the latest version and see what happens, maybe double check the settings with the GUI (I’m using CLI right now).

You're using '--i' and not '-i', correct?  The example usage in the help text (amdmemtweak --help) shows the latter, which is not valid.  (EDIT: this was the case in older versions - appears to be fixed in the latest)
jr. member
Activity: 64
Merit: 1
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.

Double-check you enumerate your GPUs correctly. I know it sounds like a silly suggestion, but you know... been there, done that.

If the onboard GPU is anything AMD, it gets listed too (usually GPU0).  

I hear ya, made plenty of stupid mistakes myself. But yeah, TRM miner shows the bus number and changes I make to the other GPUs do take effect. I’m wondering if it’s because I’m using CLI and the - -i parameter and it’s not reading the last GPU in the parameter setting?

You don't happen to start TRM with a -d in config?

No, but I’m going to do some further tests tomorrow with the latest version and see what happens, maybe double check the settings with the GUI (I’m using CLI right now).
newbie
Activity: 27
Merit: 1
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.

Double-check you enumerate your GPUs correctly. I know it sounds like a silly suggestion, but you know... been there, done that.

If the onboard GPU is anything AMD, it gets listed too (usually GPU0).  

I hear ya, made plenty of stupid mistakes myself. But yeah, TRM miner shows the bus number and changes I make to the other GPUs do take effect. I’m wondering if it’s because I’m using CLI and the - -i parameter and it’s not reading the last GPU in the parameter setting?

You don't happen to start TRM with a -d in config?
jr. member
Activity: 64
Merit: 1
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.

Double-check you enumerate your GPUs correctly. I know it sounds like a silly suggestion, but you know... been there, done that.

If the onboard GPU is anything AMD, it gets listed too (usually GPU0).  

I hear ya, made plenty of stupid mistakes myself. But yeah, TRM miner shows the bus number and changes I make to the other GPUs do take effect. I’m wondering if it’s because I’m using CLI and the - -i parameter and it’s not reading the last GPU in the parameter setting?
member
Activity: 340
Merit: 29
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14


Hey Livada, nice results.
Are these on reference 64's?
What clocks were you running them at per algo?
2.48 on CN/r is nice...

Sorry, but 1 accepted and a 3 minutes run shows nothing. These results with 24 hours would be nice, but I dont bet on it.

While it’s true a 3 min run proves nothing, 2.45+ cnr on a v64 is easily stable at 1375 (measured) / 1107 / 825-850mv using those timings and TRM
newbie
Activity: 3
Merit: 0
I have a Win 10 - Vega 56 rig

One Hynix card causes a dead GPU when trying 19.4.2, latest TR and have tried both of the suggested Hynix setttings.  Anyone have one that is working for them?   I've tried:

WinAMDTweak.exe --gpu 03 --RAS 24 --RCDRD 19 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 5 --RFC 148 --REF 15600

and

WinAMDTweak.exe --gpu 03 --RAS 22 --RCDRD 17 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 4 --RFC 148 --REF 15600

Both of these cause a dead gpu/restart
try this-

--rcdrd 19 --rcdwr 4 --rc 35 --rp 14 --rrds 4 --rrdl 5 --rfc 148 --REF 15600
or
--rp 14 --rc 42 --rfc 156 --rrd 3 --rcdrd 18 --rcdwr 3

not best but work

iff any have good setup for vega56/stockbios/hynix pls send ..

I got vega 56 strix hynix and i cant go more than 1800hs.. What is ur best results guys? Any good setup for this bad cards? Sad Huh
newbie
Activity: 27
Merit: 1
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.

Double-check you enumerate your GPUs correctly. I know it sounds like a silly suggestion, but you know... been there, done that.

If the onboard GPU is anything AMD, it gets listed too (usually GPU0).  
member
Activity: 413
Merit: 21
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14


Hey Livada, nice results.
Are these on reference 64's?
What clocks were you running them at per algo?
2.48 on CN/r is nice...

Sorry, but 1 accepted and a 3 minutes run shows nothing. These results with 24 hours would be nice, but I dont bet on it.
jr. member
Activity: 64
Merit: 1
Hello, is anyone having an issue where the last GPU of a multi-GPU rig does not get the mem tweak applied? On 3 out of my 4 rigs (6 Vega64s per rig), the last GPU does not get the tweak applied to it. I’m using CLI (last version) on Win10.
jr. member
Activity: 64
Merit: 1
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14



Hi livada, thanks for all your posts and suggestions, I’m now mining 20-25% more hash at the pool because of you (and of course Eliovp) :-)

But when you run settings tests, you need to run them longer. 1 accepted share does not make a for a very good basis for overall long-term results. Valid results would be based on hours of mining, sometimes GPU crashes with new settings after a while, sometimes many hw errors occur over time, these may not present themselves until many hours of mining.

Cheers!
newbie
Activity: 417
Merit: 0
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14

http://imgbox.com/oH0Nn1Pa
Hey Livada, nice results.
Are these on reference 64's?
What clocks were you running them at per algo?
2.48 on CN/r is nice...

GPU4 is Vega 64LE - GPU 1-2 REferent Vega 56@64 bios (+2300hr on CNR)
All algo run with identical Mem tweak.
Vega 64LE clock :
http://imgbox.com/2xmtiUyw
Vega 56 clock :
http://imgbox.com/TzsvzlCa

hero member
Activity: 1274
Merit: 556
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14


Hey Livada, nice results.
Are these on reference 64's?
What clocks were you running them at per algo?
2.48 on CN/r is nice...
legendary
Activity: 1050
Merit: 1293
Huh?
Built the latest linux version from github but get the following error message

Code:
Cannot find DRI instance for pci:0000:01:00.0

Same message regardless of what I pass with --i , e.g.

Code:
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 0 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 1 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 2 --current
Cannot find DRI instance for pci:0000:01:00.0

System details:
Code:
root@minivega:/dev/dri# uname -a
Linux minivega 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@minivega:/dev/dri# apt list --installed | grep amdgpu-pro

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

amdgpu-pro-core/unknown,now 18.10-572953 all [installed,automatic]
clinfo-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
libopencl1-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
opencl-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-orca-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed]

Anyone else got the same problem, or do I need to update amdgpu-pro?

I just pushed a new CLI version both for windows and Linux, can you please try that one. (there's a pre-built one in releases)

Cheers
jr. member
Activity: 47
Merit: 1
Built the latest linux version from github but get the following error message

Code:
Cannot find DRI instance for pci:0000:01:00.0

Same message regardless of what I pass with --i , e.g.

Code:
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 0 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 1 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 2 --current
Cannot find DRI instance for pci:0000:01:00.0

System details:
Code:
root@minivega:/dev/dri# uname -a
Linux minivega 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@minivega:/dev/dri# apt list --installed | grep amdgpu-pro

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

amdgpu-pro-core/unknown,now 18.10-572953 all [installed,automatic]
clinfo-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
libopencl1-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
opencl-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-orca-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed]

Anyone else got the same problem, or do I need to update amdgpu-pro?
newbie
Activity: 417
Merit: 0
vega samsung memory : ETH-CNR-BEAM

WinAMDTweak.exe --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14

http://imgbox.com/oH0Nn1Pa
newbie
Activity: 162
Merit: 0
New Release

  • Added FIJI support
  • Added Refresh Rate timing (RX boost  Wink)
  • Overdrive fixes
  • Added memory manufacturer detection for G5, HBM & HBM2
  • .....

Link: Here


Will upload CLI versions asap as well!


I noticed some people have figured out that there is still room to improve on RX 4**/5** cards.
Just not many people saying how..

Well, open up the tool, and raise Refresh Rate (REF) i created a separate textbox for it to make it easy.
Raise it from 5 to 7/8 (just an example) and you'll see improvement already.

Slightly dropping RFC will increase your hashrate as well.



Greetings

I tried to set the REF and RTC as you mention on my RX580 8Gb Hynex but as soon as I push apply, it gets back to original values, any idea?
thx
full member
Activity: 1120
Merit: 131
New Release

  • Added FIJI support
  • Added Refresh Rate timing (RX boost  Wink)
  • Overdrive fixes
  • Added memory manufacturer detection for G5, HBM & HBM2
  • .....

Link: Here


Will upload CLI versions asap as well!


I noticed some people have figured out that there is still room to improve on RX 4**/5** cards.
Just not many people saying how..

Well, open up the tool, and raise Refresh Rate (REF) i created a separate textbox for it to make it easy.
Raise it from 5 to 7/8 (just an example) and you'll see improvement already.

Slightly dropping RFC will increase your hashrate as well.



Greetings

It's slightly faster, thanks a lot !
I applied my usual settings for RX574.

tRFC:
- Samsung memory (tCL is 22): 117
- Hynix memory (tCL is 19): 124
- Elpida memory (tCL is 21): 94

Right now refresh at 9 for all GPUs. I'll see if it's stable.
hero member
Activity: 1274
Merit: 556
Quote from: eliovp
Added Refresh Rate timing (RX boost  Wink)
RXboost... Is that Claymore's thing?
What do you actually get out of that? Does it run independently to the timing straps? Don't want to f@ck anything up that's seemingly stable! Cheesy
hero member
Activity: 2548
Merit: 626
legendary
Activity: 1050
Merit: 1293
Huh?
New Release

  • Added FIJI support
  • Added Refresh Rate timing (RX boost  Wink)
  • Overdrive fixes
  • Added memory manufacturer detection for G5, HBM & HBM2
  • .....

Link: Here


Will upload CLI versions asap as well!


I noticed some people have figured out that there is still room to improve on RX 4**/5** cards.
Just not many people saying how..

Well, open up the tool, and raise Refresh Rate (REF) i created a separate textbox for it to make it easy.
Raise it from 5 to 7/8 (just an example) and you'll see improvement already.

Slightly dropping RFC will increase your hashrate as well.



Greetings
Pages:
Jump to: