Bluetooth not working on Asus B650E-I

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

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.

Axios

That Kernel driver in use: mt7921e went through some changes I think in 2022 in the 5 kernel wonder
if its fudded somehow
I checked is the right driver.
found in Linux kernels: 5.12–5.19, 6.0–6.3, 6.4-rc+HEAD

infinitymdm

I managed to dig up a 4GB drive and updated the BIOS. No luck 🙁

Hopefully I'll be able to acquire a larger USB drive sometime this week and check the state of things on the old ISO.

brent

https://askubuntu.com/questions/1447098/bluetooth-hci0-is-not-detected-corretcly
"I know that MEDIATEK MT7922 should be able to handle bluetooth, yet I can not turn it on. I tried everything from reinstalling bluez, btusb, etc...
Just now I dicovered that the system seems to think my bluetooth is Foxconn of USB type, even though MT7922 is PCIe."

not identical as yours, but was a bug, kernel-related. That ^ is 11/22 info.
https://forum.endeavouros.com/t/mediatek-mt7922-bluetooth-not-recognized/39841/15
This ^ is the usual troubleshooting (btctl/sysctl/dmesg/lspci) with some twists. But this ultimately solved it:
"Try shutdown the computer. Unplug the power cord. Press the power button for 30 seconds. Then plug it back in and start it up. Some of these onboard WiFi on motherboards have issues. Have seen it before on certain boards."

--I heard of 'letting the gremlins run out' but that took it to another level. That is also dated 3 weeks ago. Both these threads also reminded me that you never mentioned what 90% of inoperable bluetooth threads always mention: thebluez package/service.
I'm thinking bug or something insanely easily overlooked but you get the first one far more than the second one..

Axios

brent Bluetooth has to have a usb bluetooth device listed otherwise when you plugged
in your bluetooth usb device they would not be detected.
Those 2 things showing up in the lsusb and lspci are a good thing means things are loaded but if its buggy
thats whole different story.
Hardware wise appears cool (I mean its seeing hardware)
The main is the pci MT7922 and the usb is kinda like a subsystem

infinitymdm

brent I actually looked at both of these threads last night. Tried the shutdown procedure mentioned - no effect.

I'll certainly look into bluez. I'm pretty sure I looked at that early in my troubleshooting and concluded that my problem was at a lower level, but it definitely would be worth double-checking.

I'm considering building a kernel with some different options if we can't figure anything else out. The xanmod tip may be helpful there. Thanks.

Brucehankins

This is what I was finding also, lots of bugs related to the MediaTek MT stuff. It may be cleared up with a update to the kernel. I've found issues with the 5.15, 5.18, and 6.1 series kernels on other forums. As a PCI-e form factor card, they're pretty inexpensive (compared to the mobo). I just picked up an AX210 card for about $25. That may be an option for you if you don't want to wait for a potential fix.

infinitymdm

Brucehankins Unfortunately I'm on an ITX platform, so if I want to use a PCIe WiFi card I'd have to give up my dedicated GPU. That's a pretty tough sell 😁. I'm more likely to get a cheap USB Bluetooth module instead - always good to have one of those kicking around anyways.

infinitymdm

Axios I really appreciate your knowledge in this area. You make a good point that the hardware seems to be cooperating. But I'd like to call attention to this line in the dmesg output:

[    9.948229] Bluetooth: hci0: Opcode 0x c03 failed: -110

If I remember my reading correctly, this error code is associated with failing to load firmware to the MediaTek device. Most posts that have this error pop up also have some timeout errors though, and those aren't present here. I'm also hesitant to change firmware because WiFi is working correctly, which to me indicates that I probably have reasonable firmware. Trying different firmware is another troubleshooting option though.

brent

Axios I learn more from you in a single thread than I learn from reading 20 articles in a row (like we have all done for this subject) because no single author can distill the nuts and bolts essence of the problem into something understandable as you often do. Cheers.

Brucehankins

infinitymdm no worries, I was thinking it would be mini pcie like this one I just picked up for a laptop refurbishment.

brent

infinitymdm search engine-ing that -110 error is like going down new rabbit holes! Solved posts goes from firmware to bug to reboot to update to etc etc. Sordid reading. We're back where we started. Heartburn!

Axios

infinitymdm whenever try this see what it gives us
sudo journalctl -p 3 -b | grep Bluetooth

Lets see what this one shows to
sudo systemctl status bluetooth

Oh bout forgot can you turn off bluetooth in bios then let it bootup into solus
shutdown
Then enable back and bootup to solus see what happens
(Just a far fetched idea..lol) If it disables wifi to no problem go ahead and try it.

I think this will yeild some ideas
Laters

infinitymdm

Brucehankins It's possible that it is a mini-PCIe or M.2-2230 module. If it is, it's hidden beneath a bunch of plastic near the motherboard IO, and probably has a metal EMI shield around it. I'd rather not disassemble the system to find out, but you make a good point that it may be an option. Let's hope I can find a software fix first though 😁

infinitymdm

Axios sudo journalctl -p 3 -b | grep Bluetooth

marcus@summit ~ $ sudo journalctl -p 3 -b | grep Bluetooth
May 23 15:15:52 summit kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110

Axios sudo systemctl status bluetooth

marcus@summit ~ $ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Tue 2023-05-23 15:15:50 CDT; 2h 6min ago
       Docs: man:bluetoothd(8)
   Main PID: 713 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37412)
     Memory: 2.0M
        CPU: 8ms
     CGroup: /system.slice/bluetooth.service
             └─713 /usr/lib64/bluez/bluetooth/bluetoothd

May 23 15:15:50 summit bluetoothd[713]: Bluetooth daemon 5.66
May 23 15:15:50 summit bluetoothd[713]: Starting SDP server
May 23 15:15:50 summit bluetoothd[713]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
May 23 15:15:50 summit bluetoothd[713]: src/plugin.c:plugin_init() Failed to init vcp plugin
May 23 15:15:50 summit systemd[1]: Started Bluetooth service.
May 23 15:15:50 summit bluetoothd[713]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
May 23 15:15:50 summit bluetoothd[713]: src/plugin.c:plugin_init() Failed to init mcp plugin
May 23 15:15:50 summit bluetoothd[713]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
May 23 15:15:50 summit bluetoothd[713]: src/plugin.c:plugin_init() Failed to init bap plugin
May 23 15:15:50 summit bluetoothd[713]: Bluetooth management interface 1.22 initialized

Now off to play with BIOS settings🤞

infinitymdm

Axios can you turn off bluetooth in bios then let it bootup into solus
shutdown
Then enable back and bootup to solus see what happens

No change after turning the Bluetooth controller off in BIOS, booting into OS, enabling it again in BIOS, and booting once more.

While I was booted with the Bluetooth switched off I poked around a bit. There were no error messages in systemctl status bluetooth (it was inactive(dead) as you would expect), journalctl -p 3 -b | grep Bluetooth, or dmesg | grep -i bluetooth. WiFi worked just fine. Not sure if that's helpful information, but there it is.

« Previous Page Next Page »