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

I am trying to port this over to Windows for everybody.
Is there any tips you might have besides making use of the PCUtil's app?
I've not programmed in a long while so this is a bit out of my wheelhouse but somebody should step up.. well i'm that sucker.

Thank you! Any help is greatly appreciated. The fact you got this working on Linux and how fast the many mining OS's are implementing this, is great. I only wish i could do this conversion to Windows faster.

Thank you for this beautiful code.

Nefarious Fool
"To run a thousand miles is in awesome feat... too bad you can just take a flight and do the same thing in 2hrs... It sure does make it a lot less monumental"

YOU ARE A MASTER!

root@clarosrv:~/build/amdmemorytweak# ./amdmemtweak --current
GPU 0:  Device 67c7     pci:0000:42:00.0
CAS
  CL: 22          W2R: 16         CCDS: 5         CCLD: 3         R2W: 30         NOPR: 0         NOPW: 0
RAS
  RC: 74          RRD: 8          RCDRA: 25       RCDR: 25        RCDWA: 16       RCDW: 16
MISC
  RFC: 164        TRP: 23         RP_RDA: 26      RP_WRA: 54
MISC2
  WDATATR: 0      T32AW: 9        CRCWL: 25       CRCRL: 3        FAW: 14         PA2WDATA: 0     PA2RDATA: 0
DRAM1
  RASMACTWR: 35   RASMACTRD: 30   ACTWR: 10       ACTRD: 15
DRAM2
  RAS2RAS: 15     RP: 10          WRPLUSRP: 30    BUS_TURN: 35

You really deserve your donation man!
TXID 0x4563bf67d18a7bd552b3d78ada5ca59f57b76726f26f3263f8f48818ef30a1d8

Thank You!   

nice @Eliovp! Definitely recognized now. Time to play around, thanks for your work on this tool!  

I also tried running a Radeon Polaris Pro Duo (dual WX-7100) and got nothing when running the tool... I'm obviously doing something wrong or this uncommon gpu just isn't supported, which wouldn't be too surprising. Thought it might be worth a try, simply because like your gpu bios mods aren't particularly practical with this guy and are fairly non-existent on the web.
[/quote]

I've done some debug of the code for my card....
The card is recognized as an ATI and amdgpu_regs is read
555                     snprintf(buffer, sizeof(buffer)-1, "/sys/kernel/debug/dri/%d/amdgpu_regs", instance);

but when the program try to identify the memory type, all the defined value in the buffer are wrong:

574                             lseek(gpu->mmio, MC_SEQ_RAS_TIMING, SEEK_SET);
(gdb) p lseek(gpu->mmio, MC_SEQ_RAS_TIMING, SEEK_SET)
No symbol "MC_SEQ_RAS_TIMING" in current context.
No symbol "MC_SEQ_CAS_TIMING" in current context.
No symbol "MC_SEQ_MISC_TIMING" in current context.
etc. etc..

Simply the values in the amdgpu_regs are not as expected.
Every time I try to analize those values and correct them, my server crash an reset  

I was thinking the problem where in the driver, but if you got the same result with a wx-7100 the problem could be in the bios itself...
Surely I'm too tired tonight to try again, I will let you know if I can go further...

Bye

 

I added support for your GPU 

You can check last commits how it's done, it's fairly easy.
So next time, when you encounter this "issue" you know what to do


I also pushed a new release with a bunch of new HBM2 timings and a bunch of fixes

Enjoy!

I also tried running a Radeon Polaris Pro Duo (dual WX-7100) and got nothing when running the tool... I'm obviously doing something wrong or this uncommon gpu just isn't supported, which wouldn't be too surprising. Thought it might be worth a try, simply because like your gpu bios mods aren't particularly practical with this guy and are fairly non-existent on the web.

For me "easily" mean I caused a kernel panic and/or a pci-error on every attempt to modify your code... 
Anyway running an unmodified version of your tool I get this output:
./amdmemtweak -i 0 --current
#
NOTHING :-)

I think the problem is I'm using an OSS Driver from debian and not the amd one....
(https://wiki.debian.org/it/AtiHowTo)
My card (WX-5100) is peculiar and I could not achive a decent install on debian 9 of the amd driver..

Anyway, still reading your code, a brilliant work! (even if I can understand just a 10% of it)
Bye

its 160 wats at 50mh i have tested and have posted my results above

Probably sitting at 350w+ to get 50+Mh/s which just doesn't make sense from a hash to watt ratio standpoint.

Yep - that was kinda my point... sounds more like this guy figured out how to properly tune his vega, then added the timing benefits on top of that.

45 on a Vega 64, definitely doable with stock timings.

Add another 5Mh to that with the extra options you have now is definitely doable.


Thanks for the nice words

I don't have any AMD cards anymore, but I remember you from way back when I did and I was modding my own BIOSes. Full credit to you for sharing this phenomenal piece of work.

Ubuntu 18.04 + amdgpu-pro 18.5 is what I use, without problems.  The voltage-frequency relationship is a Vega feature (ACG), not the driver.  Same behavior is observable in Windows, though not as aggressive for some reason.  Every card is different, but depending on the algo, a 1500 cclock setting in Windows (to get to 1400 effective for example) may require a 1600-1700 setting in Linux for the same result (@ same voltage).  The trade off is while in Windows a too aggressive cclock overshoot generally caused a crash/hang on load transitions, I do not see the same problems on Linux.

Also, fyi a ~1400 effective cclock is generally achievable with <= 850mv.  950 is really high for almost any algo, unless you’re running mem above 1107 (hint: don’t - it’s not worth it wrt efficiency.)

Considering Vegas should already have been doing 45, those numbers aren’t super credible.

as it says in the new update cl is about stability messing with it in any way is not good

Has anyone tried it on 550/560 cards? Or 580 cards? Changing CL at all crashes everything.

Thanks so much, Eliovp!

ok i did a lot of playing around with this and on hive os with vega 64 i found these to be the best values

rc 45        

faw 19        

ref 15000  

rfc 247

no improvements on cryptonight algos

https://imgur.com/a/28b4I15

Answered on github, will copy what i wrote:


Open source, you can easily add whatever you want ;-)

Cheers!

Even if I can appreciate a generic answer like yours, my post was a direct request to the author to add Polaris cards in the KnownGpus of this tool

@Elivop seems like wtrl is not working hbm2