[Netherwind]

Any word on when CO will be available in BIOS for 5800X3D users?

 

[ryouiki]

Let me know how that test goes with fTPM vs discrete TPM once it's all said and done. From what I've heard, those that switched from the problematic fTPM to discrete TPM saw the issues disappear entirely. I was honestly just hoping to save a few bucks if fTPM was finally fixed after all this time.

The external modules showed up yesterday, I went ahead turned on fTPM on one system, and installed the module in the other. Will let it sit for a few days to see if I notice any differences.

 

[dox81]

I just noticed a very weird thing, both on F36 and F37a bios: The Realtek 2.5Gbe adapter is no longer working at all. I don't see it in bios when I enable the 2nd NIC and I cannot detect it in windows or linux.
Another weird one is that the intel one started to disconnect randomly when the 1gb connection is saturated.
I already flashed F37a using flashrom, no change. It just seems that the realtek died for good. Any ideeas on how I can figure out if it's really gone?
Can anybody check if the Realtek adapter can be enabled and used on your end(F36 & F37a)?

Using Aorus Master v1.0

 

[ryouiki]

The external modules showed up yesterday, I went ahead turned on fTPM on one system, and installed the module in the other. Will let it sit for a few days to see if I notice any differences.

Just turning on fTPM doesn't seem to have caused any issues, however it appears fTPM did not fully initialize properly (attestation was not available) the first time so I am re-testing again. I went ahead and enabled bitlocker etc. on system drives to make sure it is actually in use etc.

 

[Waltc]

I just noticed a very weird thing, both on F36 and F37a bios: The Realtek 2.5Gbe adapter is no longer working at all. I don't see it in bios when I enable the 2nd NIC and I cannot detect it in windows or linux.
Another weird one is that the intel one started to disconnect randomly when the 1gb connection is saturated.
I already flashed F37a using flashrom, no change. It just seems that the realtek died for good. Any ideeas on how I can figure out if it's really gone?
Can anybody check if the Realtek adapter can be enabled and used on your end(F36 & F37a)?

Using Aorus Master v1.0

You want to make sure that you have not inadvertently disabled the RealTek. When disabled, it won't appear in the bios, and behaves just as you mentioned. Also--do not forget to reset CMOS immediately after flashing. Do not attempt to load the settings from an earlier bios on top of a newer bios.

I've only used the RealTek 2.5GB Ethernet adapter for the last three years (I keep the 1GB Intel disabled.) No problems with either F36 or F37a. There were some connectivity problems with that adapter early on in W11, but those have long since been resolved, both in Win11 and in improvements in the RT driver dating back a few months (it always looked to me like a Win11 problem.) Also, you want to make sure you are testing with all overclocking turned off and reset to default, as for instance, too high a bus overclock will cause problems with an adapter or anything else hanging off the BCLK bus.

If it isn't showing up in your bios, it probably will not show up under an OS, either. The Ethernet adapters stay on all the time, both of them. You can't "enable" it in the bios, but you can disable one or both (I disable the Intel.) You also may have a peripheral installed into your system that is conflicting with the RT adapter and preventing it in some fashion.

We own the same motherboard, apparently!...

 

[Waltc]

Just turning on fTPM doesn't seem to have caused any issues, however it appears fTPM did not fully initialize properly (attestation was not available) the first time so I am re-testing again. I went ahead and enabled bitlocker etc. on system drives to make sure it is actually in use etc.

Just run the little Win11 "compatibility" test program. It will tell you whether fTPM is working.

 

[dox81]

@Waltc ,

Realtek was not disabled in BIOS. It was enabled but I couldn't see the details tab in the same page and nothing in windows. No new peripheral was added in the meantime.
In a unusual way, unplugging the PSU made the adapter work again (found some recommendation online which I thought was really stupid).
Another Gigabyte quirk, I might add.

 

[ryouiki]

Just run the little Win11 "compatibility" test program. It will tell you whether fTPM is working.

It was definately functional (otherwise bitlocker wouldn't have worked) but command-line tool "tpmtool getdeviceinformation" was stating attestation was not supported due to a certificate issue... i'm not sure what caused that, but disabling bitlocker then clearing TPM and rebooting Windows solved it for whatever reason.

 

[Zips]

Just turning on fTPM doesn't seem to have caused any issues, however it appears fTPM did not fully initialize properly (attestation was not available) the first time so I am re-testing again. I went ahead and enabled bitlocker etc. on system drives to make sure it is actually in use etc.

Thanks for the updates.

The thing with the fTPM stutter is that it can happen seemingly randomly and it lasts just for a couple of seconds. There can be several hours or even days between the hitches. You may end up missing it if not using the PC regularly.

 

[ryouiki]

The thing with the fTPM stutter is that it can happen seemingly randomly and it lasts just for a couple of seconds. There can be several hours or even days between the hitches. You may end up missing it if not using the PC regularly.

I'll reply back in a few days, fTPM was enabled on my main system I'm using most of the day since it didn't require me to move/open it to install the module... so more likely for me to see it.

 

[Waltc]

@Waltc ,

Realtek was not disabled in BIOS. It was enabled but I couldn't see the details tab in the same page and nothing in windows. No new peripheral was added in the meantime.
In a unusual way, unplugging the PSU made the adapter work again (found some recommendation online which I thought was really stupid).
Another Gigabyte quirk, I might add.

Good, I thought a failure was improbable. Glad to hear it...

 

[Waltc]

It was definately functional (otherwise bitlocker wouldn't have worked) but command-line tool "tpmtool getdeviceinformation" was stating attestation was not supported due to a certificate issue... i'm not sure what caused that, but disabling bitlocker then clearing TPM and rebooting Windows solved it for whatever reason.

I just suspected that possibly bitlocker might have complicated the situation a bit. I don't use it, actually. Glad to know that problem got sorted, as well!

 

[DocYoda]

I have the X570 aorus master v1.0 on F32 bios. Upgraded to a 5900X from 3900XT. System specs:
16GBx4 gksill 3600Mhz (b-die) stock timings @ 17-18-18-39.
6800XT
3x2TB m.2 gen4

On my 3900XT I just set it to vcore 1.375. RAM @ 1.360V @ 3600Mhz, 14-14-14-34. And the rest of the settings I totally forgot what I did about a year ago.

Current settings:
PBO enabled - advanced - motherboad
CPU thermal limit at 75C

Any tips to maximize my rig?

On stress test vcore reaches around 1.425.

 

[rob-tech]

For those wondering if AGESA 1.2.0.7 fixes the fTPM stutter, it does for me on the X570 Aorus Xtreme and I've not had stutter for months, however, there is a catch.

There are two versions of AGESA 1.2.0.7 with differing fTPM firmware revisions, only the latest one will fix the issue and not the BETA.

For reference, please see the screenshot from my TPM settings page as this is the version that fixes the issue.

I've contacted Gigabyte regarding the availability of AGESA 1.2.0.8 as they are dragging their feet and they told me that it is currently in testing phase.

 

[rod6700]

For those wondering if AGESA 1.2.0.7 fixes the fTPM stutter, it does for me on the X570 Aorus Xtreme and I've not had stutter for months, however, there is a catch.

There are two versions of AGESA 1.2.0.7 with differing fTPM firmware revisions, only the latest one will fix the issue and not the BETA.

For reference, please see the screenshot from my TPM settings page as this is the version that fixes the issue. View attachment 2597280

I've contacted Gigabyte regarding the availability of AGESA 1.2.0.8 as they are dragging their feet and they told me that it is currently in testing phase.

Seems all the OEM board makers are dragging their feet on 1.2.0.8 as it was made available second half last year. What version on the fTPM in Beta staging?

 

[99belle99]

I have the same security details as rob-tech above. But I'm not sure if I ever had the issue in the first place since I haven't gamed in a long time and haven't noticed any stutter just using the PC.

 

[99belle99]

Seems all the OEM board makers are dragging their feet on 1.2.0.8 as it was made available second half last year. What version on the fTPM in Beta staging?

Afaik the only boards to have that AGESA are the high end ASUS and they are beta bios'. Not all ASUS boards have it and the last time I checked no MSI had it either. I never checked other manufacturers.

 

[rob-tech]

Seems all the OEM board makers are dragging their feet on 1.2.0.8 as it was made available second half last year. What version on the fTPM in Beta staging?

From what I recall, the initial AGESA 1.2.0.7 BIOSs from Gigabyte had version 3.84 for the fTPM without the .0.5 ending which I believe is the key to the fix. I know from my experience that the very first 1.2.0.7 BIOS on the Xtreme did not fix my issue and caused me frustration such that I almost bought a discrete TPM, while a later version did.

I am confident that if you have the same version as me you should no longer have this issue, any current 1.2.0.7 BIOS should be good.

AGESA 1.2.0.8 fixes security issues and was sampled to board vendors in July of last year which is why it's so disappointing that the board vendors are waiting this long.

 

[Zips]

For those wondering if AGESA 1.2.0.7 fixes the fTPM stutter, it does for me on the X570 Aorus Xtreme and I've not had stutter for months, however, there is a catch.

There are two versions of AGESA 1.2.0.7 with differing fTPM firmware revisions, only the latest one will fix the issue and not the BETA.

For reference, please see the screenshot from my TPM settings page as this is the version that fixes the issue.

I've contacted Gigabyte regarding the availability of AGESA 1.2.0.8 as they are dragging their feet and they told me that it is currently in testing phase.

Very interesting. Thank you for the information!

Part of that definitely falls in line with what I heard before: Where the beta BIOS releases with 1.2.0.7 did not fix the issue. I assume now that Gigabyte was using this beta 1.2.0.7 in their beta BIOS releases and then updated it to non-beta in their non-beta BIOS update from December.

I'll hold off a bit longer though. I'm in no rush and I'd still like to hear if ryouiki had any issues. Plus it'll give me more time to order and get a physical TPM just in case.

 

[ryouiki]

I'll hold off a bit longer though. I'm in no rush and I'd still like to hear if ryouiki had any issues. Plus it'll give me more time to order and get a physical TPM just in case.

Catching up with this thread...

My TPM version for fTPM is the same as rob-tech has listed above (on F36 final). I have not seen any issues/stutters since fTPM was enabled regardless of what the system is doing (General Use/Browsing/Videos, Building OS Images, Code Compiling, Virtual Machines, Gaming, etc.). So hopefully it will work for you as well.

The external module hasn't seen any issues either, though I am not actively sitting at that system most of the day... one interesting note is the external module seems to take significantly longer to initialize / Windows to run maintenance tasks against it.