I have the same problem with a the new(ish) Apple Aluminium Wireless
Keyboard. Exactly as the main description puts it. Connecting to the
device results in a connection that lasts a few seconds and then
dissapears.


Information about bluetooth dongle:
___________________________________________

sudo hcitool info 00:22:41:DA:AB:9F
Requesting information ...
        BD Address:  00:22:41:DA:AB:9F
        Device Name: Apple Wireless Keyboard
        LMP Version: 2.0 (0x3) LMP Subversion: 0x31e
        Manufacturer: Broadcom Corporation (15)
        Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
                <encryption> <slot offset> <timing accuracy> <role switch> 
                <sniff mode> <RSSI> <power control> <enhanced iscan> 
                <interlaced iscan> <interlaced pscan> <AFH cap. slave>
___________________________________________



Information about the keyboard:
___________________________________________

hciconfig hci0 version
hci0:   Type: USB
        BD Address: 00:10:60:F1:83:35 ACL MTU: 310:10 SCO MTU: 64:8
        HCI Ver: 2.1 (0x4) HCI Rev: 0x12e7 LMP Ver: 2.1 (0x4) LMP Subver: 0x12e7
        Manufacturer: Cambridge Silicon Radio (10)
___________________________________________



Trying to do the auth manually:
___________________________________________

sudo hciconfig hci0 reset; sudo hcitool cc 00:22:41:DA:AB:9F ; sudo hcitool 
auth 00:22:41:DA:AB:9F
HCI authentication request failed: Input/output error
___________________________________________



Trying the bluez-compat package I get these results:
___________________________________________

hidd --search
Searching ...
        Connecting to device 00:22:41:DA:AB:9F
Can't create HID control channel: Connection refused
___________________________________________

It waits until I type a code into the (bluetooth) keyboard, hit enter
and then returns the connection refused message.

-- 
[Jaunty] Cannot connect to a Microsoft Bluetooth Notebook Mouse 5000
https://bugs.launchpad.net/bugs/343727
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to