Aurora R10, failed CPU upgrade from 3700x to newer 5600x

I would guess the fact that they are selling the R10 with the 5000 series chips (as opposed to rolling out an R12) suggests there's a strong likelihood that a BIOs update might get posted soon.   Also, if you check the comments section, someone mentioned contacting Dell about it and being told to check back in a couple weeks. 

I wish someone with the R10 5 series would post some photos of their BIOS menus.

Looks like a new Bios was released today (2/18/21) version 2.1.1. Can anyone confirm if they're able to upgrade their R10 to a 5000 Series CPU using this Bios?

I have an R10 on the way with a 3700X and a 3070, but was able to snipe a 5600X and I'd like to know if I'll be able to upgrade my 3700X to the 5600X or if I'm better off just selling the 5600X.

Can't confirm anything, but the update notes reference the 5000 series. On the other hand, people who purchased the R10 stock with zen 3, those PC's shipped with the 5000 on v. 2.1.0.  

Yeah, the R10 uses B550A (which is a B450 rebrand) and supports the 5000 series with the required update. 

I installed this bios on a "pre" Ryzen 5000 series R10.

Mine came with a 3700X.

This bios still shows as Agesa version 1.0.0.6 on my system.

As per AMD you need minimum Agesa version 1.1.0.0 on an AMD 500 series motherboard to be able to support a Ryzen 5000 series processor. My understanding is the R10 is a 500 series motherboard.

https://community.amd.com/t5/blogs/prepping-your-motherboard-for-the-amd-ryzen-5000-series/ba-p/414274

I guess what we need is the Agesa version of the "New" R10 from someone who has one, to see what Agesa version they run.

One other thing I noticed about this bios update is that upon getting to the windows 10 log on screen, windows said the security settings on the machine were modified and I had to perform the steps below to log into windows again. I use a PIN code to log into my desktop.

1. Login to my Microsoft account with that accounts user name and password.

2. Since I have 2 factor authentication enabled for that account, enter the passcode send to my phone.

3. Pick a new PIN code for my windows logon and confirm the new PIN. (it allows you to pick your old one).

The same thing happened to me when I updated and downgraded to the previous version of the Bios, so I am assuming it's normal behavior for an Alienware.

On what Agesa version? 1.0.0.6 or a higher version?

@Vanadiel  Yeah, I don't know this is normal or not, but me happen as well 

@Vanadiel Well! Are you sure the BIOS AGESA version still 1.0.0.6? after you upgrade the latest Version 2.1.1 release today?  

If it is still 1.0.0.6, really terrible things for the old R10.

Every BIOS update has reset the pin for me.  Same steps, but I put the old pin back in and it doesn't kick it back.

What I noticed during the bios flashing process is that when it is writing the actual data to the flash ram, it sometimes goes fast past some blocks, and slows down on some other blocks.

Therefore I am thinking that while it's a bios update, it's not rewriting the complete flash ram, only certain sections.

I am thinking it's skipping updating the Agesa version, and the new R10 ships with a different Agesa version from the factory than the old R10.

It would also explain why both R10 models can use the same bios update file, yet a different Agesa version.

Unless HWInfo is reading my Agesa version incorrect (doubtful), there's no way mine will support a 5000 series processor. For that I would need an Agesa update, which has to come from a bios update.

Would be nice if we could get some info from a user who has an r10 with a 5000 series processor, to see their Agesa version and verify they use indeed the same bios flash as me to update to 2.1.1.

Than we can confirm support is currently being disabled for series 5000 processors on the old R10, and only enabled on the new R10. Could be a different revision of the R10 motherboard, would require further analyzing.