[Bug 1200236] New: Bluetooth on Intel AX210 not working with Kernel 5.14
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236 Bug ID: 1200236 Summary: Bluetooth on Intel AX210 not working with Kernel 5.14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: severin.stampler@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Bluetooth on Intel AX210 is not working with the default kernel and firmware (5.14.21, openSUSE Leap 15.4). I tried several other newer kernel versions, all have the same problem. dmesg output shows "Failed to load Intel firmware ..." (see below), but firmware is installed. Cold or warm reboot doesn't seem to make a difference (like suggested here: https://bugzilla.kernel.org/show_bug.cgi?id=213829) dmesg | grep -i bluetooth [ 4.233063] Bluetooth: Core ver 2.22 [ 4.233084] NET: Registered PF_BLUETOOTH protocol family [ 4.233085] Bluetooth: HCI device and connection manager initialized [ 4.233089] Bluetooth: HCI socket layer initialized [ 4.233091] Bluetooth: L2CAP socket layer initialized [ 4.233093] Bluetooth: SCO socket layer initialized [ 4.239235] Bluetooth: hci0: Device revision is 0 [ 4.239237] Bluetooth: hci0: Secure boot is enabled [ 4.239238] Bluetooth: hci0: OTP lock is enabled [ 4.239238] Bluetooth: hci0: API lock is enabled [ 4.239238] Bluetooth: hci0: Debug lock is disabled [ 4.239239] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 4.239240] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 4.239257] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0041-0041.sfi (-2) [ 4.240279] Bluetooth: hci0: Failed to read MSFT supported features (-56) [ 4.330250] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.330251] Bluetooth: BNEP filters: protocol multicast [ 4.330253] Bluetooth: BNEP socket layer initialized [ 5.221888] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked lsusb | grep -i blue Bus 003 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c1
--- Comment #1 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c3
--- Comment #3 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c4
--- Comment #4 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c5
--- Comment #5 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c6
--- Comment #6 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c7
--- Comment #7 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c8
--- Comment #8 from Severin Stampler
Hm, the error -2 is -ENOENT, that is, the file doesn't exist.
Is the error from initrd, or after switching to the root? Please upload the full dmesg output, not only the snippet. Also, give hwinfo output, too.
I'm not sure about the initrd. I can see the message flashing up after the boot sequence before the login screen is loaded. I appended dmesg and hwinfo output after a reboot and after reloading the btusb kernel module. One can see, that after the module reload, the firmware is found and loaded correctly. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c9
--- Comment #9 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c10
--- Comment #10 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c11
--- Comment #11 from Severin Stampler
Could you check the contents of initrd via lsinitrd, and verify whether BT kernel module is included there or not? If they are there, it'd explain why it failed to load the firmware at first.
If so, we can either omit the loading of BT modules or adding the missing firmware file(s) to initrd.
attached lsinitrd, seems like the module is there. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c12
--- Comment #12 from Severin Stampler
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c13
--- Comment #13 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236
http://bugzilla.opensuse.org/show_bug.cgi?id=1200236#c14
--- Comment #14 from Severin Stampler
participants (1)
-
bugzilla_noreply@suse.com