yes,
it was also known as brcm - but I got no results when I grepped the term
bcrm was not bluetooth specific
btbcm is bluetooth.
I appreciate all your efforts Rick. I am trying to think why it worked in Manjaro, and I seem to recall pamac recommended some additinal packages.
Do you think I should install pamac-all just to try it out?
Michael
I do have pamac installed. I use pamac-aur-git version.
Can you try yours to see if it calls up dependencies?
What am i looking for? What package?
broadcom bt or bcrm or BCM43 or BCM43-142 or BCM43-142A0
Most of them is bluez-utils
Edit:
sudo pacman -S --needed bluez bluez-utils
Did you look at this page?
Yes I followed the blog by @joekamprad https://discovery.endeavouros.com/bluetooth/bluetooth/2021/03/ and suggested blueberry. It talks about blueman and bluedevil for KDE and xfce, but I use Gnome 41.
I guess keep digging for a solution.
Edit: Maybe this helps?
Well I thought you were my best hope when I saw how systematically you approached helping the other user with the wlan blacklisting issue.
Should my /etc/modprobe.d/ be empty?
Since I have committed 100% to EOS, it’s a small price to pay. It’s an old driver, and these comapnies are driving more users to FOSS with their petty market manipulation. There is no chance I will buy anything with Broadcom/Lite-On inside.
At least Broadcom did not block the WLAN on the same chip. I really need bt, I can buy an external usb dongle, but I will have to research the chipsets in advance.
Thank you Rick
Michael
I just wondered if there was any files inside /etc/modprob.d/ that were blacklisting any modules. It’s posssible that they could be blacklisted somewhere else maybe? Or it’s just a firmware issue because it’s proptietary drivers. I have a lot of broadcom wifi but they are newer chips.
Did you try loading the btbcm module?
These are all the firmware i have on my system for bcrm
lsmod | grep btbcm
btbcm 20480 1 btusb
bluetooth 794624 5 btrtl,btintel,btbcm,btusb
[michael@eos22 ~]$ sudo modprobe -v btbcm
[michael@eos22 ~]$ sudo systemctl enable btbcm.service
Failed to enable unit: Unit file btbcm.service does not exist.
This is a module not a service. You load the module and then try to enable the bluetooth service. Same as the btusb module. You don’t try to enable the module as a service…
Edit: Failed to enable unit: Unit file btbcm.service does not exist.
sudo modprobe btbcm
sudo systemctl enable bluetooth.service
sudo systemctl start bluetooth.service
systemctl status bluetooth
Edit2: I also found this one in the AUR.
How did I miss that.
I will try soon.
Thank you. It is on my reading list. If you find something that explains the difference and how they are enabled, I would appreciate. In the meantime, I will check the archwiki.
It is my Sabbath, so I will check again tommorw night.
Michael
I haven’t read every post in this thread, so maybe this has already been mentioned, but…
Since this worked for you previously on Manjaro, perhaps it’s not an issue with the broadcom-bt-firmware-git package, but something else?
The bluez package updated from 5.63 to 5.64 yesterday (and a bug report that appears relevant was just opened today); you could try downgrading to the previous version and see if it works.
It’s strange as i am not having any issue with the updated bluez package on my hardware.
How did I miss that.
I will try soon.