Bluetooth not working on Asus B650E-I

infinitymdm

Bluetooth is not working on my new system with an Asus ROG Strix B650E-I motherboard with integrated bluetooth chip. Interestingly, it worked on the 4.3 ISO but no longer functions after upgrading. I've seen some posts saying that this broke with the 6.0 kernel release, but haven't yet tested with LTS to see if it's working on the 5.15 kernel. (It's on the ol' to-do list though.)

inxi output:

Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed 480 Mb/s lanes: 1 bus-ID: 3-11:6 chip-ID: 0489:e0e2 class-ID: e001 serial: <filter>
Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends

The bluetooth systemd service is enabled and running. However, when I try to use bluetoothctl to scan for available connections (or do pretty much anything else) I get the message No default controller available.

dmesg | grep -i bluetooth has a few interesting messages as well:

[    7.888886] Bluetooth: Core ver 2.22
[    7.888894] NET: Registered PF_BLUETOOTH protocol family
[    7.888894] Bluetooth: HCI device and connection manager initialized
[    7.888896] Bluetooth: HCI socket layer initialized
[    7.888897] Bluetooth: L2CAP socket layer initialized
[    7.888899] Bluetooth: SCO socket layer initialized
[    8.790021] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.790025] Bluetooth: BNEP socket layer initialized
[    9.948229] Bluetooth: hci0: Opcode 0x c03 failed: -110

Currently on unstable, but this wasn't working when I was using the stable repos either.

Anybody got any ideas for how to get this working, or any new things to try? Not mission critical by any means, but it sure would be nice to be able to use bluetooth.

infinitymdm

Here are a few things I've tried, based on some web searches:

Rebooting
Restarting the bluetooth service: sudo systemctl restart bluetooth
Removing and re-adding the btusb kernel module: sudo rmmod btusb; sudo modprobe btusb

Harvey

A lot of people who report issues with bluetooth or wireless suddenly not working are dual booting with Windows. If you are boot into Windows -> disable fast boot -> shutdown (not reboot) - > boot into Solus.

If you use hibernate / suspend functionality at all. shutdown (not reboot) -> boot into Solus.

That probably solves 40% of the issues I see reported.

infinitymdm

Harvey Unfortunately this is not the case for me. This is a clean drive with just Solus on it. I think I've tried shutting down (not rebooting), but just to be sure I'll give it another try after work today.

infinitymdm

Neither of these worked:

Booting into the LTS kernel (neither WiFi or Bluetooth worked there 😛)
Shutting down (not rebooting) and powering back on

brent

enabling BT mouse and headset by going straight to BluetoothCTL/cli to make moves:
https://discuss.getsol.us/d/713-how-i-got-bluetooth-microsoft-mouse-and-awei-bluetooth-headset-to-work-in-solus

@Brucehankins found his won workaround at comment #22
https://discuss.getsol.us/d/9248-cant-connect-or-enable-bluetooth-on-plasma/33

this forum is littered with bluetooth-disabled corpses mostly unsolved...I imagine you've read most.

also: what does connection indicator on taskbar say? any clues?
is it 'competing' with eth0 (lan) right now?
your new hardware too new?
all I got I think. If services are all enabled and log doesn't look weird to me. dmesg | tail with dongle newly plugged in might have more?

infinitymdm

brent enabling BT mouse and headset by going straight to BluetoothCTL/cli

Unfortunately, bluetoothctl show spits out No default controller available, so no luck there. I suspect the issue is at a lower level.

brent Brucehankins found his won workaround at comment #22

No TLP here, so that's probably not going to fix me 😄

brent also: what does connection indicator on taskbar say? any clues?

Interestingly enough, the settings page appears in Budgie Control Center, but there is no icon on the taskbar. I would have thought that if bluetoothctl says there are no controllers, then BCC wouldn't show the Bluetooth page. I would also think that if the BCC page appears, there would be a taskbar icon, but evidently that's not the case 🤷

brent is it 'competing' with eth0 (lan) right now?

Not sure how to tell on this one, but it doesn't seem very likely to me. The wifi chipset is PCIe while the Bluetooth hardware seems to be on the serial bus. If you have any suggestions for how to check, I'm all ears.

brent your new hardware too new?

I would have agreed with your suggestion that my hardware is likely too new, but bluetooth works when booting the 4.3 ISO. It's an interesting puzzle.

brent dmesg | tail with dongle newly plugged in might have more?

It's a built-in bluetooth module, so no plugging in/unplugging.

I definitely appreciate the suggestions. It's good to have a sanity check.

brent

infinitymdm It's good to have a sanity check.

I only a play a doctor on TV😉...

re: I have seen the "competing" thing cause problems more than once so it didnt seem uncommon to me when I was listing stuff...for the life of me I don't know where you would find info on that. PCIe/bus are two entities, though you are right.

--sorry forgot about Bruce's power saver app.

infinitymdm It's a built-in bluetooth module, so no plugging in/unplugging.

as far as I can see, the module it active and solus sees it. lspci won't tell you much, but not sure if that module is truly a peripheral. Wonder why there is no icon? Applet not added? bluetoothctl doesn't see it either...? Why?

something is keeping it from being completely integrated/functioning. it is a mystery.

I'm not thinking bios at all. you have ruled out the kernel with the LTS switcheroo...

Axios

infinitymdm Run this see what it spits out about it mine was listed last see if the driver is loaded
to lspci -nnk

Brucehankins

Looks like this uses MediaTek Bluetooth and wireless. Might want to see if there's any known bugs with the 6.x series kernels as the components still seem pretty new.

infinitymdm

brent lspci won't tell you much, but not sure if that module is truly a peripheral

Axios infinitymdm Run this see what it spits out about it mine was listed last see if the driver is loaded to lspci -nnk

As I hinted at earlier, the Bluetooth module shows up on the serial bus. That means it shows up in lsusb instead of the lspci output. Just for kicks though, I've included both below.

See Bus 003 Device 005 in the lsusb output below:

marcus@summit ~ $ lsusb
Bus 009 Device 002: ID 045e:02fe Microsoft Corp. Xbox Wireless Adapter for Windows
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 0493:4170 MAG Technology Co., Ltd ARC AMP DAC
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 006 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 006: ID 0bda:5418 Realtek Semiconductor Corp. BillBoard Device
Bus 005 Device 005: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 005 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 005 Device 003: ID 7274:0001 richard.titmuss Torn
Bus 005 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 002: ID 0b05:1a5c ASUSTek Computer, Inc. USB Audio
Bus 003 Device 005: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device
Bus 003 Device 004: ID 046d:c539 Logitech, Inc. Lightspeed Receiver
Bus 003 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 001 Device 002: ID 2516:014d Cooler Master Co., Ltd. ARES
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Note that (as far as I can tell) no bluetooth-related devices show up in the lspci output here:

marcus@summit ~ $ lspci -nnk
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14d8]
	Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Device [1022:14d9]
	Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14da]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:14db]
	Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:14db]
	Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14da]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:14db]
	Kernel driver in use: pcieport
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14da]
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14da]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14da]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:14dd]
	Kernel driver in use: pcieport
00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:14dd]
	Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 71)
	Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8877]
	Kernel driver in use: piix4_smbus
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
	Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge [1043:8877]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e0]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e1]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e2]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e3]
	Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e4]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e5]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e6]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:14e7]
01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev c0)
	Kernel driver in use: pcieport
02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479]
	Kernel driver in use: pcieport
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT [1002:0e3a]
	Kernel driver in use: amdgpu
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28]
	Kernel driver in use: snd_hda_intel
03:00.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:73a6]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:73a6]
	Kernel driver in use: xhci_hcd
03:00.3 Serial bus controller [0c80]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 USB [1002:73a4]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 USB [1002:0408]
	Kernel driver in use: i2c-designware-pci
04:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P5 Plus NVMe PCIe SSD [c0a9:5407]
	Subsystem: Micron/Crucial Technology P5 Plus NVMe PCIe SSD [c0a9:0100]
	Kernel driver in use: nvme
05:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f4] (rev 01)
	Kernel driver in use: pcieport
06:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:0b.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:0c.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
06:0d.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f5] (rev 01)
	Kernel driver in use: pcieport
0a:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)
	DeviceName: Intel I225-V LAN
	Subsystem: ASUSTeK Computer Inc. Ethernet Controller I225-V [1043:87d2]
	Kernel driver in use: igc
0b:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
	Subsystem: Foxconn International, Inc. MT7922 802.11ax PCI Express Wireless Network Adapter [105b:e0cd]
	Kernel driver in use: mt7921e
0c:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f7] (rev 01)
	Subsystem: ASMedia Technology Inc. Device [1b21:3328]
	Kernel driver in use: xhci_hcd
0d:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f6] (rev 01)
	Subsystem: ASMedia Technology Inc. Device [1b21:3328]
	Kernel driver in use: ahci
0e:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c6)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e]
	Kernel driver in use: amdgpu
0e:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640]
	Kernel driver in use: snd_hda_intel
0e:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] VanGogh PSP/CCP [1022:1649]
	Subsystem: ASUSTeK Computer Inc. VanGogh PSP/CCP [1043:8877]
0e:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b6]
	Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
	Kernel driver in use: xhci_hcd
0e:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b7]
	Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
	Kernel driver in use: xhci_hcd
0f:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b8]
	Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
	Kernel driver in use: xhci_hcd

Axios

infinitymdm 0b:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express
Wireless Network Adapter [14c3:0616]
Subsystem: Foxconn International, Inc. MT7922 802.11ax PCI Express Wireless Network Adapter [105b:e0cd]
Kernel driver in use: mt7921e

infinitymdm

Axios Interesting. I wonder why my system isn't trying to use that chip for Bluetooth? inxi -Fxxxra spits out the following for Bluetooth:

Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-11:5
    chip-ID: 0489:e0e2 class-ID: e001 serial: 000000000
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends

Know of any way I can convince my system to use that MT7922 chip for bluetooth?

Axios

infinitymdm I would boot the 4.3 iso and compare the two ouputs

Axios

infinitymdm Everything cool in that respect mine lists the same to 1lsusb listing
and 1 lspci listing Yes they show that as a dual chip.
If those two outputs look the same the prob is probably elsewhere.

infinitymdm

Axios I would boot the 4.3 iso and compare the two ouputs

I'll have to get myself a new USB drive before I can do that. I had a Ventoy disk set up, but it seems to have perished.

The other lead I have is updating the BIOS. Of course, to do that I'll also need a USB drive... so once I get one I'll try those things (one at a time, of course) and report back.

brent

https://www.adamintech.com/use-lspci-lsscsi-lsusb-lsblk-to-display-devices-in-linux/
"lspci: lspci lets you see connected PCI/PCI express devices. Such examples would involve network cards and graphics cards.
lsusb: lsusb will display your connected usb devices. This can widely range from usb drives to network adapters. "

I cant tell if the omission in one command is relevant. Over my head here though

Axios

brent bluetooth has to talk over dbus

infinitymdm

brent I would have assumed the WiFi and Bluetooth were implemented in the same device - that's usually how it's done. But the inxi output had me convinced otherwise. Now that Axios has pointed out that my WiFi chipset also has Bluetooth capabilities, I'm convinced that inxi knows about as much about what's going on here as I do.

brent

infinitymdm . Now that Axios has pointed out

yeah I was really hoping he would show up on this one🙂
this is a mystery