More hciconfig options:
[root@utopia ~]# hciconfig hci0 reset [root@utopia ~]# hciconfig -a hci0: Type: USB BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1 UP RUNNING PSCAN RX bytes:2224 acl:0 sco:0 events:61 errors:0 TX bytes:733 acl:0 sco:0 commands:59 errors:2 Features: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'Accel-OB2' Class: 0x4a0104 Service Classes: Networking, Capturing, Telephony Device Class: Computer, Desktop workstation HCI Ver: 2.0 (0x3) HCI Rev: 0x3 LMP Ver: 2.0 (0x3) LMP Subver: 0x3 Manufacturer: Cambridge Silicon Radio (10)
After the hciconfig reset, this adaptor has never stopped working. Do I really have to issue hciconfig hci0 reset each boot for bluetooth to work? Is this still a kernel related problem?
More hciconfig options:
[root@utopia ~]# hciconfig hci0 reset
[root@utopia ~]# hciconfig -a
hci0: Type: USB
BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING PSCAN
RX bytes:2224 acl:0 sco:0 events:61 errors:0
TX bytes:733 acl:0 sco:0 commands:59 errors:2
Features: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Accel-OB2'
Class: 0x4a0104
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x3 LMP Ver: 2.0 (0x3) LMP Subver: 0x3
Manufacturer: Cambridge Silicon Radio (10)
After the hciconfig reset, this adaptor has never stopped working. Do I really have to issue hciconfig hci0 reset each boot for bluetooth to work? Is this still a kernel related problem?