LinHES Forums http://forums.linhes.org/ |
|
Bluetooth not working in LinHES? http://forums.linhes.org/viewtopic.php?f=23&t=24227 |
Page 1 of 1 |
Author: | Vyvontdus [ Sun Aug 23, 2015 7:46 pm ] |
Post subject: | Bluetooth not working in LinHES? |
Hoping someone can help here...... Installed 8.3 from the ISO, worked fine, put in MCE IR and PVR 150 . All looks good. I now want to install a bluetooth keyboard and mouse (just for the better range they give) Keyboard is a Logitech K480 and M557 mouse. Ok so go to install bluez Code: [mythtv@envy ~]$ su [root@envy mythtv]# pacman -Sy bluez bluez-utils :: Synchronizing package databases... core is up to date extra is up to date resolving dependencies... looking for inter-conflicts... Packages (3): Name New Version Net Change Download Size extra/libical 1.0-3 1.87 MiB 0.30 MiB extra/bluez 5.27-1 1.32 MiB 0.42 MiB extra/bluez-utils 5.27-1 4.89 MiB 0.78 MiB Total Download Size: 1.50 MiB Total Installed Size: 8.08 MiB :: Proceed with installation? [Y/n] And all appears good. Looks like the days of bluez-simple-agent are over so lets check out the bluetooth dongle thingy Code: root@envy mythtv]# hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 5C:F3:70:69:EE:73 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:564 acl:0 sco:0 events:29 errors:0 TX bytes:358 acl:0 sco:0 commands:29 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Well its down so lets fix that Code: [root@envy mythtv]# hciconfig hci0 up and indeed Code: [root@envy mythtv]# hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 5C:F3:70:69:EE:73 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1128 acl:0 sco:0 events:58 errors:0 TX bytes:716 acl:0 sco:0 commands:58 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'BCM20702A' Class: 0x000000 Service Classes: Unspecified Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) Lets start the bluetooth service and see if we can find and pair Code: [root@envy mythtv]# add_service.sh bluetoothd adding bluetoothd [root@envy mythtv]# sv start bluetoothd ok: run: bluetoothd: (pid 3412) 14s [root@envy mythtv]# hcitool scan Scanning ... 00:1F:20:F0:87:AB Logitech Keyboard K480 [root@envy mythtv]# hcitool cc 00:1F:20:F0:87:AB So hcitool sees the keyboard but it wont pair -no command line error is given - but see the output of hcidump -at below for logs from those two commands. From looking at the hci cc command and events it looks like the host initiates the disconnect 0x01|0x0006 command because of reason 0x13 whatever that is Exactly the same thing happens with the mouse. I tried simple pairing too. Using bluetoothctl instead simply freezes at its prompt - and I have to ctrl-C out to get my terminal back. If I look at /var/log/date/messages I get the following after running bluetoothctl. 2015-08-22T16:03:27.896445-06:00 bc_myth dbus[936]: [system] Activating service name='org.bluez' (using servicehelper) 2015-08-22T16:03:27.899104-06:00 bc_myth dbus[936]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code A check on Google reveals a variety of possible solutions - none of which work for me. From bluetoothd not running (it is) to adding symbolic links to almost every permutation of dbus-org.bluez and python and dbus imaginable. I am hoping someone has solved this - I know its something silly I am missing. Help! This is the log output from running the hcitool scan and cc commands Code: [root@envy mythtv]# hcidump -at
HCI sniffer - Bluetooth packet analyzer ver 5.27 device: hci0 snap_len: 1500 filter: 0xffffffffffffffff 2015-08-23 19:04:33.482501 < HCI Command: Inquiry (0x01|0x0001) plen 5 lap 0x9e8b33 len 8 num 0 2015-08-23 19:04:33.483972 > HCI Event: Command Status (0x0f) plen 4 Inquiry (0x01|0x0001) status 0x00 ncmd 1 2015-08-23 19:04:34.019934 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:1F:20:F0:87:AB mode 1 clkoffset 0x4d86 class 0x002540 rssi -62 2015-08-23 19:04:43.725332 > HCI Event: Inquiry Complete (0x01) plen 1 status 0x00 2015-08-23 19:04:43.725481 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 bdaddr 00:1F:20:F0:87:AB mode 1 clkoffset 0x4d86 (valid) 2015-08-23 19:04:43.726329 > HCI Event: Command Status (0x0f) plen 4 Remote Name Request (0x01|0x0019) status 0x00 ncmd 1 2015-08-23 19:04:44.434290 > HCI Event: Remote Host Supported Features Notification (0x3d) plen 14 bdaddr 00:1F:20:F0:87:AB Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 2015-08-23 19:04:44.452242 > HCI Event: Remote Name Req Complete (0x07) plen 255 status 0x00 bdaddr 00:1F:20:F0:87:AB name 'Logitech Keyboard K480' 2015-08-23 19:05:06.456902 < HCI Command: Create Connection (0x01|0x0005) plen 13 bdaddr 00:1F:20:F0:87:AB ptype 0xcc18 rswitch 0x01 clkoffset 0x0000 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 2015-08-23 19:05:06.457915 > HCI Event: Command Status (0x0f) plen 4 Create Connection (0x01|0x0005) status 0x00 ncmd 1 2015-08-23 19:05:07.625845 > HCI Event: Connect Complete (0x03) plen 11 status 0x00 handle 11 bdaddr 00:1F:20:F0:87:AB type ACL encrypt 0x00 2015-08-23 19:05:07.625931 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 handle 11 2015-08-23 19:05:07.627792 > HCI Event: Command Status (0x0f) plen 4 Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1 2015-08-23 19:05:07.634841 > HCI Event: Read Remote Supported Features (0x0b) plen 11 status 0x00 handle 11 Features: 0xbc 0x04 0x82 0x78 0x00 0x06 0x59 0x83 2015-08-23 19:05:07.634869 < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3 handle 11 page 1 2015-08-23 19:05:07.636838 > HCI Event: Command Status (0x0f) plen 4 Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1 2015-08-23 19:05:07.639840 > HCI Event: Read Remote Extended Features (0x23) plen 13 status 0x00 handle 11 page 1 max 1 Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 2015-08-23 19:05:07.639902 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 bdaddr 00:1F:20:F0:87:AB mode 2 clkoffset 0x0000 2015-08-23 19:05:07.639911 < ACL data: handle 11 flags 0x00 dlen 10 L2CAP(s): Info req: type 2 2015-08-23 19:05:07.641838 > HCI Event: Command Status (0x0f) plen 4 Remote Name Request (0x01|0x0019) status 0x00 ncmd 1 2015-08-23 19:05:07.645784 > ACL data: handle 11 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x0280 Fixed Channels Unicast Connectless Data Reception 2015-08-23 19:05:07.645813 < ACL data: handle 11 flags 0x00 dlen 10 L2CAP(s): Info req: type 3 2015-08-23 19:05:07.648840 > HCI Event: Number of Completed Packets (0x13) plen 5 handle 11 packets 2 2015-08-23 19:05:07.649669 > ACL data: handle 11 flags 0x02 dlen 20 L2CAP(s): Info rsp: type 3 result 0 Fixed channel list 0x00000006 L2CAP Signalling Channel L2CAP Connless 2015-08-23 19:05:07.665845 > HCI Event: Remote Name Req Complete (0x07) plen 255 status 0x00 bdaddr 00:1F:20:F0:87:AB name 'Logitech Keyboard K480' 2015-08-23 19:05:09.642311 < HCI Command: Read Clock Offset (0x01|0x001f) plen 2 handle 11 2015-08-23 19:05:09.643717 > HCI Event: Command Status (0x0f) plen 4 Read Clock Offset (0x01|0x001f) status 0x00 ncmd 1 2015-08-23 19:05:09.643769 < HCI Command: Disconnect (0x01|0x0006) plen 3 handle 11 reason 0x13 Reason: Remote User Terminated Connection 2015-08-23 19:05:09.644715 > HCI Event: Command Status (0x0f) plen 4 Disconnect (0x01|0x0006) status 0x00 ncmd 1 2015-08-23 19:05:09.721713 > HCI Event: Disconn Complete (0x05) plen 4 status 0x00 handle 11 reason 0x16 Reason: Connection Terminated by Local Host |
Author: | nullsmack [ Tue Sep 08, 2015 5:26 pm ] |
Post subject: | Re: Bluetooth not working in LinHES? |
I am stuck at the same place you are. I'm trying to connect my wii remote for emulation use and can't pair it either. Starting bluetoothctl fails because it is expecting to connect to D-BUS. Starting systemctl fails for the same reason but it gives an error message and then closes. The error message is "Failed to get D-Bus connection: No connection to service manager." Apparently the project is using an old runit instead of the newer systemd to start services and this is causing problems with bluez? I'm not one to want to use the wii remote as a mouse device, so I don't want to go that way and use the wminput. It probably won't work either. |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |