[Jaunty] Cannot connect to a Microsoft Bluetooth Notebook Mouse 5000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NULL Project |
Invalid
|
Undecided
|
Unassigned | ||
bluez (Ubuntu) |
Fix Released
|
Undecided
|
Cyberfux | ||
Bug Description
I'm using Ubuntu 9.04 (Jaunty) Development Version and have all packages update to date.
This is a ThinkPad T43 laptop and the bluetooth adapter as listed by "lsusb | grep Bluetooth" is:
Bus 003 Device 002: ID 0a5c:201e Broadcom Corp. IBM Integrated Bluetooth IV
The mouse is a Microsoft Bluetooth Notebook Mouse 5000.
I use the "Setup a new device ..." option from the bluetooth applet on gnome-panel. I also have to mouse switched into pairing mode. The wizard dialog can detect my bluetooth mouse and it reports successful connecting to the mouse but at this time the mouse is still in pairing mode. (with previous Ubuntu the mouse should've returned to normal mode after pairing). I have to manually switch the mouse off and on to let it be in normal mode.
The Known devices list in Bluetooth Preferences dialog will show the mouse with an "i" icon but the mouse won't work no matter how I adjust the settings there.
I noticed if I use "sudo hcitool cc <address>" then the connect can exist for 1 second or so because "sudo hictool con" will show an output like "Connections: < ACL 00:1D:D8:93:24:28 handle 6 state 1 lm MASTER" but then the connection will drop.
When I manually start and stop the bluetooth adapter using "sudo hciconfig hci0 down/up", the /var/log/syslog will show informaitons like:
Mar 16 15:29:32 berlin bluetoothd[3753]: HCI dev 0 down
Mar 16 15:29:32 berlin bluetoothd[3753]: Adapter /org/bluez/
Mar 16 15:29:32 berlin bluetoothd[3753]: Stopping security manager 0
Mar 16 15:29:35 berlin bluetoothd[3753]: HCI dev 0 up
Mar 16 15:29:35 berlin bluetoothd[3753]: Starting security manager 0
Mar 16 15:29:40 berlin bluetoothd[3753]: Can't write inquiry mode for /org/bluez/
Mar 16 15:29:40 berlin bluetoothd[3753]: Adapter /org/bluez/
Mar 16 15:29:40 berlin kernel: [13071.930774] hci_cmd_task: hci0 command tx timeout
Following are other outputs using hcitool and hciconfig:
$ hcitool dev
Devices:
hci0 00:0E:9B:DC:B8:0A
$ hcitool scan
Scanning ...
00:1D:D8:93:24:28 Microsoft Bluetooth Notebook Mouse 5000
$ sudo hcitool info 00:1D:D8:93:24:28
Requesting information ...
BD Address: 00:1D:D8:93:24:28
Device Name: Microsoft Bluetooth Notebook Mouse 5000
LMP Version: 2.0 (0x3) LMP Subversion: 0x5cb2
Manufacturer: Infineon Technologies AG (9)
Features: 0xbc 0x02 0x04 0x38 0x18 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<sniff mode> <RSSI> <power control> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <AFH cap. slave>
<AFH class. slave>
$ hciconfig
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:3013 acl:0 sco:0 events:111 errors:0
TX bytes:688 acl:0 sco:0 commands:75 errors:0
$ hciconfig hci0 version
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
HCI Ver: 1.2 (0x2) HCI Rev: 0x9 LMP Ver: 1.2 (0x2) LMP Subver: 0x6963
Manufacturer: Broadcom Corporation (15)
$ hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Firmware 9.105 / 99
$ hciconfig hci0 features
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <AFH cap. slave> <AFH cap. master>
$ hciconfig hci0 ptype
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
$ hciconfig hci0 lm
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Link mode: SLAVE ACCEPT
$ hciconfig hci0 name
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Name: 'berlin-0'
$ hciconfig hci0 class
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Class: 0x0a210c
Service Classes: Networking, Capturing
Device Class: Computer, Laptop
$ hciconfig hci0 voice
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Voice setting: 0x0060 (Default Condition)
Input Coding: Linear
Input Data Format: 2's complement
Input Sample Size: 16 bit
# of bits padding at MSB: 0
Air Coding Format: CVSD
$ hciconfig hci0 pageparms
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Page interval: 2048 slots (1280.00 ms), window: 18 slots (11.25 ms)
$ hciconfig hci0 pageto
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
Page timeout: 8192 slots (5120.00 ms)
$ hciconfig hci0 afhmode
hci0: Type: USB
BD Address: 00:0E:9B:DC:B8:0A ACL MTU: 377:10 SCO MTU: 64:8
AFH mode: Enabled
Changed in bluez (Ubuntu): | |
status: | New → Confirmed |
summary: |
- [Jaunty] Cannot connect to a bluetooth mouse + [Jaunty] Cannot connect to a Microsoft Bluetooth Notebook Mouse 5000 |
tags: | added: regression |
affects: | hundredpapercuts → null |
Changed in bluez (Ubuntu): | |
status: | Confirmed → Fix Released |
I installed the netbook remix of jaunty on an acer aspire one
with an external dongle which worked fine on hardy
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
The mouse is a Microsoft Bluetooth Notebook Mouse 5000 which worked fine in hardy too
In syslog I find a Connection refused (111) error after trying to pair iwth the mouse... but gnome-bluetooth reports pairing successful
Using sudo hcitool cc <address>
makes the connection last 1 sec then it gets off