search

blueman-project / blueman

Blueman is a GTK+ Bluetooth Manager
GNU General Public License v3.0
1.27k stars 192 forks source link

Broadcom Corp. BCM2046B1 Not Working #1348

Closed JordanPlayz158 closed 4 years ago

JordanPlayz158 commented 4 years ago

blueman: 2.1.3-1 BlueZ: 5.54-2 Distribution: Manjaro Desktop environment: XFCE

(I unplugged and replugged in my adapter and tried to scan for devices blueman-applet --loglevel debug: https://pastebin.com/yspGvPxs

bluetoothctl list (didn't think 1 line of text warranted a pastebin): Controller 98:00:20:04:00:00 Jordan-PC [default]

(I unplugged, replugged, and scanned) Output in "journalctl -f" (Think this contains most useful information): https://pastebin.com/qnT4F4Uv

I had to load up the device in a windows vm and found out it uses the BCM2046B1 (I tried lsusb and it only said Broadcom Corp.)

cschramm commented 4 years ago

First and foremost, this is clearly not a blueman issue, rather most probably firmware related. There are all sorts of issues with Broadcom Bluetooth chips and BCM2046 seems to be one of the bestest of them. You can even find a handful of issues that refer to it right here in blueman's issue tracker.

Regarding the blueman-applet log I see a rather usual startup, 10 seconds later an adapter shows up and another 24 seconds later it disappears again. There's nothing about an attempted discovery. :thinking:

Regarding the syslog, I fully agree that kernel: Bluetooth: hci0: command 0x0401 tx timeout is concerning, yes.

Unfortunately I have no idea how and what firmware Arch ships for those chips but I think your only chance will be to find a replacement.

JordanPlayz158 commented 4 years ago

Well the kernel: Bluetooth: hci0: command 0x0401 tx timeout happens when I try to scan via the gui (blueman-manager) so I think if we could fix that shouldn't the bluetooth work?

cschramm commented 4 years ago

Probably, but it's most probably related to firmware and unless somebody already did some work that helps you (i.e. you can find a relevant update somewhere), the only thing you could go through is stuff like downloading some official firmware versions and somehow getting them into the Linux driver and see how things evolve.

JordanPlayz158 commented 4 years ago

I will look for drivers but solution will most likely be to find a replacement Bluetooth adapter