Quote from: Remember remember the 5th of November on March 23, 2019, 02:41:48 PM

@OP, can you do me a favor?

Can you cat /sys/kernel/debug/dri/%d/amdgpu_regs for me please? is amdgpu_regs static, or does it change?

Have you tried it yourself? Wink

Quote from: buzzkillb on March 23, 2019, 03:17:44 PM

nice work, taking mining back to the old days of people helping each other, and not being a bunch of greedy bastards! Kiss

Thank you

Quote from: PharmEcis on March 23, 2019, 03:28:30 PM

What I'm able to decipher here is that someone got a just desert served nice and cold and can no longer steal another's glory like it was done last time.

KUDOS on every single fucking front mate!

Time to convert my vega boxes to linux!

Very welcome!

Quote from: Docice on March 23, 2019, 04:22:15 PM

Hi, does it work with rx580?

It sure does.

Quote from: scryptr on March 23, 2019, 05:36:28 PM

Quote from: dagarair on March 23, 2019, 04:58:37 PM

OhGodAnHELIOXlargementPill
(theoriginalgangsta)
Tongue

THE EXECUTABLE IS NOT LIKE THE PILL--

The ETHlargementpill is "full auto", it runs for the 1080ti and is pre-programmed with memory timings. However, the AMDmemtool is very basic and allows the user to apply each memory tweak separately. The user must put his own tweaks in place, and understand the terms and shorthand for each tweak.

This tool is usefull for a user to put together custom timings prior to programming the GPU BIOS with straps. An analogy: like giving a user a stickshift assembly, but requiring the user to bolt it into the manual transmission case and mounting it in the car himself.

The "*.cpp" file compiles readily if the instructions in the README.md are followed. It reads data from my R9 Fury cards with no problem. But, as I do not know the tweaks necessary to improve the "--current" settings, I need to refer to a memory timings manual. The downloadable binary from the Releases page works the same as my own compiled binary. --scryptr

No, true, it's not like "the pill".
It's better.
- You have the option to finetune yourself.
- It's open source
- It's based on data discovered by myself and not someone else. The only person that helped me to write the code is mentioned.
- ....

So no, it's not the same no

Btw, you can run the tool with multiple flags, ./amdmemorytweak --i 0,2,5 --CL 19 --RFC 260 --RAS ... etc

Quote from: ocminer on March 23, 2019, 06:35:35 PM

Expect this tool, maybe super-slightly optimized closed source and with 2-5% dev-fee under some other name(s) soon

There's no "optimized" source possibility here. Exactly as Laik pointed out.

The only thing that could be done is automate the process with predefined timings. Something you can do yourself.
Heck, you can do even better if you take the time to figure them out.

Reading your comment makes me extra happy that i released this open source because 2-5% is in my eyes "theft".

Cheers!