Bug 13104 - Apple Aluminium Bluetooth Keyboard is not usable
Summary: Apple Aluminium Bluetooth Keyboard is not usable
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 12:03 UTC by Michael Long
Modified: 2009-10-30 10:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.29.1, 2.6.30-rc2
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
.config of 2.6.29.1 (45.29 KB, application/octet-stream)
2009-04-16 12:03 UTC, Michael Long
Details

Description Michael Long 2009-04-16 12:03:47 UTC
Created attachment 21010 [details]
.config of 2.6.29.1

Latest working kernel version: not sure maybe 2.6.22
Earliest failing kernel version: not sure maybe 2.6.25
Hardware Environment: x86, x86_64
Software Environment: bluez-libs-3.36, bluez-utils 3.36

Problem Description: 

When I try to connect the Apple Aluminium Bluetooth Keyaboard via hidd --connect XX:XX:XX:XX:XX:XX there is no new input-device created, instead dmesg shows:

[  623.035770] apple 0005:05AC:022D.0005: parse failed
[  623.035776] apple: probe of 0005:05AC:022D.0005 failed with error -14

hidd --show still shows 

XX:XX:XX:XX:XX:XX Apple Inc. Keyboard [05ac:022d] connected

and a running hcidump -X shows a valid communication (to my knowledge) like:

> ACL data: handle 6 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 19]
      HIDP: Data: Input report
      0000: 01 00 00 0a 1c 00 00 00  00                       .........
> ACL data: handle 6 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 19]
      HIDP: Data: Input report
      0000: 01 00 00 0a 1c 18 00 00  00                       .........
> ACL data: handle 6 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 19]
      HIDP: Data: Input report
      0000: 01 00 00 18 1c 00 00 00  00

Unfortunately I can't really remember when this started, but I've had used this keyboard with the same USB-BT-dongle a while back with bluez 2.x and a kernel 2.6.2x. I've tested this on several newer custom and distribution kernels with the same reproducable result.
Comment 1 Rickard Nilsson 2009-05-22 07:19:10 UTC
I get exactly the same error, but if I turn the keyboard off and on, it connects correctly and becomes usable. However, it is annoying to having to do that each time I start my computer.

I run 2.6.29.4 x86_64, I haven't tried with any other kernel (the keyboard is new).
Comment 2 Michael Long 2009-10-30 10:49:28 UTC
Due to hardware change and newer kernel, this problem is not reproducable anymore. Fixed for me.

Note You need to log in before you can comment on or make changes to this bug.