hey stasio can we get an update for X570 Elite to a final stable version or at least an updated version. I'm not sure if its related to this bios version of the latest one but I get a bsod every couple weeks now and the dump file is not able to be created, so I'm not sure what the problem is. Hoping a new bios may resolve some issues, first legit bsod I've had since I bought the board at launch.
Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
can we pretty please get an updated or final build bios for X570 Aorus Elite, thank you so much for what you do here for the community, I've been lurking for years. I've been waiting patiently for a new bios for my X570 Aorus Elite :)
Comment
-
How does this differ from the F14 final on Gigabyte's website?
Comment
-
Originally posted by saereth View Post
can we pretty please get an updated or final build bios for X570 Aorus Elite, thank you so much for what you do here for the community, I've been lurking for years. I've been waiting patiently for a new bios for my X570 Aorus Elite :)
Comment
-
B550 Aorus Elite AX V2 - still F15 not exist :-) Just for fun i make a program to scan bioses hidden from support page...
(nothing serious, just replace end of link "F14.zip", to generated "F[1-?][a-f].zip" in a cycle)
- Likes 2
Comment
-
Originally posted by oschmadi View Post
Have you tried disabling Secure BOOT in the BIOS of the B550M Aorus Pro P? The LSI BIOS/UEFI from older cards (or older Firmware versions) tend to use unsigned UEFI Code, which is then not allowed to start, if Secure BOOT is enabled. Try disabling that and see, if this works.
-I did disable secure boot suspecting such a thing
-the UEFI ROM on the card is the latest version and I have flashed the signed version (by Microsoft)
The problem relies close to this validation indeed, but i believe it is even before. The card gets blacklisted from its Serial Boot Rom. I have analyzed the content of this ROM and it is correct.
It states the SSID Vendor ID and subsystem correctly. They correspond to the card according to SSID reference found here : https://pci-ids.ucw.cz/read/PC/1000/0097
01:00.0 0107: 1000:0097 (rev 02)
Subsystem: 1000:30e0
Flags: bus master, fast devsel, latency 0, IRQ 16
I/O ports at e000 [size=256]
Memory at f7940000 (64-bit, non-prefetchable) [size=64K]
Memory at f7900000 (64-bit, non-prefetchable) [size=256K]
Expansion ROM at f7800000 [disabled] [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=96 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] Secondary PCI Express
Capabilities: [1c0] Power Budgeting <?>
Capabilities: [190] Dynamic Power Allocation <?>
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: mpt3sas
Kernel modules: mpt3sas
01:00.0 0107: 1000:0097 (rev 02)
Subsystem: 1000:30e0
Flags: bus master, fast devsel, latency 0, IRQ 16
I/O ports at e000 [size=256]
Memory at f7940000 (64-bit, non-prefetchable) [size=64K]
Memory at f7900000 (64-bit, non-prefetchable) [size=256K]
Expansion ROM at f7800000 [disabled] [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=96 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] Secondary PCI Express
Capabilities: [1c0] Power Budgeting <?>
Capabilities: [190] Dynamic Power Allocation <?>
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: mpt3sas
Kernel modules: mpt3sas
I have tried other things, having a HP microserver Gen8 at home as well.
-I have removed the LSI SAS2008 (original) from the server and it is recognized by the GB motherboard
-I have put the problematic SAS3008 into the HP Microserver and it is recognized perfectly !
It is definitely the BIOS that is doing a dirty trick to avoid the card starting up. I have tried to mask pin A11 (PCI RESET) as well without success. I then get 0V instead of 0.69V.
Having also tried to mask pins B5 and B6 (SM BUS) I can only conclude that the enumeration uses the JTAG interface to blacklist the card.
Comment
-
Originally posted by g111 View Post
Hi there, thanks for the analysis, it is very interesting. Unfortunately I think your analysis here will fall on deaf ears. There's not many knowledgable people here, just BIOS beggars and other people with issues - there's rarely any real advice or help here other than the most basic of things.
I'd suggest reaching out directly to Gigabyte and ask their support to forward your findings to their BIOS engineer team (if they even have one because it is a joke in the first place) and hope they will implement a fix for future BIOS revisions
Comment
-
I have tried flashing the SBR of the HAB, validated its VPD data with several software. No matter what I have tried the motherboard refuses to enable the card, which works in EVERY other computer and server I have tried. It is definitely a buggy motherboard. Maybe it is down to the chipset but I doubt it. I think something bad is happening with PCIe enumeration in link with Secure Boot. No time to wait for Gigabyte to correct their BIOS. I have to try another product.
Comment
-
stasio
For other Gigabyte TRX Aorus Master Rev1.1 Threadripper users
BIOS FCa was pulled from Gigabyte's webpage - so we now only have one bios update since the board was released FB 2021/09/06 that is now 1 year and 3 months old!
Do you know if anything is in the works to replace FCa or if there will be a bios released anytime soon?
Scott
Comment
-
preferably not 1204A as that's bugged, but not to old as its a B2
this really limiting my chances of testing oc stability for Hydra development not being able to tune voltages for higher flck then 1800
I'm really close to just scrapping gigabyte cause of this, and putting my unify-x b550 in daily instead unfortunately I cant use b550master for rabbit hole ram oc for superPI due to the horrible dual bios without a switch (it is a good board for daily running though, just really sucks for people with cpu's and ram capable of more then 1800flck ;(
A word at least would be nice like hey 1205 is trash and we cant release a version with it and 1206 isn't ready or something
Maybe have a new 1203 with security patches as we wait if we never going to get a 1205 if that's the case
Sorry for the frustration but it is really getting to be that I'm stuck with auto voltages for soc iod ccd as max voltages (cause that causes USB dropouts at 2000 flck ;( (yes chip can do 2000flck fine I checked with 1203 )
Comment
-
AGESA 1.2.0.5 obviously has also issues ....... maybe that's the reason why GB is silent.
ASUS has released a beta with AGESA 1.2.0.6 so far probably GB is waiting for it or testing that already?
https://www.overclock.net/threads/as.../post-28928913
Cheers
Gulp
- Likes 2
Comment
-
Using a B550M Aorus Pro P does someone know if there is a way to avoid the secondary NVMe to be ignored on a cold boot ? Is there a BIOS setting to make the enumeration more successful on a cold boot ? I think this is a chipset related issue, but I'd like to know if there is a setting that would make this cold boot detection more consistent and successful the first time. Thanks !
Comment
Comment