Friday, March 12th 2021
AMD Fixes Intermittent USB Connectivity Issues on 500 Series Chipsets, BIOS Update Arrives in April
AMD has four weeks ago acknowledged that there was a problem with 500 series motherboard chipsets. The problem has occurred with a few chipset functions like USB connectivity, USB 2.0 audio crackling (e.g. DAC/AMP combos), and USB/PCIe Gen 4 exclusion. To fix these problems, consumers were forced to either put up with problems or lower the PCIe standard from Gen 4 to Gen 3 and switch USB protocol revision from 3.0 to 2.0. This of course wasn't the ideal solution, especially for bandwidth-heavy applications. Users have submitted many reports to AMD, and the company appears to have found a root cause of these issues. AMD has published a Reddit thread, that reports that the company found a solution to the problem and that we are going to see a fix for it in a form in AGESA BIOS update.
Source:
AMD Subreddit
AMD RedditAMD has prepared AGESA 1.2.0.2 to deploy this update, and we plan to distribute 1.2.0.2 to our motherboard partners for integration in about a week. Customers can expect downloadable BIOSes containing AGESA 1.2.0.2 to begin with beta updates in early April. The exact update schedule for your system will depend on the test and implementation schedule for your vendor and specific motherboard model. If you continue to experience intermittent USB connectivity issues after updating your system to AGESA 1.2.0.2, we encourage you to download the standalone AMD Bug Report Tool and open a ticket with AMD Customer Support.
107 Comments on AMD Fixes Intermittent USB Connectivity Issues on 500 Series Chipsets, BIOS Update Arrives in April
Obviously an annoying issue for those that experienced it, but it was clearly not a hardware flaw as some seemed to suggest.
The REAL question is (IMHO): why this was not discovered & fixed PRIOR to release ?????
Who can old tech, there is second hand market!
AMD should have just released a X670, B650 motherboards with ryzen 5000 series..
Few, if any, manufacturers are going to implement USB 3.0 on any device if said device doesn't need the extra speed/power.
Everything else, probably same story or it's so ingrained somewhere that removing it brings far more headaches.
I mean, it's not as if Intel haven't had their fair of issues over the years.
In fact, at one point, SiS made a better chipset for Intel than Intel did, not long after Intel banned third party chipsets.
What does I/O and physical interfaces have to do with it?
If you have an issue with drivers, take that up with Microsoft. Most drivers are tiny in Linux.
PCIe is a backwards compatible technology by design. Ethernet doesn't cause any known issues. USB is in every single modern computer.
Sure, we can get rid of VGA and DVI, but considering that most VGA ports today use a D/A chip and takes a digital signal from the GPU, it's hardly an issue.
DVI uses more or less the same standard as HDMI, so should we get rid of HDMI too then?
COM ports might not be useful to you, but the serial bus is still used in a ton of devices. It's not something that's going to have a detrimental effect on the system.
Sure, tidy up the code, but that's not the same as getting rid of still widely used standards just because you don't like them. Can you please provide proof of this?
There seems to be a fair amount of issues with Intel these days too and always have been.
Shit, Intel used to make some horrible motherboards back in the days. Why? What new technology could they possibly have added that would've made sense?
And if this is a USB issue that is not exclusive to the 5000-series CPUs or the two (by two different companies I should point out) 500-series chipsets, as it clearly affects the 400-series in some cases as well, what use would a new chipset have been? Please enlighten me.
I was on socket 1366 for 10 years and now AM4 1 1/2 years and this platform is just as stable as my previous intel rig.
The truth is that AMD has rushed out their platforms and as an early adopter on the first gen Ryzen and the third gen Ryzen platforms I can honestly say there have been issues.
Have they been fixed? Yes, but it did take about three months each time to get the platform to where it should've been at launch.
Part of the reason here is that AMD is a much smaller company than Intel and doesn't have the resources Intel have.
At the same time, AMD put too much trust in the ability of the board makers, who are used to get finished reference platforms from Intel to base their own designs on.
AMD turned up with a tray of chipsets and said call us if you're having any problems.
So yes, AMD can do a lot better, but considering the resources Intel has and the way they do things, shouldn't their platforms be flawless at launch in comparison then?
At least that's what it sounds like here.
It feels like a lot of people like to throw some crap out on the internet because they think they know something.
I spent over a decade of my life as a tech journalist and I started back in the days when you had 20-odd motherboard manufactures to choose from and 6-7 chipset vendors and at least four x86 CPU manufacturers.
I remember testing the first DDR 133MHz capable chipset from VIA with a stick of some crap RAM they sent along. I could never get that stick of RAM working and they could never figure out why.
I remember testing the first ATA-66 controller from Promise, turned out the company that supplied it hadn't been given the latest firmware update for it, so I spent three days trying to get it working, when in fact, it couldn't work at ATA-66 speeds.
I mean, this is nothing new or unique, but if all it takes is a firmware/BIOS/UEFI update to fix the problem, it's really not a big deal.
When you have to a hardware recall, because something i borked on the hardware side, that's when you have serious problems.
I cannot recall any stability issues from any other build I've done in the past with AMD or Intel. I can say that I've experienced some performance loss when they released software patches for security issues on my last Intel build. Sure, it wasn't a stability issue, but apparently a glaring enough security risk that the patch actually hindered performance some.
Neither company is without their faults. It's a good thing when they are able to fix the faults and the consumers can continue to utilize the hardware as needed. Why one needs to blast one company over the other, that just seems childish.
Mind you, they both ended up as excellent chipsets, but the initial problems is something Intel managed to avoid. Was that the chipset that employed a crossbar-switch design? My memory is failing me.
Yes, the KT266 had an issue with AGP 4x, but I don't know what the KT400 was supposed to suffer from.
It was back in 2003, I worked at MSI in the UK at the time. It must've been the SiS 655 which had dual channel RAM. Unfortunately it's so long ago that I can't find any reliable benchmarks...
But yes, it was a bit of a one off from SiS, but it showed that Intel could face some real competition on the chipset side of things. I don't think he did, it looks like he blamed VIA for VIA's mistakes.
AMD put out some terrible chipsets, the 750 chipset was a turd for example. I mean, not even MSI (or possibly Biostar, too long ago) wanted to put their name on the first board with the 750 chipset.
Then Asus finally brought one out and things improved a bit, but AMD would've been screwed back in the day if it wasn't for Nvidia and VIA and to a lesser extent ALi and SiS.