Skip to content

Instantly share code, notes, and snippets.

@diffficult

diffficult/AX200_Bluetooth_issues.md

Last active October 9, 2025 20:12
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save diffficult/1995b30226a3221dc63515e78b6ec405 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save diffficult/1995b30226a3221dc63515e78b6ec405 to your computer and use it in GitHub Desktop.
Download ZIP
AX200 Intel Chipset Bluetooth issues on powerloss
Raw
AX200_Bluetooth_issues.md

Intel AX200 Bluetooth Issues on ASUS X570 Motherboards: Findings, Problems, and Solutions

Last Updated: February 27, 2025

Overview

The Intel Wi-Fi 6 AX200 chipset, commonly integrated into motherboards like the ASUS ROG Strix X570-I Gaming or added as an M.2 module, promises robust Wi-Fi and Bluetooth 5.2 connectivity. However, a recurring issue across both Windows and Linux systems, including Arch Linux, is the Bluetooth controller failing to initialize or function after a system reboot. This document synthesizes findings from community forums, official documentation, and user experiences to detail the problem, its potential impacts, and actionable solutions.

Findings

Cross-Platform Consistency

The Bluetooth failure is not isolated to a single operating system:

  • Windows Users: Report Bluetooth disappearing from Device Manager post-reboot, often with error codes like Code 39 ("Windows cannot load the device driver") or devices simply not responding (Intel Community).
  • Linux Users: On distributions like Arch Linux, Ubuntu, and Fedora, Bluetooth is often missing from hciconfig or bluetoothctl, with kernel logs (dmesg) showing firmware load failures or no device detection (Arch Linux Forums, Ask Ubuntu).

Common Symptoms

  • Post-Reboot Failure: Bluetooth works initially but fails after a restart, suggesting a power or initialization issue.
  • Firmware Dependency: Linux requires specific firmware files (e.g., ibt-20-1-4.sfi) from the linux-firmware package, while Windows relies on Intel driver updates (linux-firmware git).
  • Hardware Detection: Wi-Fi often remains functional via the iwlwifi driver, but Bluetooth, managed by btintel, does not (Phoronix).

Unexpected Insight

A notable finding is the effectiveness of power cycling—shutting down, unplugging, and draining residual power—as a solution across platforms. This points to a hardware-level power management flaw rather than a pure software issue, a detail echoed in both Windows and Linux communities (Reddit r/techsupport).

Possible Problems Due to the Faulty Chipset

  1. Intermittent Connectivity:

    • Devices like Bluetooth mice, keyboards, or speakers (image example) may disconnect unexpectedly after reboots, disrupting workflows or gaming sessions.
    • Impact: Loss of productivity or inability to use critical peripherals.

  2. System Instability:

    • Repeated driver or firmware load failures could lead to broader USB or PCIe bus issues, especially on compact boards like the X570-I where resources are shared.
    • Impact: Potential crashes or degraded performance in Wi-Fi or other components.

  3. User Frustration and Downtime:

    • Troubleshooting requires manual intervention (power cycling, driver updates), which is time-consuming and unintuitive for non-technical users.
    • Impact: Increased support requests or hardware returns.

  4. Compatibility Risks:

    • BIOS settings like Fast Boot, which skips full hardware initialization, might exacerbate the issue by not properly resetting the chipset’s power state.
    • Impact: Persistent failures even after applying fixes, requiring deeper configuration changes.

Possible Solutions

Power Cycling: A Top Fix

Power cycling has proven to be one of the best solutions across platforms:

  • How: Shut down the system, unplug the power cord, hold the power button for 60 seconds to drain residual power, then restart.
  • Why It Works: Resets the AX200’s power state, addressing a suspected hardware bug in power management (Intel Community).
  • Effectiveness: High, with users reporting immediate restoration of Bluetooth functionality.

Fast Boot Consideration

If power cycling fails, the power problem might be tied to Fast Boot settings in the BIOS:

  • Test: Enter BIOS (usually by pressing Del or F2 on boot), disable Fast Boot, save, and reboot. Test Bluetooth functionality.
  • Reason: Fast Boot skips full hardware initialization, potentially leaving the AX200 in an unpowered or misconfigured state (ASUS Support).
  • Effectiveness: Moderate; varies by motherboard firmware and user configuration.

Software-Based Solutions

  1. Windows:

    • Update Drivers: Download the latest Bluetooth drivers from Intel Downloads. Install and reboot.
    • Reinstall: Uninstall the Bluetooth device in Device Manager (check “Delete driver software”), then reinstall.
    • Effectiveness: Moderate; driver updates fix some cases, but not all.

  2. Linux (Arch):

    • Update Packages: Run sudo pacman -Syu to ensure linux and linux-firmware are current.
    • Check Firmware: Verify /lib/firmware/intel/ibt-20-1-4.* exists; download from linux-firmware git if missing.
    • Enable Service: Start and enable Bluetooth with sudo systemctl start bluetooth and sudo systemctl enable bluetooth.
    • Unblock: Use rfkill list and sudo rfkill unblock bluetooth if blocked.
    • Effectiveness: High when firmware and services are correctly configured (ArchWiki).

  3. BIOS Update:

    • How: Download the latest BIOS (e.g., version 5204) from ASUS ROG Strix X570-I Gaming Support, rename to SX570IG.CAP, use USB BIOS FlashBack (see ASUS Manual).
    • Why: Updates may fix power management or compatibility issues with the AX200.
    • Effectiveness: Moderate; depends on whether ASUS addressed this in firmware.

Recommendations

  1. Start with Power Cycling: It’s simple, non-invasive, and widely effective. Test Bluetooth post-reboot.
  2. Check Fast Boot: If power cycling doesn’t stick, disable Fast Boot in BIOS and retest.
  3. Software Fixes: Update drivers/firmware based on your OS (Windows or Linux).
  4. BIOS Update: If all else fails, flash the latest BIOS using FlashBack, ensuring Bluetooth is enabled in settings.
  5. Monitor Logs: Use dmesg | grep -i bluetooth (Linux) or Event Viewer (Windows) to diagnose persistent issues.

Sources

Conclusion

The Intel AX200’s Bluetooth woes stem from a likely power management flaw, exacerbated by settings like Fast Boot and inconsistent firmware support. Power cycling stands out as a reliable fix, but a combination of software updates and BIOS tweaks offers a comprehensive solution. This write-up provides a reusable guide for tackling this issue on ASUS X570 systems, whether on Windows or Linux.

@xyhbhtt
Copy link

xyhbhtt commented Oct 9, 2025

I've had a problem with my AX200 (Gigabyte Aorus X570) for the last two weeks. I'm running Archlinux and all of a sudden my Bluetooth adapter was nowhere to be found anymore. A look into the journal mainly lead me to these entries:
kernel: Bluetooth: hci0: command 0xfc05 tx timeout
kernel: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-20-1-3.sfi (-2)
So I looked for solutions and tried all of the ones listed above, as well as others, without avail. After some time I thought "let's do a sanity check and see if the Bluetooth part of the AX200 is even functional". How? By loading up the archlinux.iso from a USB, installing bluez and bluez-utils, enabling bluetooth.service and trying to connect to some device via bluetoothctl.
And would you look at that! The AX200 Bluetooth adapter re-appeared like nothing had happened! This behavior even persisted!
My only explanation would be that some internal config, or something like it, corrupted and that needs to be re-initialized and overwritten from a "clean" system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment