On Friday 30 May 2014 06:34:13 Mick wrote: > On Thursday 29 May 2014 23:32:55 William Kenworthy wrote: > > I am not using systemd either - there is no bluetoothctl service (its an > > application and written with no remote control capabilities - why?: no > > idea - in my reading I came across a message saying that its designed > > for use with systemd but I thought it would still need the remote option > > unless bluetoothctl like functions are natively included in systemd) > > > > You will probably have to load the modules manually > > (/etc/conf.d/modules) - mine do load automatically though > > Right, so did mine until recently. I'm guessing that it's something to do > with udev, or with changes in the kernel that affect my Broadcom bluetooth > chip. > > > moriah ~ # lsmod|grep bt > > btusb 14099 0 > > bluetooth 191573 24 bnep,btusb,rfcomm > > usbcore 132770 10 > > btusb,usblp,uhci_hcd,usb_storage,usbserial,ehci_hcd,ehci_pci,usbhid,ftdi_ > > si o,cdc_acm moriah ~ # > > > > Sounds like you have more than one problem and you need to get the > > modules loaded and working first, then you can run bluetoothctl manually. > > I already tried that. The modules load, hciconfig works to bring up hci0, > but bluetoothctl complains that there is no available bluetooth > controller. :-/
I tried bluetooth with another laptop - also broadcom bluetooth but a different chip. Well, what do you know. I had to manually modprobe bnep and rfcomm, but /etc/init.d/bluetooth started without complaining that it needs the rfcomm service and bluetoothctl worked fine showing the bt controller SSID and other devices in the vicinity. So the problem seems to be with the particular broadcom BCM2046 Bluetooth device that I have on my laptop. :-( I've posted in the forums in case someone there has any ideas. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
