Skip to main content

AMD attempts to defuse controversy around RDNA 3 GPUs and ‘broken’ feature

AMD’s new RDNA 3 graphics cards have run into some controversy post-release, and the company has directly addressed a point of criticism raised by the rumor mill.

Namely that Team Red released Navi 31 with non-functional shader pre-fetch hardware (on A0 silicon – we’ll come back to what that means), a theory put forward by hardware leaker Kepler_L2 on Twitter (among others).

AMD told Tom’s Hardware: “Like previous hardware generations, shader pre-fetching is supported on RDNA 3 as per [gitlab link]. The code in question [highlighted by Kepler_L2] controls an experimental function that was not targeted for inclusion in these products and will not be enabled in this generation of the product.

“This is a common industry practice to include experimental features to enable exploration and tuning for deployment in a future product generation.”

In other words, there’s nothing broken here as the hardware leaker suggested, but the relevant code is for an experimental feature that isn’t supposed to be enabled yet (but will be used down the line with a future generation of Radeon graphics cards).

Analysis: Getting it right first time – but what about the graphics driver?

In short, what AMD is saying is that there’s nothing to see here, move along.

This controversy has also been mired in the suggestion that there’s something wrong with the (purported) A0 silicon used in these initial RDNA 3 boards, with ‘A0’ meaning it’s the initial physical version of the silicon from the fab. A1 would be the next (minor) revision (to correct issues found with the first outing), then A2, and so on (with a switch to B for bigger changes, and then C, etcetera – more versions may appear as time rolls on, and honing or additional fixing is applied).

There are a couple of points to note here. Firstly, that AMD hasn’t confirmed that the RDNA 3 cards use the A0 version (this comes from industry sources and chatter on the grapevine; so we must be careful there). And the second point is that the A0 silicon can be – and is – used by chip makers with finished products, it just means that the silicon works fine and doesn’t need a further re-spin – which is actually an impressive thing (the engineers got it right first time, in other words).

Of course, you could argue that AMD might’ve wanted to get the mentioned shader pre-fetching feature working in RDNA 3, but it failed to make the cut, and so now Team Red is calling it experimental, and some folks have indeed asserted this – but obviously we can’t know what’s happened behind the scenes, and this is pure speculation.

Aside from this controversy, there still remains the issue of apparently wonky clock speeds with big variances on the RX 7900 XTX and 7900 XT as highlighted by some other folks on Twitter (and reviewers), as we discussed recently. According to those reports, clocks can vary from something like 2.4GHz to 2.9GHz from game to game.

This could be related to power usage going up, and clocks being lessened as a result, but some observations have been made about similar power draw between these much higher and lower speeds (oddly). It’s difficult to judge what’s going on here, then, at this early stage of the game. AMD has stated that it's investigating the issue with the help of the user who originally discovered it.

And at any rate, broadly speaking, game benchmarks indicate a strong performance in the case of the 7900 XTX compared to its rival, Nvidia’s RTX 4080 – and driver fixes could well smooth out larger clock frequency variations, perhaps. Still, concerns around power usage and boost speeds remain something of a worry, but hopefully, anything wonky is fixable enough on the software front.

Indeed, there’s more than a bit of chatter on the grapevine about how AMD might have rushed out RDNA 3 to meet its long-held end-of-year launch timeframe, in order to prevent Nvidia from dominating holiday sales, and to keep its investors happy. So, it’s entirely possible that polishing the Adrenalin drivers might add a considerable chunk of performance in the near(ish) future.

Releasing a product without the drivers being fully on point is hardly a new situation, of course, but it’s hardly ideal, either; far from it. That said, we suppose the (kind of) good news for RDNA 3 buyers is that their cards could get faster in the next month or two, and maybe even considerably faster. This might lead to a situation where the 7900 XTX really muscles past the RTX 4080, and more ably rivals the 4090 (for rasterization, meaning non-ray tracing performance); but we’re getting ahead of ourselves here.

Source: TechRadar

Popular posts from this blog

Code-generating tools could be more of a security hindrance than help

New research by a group of Stanford-affiliated researchers has uncovered that code-generating AI tools such as Github Copilot can present more security risks than many users may realize. The study looked specifically at Codex, a product of OpenAI, of which Elon Musk is among the co-founders.  Codex powers the Microsoft-owned GitHub Copilot platform, which is designed to make coding easier and more accessible by translating natural language into code and suggesting changes based on contextual evidence. AI-coding problems Lead co-author of the study, Neil Perry, explains that “code-generating systems are currently not a replacement for human developers”. The study asked 47 developers of differing abilities to use Codex for security-related problems, using Python, JavaScript and C programming languages. It concluded that the participants who relied on Codex were more likely to write insecure code compared with a control group. Read more > These are the best laptops for progr

Port of Lisbon hit by ransomware attack

One of Europe’s busiest seaports, the Port of Lisbon, has been hit with a ransomware attack that knocked some of its digital systems offline. "All safety protocols and response measures provided for this type of occurrence were quickly activated, the situation being monitored by the National Cybersecurity Center and the Judicial Police," a statement shared by the Port of Lisbon Administration (APL) with local media earlier this week said. The incident failed to impact the port’s operations, but did take its official website,, offline. LockBit taking responsibility "The Port of Lisbon Administration is working permanently and closely with all competent entities in order to guarantee the security of the systems and respective data," the statement concludes. While the company doesn’t explicitly say it was targeted with ransomware, the LockBit ransomware operator has added APL to its leaks website, taking responsibility for the hit.  The databas

This new Linux malware floods machines with cryptominers and DDoS bots

Cybersecurity researchers have spotted a new Linux malware downloader that targets poorly defended Linux servers with cryptocurrency miners and DDoS IRC bots. Researchers from ASEC discovered the attack after the Shell Script Compiler (SHC) used to create the downloader was uploaded to VirusTotal. Apparently, Korean users were the ones uploading the SHC, and it’s Korean users who are targets, as well. Further analysis has shown that the threat actors are going after poorly defended Linux servers, brute-forcing their way into administrator accounts over SSH.  Mining Monero Once they make their way in, they’ll either install a cryptocurrency miner, or a DDoS IRC bot. The miner being deployed is XMRig, arguably the most popular cryptocurrency miner among hackers. It uses the computing power of a victim's endpoints to generate Monero, a privacy-oriented cryptocurrency whose transactions are seemingly impossible to track, and whose users are allegedly impossible to identify. Fo

Twitter has hidden the chronological feed on iOS again – and I'm furious

In a controversial move, Twitter has brought back a feature that removes the 'Latest Tweets' view for users on iOS, which is something that many users, including me, hated back in March 2022 – and it's now rolling out. The first time the company decided to do this, 'Home' would appear first in a tab at the top, and there was no way of changing it so that 'Latest Tweets' would be the default view. It was reverted back after the company said it was a 'bug' for iOS users. This time though, it's no bug. Instead, it's 'For You' and 'Following' where you can only swipe between them now, which doesn't make much sense for a platform where you're using the platform to keep up to date with who you follow. It's a bizarre change that makes me ask – who wants this, especially during a time when its new owner, Elon Musk, is bringing in and reversing changes almost every week still? This one change will have big consequenc