Comment # 75
on bug 76490
from Maxim Sheviakov
(In reply to Maxim Sheviakov from comment #74) > (In reply to Maxim Sheviakov from comment #73) > > (In reply to Alex Deucher from comment #72) > > > (In reply to Maxim Sheviakov from comment #71) > > > > Hmm, nice point. By the way, is the MCLK kinda divided by four? So, if > > > > Memory Clock is 5600MHz, I'll have to do 5600/4*10000 to get the correct > > > > value? It's like, 120000 value = 1.2GHz*4 = Original frequency = 4800MHz, > > > > right? If that's it, I'll fix my quirk (AGAIN, LOL) and try using 970MHz and > > > > 5600MHz written as needed, 'cause my GPU is MSI R7 370 Armor 2X, and looks > > > > like values in quirk are *kinda* low for it. > > > > > > The mclk values are the actual mclk values. GDDR5 is quad pumped so you get > > > 4x effective data rate per clock. That might be what you are thinking of. > > > > Looks like I get it now. Today I'll try to play with those values and > > experiment with MCLK values, maybe with GPU clock too; if it's good, I will > > let everyone know. > > So right now I'm building a test kernel based on Linux Zen 4.3. Changed > values in my line: from "{... 0, 120000}," to "{... 97000, 140000}", so that > GPU clock is 970MHz and Memory clock is 1.4GHz aka 5.6GHz. Will let you all > know if I succeed in that. Nope, the system is unusable after Plymouth tries to start. Even with 1.3GHz. Looks like it's a dpm error, as on Windows the card is really stable. with those values, even if it's a bit overclocked.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
