Hi everyone,
I am setting up an installation of Qubes 4.2 in my laptop, the thing is that I use bluetooth headset so I was following the next guide. Audio qube
But the problem comes when I run into blueman-manager as it doesn’t show any device (at this moment, my bluetooth headphones are on) and no adapter, also, when blueman-manager is started, it tickles bluetooth on automatically but in a second it powers off (meaning there could be some incompatibility?)
I am able to get bluetooth.service running after sudo modprobe btusb and the systemctl start bluetooth.service but blueman-manager can’t detect anything and i get no info from it
Yes, I feel like the device is not working correctly (strange because in ParrotOS blueman-manager actually works and finds bluetooth devices) , not detected or that I am missing something as everything goes arround device
Maybe you have an issue with your bluetooth controller driver/firmware.
Detach your bluetooth controller from sys-audio.
Run this command in sys-audio terminal:
sudo journalctl -f -n0
Atach your bluetooth controller to sys-audio.
Check the log output in the terminal to see if there are any errors with bluetooth controller initialization.
Definitely there is something, the full response is too long for me to send (if you need this complete tell me and i will search how to share it) so I have pictures of various errors, being the second one the most important at first sight
Try to use latest kernel version and firmware in your template.
If it won’t help then check if it’s an issue specific to Qubes OS or it just don’t work in Linux in general. Boot from some Live USB Linux OS and test your bluetooth there.
I installed qubes with latest-kernel option as the normal installation threw me a kernel panic error and in parrotOS I actually can use my bluetooth, i can start blueman-manager and detect devices. It seems there is problem with both Qubes (or Linux) and Asus (and its Mediatek chip) because there are some posts about bluetooth problem.
If a buy a bluetooth adapter usb to use to connect to my headseat, could I fix this incompability? There would be any security-privacy risk from it? I’m just checking all available options
I checked and i have in both Fedora Forty. I tried the Fedora Live version, with the UI I couldn’t do much (didn’t work) but with bluetoothctl i was able to start scan, find phones and even connect to my headseat (version of fedora I think it was 40 too, and linux kernel 6.8.5, lower than in qubes).
What I found is two things and both about my bluetooth chip, which I think is MediaTekMT7922, and they are:
•First, How to easily enable MediaTek MT7922 Bluetooth on Ubuntu 24.04 - CNX Software in this article about ubuntu they suggest updating to kernel 6.10 (I am in 6.9.10, i saw yesterday 6.10 is announced in qubes), the thing is that now in Fedora I was able to use bluetooth without that kernel
•The second one is that if MediaTek is actually my bluetooth chip as other asus have, Mediatek is the same device that appears attached to my sys-net as it is the same for connecting to the network. I have tried running both blueman-manager and bluetoothctl in sys-net but got same errors than in sys-audio.
It is done and solved, as suspected, it was the kernel version. I upgraded from 6.9.10 to 6.10.3-1, started sys-audio and then sudo modprobe btusb systemctl start bluetooth.service
Connect from sys-usb the device (MediTek Wireless)
And then, both bluetoothctl and blueman-manager started working. As I am writing this, my headseat is paired and connected to my sys-audio. Thanks for all the help.
