Their support blatantly lies and hopes to get away with it, betting on their users being stupid enough, because they are too lazy to actually deal with problems.
Long time AMD user, had this problem, MSI support was very friendly and helpful, built even test rigs with identical parts to duplicated and find the problem I had, while AMD just closes tickets or (pic related) lies.
They can definitely flick off if I have to pay for advertised features that I can't even use.
Other urls found in this thread:
reddit.com
twitter.com
Uhm, that's technically the truth. PBO is only officially supported and advertised as a feature of Threadripper, not 2600X nor 2700X. Motherboard makers went against spec and implemented it themselves.
Techpajeet is just going by the official script and can't offer you support on it.
Not OP but you're only partially right
AMD for the most part only advertised TR as BPO capable, even though there's is marketing material from them saying that X gen 2 CPUs support it too
Plus its advertised with the 400 series of chipsets by AMD themselves too, which is obviously not a TR chipset
>They can definitely flick off
Ouchie :(
>uses RAID circa 2019
Get what you deserve
The CPU itself supports these features but AMD doesn't require board partners to.
But wasn't PBO added to Ryzen Master for Ryzen 2000 chips as of many months ago?
Have you tried downloading the latest Ryzen Master?
>flick off
You can say fuck on the internet user, it's okay.
You realize that PBO is part of AMDs own AGESA BIOS code that they distribute to motherboard manufacturers, including 400 chipset
Yes, but it is not an advertized nor supported feature on those chips.
OP here. Yes, PBO has been working for these chips for soon to be a year and it works fine for mine also, but only when chipset RAID is turned off, I turn it on and it breaks. AMD themselves already acknowledged this problem in a previous ticket.
See, that's what I've been thinking, since I've been talking about this problem previously with their support for months. It's only after much troubleshooting together with AMD (and that I still found the problem myself) and after contacting MSI too, when MSI said that it's a problem on the AMD side that this lack of answers started.