This may be a separate issue from the btusb binding problem described above.
Additional data that may be relevant: Hardware: MT7925 (Lenovo laptop, Ubuntu-based system) Observed behavior: - Bluetooth controller is present (bluetoothctl list works) - bluetoothctl show → Powered: no - bluetoothctl power on → org.bluez.Error.Failed - GUI toggle successfully enables Bluetooth Key finding: The device is soft-blocked at boot: rfkill list → hci0: Bluetooth Soft blocked: yes Manually unblocking resolves the issue immediately: sudo rfkill unblock bluetooth Permanent workaround: A systemd service that runs "rfkill unblock bluetooth" at boot resolves the issue completely. Conclusion: This appears to be a power/control state issue (rfkill), not a driver binding or firmware problem. Possibly related to ideapad_laptop or ACPI behavior. It may be useful to investigate why Bluetooth is soft-blocked at boot on this hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2148089 Title: MediaTek MT7925 Bluetooth (0489:e111) not auto-bound by btusb on kernel 6.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148089/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
