[Bug 221357] New: Lenovo Ideapad - Bluetooth (MT7925) soft-blocked by rfkill at boot (hci0 blocked while ideapad_bluetooth is not)

[Bug 221357] New: Lenovo Ideapad - Bluetooth (MT7925) soft-blocked by rfkill at boot (hci0 blocked while ideapad_bluetooth is not)

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221357

            Bug ID: 221357
           Summary: Lenovo Ideapad - Bluetooth (MT7925) soft-blocked by
                    rfkill at boot (hci0 blocked while ideapad_bluetooth
                    is not)
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: cverellen@hotmail.com
        Regression: No

Created attachment 309864
  --> https://bugzilla.kernel.org/attachment.cgi?id=309864&action=edit
Support document

Summary:
Bluetooth is soft-blocked at boot by rfkill on a Lenovo laptop, preventing it
from powering on automatically. Manual unblocking resolves the issue
immediately.

System:
- Device: Lenovo Legion 5 (Ideapad platform)
- Bluetooth: MediaTek MT7925 (USB ID 0489:e111)
- OS: Linux Mint 22.3 (Ubuntu 24.04 base)
- Kernel: 6.17.0-20-generic (also observed on 6.14.x)

Problem:
After boot, Bluetooth is present but cannot be powered on:

$ bluetoothctl show
Powered: no

$ bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed

rfkill state shows:

$ rfkill list
0: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no

2: ideapad_bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no

Key Observation:
The platform rfkill device (ideapad_bluetooth) is NOT blocked,
but the actual Bluetooth controller (hci0) IS soft-blocked.

This indicates an inconsistency in rfkill state between the platform driver and
the Bluetooth device.

Manual Fix:
$ rfkill unblock bluetooth

Immediately results in:

$ bluetoothctl show
Powered: yes

Bluetooth then works normally.

Additional Observations:
- Device is correctly detected (lsusb shows 0489:e111)
- btusb driver is loaded
- Firmware is present and loads correctly
- No rfkill-related messages appear in dmesg
- Issue is reproducible on every boot
- GUI toggle also resolves the issue (likely unblocks rfkill internally)

Conclusion:
Bluetooth is being soft-blocked at boot without user interaction.
This appears to be caused by platform/ACPI behavior, likely related to
ideapad_laptop or platform x86 handling.

The mismatch between ideapad_bluetooth (unblocked) and hci0 (blocked) suggests
a kernel rfkill state inconsistency.

Workaround:
A systemd service that runs:
rfkill unblock bluetooth

restores correct behavior at boot.

Expected Behavior:
Bluetooth should not be soft-blocked at boot unless explicitly requested.

Actual Behavior:
Bluetooth is soft-blocked at boot, preventing it from powering on.

Request:
Investigate rfkill state handling for this platform, particularly interaction
between ideapad_laptop and the Bluetooth controller. A platform-specific quirk
or fix may be required.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.