[SOLVED] New kernel driver for the BCM5974 touchpad (Macbook Air, Penryn)

[eindgebruiker]

OK, this is the Penryn:

x: +4825
x: -4825
y: +4290
y: -0171

[Botto]

I can confirm these values.
I took 10 samples and calculated the mean value:


x: +4820
x: -4781
y: +4245
y: -0141


Looking at the debug output, I can see that it can feel 4 fingers. Can we use this in xorg config?

[letic]

Hey Henrik,

I'm experiencing some random issues with a MBP, when booting/rebooting the driver is working alternatively.

I guess this is due to usbhid loading before bcm5974. When checking the logs I can see the usbhid loading first most of the time.

I checked the quirks but they are correct. I put some info below, let me know what you would need to debug.

cat /etc/modprobe.d/bcm5974 
### Options for the bcm5974 driver

## quirks for the Macbook Air
#options usbhid quirks=0x05ac:0x0223:0x00020800,0x05ac:0x0224:0x00024800,0x05ac:0x0225:0x00020800

## quirks for the Macbook Pro Penryn
options usbhid quirks=0x05ac:0x0230:0x00020800,0x05ac:0x0231:0x00024800,0x05ac:0x0232:0x00020800

## Debug level - uncomment this to get raw packets in /var/log/debug
#options bcm5974 debug=99

lsusb | grep 05ac
Bus 007 Device 003: ID 05ac:0230 Apple Computer, Inc. 
Bus 007 Device 002: ID 05ac:8242 Apple Computer, Inc. 
Bus 003 Device 005: ID 05ac:820b Apple Computer, Inc. 
Bus 003 Device 004: ID 05ac:820a Apple Computer, Inc. 
Bus 003 Device 003: ID 05ac:820f Apple Computer, Inc. 
Bus 002 Device 002: ID 05ac:8502 Apple Computer, Inc.

Cheers
LeTic

[kosumi68]

eindgebruiker, Botto, much obliged!

Apparently the penryn trackpad is slightly shorter than the MBA. The values have been saved and will appear in the next release.

[Botto]

One bug I have found is when forcfully shutting down and booting up again, the trackpad doesnt have any of the advanced features, just moving the mouse, no tapping or anything.

[kosumi68]

Greetings Letic,

I'm experiencing some random issues with a MBP, when booting/rebooting the driver is working alternatively.
[..]
I checked the quirks but they are correct. I put some info below, let me know what you would need to debug.

Have you tried out the bcm5974-diagnostics at a point where you are experiencing problem? It could reveal something.

Otherwise, the thing that comes to mind is to check that no other files contains quirks in /etc/modprobe.d/. Also if your are running mouseemu, that could be a problem. A printout of dmesg when the problem appears is also helpful.

[kosumi68]

One bug I have found is when forcfully shutting down and booting up again, the trackpad doesnt have any of the advanced features, just moving the mouse, no tapping or anything.

This sounds profoundly odd. Could you please provide the output of dmesg when this happens? Maybe it is related to letics problem, maybe the quirk settings are ignored for some reason.

[kimtiede]

Heres one more Macbook Pro Penryn working.

I installed the 0.53 deb package and the quirks in /etc/modprobe.d/bcm5974 had the penryn commented out, so I had to change that. Afterwards it worked

Cheers and thanks a lot for the work!!

Kim

Macbook Pro Penryn
Ubuntu 8.04
Danish keyboard

[cyberdork33]

kosumi,

This will likely not be available in the Ubuntu kernel anytime soon. Would you like to put it in the mactel-support PPA? This should make it much easier for users to get the driver and update it.

https://launchpad.net/~mactel-support/+archive

Request to join, and I will gladly approve.

[_alex_]

Hi Henrik,

I just got my MacbookPro back from the repair shop. As expected everything works perfectly now. I'm using the latest (v0.53) driver. I too had the penryn line commented out in /etc/modprobe.d/bcm5974.
An easier way would be to just use one quirks line for both Air and Penryn as follows:

options usbhid quirks=0x05ac:0x0223:0x00020800,0x05ac:0x0224:0x00024800,0x05ac:0x0225:0x00020800,0x05ac:0x0230:0x00020800,0x05ac:0x0231:0x00024800,0x05ac:0x0232:0x00020800

Since there is no clash for the device ids, the hid module will use the corresponding quirk for the given hardware. That way you won't have to do any sort of hardware detection during installation.