{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by HanSoloUlt:
7/19/2019 1:15:27 PM
8
AMD pulled back the fix for D2/Linux issues due to a bug. Could Bungie fix D2 issues with Zen 2 processors?
It has been 12 days since Zen 2 CPUs launched. AMD launched a fix and distributed it to vendors last week but it was pulled back due to a bug.
[url=https://rog.asus.com/forum/showthread.php?112003-Latest-C7H-BIOS/page4#post777109]From Asus forums[/url], here is the direct quote
[quote]we just got told to pull (was undergoing validation prior) 1003 ABA version: "... found that PCIE speed of BXB-C downgraded from gen4 to gen2,..." so its not surprising that bugs emerge since the source has hidden bugs that only gets unraveled with thorough testing. combine that with trying to get firmwares out in a tight time frame, kinda damn if you do (release f/w quickly) and damn if you dont (dont release fw quickly) situation[/quote]
[url=https://old.reddit.com/r/Amd/comments/ceuy6x/asus_released_new_bios_version_2501_for_some_b450/eu59l27/]From Gigabyte[/url]
[quote]1003aba, as shamino indicated, has been pulled. We are all waiting new code to test / implement.[/quote]
It is almost the weekend again so the new AGESA version probably won't get to vendors at least till Monday. Even after distributing the fix to vendors, vendors probably won't implement it anytime soon since some of them are working on fixing the compatibility issues with older gen motherboards that won'e even boot. I say this because they were given a fix on last Friday, no one implemented it in any of their BIOS till yesterday and fix was pulled back.
Is it possible for Bungie to fix this issue from their side?
-
2 RepliesAny update on problem being resolved or are we still going up a creek without a paddle? Been itching to play D2 on this new setup!
-
4 RepliesCame here to post this as well. My new build has been sitting on the table collecting dust over the past week. Destiny 2 is pretty much the only game I play, and so I cannot switch to the new build until this is fixed. I know it's partially my fault for not waiting, but am hoping Bungie can help with a patch on their side. The Ryzen 3000 launch was pretty big, and it sounds like a lot of people are affected. It especially sucks for those who did a partial upgrade and are now stuck with a single rig that can't play D2.
-
1 Replyits ok now with amd 3000 processor ?
-
1 ReplyIt is possible for them to fix it, yes, and it would be possible to fix it with a tiny patch in a day. That's not some sort of hubris. They're making an unnecessary hardware call that could be done *much* easier by calling OS/platform-provided functions, which is what they should have done in the first place.
-
2 RepliesYeah this is disappointing to say the least. I really hope it gets resolved soon. I really hope bungie is just able to fix it on their end faster than having motherboard manufacturers roll out BIOS updates for every new motherboard.
-
The issue is two-fold but can be resolved by either AMD or Bungie. Since AMD has announced that they are "fixing it" I doubt Bungie will commit resources to it. AMD had released a microcode update to motherboard manufacturers but has since pulled it because of a flaw. https://www.tomshardware.com/news/amd-buggy-agesa-1.0.0.3aba-microcode,39974.html It sounds like it could be a while before Ryzen 3000 series gets a fix to play Destiny 2. In my experience, it usually take 6-8 weeks to get fixes like this. AMD has yet to provide a working bios update then manufacturers have to build it into a new bios, test it, and deploy it to us. It might be a while.
-
6 RepliesNo, because its all AMD's fault, they worried about getting fast and powerful to catch intel that they dumped absolute stability. D2 isn the only game choking on Ryzen right now. This launch has been a disaster
-
25 RepliesIf the issue is at the BIOS level, a game patch is not going to fix it.
