On 29/05/14 18:18, Mick wrote: > On Thursday 29 May 2014 07:27:24 Mick wrote: >> On Thursday 29 May 2014 00:05:16 William Kenworthy wrote: >>> On 29/05/14 06:28, Mick wrote: >>>> On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: >>>>> On 28/05/14 21:42, Mick wrote: >>>>>> Hmm ... am I alone in this quest? >>>>> >>>>> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 >>>> >>>> Thanks! I missed this bug when I glanced earlier. However, it does >>>> not mention rfcomm is now missing, or the fact that the gentoo rc >>>> script fails to initialise bluethooth and complains about rfcomm >>>> service not having started/exist, or that bluetoothctl now does not >>>> work at all. Is all this down to a missing udev rule? >>> >>> No its the fact that bluez 5 has been redesigned to fit in more with the >>> systemd world. >>
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 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_sio,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. BillK
