All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206351] RX 5600 XT Not Correctly Recognized, Max Memory Frequency Below Where it Should Be
Date: Thu, 30 Jan 2020 18:52:51 +0000	[thread overview]
Message-ID: <bug-206351-2300-CCsIG0Dtmf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206351-2300@https.bugzilla.kernel.org/>

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

--- Comment #3 from Matt McDonald (gardotd426@gmail.com) ---
This is the card and its specifications from the official website:
https://www.sapphiretech.com/en/consumer/pulse-radeon-rx-5600-xt-6g-gddr6#Specification

As you'll see, memory clock is supposed to be 14Gbps on the new vBIOS, which is
equal to 1750MHz, which is exactly what GPU-z reports on Windows (as does every
other piece of GPU monitoring software like MSI Afterburner and Radeon
Wattman). And if you look at the specs for the card with the old performance
vBIOS, it was 12Gbps effective which is 1500MHz, and again GPU-z and every
other windows utility correctly reports this. Also, Linux correctly reports
memory clock frequency for older cards like the RX 580, my XFX GTS XXX model
was correctly reported at memory clock boosting to 1750 MHz

However with the 5600 XT, even with overclocking enabled, the powerplay tables
range is only 930MHz at the maximum end.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-01-30 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30  9:24 [Bug 206351] New: RX 5600 XT Not Correctly Recognized, Max Memory Frequency Below Where it Should Be bugzilla-daemon
2020-01-30  9:31 ` [Bug 206351] " bugzilla-daemon
2020-01-30 18:12 ` bugzilla-daemon
2020-01-30 18:52 ` bugzilla-daemon [this message]
2020-01-30 21:21 ` bugzilla-daemon
2020-01-31  1:46 ` bugzilla-daemon
2020-01-31 18:00 ` bugzilla-daemon
2020-01-31 18:28 ` bugzilla-daemon
2020-01-31 19:26 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-206351-2300-CCsIG0Dtmf@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.