Bluetooth not working on Asus B650E-I
infinitymdm no worries, I was thinking it would be mini pcie like this one I just picked up for a laptop refurbishment.
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 
- Edited
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
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: -110Axios 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 initializedNow off to play with BIOS settings
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.
- Edited
infinitymdm Never say bluetooth is dull-sheesh
I forget how its done on budgie I take it thats what your using go into startup programs
and see if you can disable bluemanager and just do a restart
then run sudo journalctl -p 3 -b | grep Bluetooth and see if that error goes away
You can run blueman-manager from terminal and see if it starts and gives you an icon applet
(Interestingly enough, the settings page appears in Budgie Control Center, but there is no icon on the taskbar)
If the blueman-applet dont contact home it doesnt show up on taskbar
And if we cant get signs of life from that I would say its a firmware issue because the applet talks
to bluetooth different.
I didnt see anything wrong with those listings except the error one.
The services and dameon are running.
Seems to zero in on firmware just not talking to each for some reason
infinitymdm 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.
again, out of my depth here, I just see patterns. last night and today (you likely have read/skimmed 25-30 articles too) in so much of my reading the person with the BT problem mentioned this correlation...one works and one doesn't....I never saw its significance ....do wifi and BT share common daemons/hardware?
(i always was a plug in the ether cord person)
- Edited
brent Thats a wild question about the only things on the board hardware would the
power supply,clock,and antenna circuits bluetooth and 2.4g wifi share the same antenna circuits.
everything else is pretty much seperate.
Its kinda one those 50/50 things
If your 2.4g wifi and bluetooth died it could be the antenna circuit on the pci board
If 5g,2.4,bluetooth died it could be power supply problem on pci board
If 5g,2.4,Bluetooth died could be the clock circuit on pci board.
You basically have 3chips on 1 big chip 5g,2.4g,bluetooth so communication to those 3 are seperate.
Clear as mud?
Just a way of making things smaller and more economic
My point earlier to him was
1 it appears harware is ok
2bluetoothctl (doesnt work)
3blueman manager/applet (dont work)
4 So its got to be something common to all those since terminal,and applet talk different to the bluetooth
kinda went around and right back to firmware it could be something else but I would not know what.
(Not sure I know everything common)
Just tidbit of info when you turn bluetooth off or sleep or any those things you are putting those chips
in a low power mode (Not turning them off like light switch otherwise you couldnt turn them back on)
And like harvey pointed out early on about those modes,sometimes when those chips are put into
low power mode they are a B**ch to wake up again if not designed properly.
I had him do the bios thing to see if it was switching alright to low power mode = (off) and it was.
I am done sorry got long winded.
Axios 4 So its got to be something common to all those since terminal,and applet talk different to the bluetooth
kinda went around and right back to firmware it could be something else but I would not know what.
(Not sure I know everything common)
you did a good job covering the bases. bug still seems the easiest and most likely.
antennta circuit, power supply problem, clock circuit...those are longshots and would only happen to me
. are they even testable with an ohmeter and positive and negative wands?
the testing to see if the chips would wake up eliminates variables.
in most mysteries, knowing what something is not, usually helps determining what the problem is. But this one?
hardware is mostly eliminated but not all the way. firmware a question mark. bios is eliminated? bug not eliminated. and software only doing about half of what it should? but systemctl services are fine. this is a tough one
Poking at things a bit more. It turns out my Ventoy drive hadn't died after all, just wasn't happy with my other PC for some reason (but that's a problem for future me). So I can boot up the old ISO and check things out. Previously, when I booted the 4.3 ISO the Bluetooth worked but WiFi (and built-in Intel LAN) did not. After install + upgrade, WiFi works and Bluetooth does not. Admittedly, WiFi is more important to me right now than Bluetooth, so I consider that an improvement in the situation.
If I need to boot that up and gather more logs I can do so. I may also try booting another distro (probably endeavorOS) and see if things work over there. (No chance of me distrohopping though - I vastly prefer working with Solus infrastructure.)
Oh, and another note - if I switch Bluetooth on and then off in the Budgie Control Center GUI, I do get an applet icon that indicates Bluetooth is off. But when booting, or when switching on, the applet icon doesn't appear in the system tray.
As I see it, the current most likely culprit is firmware. It's probably worth trying to bisect changes to the firmware files and see if I can find one that does both WiFi and Bluetooth for me. I recall seeing a thread somewhere that pointed out the specific file, so I guess I'll have to go dig that up again
Thanks again to all for help. I think my next steps are:
- Disable blueman-manager as @Axios has suggested and see if I get an applet (not sure if this is necessary considering what I posted above, but it probably can't hurt)
- Bisect changes to the firmware file and see if I can find a firmware binary that works for me
infinitymdm Just the fact it showed up means its seeing hardware.
I would prob just go to the firmware for now. (see if you can get it to act different)
Got One command I am working on but I cant get it to work right think it would tell us
but cant get it to work will keep messing with it.
Linux gets me errrrrrrr with these one liner error codes sheesh it is what it is..
Brent got it about right I think (software only doing about half of what it should) to put it mildly
Sorry I wasnt of more help.
infinitymdm Ahhh np just grumbling I guess just like to fix things but sometimes
they arent so simple. And since I dont keep up with programming anymore kinda the dark side
on whats happening Makes it kinda like the missing piece sometimes.
Its cool!! Wasnt meant anyway towards you And your Understanding of linux stuff made it enjoyable
- Edited
Hardware for linux show both those detected but with issues go figure they say kernel 5.17-6.3 supported
Thats a strange listing dont know how thats poss.
I got think about that for abit.. makes no sense
Making some computers work and others not...hmmm
Ya I knew it looked closer they list wifi as detected and bluetooth as working (stuff we already new)
Axios kernel 5.17-6.3 supported
Through the power of open source, we can find out exactly when support was added! I believe that the firmware binary of interest is BT_RAM_CODE_MT7922_1_1_hdr.bin in linux-firmware/mediatek. The git logs show 7 revisions to the firmware, with the first in August 2021. I've seen 5.19 mentioned in a couple of posts as the first kernel release with decent support for this chip, so I'll probably start my bisect at that July 2022 firmware update and see how things go.
Hopefully I'll have some time this evening to take a look. If I can't find any working firmware version, I'll boot up EndeavorOS (with kernel 6.2) from my Ventoy disk and see if things work there. If Bluetooth and WIFI work, I'll try stealing their firmware files and give those a try on Solus. That should let us eliminate bad firmware as the root cause here. Though hopefully I'll find a fix instead 
Axios that is wild.
: infinitymdm ahhh the old firmware heist from endeavour...thats an idea. I love my Ventoy. Instant OS and no more burning over usbs endlessly.
- Edited
brent We picked the wildest narliest animal to deal with its a complicated beast.
People all over the net would like to sh--t it and be done with it.
I am like how long has it been around 15years or so and we cant make it work properly yet..sheesh
It F**rts and goes up in smoke..rofl
Just needed a laff...
- Edited
Axios We picked the wildest narliest animal to deal with its a complicated beast.
People all over the net would like to sh--t it and be done with it.
I am like how long has it been around 15years or so and we cant make it work properly yet..sheesh"
yep. but we always pick that animal.
Stockholm Linux Syndrome definition: "Stockholm Linux syndrome is a proposed condition in which hostages develop a psychological bond with their captors.[1][2] It is supposed to result from a rather specific set of circumstances, namely the power imbalances contained in hostage-taking, kidnapping, and imbalanced relationships. Therefore, it is difficult to find a large number of people who experience Stockholm Linux syndrome to conduct studies with any sort of validity or useful sample size."
---sort of found on the internet/edit there's a reason we keep going back
Tested five firmware files, each downloaded by navigating from this page into the diff details and clicking the "plain" download link on the file details page.
Just in case there were any flaws in my thinking, here's the procedure I followed:
- Download all 5 firmware files, starting with the file dated June 2022.
- Using Nemo (opened as root) navigate to /lib/firmware/mediatek and rename the original firmware file (just appended .original to it).
- Copy the new firmware file into /lib/firmware/mediatek, making sure it has the correct filename.
- Reboot, then check for a) a Bluetooth icon and b) that -110 error code in the output of
sudo dmesg | grep -i bluetooth. - Repeat 3 and 4 for each test firmware file.
Unfortunately, none of the firmware files made any difference in either of my evaluation parameters. After testing, I removed the new firmware files and restored the original firmware filename, so the system should be back in the original state. I'll probably check whether Bluetooth works with EndeavorOS live tomorrow, but I'm honestly not too hopeful. I may just have to wait a while to get proper Bluetooth support 