[Bug 220560] New: Bluetooth adapter not found (MediaTek)

public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed

* [Bug 220560] New: Bluetooth adapter not found (MediaTek)
@ 2025-09-10 16:49 bugzilla-daemon
  2025-09-15 18:23 ` [Bug 220560] " bugzilla-daemon
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2025-09-10 16:49 UTC (permalink / raw)
  To: linux-bluetooth

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

            Bug ID: 220560
           Summary: Bluetooth adapter not found (MediaTek)
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: mattias.ohrn@gmail.com
        Regression: No

Created attachment 308651
  --> https://bugzilla.kernel.org/attachment.cgi?id=308651&action=edit
dmesg after booting kernel 6.16.5 OpenSuse TW

Bluetooth has stopped working completely for me on OpenSuse Tumbleweed. When I
installed TW on my HP ZBook Ultra 14 G1a (AMD Strix Halo) around Aug 10 it
worked as expected. It stopped working at some point but I don't know when
because I wasn't using any BT devices for a couple of weeks, until Sep 8.

I was directed here by distro maintainers after filing a bug there:
https://bugzilla.opensuse.org/show_bug.cgi?id=1249369

I initially created this forum thread, which contains some more info:
https://forums.opensuse.org/t/bluetooth-adapter-not-found-used-to-work/187941

I have tried the following kernel versions:
- 6.17-rc5
- 6.16.5
- 6.16.3
- 6.16.1
- 6.15.8 (version when I initially set up the machine)
- 6.12.45

I have also tried kernel-firmware-mediatek 20250804-1.1 in combination with the
6.15.8 kernel (in addition to the 20250903-1.1 version) without seeing any
differences.

Some more info (all from after booting 6.16.5), and I'm also attaching full
dmesg from immediately after boot:

$ bluetoothctl show
No default controller available

$ sudo rfkill list all
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

$ sudo hwinfo | grep -E "blue|Blue|BLUE"   
  P:
/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0
  J: +bluetooth:hci0
  U: bluetooth
  E:
DEVPATH=/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0
  E: SUBSYSTEM=bluetooth
  E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0
  E: SYSTEMD_WANTS=bluetooth.target
  E: SYSTEMD_USER_WANTS=bluetooth.target
  P:
/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0/rfkill0
  E:
DEVPATH=/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0/rfkill0
  E: RFKILL_TYPE=bluetooth
/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0
/devices/pci0000:00/0000:00:08.3/0000:c5:00.0/usb3/3-5/3-5:1.0/bluetooth/hci0/rfkill0
  bluetooth 1056768 15 bnep,btusb,btrtl,btintel,btbcm,btmtk, Live
0xffffffffc0ca1000
  rfkill 45056 10 mt7925e,hp_wmi,cfg80211,bluetooth, Live 0xffffffffc0c9e000
  crc16 12288 2 bluetooth,amdgpu, Live 0xffffffffc0c9c000
103: USB 00.2: 11500 Bluetooth Device
  Hardware Class: bluetooth
107: USB 00.0: 11500 Bluetooth Device
  Hardware Class: bluetooth
114: USB 00.1: 11500 Bluetooth Device
  Hardware Class: bluetooth

$ usb-devices | awk 'BEGIN{RS=""; FS="\n"} /8c38/'     
T:  Bus=03 Lev=01 Prnt=02 Port=04 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0e8d ProdID=8c38 Rev=01.00
S:  Manufacturer=MediaTek Inc.
S:  Product=Wireless_Device
S:  SerialNumber=000000000
C:  #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=125us
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=0a(O) Atr=03(Int.) MxPS=  64 Ivl=125us
E:  Ad=8a(I) Atr=03(Int.) MxPS=  64 Ivl=125us

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 06cb:0106 Synaptics, Inc. 
Bus 003 Device 003: ID 0e8d:8c38 MediaTek Inc. Wireless_Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

$ ~ sudo journalctl -b -p 0..3
Sep 08 13:19:12 localhost kernel: platform AMDI0201:00: AMD-Vi: [Firmware Bug]:
No ACPI device matched UID, but 1 device matched HID.
Sep 08 13:19:25 localhost kernel: Bluetooth: hci0: Execution of wmt command
timed out
Sep 08 13:19:25 localhost kernel: Bluetooth: hci0: Failed to send wmt patch
dwnld (-110)
Sep 08 13:19:25 localhost kernel: Bluetooth: hci0: Failed to set up firmware
(-110)
Sep 08 13:19:33 localhost.localdomain firewalld[1902]: ERROR: NAME_CONFLICT:
new_policy_object(): 'docker-forwarding'
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987]
Error(s) opening ddc devices
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-4
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-5
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-6
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-7
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-8
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-9
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-10
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-11
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-12
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-13
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-14
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-15
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-16
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-17
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-18
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-19
Sep 08 13:19:35 localhost.localdomain org_kde_powerdevil[2987]: [  2987] Error
EACCES(-13): Permission denied opening /dev/i2c-20

I believe the first log line is related to the webcam support not yet being in
the mainline kernel so I think that can be ignored here (I have seen that
message since day one).

Please let me know if I can provide more information.

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

You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug 220560] Bluetooth adapter not found (MediaTek)
  2025-09-10 16:49 [Bug 220560] New: Bluetooth adapter not found (MediaTek) bugzilla-daemon
@ 2025-09-15 18:23 ` bugzilla-daemon
  0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2025-09-15 18:23 UTC (permalink / raw)
  To: linux-bluetooth

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

Mattias Öhrn (mattias.ohrn@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |UNREPRODUCIBLE

--- Comment #1 from Mattias Öhrn (mattias.ohrn@gmail.com) ---
A strange thing happened. I didn't touch the laptop during the weekend but
apparently there was some battery drain because the battery was flat this
morning. When I plugged it in I was greeted with a ‘updating, please do not
unplug power’ BIOS message and then it booted normally and now Blutooth is
working again. I have no idea where that update came from nor what it
contained. I was checking for updates with `fwupdmgr` last Friday but it didn't
show anything at that point and it seems like this have happened to others on
other distros as well
(https://forum.level1techs.com/t/the-ultimate-arch-secureboot-guide-for-ryzen-ai-max-ft-hp-g1a-128gb-8060s-monster-laptop/230652/127).

Anyway, since it seems like the problem is solved, I'm resolving this ticket.

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

You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-09-15 18:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-10 16:49 [Bug 220560] New: Bluetooth adapter not found (MediaTek) bugzilla-daemon
2025-09-15 18:23 ` [Bug 220560] " bugzilla-daemon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox