You are not logged in.
Hi there!
a month ago I managed to finally get my bluez working. It is a BCM43142 combo card, and you have to upload the firmware to make it work. Thanks to the fantastic package brcm_pathram_plus-git in AUR (https://aur.archlinux.org/packages/brcm … m_plus-git) I made it work.
Sadly, with the deprecation of bluez4 it does not work anymore. Maybe its a matter of device initialization, but when I try to path the firmware, it gets stuck at the first write:
writing
01 03 0c 00
writing
01 03 0c 00
writing
01 03 0c 00
writing
...
Besides, I have to "power on" the device to make hci0 interface to show up. Conversely, using bluez4 I didn't need to do such a thing.
As the creator of the AUR package has a different card than mine, and it still works for him (lucky you!), I would really appreciate if anyone could enlighten me here, because I'm swimming in the dark right now :S
Regards
Last edited by alejandro.perez (2013-11-05 16:50:03)
Offline
Now let's see what we can do
I need more input - type of hardware (brand, manufacturer a.s.o.)
Also the output of
lsusb -vv
for the device would be interesting (I guess it's an usb one because you use brcm_pathram_plus_usb)
Just to be sure: it is enabled in the BIOS setup? Did you update to the latest Bluez in the testing repo? My setup is now:
harvey@obelix ~ $ pacman -Qs blue
local/bluedevil 2.0-0.1
KDE bluetooth framework
local/bluez 5.10-2
Daemons for the bluetooth protocol stack
local/bluez-libs 5.10-2
Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.10-2
Development and debugging utilities for the bluetooth protocol stack
local/libbluedevil 2.0-0.1
A Qt4 wrapper for bluez used in the new KDE bluetooth stack
local/sbc 1.1-1
Bluetooth Subband Codec (SBC) library
The 'power on' defect is a different thing, I have this on different adapters also the ones natively supported.
Harvey
Last edited by Harey (2013-11-05 16:00:07)
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Oh my!
I just discovered the problem, thanks to Dropbox. It happens that I had, somehow, modified the firmware file !!!!
I restored it and everything works!
What I don't know is how to set tethering now that pand is gone :S
Regards
Offline
Glad you found out that I am not to blame
IMHO Bluetooth is not really usable with bluez5 ATM. Maybe hcitool is your friend? It seems to be the new bluetooth swiss army knife for the console.
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
I was unable to find out how to make a decent tethering with hcitool / bluetoothctl without pand (which was removed in bluez5). I just reverted to bluez4 (again) and to the previous blueman release, which used bluez4. Now I can use bluetooth again!
I will include them in my ignore list, and pray for not making my system unstable
Thanks for everything!
Offline