Author: Xaltar
Subject: Ryzen 3000 series support
Posted: 13 Aug 2019 at 4:00am
Guys, how many AGESA codes have been released in beta since Ryzen 3000 launched?
If it were just one and your motherboard manufacturer was lagging behind or had issues when no one else did then by all means, blame the manufacturer of your board. That however is not the case, there have been several AGESA codes released by AMD and most have not fixed the issues everyone is having, some are even breaking more than they solve. Don't get me wrong, there is certainly an issue but blaming motherboard manufacturers (I am not even being specific here) when boards have worked fine for months if not years prior to Ryzen 3000 is uncalled for.
Ryzen 3000 support is still buggy for a lot of users, not just on ASRock boards. My contacts at ASRock have informed me they are hard at work trying to implement every new AGESA to fix issues for everyone and the fact that we are seeing frequent beta BIOS releases every time a new AGESA drops means they are doing all they can. AGESA is not a plugin to the BIOS, it is the heart of the BIOS around which all the rest of the specific code for a particular board must be built from scratch. This takes time and worse still, just as testing of one is complete and it is ready for launch, there is another AGESA drop and the process begins anew.
Now I get it, you are frustrated and it feels like nothing is being done but rest assured, everything that can be done is being done. Bare in mind that for every one of you reporting an issue there are thousands of other users that have no problems at all. This is the ASRock community forum, people with issues congregate here. If everyone with an AM4 board had issues I assure you, this forum would be exploding with complaints.
I created this thread to help users find new BETA BIOS releases and help each-other out as well as to provide ASRock with a running tally of current issues vs issues solved with each new AGESA iteration. AMD is pushing hard to get their AGESA sorted and every board partner is rushing twice as hard to push their updates out, not to a single BIOS but to every single board model on the AM4 platform. This thread is not for lamenting your purchase decisions or throwing shade. Keep this thread helpful guys, I would hate to have to lock it because people are more interested in making a scene than they are being helpful and productive.
AMD is attempting to tackle a rather large logistical issue and they are doing it because they promised to keep AM4 as compatible with each new generation as possible. The fact that they have dropped gen 1 support from 500 series boards should give a clue as to how difficult this is proving to be for them. With every possible hardware config out there they need time to work out all the kinks. I don't like it either, I have 2 systems of my own more or less out of commission while I wait for fixes.
Stay calm, stay friendly.
Edited by Xaltar - 26 minutes ago at 4:04am
Subject: Ryzen 3000 series support
Posted: 13 Aug 2019 at 4:00am
Guys, how many AGESA codes have been released in beta since Ryzen 3000 launched?
If it were just one and your motherboard manufacturer was lagging behind or had issues when no one else did then by all means, blame the manufacturer of your board. That however is not the case, there have been several AGESA codes released by AMD and most have not fixed the issues everyone is having, some are even breaking more than they solve. Don't get me wrong, there is certainly an issue but blaming motherboard manufacturers (I am not even being specific here) when boards have worked fine for months if not years prior to Ryzen 3000 is uncalled for.
Ryzen 3000 support is still buggy for a lot of users, not just on ASRock boards. My contacts at ASRock have informed me they are hard at work trying to implement every new AGESA to fix issues for everyone and the fact that we are seeing frequent beta BIOS releases every time a new AGESA drops means they are doing all they can. AGESA is not a plugin to the BIOS, it is the heart of the BIOS around which all the rest of the specific code for a particular board must be built from scratch. This takes time and worse still, just as testing of one is complete and it is ready for launch, there is another AGESA drop and the process begins anew.
Now I get it, you are frustrated and it feels like nothing is being done but rest assured, everything that can be done is being done. Bare in mind that for every one of you reporting an issue there are thousands of other users that have no problems at all. This is the ASRock community forum, people with issues congregate here. If everyone with an AM4 board had issues I assure you, this forum would be exploding with complaints.
I created this thread to help users find new BETA BIOS releases and help each-other out as well as to provide ASRock with a running tally of current issues vs issues solved with each new AGESA iteration. AMD is pushing hard to get their AGESA sorted and every board partner is rushing twice as hard to push their updates out, not to a single BIOS but to every single board model on the AM4 platform. This thread is not for lamenting your purchase decisions or throwing shade. Keep this thread helpful guys, I would hate to have to lock it because people are more interested in making a scene than they are being helpful and productive.
AMD is attempting to tackle a rather large logistical issue and they are doing it because they promised to keep AM4 as compatible with each new generation as possible. The fact that they have dropped gen 1 support from 500 series boards should give a clue as to how difficult this is proving to be for them. With every possible hardware config out there they need time to work out all the kinks. I don't like it either, I have 2 systems of my own more or less out of commission while I wait for fixes.
Stay calm, stay friendly.
Edited by Xaltar - 26 minutes ago at 4:04am