The straps do not work on Radeon Vii thats why you're getting that error, its not supported. You should try running the intensity tricks on the miner vs straps.

Yes I'm checking this card, but I need a few days to see what hashrate it can achieve.
[/quote]

Any update friend? We are sitting on the edge of our seats!  Is there anything anybody can contribute to help you out with this process?

Did you try the washer fix for cooling on your card if you have one?

you need to have the two dll's in the same directory as the amdtweak tool and that will resolve that. they are built in the download.

Its similar yes. But if you're running phoenix miner, or some other windows based miner, you'll need to use the amd tweaking tool. or start the claymore miner with the strap and rxboost enabled then start the other miner you want with claymore paused as long as you pause it before it starts hashing the settings will stay for the other miner.

I would not run both Amd tweaking and Claymore 14.x together. as the are both accomplishing the same thing. use the command line in your start.bat file for claymore to set your memory and core clock settings as well as the voltages.

As with the AMD mem Tweak you can set the core voltages and memory/core clock speeds as well. they will overwrite one another if you run both.

As both applications temporarily overwrite the existing BIOS timings/strap settings until you reboot.

Use the .23 or later version of the tool. just set your memory and clock settings and change only the REF and i was getting 30 to 32Mhs.

I run the Claymore 14.1 and 14.0, the differences seem to be the way the card is handling the straps is subtle, but there is a little bit of a difference on the Polaris cards.

Our group is seeing some cards that have not as good of memory, with settings that work great in 14.0 are having throttling and blue screen issues on 14.1.

Also experiencing some weird strap errors on one of my Vega's, but it might be my card. It says it cannot apply strap setting to this device.

I am seeing the Polaris on the cards running much better on 14.1 when the memory is good.
I had a card go from 31.2 to 31.5 for my Sapphire 590. and my 570 went from 30.68 to 31.2 mhs. Running at 2250 strap and 850 core voltage.

Make sure when you set your straps, and if you have different cards or memory types, I strongly suggest using the command line to control your voltage & clock speeds via cclock, cvddc, mclock & mvddc.

I have experienced and seen other members with the cards on 14.1 and 14.0 act differently So you may need to manually setup each card this way. Only use the Wattman Tool & afterburner tools to control your fan speeds, until or unless Claymore states that he has resolved the fan control API issue.

We did have a couple members get their Vega 56's and 64's clock in 48Mhs to 50 Mhs but i was unsuccessful but i have issues with my cards.

With 14.0 and you have a mixed environment, do your -di 0,3 - if your RX are on card ID 0 & 3 then do after your strap code -di 0123, this actually will re assign port addresses to your cards. I had to do this with one of my rigs that is a  mixed Polaris / Vega. The Polaris will be come id's 0 & 1 then the Vega's became 2 & 3 instead of 0 & 2.

One question i have is, on the Polaris the strap tells you the POL8H1 - meaning Polaris 8 GB with Hynix memory as very helpful and informative, however the Strap does not provide any information as to its settings or card information with the Vega series. Is there a way to have the line display more information or is it a limitation of the driver?

With the AMD Tweak tool i was able to get my 570 to run at 2300 Strap but on the Claymore it clearly is cap'd at 2250. Any suggestions? 2300 will get a 570 to 32.1 Mhs.

I also wish we could hammer home to everybody, with the memory strap being controlled by the Miner, REGARDLESS if you've modded  your bios or not. The strap timings will be the same. As all the BIOS mod was doing was modifying the strap timings.

I know this post is all over sorry answering questions and posing a few while i'm at it.

Eliovp - can you possibly add a version somewhere on the gui?
I know its a pain, but I am looking at multiple version and comparing things and i get lost.

Thank you!

You also fixed the refresh bug!!

sweetness! Thanks Eliovp

OK i'm kinda half awake here.. played with this all night and got 45 min sleep going to update my current settings and try to get some rest see if they can run longer now.

Thank you again. Loving this tool

IF You have an on-board video device or a non AMD card in your system you will get those errors.
The GUI is based off of Overdrive N Tool code. As a result it will ONLY work with an all AMD environment.

I am not sure if Eliovp has a solution to that particular issue, so for now as you get to test and run your settings be sure to disable your onboard adapter and run your system  with 2 cards, 1 to  view your screen and the 2nd to test and configure your settings.

ALSO A MUST HAVE this link
https://www.overclock.net/attachments/47806

That is the R_timings program you need.  You will also need the Polaris BIOS tool.

You can then read the BIOS and get the timing straps and use Power shell to convert that timing to the appropriate settings.

There are a few things that are incorrect in the GUI. Such as the following:
Under the CAS Timing. - tR2R is actually TCCDS / tCCLD is actually TCCDL

In your timings settings you will NOT get an RAS setting.
In your timings settings you do not need to configure ALL the settings you can simply configure the
RMG Timing, CAS timing, RAS timing, Misc Timing, and Dram Timings.


You will also note that on the bottom right there is a Timing level setting.
Default (0) - will get you 18 to 20 mhs
Level 1 - 21 to 25 mhs
Level 2 - 27 to 30 mhs

SO you will want to set your timing level to 2.

As for your memory and core settings that is what you nomrally configure I am still tweaking.
I was able to get 29.921 Mhs with 2300 / 900 / 1175 / 900 I did get a share but it locked up after 10 min.
I am still working on settings but i wanted to take the time to respond to your question and post an update to my findings this evening.

Thank you!

Eliovp:

RX series modifications suggestion?

quick question. The order of the listings vs the order of the timings list is there away you can flip the positions?

when you run a timings Query the order is PMG, RAS, CAS... but the tools GUI goes PMG, CAS, RAS... just curious.

and is there a possible typo on the CAS timings? there's tCCLD however in the query there's tCCDL is this a typo or a different setting?

-------

So far managed to increase stock bios RX 570 from 22.4 to 27.721 via the tool.

After i get above 30 mhs i'll go a head and post my settings.
As 29 to 33.4 mhs is achievable with a 570 via BIOS mod no point in posting things that are less than that currently.

------------

Also dunno if you or anybody else knows.. if you zero out all the P states on the core control it'll actually remove the P state out of Wattman. which is pretty sick I love it.

If you're running the memory tweak also noticing that when you set the P state setting it'll fight you using the Wattman so this tool will replace your management for ALL of your settings.

-----------

Previously i thought you had to setup batch files to run for the cards, which you can do, however you can also just export the settings and import them.
    I understand this is probably stating the obvious, however just thought i'd point it out anyways in case people didn't see it.

However when you import the Fan control settings are blank and you have to put them in manually every time. Can you fix this?
----------
The biggest AH HA moment was when you click the timing level changed it from the default 0 timing level to timing level 1 or 2 the crashing on the card when certain changes were applied stopped occurring. check it out guys.

Once again... Eliovp.. thank you for making such a kick ass tool!!

Sadly the timings need to be adjusted to make the tool work properly. still working on an effective method on this myself. However I can get .6 mhs improvement on Claymore 10.8 Eth. So there's something it will work just need to figure out the strategy still.
I just have so many distractions it keeps me away.

Trying to see what we can get for an improvement w/out flashing the bios for some of the new guys coming into the community. And save the hassle of flashing bios on older cards.
So all the fun.

Thank you for the response!



Thank you!! I will mess with this some more. And post any results. I am trying to simplify some of the newer miners coming process and eliminate the need to flash bios for cards for the newbies.

Loving the tool!

Bestest thing ever! Thank you for ALL your work.

2 questions.
1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.
However with the tool there is no option to actually configure those said timing straps. Do you think this is why people are having issues with Polaris not seeing much performance increase? Thus far the  most improvement our community has gotten is .2 hash on ETH.

2. Can you add a night version? the white is soooo bright when 90% of your windows are set to night mode. LOL

>>Posted by: dragonmike

>> Has nobody ported this to Windows yet?

>> I'd be happy to do all testing myself and share my findings in this and other threads... But I'm not going to install Ubuntu and all that shizzle for that sole purpose. I suck at Linux unfortunately...
________

I've been trying to but my plate is pretty over topped at the moment but it is something I have been working on. Sadly not having luck finding somebody to help so its all on when i can get time.

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"