Quote from: NefariousFool on May 06, 2019, 08:06:44 PM

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!

Hey,

Yeah, i can do that.
There has been a request to add a --version flag to the cli version as well.
It's on my todo list!

For now, you could always check assembly info (right click exe), you can find version info in there.

Quote from: mtrai on May 06, 2019, 08:13:56 PM

@eliovp can you check something tCL does not seem to change anything. This was pointed out by someone else on reddit. Anyhow I tested it, and it does indeed seem to be true. You can set the tCL value to 0, 1 up to 50.

Are you referring to HBM2 or GDDR5?

For GDDR5 i disabled this (for the GUI) on purpose.
You can create a strap for the vbios with tCL being at 24 (decimal) for example and it will work just fine.
Now the strange thing about this is the fact that it should in theory be a value between 0 and 20.

I have to be honest here, i believe programming it on a live system with a value between 0 to 20 might just be possible, it should! , i have only tested this with a default Cas Latency of higher than 20. So that might have been the reason for the GPU to bail on me.
I will look into this in more depth.

For HBM2 you can raise tCL to offer a little bit of extra stability.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)

Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.

In a way, perhaps a bit comparable to the dram values on the GDDR5 side.
These get loaded into the registers and based on clocks, they change.

I wish i had all the answers, but unfortunately, not "yet" Wink

Cheers

Edit:

Quote from: bobymoore on May 06, 2019, 08:34:31 PM

Quote from: kamisama233 on May 06, 2019, 11:39:10 AM

Quote from: bobymoore on May 06, 2019, 09:47:52 AM

I made a good set up for my two vega 56@64,i get 2350 hash each, but my pc lag, stuck when I do anything even when I move mouse, I use red team miner, the amd mem tweak tool, win 10 pro 64,drivers 19.4.1,19.42.

what's your setup, can you share it, and what card you own?

https://i.postimg.cc/zBn5cN3N/Untitled1.png happy mining my friend!thanks to ~~Eviolp~~Eliovp!

Try latest GUI mate, you're using an old version.
You won't need overdriventool anymore, can do it all in the gui.

Cheerio!