[Bug 1214133] New: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes
https://bugzilla.suse.com/show_bug.cgi?id=1214133 Bug ID: 1214133 Summary: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: hofmann@shiphrah.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868726 --> https://bugzilla.suse.com/attachment.cgi?id=868726&action=edit dmesg on TW 20230808 After update to Tumbleweed 20230808 bluetooth is disabled and can not be enabled again. dmesg | grep luetooth (on TW 20230806) [ 6.098671] Bluetooth: Core ver 2.22 [ 6.098681] Bluetooth: HCI device and connection manager initialized [ 6.098683] Bluetooth: HCI socket layer initialized [ 6.098684] Bluetooth: L2CAP socket layer initialized [ 6.098685] Bluetooth: SCO socket layer initialized [ 26.836464] Bluetooth: hci0: Device setup in 20228164 usecs [ 26.836469] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 27.115864] Bluetooth: hci0: AOSP extensions version v1.00 [ 27.115870] Bluetooth: hci0: AOSP quality report is supported dmesg | grep luetooth (on TW 20230808) [ 4.355787] Bluetooth: Core ver 2.22 [ 4.355794] Bluetooth: HCI device and connection manager initialized [ 4.355797] Bluetooth: HCI socket layer initialized [ 4.355798] Bluetooth: L2CAP socket layer initialized [ 4.355799] Bluetooth: SCO socket layer initialized [ 4.368031] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 4.368034] Bluetooth: hci0: Failed to load firmware file (-2) [ 4.368045] Bluetooth: hci0: Failed to set up firmware (-2) [ 4.368053] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 4.438485] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.438487] Bluetooth: BNEP filters: protocol multicast [ 4.438489] Bluetooth: BNEP socket layer initialized unfortunately I can not say if it was working in TW 20230807 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214133 https://bugzilla.suse.com/show_bug.cgi?id=1214133#c1 --- Comment #1 from Jürgen Hofmann <hofmann@shiphrah.com> --- Created attachment 868727 --> https://bugzilla.suse.com/attachment.cgi?id=868727&action=edit dmesg on TW 20230808 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214133 Jürgen Hofmann <hofmann@shiphrah.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hofmann@shiphrah.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214133 https://bugzilla.suse.com/show_bug.cgi?id=1214133#c9 Badke <suse.omit097@aleeas.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse.omit097@aleeas.com --- Comment #9 from Badke <suse.omit097@aleeas.com> --- For me it's now the same problem, starting with one of the February-Snapshots. In January my bluetooth adapter still worked. Unfortunately I cannot specify the last snapshot where it worked. I didn't plug in any bluetooth adapter or keyboard. I just want to use my headphones with mouse and keyboard via the internal adapter (MT7922). The command outputs are comparable to the first reporter's (see below). My machine is an HP elitebook 845 G10 with Ryzen 8740HS and Radeon 780M Graphics 64GB RAM, if that helps in any way. Seeing myself as a junior-amateur in handling linux, but a complete rookie regarding Bug reports, do you have any suggestion to solve the problem for me? Would it be a technically safe way to manually import the firmware and rebuild initrd myself, as you mentioned before? Is this procedure compatbible with further upgrades? Or should I rather wait, until the problem is resolved? Unfortunately a downgrade to Leap or Slowroll is not an Option for me (Bluetooth not supprted on Leap, since Kernel is too old, and Slowroll shows the same Bluetooth bug). Let me know, if I can help with additional information. Thanks for advice. dmesg | grep luetooth [ 3.199354] Bluetooth: Core ver 2.22 [ 3.199385] Bluetooth: HCI device and connection manager initialized [ 3.199393] Bluetooth: HCI socket layer initialized [ 3.199396] Bluetooth: L2CAP socket layer initialized [ 3.199398] Bluetooth: SCO socket layer initialized [ 3.204375] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 3.204381] Bluetooth: hci0: Failed to load firmware file (-2) [ 3.204391] Bluetooth: hci0: Failed to set up firmware (-2) [ 3.204398] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 3.261655] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 3.261657] Bluetooth: BNEP filters: protocol multicast [ 3.261661] Bluetooth: BNEP socket layer initialized lsinitrd | grep BT_RAM_CODE -rw-r--r-- 1 root root 343196 Feb 15 22:08 usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.xz -rw-r--r-- 1 root root 446012 Feb 15 22:08 usr/lib/firmware/mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin.xz ls -l /usr/lib/firmware/mediatek/BT_RAM_CODE* -rw-r--r-- 1 root root 513960 23. Feb 17:25 /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin.xz -rw-r--r-- 1 root root 343196 23. Feb 17:25 /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.xz -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com