Hello I am building a pc with PCZZOI H05 case and gigabyte b550 eagle but I can see to get the rgb led fans to light up the fans are working but no led

im struggling to get a simple fan curve working, i dont know if its a ME problem or a gigabyte problem

so i have the 5060 and im trying to set a fancurve via GCC, i want the gpu to be at 0rpm till 60 degrees or 65... i legit dont know why the curve is not working (and msi afterburner is not overriding it i checked)

also are fans loud? or its just me?

would appreciate some help here if im doing something wrong

To the Gigabyte Motherboard Engineering and BIOS Development Team,

I am writing to formally request a BIOS update for the Z170 motherboard series (specifically GA-Z170-HD3 Rev 1.0) to resolve fundamental ACPI table errors that prevent Linux kernels from communicating with Intel PTT (fTPM) and discrete TPMs (dTPM). While the Z170 is a legacy platform, the modern requirement for FIDO2, Passkeys, and TPM-backed Full Disk Encryption has made this ACPI bug a critical security blocker for your loyal user base.

Below are 20 business and community-driven arguments for why Gigabyte should release a final BIOS patch for this platform, followed by 30 specific technical action items and implementation hints to streamline the engineering effort.

Arguments for Releasing a Patch

1. E-Waste Reduction: Fixing TPM support allows perfectly capable Skylake processors and Z170 boards to remain securely in service, preventing unnecessary e-waste.

2. Brand Loyalty & Trust: Users who see Gigabyte supporting a decade-old platform for a critical security flaw will guaranteed purchase Gigabyte for their next high-end build.

3. Rise of FIDO2 & Passkeys: Modern web authentication (WebAuthn) heavily relies on TPM 2.0. Users currently cannot use Passkeys natively on Linux due to this bug.

4. Linux Desktop Growth: The Linux desktop market share has grown significantly; ignoring Linux ACPI standards alienates a highly vocal technical demographic.

5. Full Disk Encryption (FDE): Modern Linux distributions (Fedora, Ubuntu) default to systemd-cryptenroll, which requires a functioning TPM for LUKS decryption.

6. Minimal Backporting Effort: The ACPI DSDT/SSDT logic for properly exposing TPMs to Linux has already been perfected by Gigabyte for Z390 and newer boards. This is a backporting task, not a from-scratch development.

7. PR and Marketing Value: Releasing a "Security & Linux Compatibility Update" for legacy boards generates massive positive PR in tech media (e.g., Phoronix, Linus Tech Tips).

8. Corporate Legacy Infrastructure: Many enterprise users repurpose Z170 systems as edge servers or internal testing nodes where TPM-backed SSH keys are mandatory.

9. Security as a Basic Right: Hardware cryptography should not be locked behind an OS-detection wall in the BIOS.

10. Community Goodwill: The open-source community heavily relies on word-of-mouth. A proactive fix turns frustrated users into brand advocates.

11. Systemd-tpm2 Integration: Recent Linux user-space architectures treat TPMs as mandatory hardware. The current ACPI conflict causes 90-second boot delays (systemd waiting for `dev-tpm0.device`).

12. Right to Maintain: Providing standard ACPI compliance fulfills the industry movement towards user-maintainable hardware.

13. Reducing Support Tickets: Users constantly attempt to debug this issue on forums. A clear BIOS update eliminates recurring troubleshooting overhead.

14. IoT and Edge Repurposing: Secure Boot and TPM are mandatory for repurposing these boards for secure IoT gateway appliances.

15. Alignment with Modern Security Standards: CISA and other cybersecurity agencies mandate hardware root of trust.

16. Eliminating the "Windows 8/10" Toggle Confusion: The current BIOS UI obfuscates TPM functionality based on arbitrary OS naming conventions, causing widespread confusion.

17. Proving Hardware Longevity: It demonstrates that Gigabyte components are built to last and are backed by long-term software commitment.

18. Open-Source Advocates are Influencers: The technical users affected by this bug are the same system builders who recommend hardware to friends, family, and enterprise IT departments.

19. Standardization: ACPI is an OS-agnostic standard. The BIOS should not behave differently whether the payload is the Windows NT kernel or the Linux kernel.

20. Zero Hardware Cost to Gigabyte: This is a pure firmware patch that significantly elevates the perceived value of the Gigabyte ecosystem.

Technical Details & Required Action Items

* Ensure the `MSFT0101` hardware ID is universally exposed in the ACPI tables regardless of the `_OSI` string provided by the bootloader.

* Remove any `If (_OSI ("Windows 2015"))` or similar OS-gating logic that hides the TPM2 ACPI table from Linux.

* Guarantee that the `TPM2` static ACPI table is loaded and properly populated into memory during the UEFI DXE phase.

* Correct the `_STA` (Status) method for the TPM device to return `0x0F` (Present, Enabled, UI-Visible, Functioning) when PTT is enabled, instead of dynamically hiding it.

* Standardize the `_HID` (Hardware ID) mapping for discrete TPMs (dTPM) to ensure they are picked up by standard Linux drivers.

* Provide a fallback `_CID` (Compatible ID) if specific vendor IDs are used.

* Fix the `Memory32Fixed` resource descriptors in the ACPI table to prevent the "can't request region" conflict with the Linux kernel.

* Resolve memory address overlaps between Intel Management Engine (ME) regions and the PTT CRB buffer.

* Ensure the TPM Event Log memory address pointers (`TPMFinalLog`, `TPMEventLog`) are correctly passed to the EFI stub.

* Validate that the ACPI table reserves the exact byte range required for the CRB (Command Response Buffer) to prevent OS-level memory reallocation panics.

* Ensure seamless binding for the Linux `tpm_crb` kernel module for Intel PTT.

* Ensure seamless binding for the Linux `tpm_tis` kernel module for physical TPM chips connected via the motherboard's SPI/LPC header.

* Define hardware interrupts correctly in the ACPI table so `tpm_tis` does not fall back to polling mode, or explicitly disable interrupts (`tpm_tis.interrupts=0` equivalent in ACPI) if the board lacks physical routing.

* Address the `transmit timeout` error caused by the BIOS failing to wake the PTT module from a low-power state upon OS request.

* Standardize physical TPM header routing to ensure the I2C/SPI bus is actively listening when a dTPM is installed, without requiring a Windows-specific UEFI driver.

* Implement proper Physical Presence Interface (PPI) ACPI methods to allow `systemd-tpm2-clear.service` to issue clearing requests natively from Linux.

* Ensure TPM PCR7 correctly reflects the Secure Boot state and certificates (MOK/db/dbx) passed from UEFI to Linux.

* Ensure PCR0 accurately measures the core UEFI firmware without arbitrary fluctuations on warm reboots under Linux.

* Map the "Clear TPM" (fTPM NVRAM erasure) function to correctly reset the endorsement keys without requiring a total CMOS reset.

* Address Intel ME initialization delays during POST that cause the TPM to be reported as "dead" to the Linux IMA (Integrity Measurement Architecture) subsystem.

* Separate the "Intel PTT" toggle from the "Windows 8/10 Features" toggle in the BIOS GUI; TPM functionality must be OS-agnostic.

* Provide explicit BIOS toggles to select between "fTPM (Intel PTT)" and "dTPM (Physical Header)" without automatic overrides that fail under Linux.

* Ensure that resuming from S3/S4 sleep states successfully restores the TPM CRB context without throwing `tpm_crb MSFT0101:00: can't request region` upon wake.

* Synchronize SMBIOS tables (Type 0, Type 1) with TPM measurements to ensure unified attestation strings.

* Expose Endorsement Key (EK) certificate generation status directly to the OS to prevent timeout loops in user-space applications.

* Validate the TPM2.0 ACPI table checksums dynamically; hardcoded checksums often fail after microcode updates.

* Disable legacy BIOS fallback hooks that inadvertently lock the TPM I/O ports before handing off to the Linux EFI bootloader.

* Ensure `tpm2_getcap properties-fixed` returns hardware capabilities without triggering an ACPI timeout loop.

* Patch the watchdog timer ACPI hooks (`iTCO_wdt`) that often conflict with ME/PTT polling on shutdown.

Perform final validation of the patched BIOS using a live USB of Fedora 40+ or Ubuntu 24.04, confirming that `ls /dev/tpm` immediately populates `/dev/tpm0` and `/dev/tpmrm0`.

Technical Hints & Starting Points for Your Engineers

* The Root Cause: The primary reason Linux fails to see the PTT on the Z170 is rooted in the DSDT. When the BIOS setting is set to "Other OS", the UEFI firmware alters the ACPI generation to completely omit the `TPM2` table and the `MSFT0101` device, assuming Linux does not support TPM.

* The Quick Fix: You can resolve 80% of this issue by simply removing the conditional OS checks applied to the TPM device node in the ACPI ASL source. The TPM device should be statically defined in the DSDT and unconditionally returned as active (`_STA = 0x0F`) as long as PTT is enabled in the BIOS, regardless of the CSM or OS Type settings.

* For dTPM (Physical Chips): Ensure that the LPC/SPI bus pins dedicated to the TPM header are not power-gated by default when a non-Windows OS is detected. The `tpm_tis` driver in the Linux kernel requires the IO ports (usually `0xFED40000`) to be strictly declared as reserved in the ACPI memory map.

Thank you for your dedication to hardware excellence and for considering this critical update for the open-source community.

Hey everyone,

I'm currently mapping out the ARGB wiring for my build on a Gigabyte B760M AORUS ELITE AX DDR5 Rev1.0, and I want to make absolute sure I don't overload anything.

According to the board manual for the D_LED1 and D_LED2 headers:

"The headers can be used to connect a standard 5050 addressable LED strip, with maximum power rating of 5A (5V) and maximim number of 1000 LEDs."

Can someone confirm if that 5A limit is per individual D_LED header, or is it a combined total of 5A shared across both headers?

I have 9 of the Cooler Master MasterFan MF120 Halo ARGB 120mm Case Fan (White) fans which are rated at 0.55A LED, daisy chaining all of them, adds up to 4.95A, which is just under the 5A limit, however, this leaves no safety margin. Therefore, I just wanted to make sure if the 5A limit is for each individual D_LED header, that would make it much safer for my 9 fans.

Thanks in advance!

Hi everyone,

I’m using a GIGABYTE M28U with a PS5 pro, and I’m experiencing an issue whenever I launch a game from the PS5 home screen.

The screen goes completely black for a few seconds and then returns to normal once the game loads. There’s no GIGABYTE logo or anything indicating that the monitor is restarting.

Interestingly, this only happens when launching a game for the first time. If I return to the PS5 home screen mid-game and going back to the same game again, it doesn’t happen.

I’m wondering if this is related to the monitor switching resolution, refresh rate, HDR, or another video output setting. My PS5 set to enable 120hz, VRR always on, and HDR is disabled, firmware is F11.

Has anyone experienced the same issue with the M28U? Is this normal behavior, or is there a way to fix it through the PS5 or monitor settings?

Thanks!

Hello, so as the title says FN+F3 and FN+F4 no longer work on my laptop yet the keys themselves work fine and so does every other key. I would really appreciate for any kind of help. Thank you

I wanted to share a real life story about my PC setup, starting with my Gigabyte RTX 5060 undervolt journey. As a beginner in undervolting, the process was surprisingly smooth and stable, allowing me to push the card to 2950 MHz at just 875mV, which keeps temperatures below 65°C under maximum load, my friend has a diffrent version(from a diffrent manufacturer) of the RTX 5060 and he couldn't achieve these results. Meanwhile, my B660M AORUS PRO AX motherboard has been running flawlessly for over 4 years without a single issue. Most importantly, it actually saved my entire system when a loose wire caused a sudden short circuit, the board instantly refused to boot up to protect all my components from burning out. Building with reliable hardware truly makes a massive difference, and I wanted to share this genuine experience with you all!

I bought a gigabyte Rx 6800XT from a 3rd party, the 2x 8pin connector one. The card came with the PCB and Cooler and heatsink seperated, the heatsink nor PCB has any Thermal pads anywhere.

Does anyone know any resource to check the TP thickness, or does anyone know those thicknesses out of the blue?

I've already checked into gigabyte's customer service page, but until they respond I'd like to ask here too.

model - GV-R68XTGAMING OC-16GD rev.1.0

Looking for someone with an Aero X16 who can check their BIOS layout for me.

My Aero X16 (2025, RTX 50 series) currently has no display output at all. Short version: the USB-C port shorted and a repair shop removed the faulty component, which killed HDMI and USB-C. Last week after a Windows update I got a black screen in Windows, so I went into BIOS and switched GPU mode from MSHybrid to Discrete. That was a mistake – in Discrete the panel is driven by the RTX, which clearly isn't outputting anymore, so now I get nothing: no Gigabyte logo, no BIOS, nothing. No external display possible either.

The laptop is otherwise fine. It boots all the way into Windows (I hear the startup sound) and the keyboard works. I just can't see anything. I need to flip GPU mode back to MSHybrid blind.

What I've tried:
- Battery disconnect + hold power 60 s – no change (setting is in flash, not CMOS)
- Tapping/holding F2 at power-on, then F9 → Enter → F10 → Enter – no reboot, nothing. Not sure if Fast Boot is blocking F2 or if those aren't the right keys on this BIOS.

What would help massively – if you have an Aero X16 (or any recent Aero/Aorus), could you jump into your BIOS and tell me:

1. The tab order along the top (Main, Advanced, Chipset, Security, Boot, Save & Exit?)
2. Which tab the GPU mode / MSHybrid-Discrete option is on, and how many items down from the top
3. What the bottom legend says for "Optimized Defaults" and "Save & Exit" (F9/F10? F3/F4?)
4. Whether F2 gets you into BIOS at power-on, or you have to go through Windows Advanced Startup

With that I can write an exact keystroke sequence and do it blind. Any other tricks for getting into BIOS without a display are welcome too. Thanks.

Hello everyone. About two months ago, I joined the "OLED club" by purchasing a Gigabyte Aorus FO32U2P OLED monitor. I use it with my PlayStation 5 Pro, and for the first 50 hours or so, everything was fine. However, when I started playing Alan Wake 2, I noticed flickering vertical lines on the screen, especially in the game's darker areas. At first, I thought it might be an issue specific to that game, but I soon realized it happens in other games as well. In fact, the problem isn't limited to games; it appears everywhere—on the home screen, while watching YouTube, and so on. It is particularly noticeable in scenes with lower brightness. I’ve sent the monitor to the authorized Gigabyte service center in my country twice, but both times they claimed they couldn't find any issues. I also reached out to Gigabyte’s eSupport, but they simply suggested trying the monitor with different devices and stated there was nothing they could do. I tested it with my gaming PC, and the only thing that resolved the issue was setting the refresh rate to 240Hz—which I cannot do on the PS5, as it is locked to 60Hz. Consequently, this OLED monitor, which I bought with such excitement, has become completely unusable for me on the PS5. Is there any way to resolve this? Thanks in advance.

Purchased Gigabyte laptop from flipkart last week. The specifications on the app was showing 85 watt TGP but when checked in NVIDIA control pannel it shows 80 watt but the main problem is that it's not giving even 80 watt, the max it's going in any highest graphics game is 60-65 watt sometimes 70 watt, and gpu usage is showing 100%.

Please if anyone knows the solution kindly help me.

Also I purchased 512 gb model and it's usable is showing only 425gb, google is telling it is using around 30 gb for smart reset, so please tell me how to remove this and if removing it will cause any problems.

Thank you

For anyone curious, i used this prompt to create it : A fierce, futuristic mechanical cybernetic eagle inspired by the AORUS logo, made of glowing orange and fiery neon energy, dark metallic slate armor, hyper-detailed circuit board patterns, high-tech glowing eyes, dark cinematic moody background, 8k resolution, ultra-detailed, unreal engine 5 render, cyberpunk aesthetic, volumetric lighting, wide angle wallpaper 16:9