The company releases an AGESA microcode that fixes the problem with Destiny 2 and Linux of the AMD Ryzen 3000
Quick response from AMD, which has already released a new AGESA BIOS microcode that fixes Destiny 2 and Linux issues.
Following the release of AMD Ryzen 3000 processors, different issues have appeared. The most important are the impossibility of run the Destiny 2 title and some Linux distributions. Within the latter case, any distribution of Kernel 5.0, 5.1 and 5.2 does not run with the new Zen2 architecture processors. To solve this problem, the company has launched a new AGESA microcode that must be implemented.
Bungie has investigated the issue and it is not a gaming issue, but Ryzen 3000 processors. The issue appears on AMD X570 and X470 chipset motherboards. The company's title is not being executed and that is a pretty serious problem. The task manager indicates the launch, but nothing else happens. You must force close to finish the process.
AMD releases new BIOS to solve the problem with Destiny 2 and Linux
Regarding the problems with the Linux open source operating system, this affects all 2019 distributions. Any version of this OS based on the 5.0, 5.1 and 5.2 kernel has problems. The problem is that the RdRand instruction prevents the system from booting into MAD Ryzen 3000 processors.
The company has said that they are aware of the problems and that they have worked against the clock to fix it. To solve this, they have launched an AGESA microcode that will arrive in future BIOS updates. It will be each motherboard manufacturer who must implement it in the BIOS they distribute.
“AMD has identified the root issue and implemented a fix via a BIOS update for an issue that affects the ability to run certain Linux and Destiny 2 distributions on AMD Ryzen 3000 processors. We have distributed an updated BIOS to our partners. motherboards, and we hope consumers will have access to the new BIOS in the coming days. "
This forces users to be very aware of BIOS updates from manufacturers. We assume that next week or the next, at the latest, we will have this code in some BIOS in beta.
