[Bug 206351] RX 5600 XT Not Correctly Recognized, Max Memory Frequency Below Where it Should Be

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=206351

--- Comment #7 from Matt McDonald (gardotd426 at gmail.com) ---
Ahhh I understand now. So, just to recap and make sure everything is covered...

- The new firmware for the new vBIOS is in QA right now but available for
download (which I've tested, it seems to work for me).

- The Memory clock is correct, but it's the true clock and not the effective
speed

- The marketing strings required for the card to properly be recognized (and
recognized as a 5600 XT as opposed to a 5700/5700 XT) for Vulkan/OpenGL/etc.
are currently being worked on/added?

- This wasn't mentioned in the initial report but I'm assuming the lack of
memory voltage reporting is just an aspect of Navi? For example, Polaris cards
provide a core frequency and a voltage for both the memory and core, but with
Navi it just provides a vddc curve (which is for some reason listed as 0mV for
every state), but I've heard this is just down to Navi. Is this true, or will
we at some point be able to see (and potentially set) voltages for memory (and
individual core states)?

- And finally, there are some rendering issues in certain games that did not
exist with the same drivers with my Polaris card (even with the new firmware).
Are these bugs that should be reported to Mesa, or the amdgpu kernel devs?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.