FS#13665 - /etc/rc.d/bluetooth in BlueZ 4.30 stops USB dongle from working

Attached to Project: Arch Linux
Opened by Hans-Kristian Arntzen (Themaister) - Wednesday, 04 March 2009, 20:52 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 28 May 2009, 19:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
My broadcom based USB Bluetooth dongle works normally by doing sudo hciconfig hci0 up, but the "/usr/bin/hidd --server" command in the /etc/rc.d/bluetooth stops it from working.

Additional info:
BlueZ 4.30

Config files are as they are given in the package.

Working:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:10:60:AD:B0:4E ACL MTU: 377:10 SCO MTU: 64:8
UP RUNNING
RX bytes:64984 acl:3258 sco:0 events:508 errors:0
TX bytes:7034 acl:169 sco:0 commands:278 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'Broadcom BCM2035'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
Manufacturer: Broadcom Corporation (15)

After starting bluetooth daemon:

$ hciconfig -a
hci0: Type: USB
BD Address: 00:10:60:AD:B0:4E ACL MTU: 377:10 SCO MTU: 64:8
UP RUNNING
RX bytes:65592 acl:3258 sco:0 events:521 errors:0
TX bytes:7340 acl:169 sco:0 commands:292 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

To get it working again, I have to stop daemon and bring the interface back and up again.

$ lsusb
Bus 001 Device 003: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 009: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 002 Device 003: ID 046d:c042 Logitech, Inc.
Bus 002 Device 002: ID 04f2:0112 Chicony Electronics Co., Ltd KU-8933 Keyboard with PS/2 Mouse port
Bus 002 Device 001: ID 1d6b:0001

Drivers used and tried are both hci_usb and btusb.

Steps to reproduce:

Start bluetooth daemon with (at least my dongle), verify that it is not working.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 28 May 2009, 19:01 GMT
Reason for closing:  Fixed
Comment by fluxbox (fluxbox) - Thursday, 05 March 2009, 16:09 GMT
Same dongle, same problem here. Error message in /var/log/daemon.log is:

Can't write class of device: Unknown error 4294967186 (-110)

I don't think the hidd command is responsible, I get the same error when starting bluetoothd manually.
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 07 March 2009, 06:54 GMT
I am not sure about this (i don't use bluetooth devices), but maybe related with this  FS#13633 

Try this
mv /etc/udev/bluetooth.rules /etc/udev/rules.d/60-bluetooth.rules
Comment by fluxbox (fluxbox) - Saturday, 07 March 2009, 15:37 GMT
Thanks, but it didn't help. Looks like the udev rules are only for PC Cards.
Comment by fluxbox (fluxbox) - Tuesday, 26 May 2009, 08:43 GMT
The problem is solved in bluez 4.40.

Loading...