I'm really puzzled by this. I'm using the same machine, with the exact
same touchpad based on the USB id, and I don't see anything like this.
The bcm5974 driver in precise is identical to the one in 3.2, aside from
the patch that Chase mentioned that wasn't present prior to 3.2.0-17.26.
It's hard to imagine what might be causing the difference in behavior.

The logs show that even when the touchpad isn't fully functioning that
it's being correctly detected, that the driver is being loaded, and that
X is using the synaptics driver to support it. The driver never sends
relative motion events, so the fact that it works at all suggests that
the absolute coordinate events are being sent from the kernel driver.

Chase, given the above, can you provide any insight on what the driver
could be doing that could be resulting in the behavior that Clint is
seeing? On the surface everything looks okay, yet there's obviously some
problem here that I'm at a loss to explain.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936552

Title:
  MacBookAir 4,1 trackpad does not work with synaptics driver until boot
  into 3.2.1 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/936552/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to