So here it is..

amd is trying to act like nvidia.
promise, underdeliver, deliver, reach up to hype, update, increase performance,
in all of the steps they are playing for the marketing, it is simple as that.

The fact that this wasn't present from day 1 shows how much of a panicked rush job this product is.

XXL_AIamd is trying to act like nvidia.
promise, underdeliver, deliver, reach up to hype, update, increase performance,
in all of the steps they are playing for the marketing, it is simple as that.

Few years back AMD released Catalyst 12.11 drivers, which boosted all HD7xxx GPUs' performance even up to 10%, just by pure optimization. I wish something similar happened now with Vega II.

the majority of cards sold will have this installed from the factory, just a f*ck up for the initial batch i guess

XXL_AIamd is trying to act like nvidia.
promise, underdeliver, deliver, reach up to hype, update, increase performance,
in all of the steps they are playing for the marketing, it is simple as that.

same shit different bowl

Musselsthe majority of cards sold will have this installed from the factory, just a f*ck up for the initial batch i guess

... or most likely the only batch. I doubt they can afford selling Instinct cards rebranded for consumers any longer.

I dunno, is it possible that Instinct cards aren't selling that well &/or AMD are seeing high failure rates - hence the Radeon VII almost as an afterthought?

You're talking about UEFI or Secure boot? many gamers don't use secure boot and It's disabled by default.If it was non-UEFI , Many reviewers would report it.So your title should change a bit.

one explains this :

This headline statement is a blatant lie.

Anybody who owns RVII and runs UEFI without CSM enabled can confirm & prove that it boots & works perfectly.

Furthermore CSM is disabled by default on all modern boards so if it had been a problem we would have encountered it already in the day-1 reviews.

This is an agenda driven post (either by TPU or the OP, or both), which I wonder why the mods allow to be spread, while other users get their posts deleted to point out a spammer (see in comment section) while the spammer himself unobstructedly continues to post his trash over months now.

These articles are being spread by certain individuals to obviously farm for AMD bashing in forums and on reddit.

It's a post made to smear the image of AMD and it's all the same usernames that come here and leave their rubbish in the comment section. It's telling that NV has to resort to such corrupt marketing methods to try to sabotage their competition. I wonder who will once and for all put an end to this practice.

This article is a lie - The readout means nothing. The people who interpreted this as "no UEFI support" have no idea what the prerequisite for UEFI compatiblity are.

TLDR :
it's a missing info-flag , nothing else. they flash another bios with the flag and call it "FIXED" ... laughable.

the card has UEFI support & capability regardless if that info-flag is set or not.

it's like saying your coca cola has no part water in it just because the labelling machine "forgot" to print it in the ingredient list. and then you write water on the can and pretend only because you wrote it , it now contains water and didn't before. *FACEPALM*

also for the people who don't know anything about this topic (in terms of certification etc.) - read:

docs.microsoft.com/en-us/previous-versions/windows/hardware/cert-program/windows-hardware-certification-requirements-for-client-and-server-systems

So it has UEFI working, just some flag shows that it doesnt to certain programs?

TPU does have a habit of updating our titles/news posts when new info becomes available...

No. That is NOT correct. The UEFI GOP image(AMD GOP version 2.5.0.0.0 to be precise), which provides UEFI GOP functionality, was missing from the original BIOS. And was added by ASRock via their BIOS update first(which was brought to my attention yesterday). Now...not to toot my own horn. But TOOT TOOT!!! I know exactly what I'm talking about here. I performed the investigation personally and confirmed all of that information as a stone cold factuality(which I can prove with evidence if required). As well as discussing it with other experts on the subject who's findings corroborated mine. Just to be 100% sure I wasn't mistaken.

TLDR:
That dude obviously has no clue what he's talking about. Lucky guess on the "flag"(which I'd bet a million $ he has no idea where to even find, or much less how it's set). Total BS on UEFI support and capability with it set or not. If the correct "flag" bytes aren't set, UEFI functionality is disabled, regardless of whether or not the BIOS has a UEFI GOP image. If the BIOS has no UEFI GOP image there will be no UEFI support and capability even with the correct "flag" bytes set.

Yes, the card will boot without a UEFI GOP image(or with a deactivated UEFI GOP image) in its BIOS, and UEFI functions "enabled"(and/or CSM disabled) in the motherboard's UEFI/BIOS. So long as those enabled UEFI functions are NOT Secure Boot. With Secure Boot enabled and no UEFI GOP image(or one that's deactivated) in the card's BIOS you are not booting with the card. Period. And...even though you CAN boot without a UEFI GOP image(or with a deactivated UEFI GOP image) and Secure Boot disabled, all other UEFI functions(if enabled in the motherboard's UEFI/BIOS) will fail to operate as well(fast boot etc.). Just because it boots doesn't mean it's working as intended. Do your own research/experimentation(as I've done extensively) and you will find that to be true. ALL UEFI functionality requires the UEFI GOP image in the card's BIOS to be present and activated(via the "flag").

Strangely Sapphiretechs list UEFI support for their cards? www.sapphiretech.com/productdetial.asp?pid=653DD044-C784-46AC-AFF4-84881431E725&lang=eng see specifications

jesdalsStrangely Sapphiretechs list UEFI support for their cards? www.sapphiretech.com/productdetial.asp?pid=653DD044-C784-46AC-AFF4-84881431E725&lang=eng see specifications

Easy to check if you have one at hand. Dump the vBIOS in GPU-z and check at offset 0x0000E630.

BTW, AMD has released an update:
www.amd.com/en/support/radeonvii-vbios-eula

GOP section is present:


EDIT: LOL. I've just cut the BIOS out of AMD installer and it is 100% identical to AsRock, so if anyone already flashed the AsRock vBIOS, don't bother downloading one from AMD (or vice-versa).