BCM4313, WIFI/Bluetooth, driver load sequence?

Hi,

I have a Broadcom BCM4313 in my HP Notebook. This device is a combo wifi/bt device. Some time back I spent a long time chatting with you folk on improving the signal strength, so that I could get both interfaces working. I seem to remember that one of the comments was “wait for kernel 3.4”.

So I have now upgraded to OpenSuSE 12.2. Though, during install, the suspect bcmsmac drivers were installed which set me back to square one (BT working/WIFI very poor signal strength). So I adding the Packman repo and installed the broadcom-wl and broadcom-wl-kmp-desktop packages.
This proved to be less than the outstanding success that I was hoping for! The WIFI signal strength was back to practical values BUT still no Bluetooth!!

That is, until, I tried toggling the RF Kill switch (F12 on this notebook). Then both (wifi and bt) interfaces worked. However, after a reboot the bt failed to come back up? I could get it back by toggling the kill switch (but not by running the rfkill utility?).

So, I guess that this is a step in the right direction. However, I would like to get it working properly. My guess is, that ,it is only a question of the order or timing of the start-up scripts?

Any advise, will be most welcome.

Regards, Martin

Hi,

Just a bit more information, in the hope that it “rings a bell” somewhere…

This is the output from:

grep “<datetime>” /var/log/messages | grep bluetooth

Sep 30 10:37:07 hp-dm1 bluetoothd[566]: Bluetooth daemon 4.99
Sep 30 10:37:07 hp-dm1 bluetoothd[572]: Starting SDP server
Sep 30 10:37:09 hp-dm1 kernel:    10.101009] bluetoothd[572]: segfault at 240 ip 00007fbccf5491a4 sp 00007fffedc295f0 error 6 in bluetoothd[7fbccf4f8000+b5000]
Sep 30 10:37:09 hp-dm1 bluetoothd[572]: HCI dev 0 down

*#### Press RFKill (turn off)*

Sep 30 10:38:10 hp-dm1 systemd[1]: Service bluetooth.target is not needed anymore. Stopping.

*#### Press RFKill (turn on)*

Sep 30 10:38:16 hp-dm1 bluetoothd[1572]: Bluetooth daemon 4.99
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Starting SDP server
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Listening for HCI events on hci0
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: HCI dev 0 up
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Proximity GATT Reporter Driver: Operation not permitted (1)
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Unable to load keys to adapter_ops: Function not implemented (38)
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Adapter /org/bluez/1572/hci0 has been enabled
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/HFPAG
Sep 30 10:38:16 hp-dm1 bluetoothd[1575]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSource

As the comments show, after stoping and starting (with the rfkill button), all seems well. In that the bluetooth daemon starts with a segfault?
If anyone can point me at any tips to debug a “segfault”, I’d be most grateful.

Regards, Martin