Additional regression confirmation: I booted the same system into kernel 7.0.0-28-generic without changing any hardware or Bluetooth configuration.
On 7.0.0-28-generic: $ uname -r 7.0.0-28-generic Bluetooth initializes successfully: $ bluetoothctl list Controller 4C:23:38:F8:65:9C CORE-01 [default] The same internal USB Bluetooth device is used: Vendor ID: 0489 Product ID: e156 Vendor: Foxconn / Hon Hai The same custom DKMS btmtk module version 0.1 is installed on both kernels. Comparison: 7.0.0-28-generic: - Bluetooth works - Controller appears normally in bluetoothctl - hci0 initializes successfully 7.0.0-30-generic: - hci0 is created but initialization fails - Bluetooth: hci0: Opcode 0x0c03 failed: -110 - bluetoothctl show: No default controller available - BD Address is 00:00:00:00:00:00 - Controller remains DOWN This confirms the issue is reproducible and is a regression introduced between 7.0.0-28-generic and 7.0.0-30-generic. As a temporary workaround, booting kernel 7.0.0-28-generic restores Bluetooth functionality immediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164852 Title: Bluetooth regression in kernel 7.0.0-30-generic: MediaTek/Foxconn 0489:e156 fails to initialize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-7.0/+bug/2164852/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
