GIGABYTE Latest Beta BIOS

[TweakinOut!]

AM4 X570

What changed from AGESA 1.2.0.7 to 1.2.0.8 in terms of voltages? The differences I'm experiencing is with 1.2.0.8 I have random USB disconnect issues which are indicated through the RGB lighting on my keybard shutting off and input function dead, and also I see a "notification" in Device Manager. With 1.2.0.7 I have no USB disconnect issues. Same CPU on both AGESA in the same board.

[krato]

AM4 X570

What changed from AGESA 1.2.0.7 to 1.2.0.8 in terms of voltages? The differences I'm experiencing is with 1.2.0.8 I have random USB disconnect issues which are indicated through the RGB lighting on my keybard shutting off and input function dead, and also I see a "notification" in Device Manager. With 1.2.0.7 I have no USB disconnect issues. Same CPU on both AGESA in the same board.

Have read about that, too. Had sometimes those "old" press a key and its printed twice feels again. But its not that bad as it has been. Otherwise there seem to be some work ongoing, which i find good.? Im still waiting for my bios not to be laggy in native resolution while CSM is off. I hope gigabyte is at least working on a final bios with all those little quirks fixed.
Have you tried disabling TPM in bios? For me, especially in Win 11, TPM seems to make some problems with further updates and "the need to reinstall to get the newest os ''''''security''''' features" running.

Looking at asrock support page seems like AMD have released a new agesa for AM4 called AGESA Combo V2 PI 1.2.0.A
After looking around seems just a security fix release: https://community.amd.com/t5/process...-a/td-p/598921

?
In that thread there are some interesting posts, but it doesnt sound like only updating some libs or smth like that.

1.2.0.A really is the official successor to 1.2.0.8 which does not saw such a widespread use on AM4. Right now there are not many public posts about it, but as Allen said, it contains a LOT of security fixes and mitigations and some other improvements. I still don't see an official changelog, though, which I really would like to see.

In this regard they really must improve, I don't want to gather GitHub, multiple forums etc. for a full changelog beside the security bulletins.

Im always optimistic in this as working on code to improve security doesnt mean that it is only security wise. Security and functionality have intersections, at least that is how I imagine AGESA.

Best regards?

[jwsg]

Intel BT 22.220.1 https://www.intel.com/content/www/us...indows-11.html
Intel WiFi 22.220.0 https://www.intel.com/content/www/us...-adapters.html

[Flameancer]

It look like they released a new beta bios for the X570 Aorus Pro Wifi but beware my system has failed to boot afterwards. I was only able to get into the bios once with a roll back to f36 and that was after only using one ram slot. I tried all four again and no dice anymore and have reset the cmos multiple times. The EZ light DRAM and CPU light blink back and forth between each other though it mainly stays in the DRAM light.

CPU: 5800X3D

[Flameancer]

It look like they released a new beta bios for the X570 Aorus Pro Wifi but beware my system has failed to boot afterwards. I was only able to get into the bios once with a roll back to f36 and that was after only using one ram slot. I tried all four again and no dice anymore and have reset the cmos multiple times. The EZ light DRAM and CPU light blink back and forth between each other though it mainly stays in the DRAM light.

CPU: 5800X3D

I want to reply and say that I ended up getting a new RAM kit, somewhere in the process of attempting to get my machine to boot one of the RAM sticks lost a capcictor. New RAM kit instantly booted the system. Although my frequency is stuck at 3.4Ghz with a Max PBO but 3.5GHz, but I thought the 5800X3D is supposed to boost at least to 4.2GHz? On the bright side, my core voltage isn't going above 1.0V either. It's current average is around 0.978V which means my temps have gone down significantly.

[Tobiaz Bj�rknert]

Z790 Aorus Master do not show up in GCC for rgb only GPU in bios f8c

[chris19756]

Edit for my last post a Picture from BIOS flash

[amEliza]

hi peoples, question

gigabyte lets me disable secure boot and reset secure boot keys to factory from within the OS, for example using scewin

does anybody know if there is a way to mitigate this?

normally with an AMI uefi you could set a password, which requires you to enter the password before you can read or write uefi settings from the os

that would be fine but gigabyte has disabled this, so a uefi password does nothing functional

i figured at first it was a misconfiguration on my part, since i enter the password on system boot maybe that is unlocking uefi settings during boot, but changing it to setup only didnt fix that

probably it will take a bios mod to enable password protection, i see no other way of getting this resolved

thanks
?

[krato]

hi peoples, question

gigabyte lets me disable secure boot and reset secure boot keys to factory from within the OS, for example using scewin

Unfortunately, I'm not able to speak about this much. Only that if u use Win10/Win11 the whole sense of "security" might be broken by design.
Otherwise I'm not sure if this is the right place to ask such questions to get an answer.

Best regards,

[Waltc]

From what I've read, scewin is an AMI tool, requiring physical access to a machine. If a person has physical access to your machine, theoretically they can do anything they want and no security measures can stop them. Including secure-boot. Doesn't matter the OS. Sounds like you are needlessly worrying, though. Although I think writing bios changes from the OS is terrible practice, because you have to reboot, anyway, to see the changes, in order to do so you must have admin privileges in the OS, AFAIK. But, how is someone going to run scewin on your machine without physical access to your machine? Not sure I understand you. x570 Aorus Master, F37c.

[amEliza]

thanks krato, i'm not expecting there to be a user accessible fix, but my expectations can be wrong, each oem firmware has its quirks


hey waltc, to simplify

gigabyte uefi says secure boot is enabled

os say secure boot is enabled

howeverrrrr: secure boot is not actually enabled

secure boot being disabled is okay (i'm not worried :)

secure boot being disabled when its meant to be enabled? that means gigabyte uefi is broken

my question is essentially just "does anybody know a fix?" (maybe i didnt set it up right, maybe i broke it, maybe somebody asked gigabyte to fix it before me)

not understanding me is okay!

[Bcknee]

thanks krato, i'm not expecting there to be a user accessible fix, but my expectations can be wrong, each oem firmware has its quirks


hey waltc, to simplify

gigabyte uefi says secure boot is enabled

os say secure boot is enabled

howeverrrrr: secure boot is not actually enabled

secure boot being disabled is okay (i'm not worried :)

secure boot being disabled when its meant to be enabled? that means gigabyte uefi is broken

my question is essentially just "does anybody know a fix?" (maybe i didnt set it up right, maybe i broke it, maybe somebody asked gigabyte to fix it before me)

not understanding me is okay!

I had it off for a long time not realizing I found these steps on reddit and it fixed it for me

Make sure you are booting OK with CSM disabled before changing Secure Boot settings. People have bricked their system by following the wrong steps.

I also had it saying enabled not Active - this is a BIOS glitch it's not really enabled

On the secure boot settings if it says Mode:User you should be able to simply Enable Secure Boot

Otherwise (if it says Mode:Setup)

- Disable Secure Boot if it says Enabled

- If it says Standard change to Custom

- Change Custom to Standard accepting Factory Defaults

- Enable Secure Boot
?

[rod6700]

I had it off for a long time not realizing I found these steps on reddit and it fixed it for me

Make sure you are booting OK with CSM disabled before changing Secure Boot settings. People have bricked their system by following the wrong steps.

I also had it saying enabled not Active - this is a BIOS glitch it's not really enabled

On the secure boot settings if it says Mode:User you should be able to simply Enable Secure Boot

Otherwise (if it says Mode:Setup)

- Disable Secure Boot if it says Enabled

- If it says Standard change to Custom

- Change Custom to Standard accepting Factory Defaults

- Enable Secure Boot
?

I don't think the issue that amEliza is seeing is what you describe as I am familiar with your workaround to get secure boot enabled on Gigabyte AM4. What happens when your suggested workaround is not used, BIOS shows secure boot enabled but Windows does not. amEliza is showing secure boot enabled both in BIOS and the OS. If what they are saying is fact, then Gigabytes implementation of secure boot is utterly broken.

[krato]

thanks krato, i'm not expecting there to be a user accessible fix, but my expectations can be wrong, each oem firmware has its quirks

What you try to say, I guess, is that it should not be possible to disable secure boot in any kind by os, or altering the keys? Dunno if this is still the expected behavior, or ever was. Like Walt said if you have physical access to someones running pc its over, even though secure boot is enabled. But what do you mean by "resetting to factory"? Do you have some self generated pk that is getting deleted? R u in setup mode again? Have you som good ol' "serious business" gigabyte software installed?

According to the specification, this results in the following scheme: PK and KEK can only be changed if:

In Setup Mode, when PKpub is signed with its associated PKpriv.
In User Mode, if the PKpub is signed with the current PKpriv of the firmware.??

Im quoting from this, hopefully translatable, german url, https://www.thomas-krenn.com/de/wiki/UEFI_Secure_Boot, but my guess is that windows is allowed to do so since its in the db. If you dont want anybody being able to alter secure boot you should consider using full disk encryption. Also, you could create your own PK and use daisy chain loading of bootloaders, with refind perhaps. If u have some kind of linux installed you could investigate better, also reading linux wiki is always good https://wiki.archlinux.org/title/Uni...ce/Secure_Boot
But in the end, im just guessing here, since im noob.

Best regards, hope I could help

[Waltc]

I had it off for a long time not realizing I found these steps on reddit and it fixed it for me

Make sure you are booting OK with CSM disabled before changing Secure Boot settings. People have bricked their system by following the wrong steps.

I also had it saying enabled not Active - this is a BIOS glitch it's not really enabled

On the secure boot settings if it says Mode:User you should be able to simply Enable Secure Boot

Otherwise (if it says Mode:Setup)

- Disable Secure Boot if it says Enabled

- If it says Standard change to Custom

- Change Custom to Standard accepting Factory Defaults

- Enable Secure Boot
?

All of that is correct...it figures that people who use it would know how to use it...;) It's eminently Googleable. But your instructions here may be very helpful to some people!

@amEliza-- hope you get it sorted, Bcknee may have nailed it for you.