Discussion in 'Frontpage news' started by Hilbert Hagedoorn, Oct 27, 2020.
you must be confused.
Yeah its there now i can swear it was not there yesterday on gaming x.
Seems gigabyte pulled F11 again Hahaha what a joke Gigabyte is
Seriosly , i posted numerous times that F11 is buged beyond reality.
Well I guess we're skipping that 184.108.40.206 code then. (EDIT: Meaning Gigabyte. )
Not bad though, all the fixes and the newest AGESA AMD code is optimal long as nothing regresses or breaks after all.
Presumably once the X570 beta builds here are deemed stable enough the B550 motherboards should follow along with the 400 and 300 series for what's still actively supported.
Also not sure how it compares to F32A 220.127.116.11 but I assume this has been worked on a bit more so there could be additional Gigabyte fixes included even if the AMD AGESA code might be identical.
(A likely one would be further USB2.0 fixes though it sounds like it's not fully resolved still.)
Thanks that’s the one I’ve been waiting for F32 is same notes as F31 was I want 18.104.22.168
So how's F32? Anyone here with x570 Aorus Elite?
Gigabyte just posted F12 bios ... don't know if i even should try it as it is still OLD AMD AGESA ComboV2 22.214.171.124 D.
So no hope for 1900-2000 FCLK .
32a did have 126.96.36.199, you needed the one from the 13th, the testing bios.
Tried it took away the 500mhz PBO and back to 209Mhz gone back to F32
F33a available for x570's and finally 188.8.131.52.
Yeah it looks like a number of bios updates are out for Gigabyte and the 300 and 400 series now though it might just be the final version of the previous beta that is now posted on various sites.
No issues so far on F33A here but going by updates from MSI and Asus there might be more to come looks like there's fixes to RAID and some other bits which I would think are part of the AGESA code.
(Fifth or fourth update for 184.108.40.206 on these motherboards now I think might have started on 220.127.116.11 though before moving to this newer code.)
Guess that will be clear if there's a F33B update with additional fixes unless it's for some Gigabyte's own code and specific problems on their hardware.
B550 bios should also eventually be updated and from there the code for the 400 series at least since AMD did change their decision and the updates and Zen3 compatibility improvements with the newer code should be quite useful on all support boards.
Yesterday updated to F12 , mess again . If you enable Resize bar you end up :
1. No boot from M.2 (if enabled above 4g encoding).
2. No display output ( 4g encoding disabled).
Maybe F16 or F22 will be good BIOS . Asus would have been better option this round .
I'm not sure if i will ever get SAM support .....
Your boot loader is legacy or CSM is enabled.
Hmm was expecting another beta for the X570's first but maybe Gigabyte is satisfied with their own and user reported testing for F33A or AMD hasn't provided any newer builds for them to integrate into the bios yet.
EDIT: Once this version is wrapped up hopefully that takes care of the more important outstanding Gigabyte motherboard bios issues and the AGESA and related (AMD Boot loader.) problems that have been ongoing for a while now.
Some of it might be hardware level though, not really sure if it's a faulty revision or a subset of these boards that have some of the more severe issues like faulty bios that resets to defaults if you don't take the battery out and power the board down completely for a few minutes.
Realtek is trying to mitigate the 2.5GB network chipset issues with a software driver and the USB2 issues I presume are AMD's problem though the 3.0 and up ports seemingly work fine.
There's a key binding for controlling the UEFI bios resolution??
F6 does show bios resolutions, I'm unsure how to select them other than ctrl alt and f6 does down Res it just once.
Odd bios, crap motherboard tbh, thinking of switching to an x570 formula
Guys just wanted to inform that new F13a BIOS is up and lets me boot 2000FCLK
Actually 1966 is faster than 2000 and i have no idea why.
33b dropped like its hot today.
Also F13B for the B550's but no actual changelog besides AGESA 18.104.22.168 again.
Presumably either minor bug fixes then unless AMD provided a newer build of this code though I believe they usually change the version number or denote it in some other way like the Patch A to C earlier.
Wonder if they can get rid of WHEA errors. It's weird because FCLK 2000 seems stable but i get alot of WHEA errors.
Then its not stable. Dial back down to 1800 and 3600 ram.