On 01/08/2018 06:24 PM, Antony Stone wrote: > On Monday 08 January 2018 at 17:20:42, Lars Noodén wrote: > >> The Blueman Assistant appears to let me turn the bluetooth adapter on or >> off. However, when I go to actually set up a new device, it claims no >> adapters found. >> >> bluetoothctl can connect to the daemon but cannot find any devices either. >> "No default controller available" > > I ran into this the other day. > > You have to run it as root (unlike much of the other bluetooth stuff).
Even running bluetoothctl as root, it still complains about no default controller available. From the new dmesg: [ 2.711929] Bluetooth: Core ver 2.22 [ 2.711938] NET: Registered protocol family 31 [ 2.711939] Bluetooth: HCI device and connection manager initialized [ 2.711941] Bluetooth: HCI socket layer initialized [ 2.711943] Bluetooth: L2CAP socket layer initialized [ 2.711948] Bluetooth: SCO socket layer initialized [ 2.713202] [drm] Memory usable by graphics device = 4096M [ 2.713204] [drm] Replacing VGA console driver [ 2.714734] Console: switching to colour dummy device 80x25 [ 2.722975] Bluetooth: HCI UART driver ver 2.3 [ 2.722977] Bluetooth: HCI UART protocol H4 registered [ 2.722978] Bluetooth: HCI UART protocol BCSP registered [ 2.722978] Bluetooth: HCI UART protocol LL registered [ 2.722979] Bluetooth: HCI UART protocol ATH3K registered [ 2.722979] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 2.723011] Bluetooth: HCI UART protocol Intel registered [ 2.723021] Bluetooth: HCI UART protocol Broadcom registered [ 2.723021] Bluetooth: HCI UART protocol QCA registered [ 2.723022] Bluetooth: HCI UART protocol AG6XX registered [ 2.723022] Bluetooth: HCI UART protocol Marvell registered /Lars _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
