On Sep 21, 2011, at 11:29 AM, Thierry Chatelet wrote: > On Wednesday 21 September 2011 15:56:42 David Roguin wrote: >> Hi! >> >> I have an InputClass section in my xorg.conf that catches whenever a >> touchpad is detected (MatchIsTouchpad "on"), but the driver on that >> section never loads. If I change the MatchIsTouchpad for other Match like >> the MatchIsPointer the driver gets loaded, but of course it doesn't work >> properly. >> >> I was wondering what is happening that triggers that kind of behavior. I'm >> thinking maybe udev is not recognizing properly the tochpad… (i can't >> think of anything else right now :) ) If udev is guilty, then how can I >> add a rule to to that? >> >> By the way, I have a macbook pro (8,1) with debian wheezy. >> >> Any ideas? >> Thanks! >> -- >> David > > What happen if you remove/comment out that inputclass section and let > udev/xorg > work things out by themselves?
It lets evdev driver handles the Pointer, and I have a touchpad as useful as a mouse with only one button. There's an evdev that catches all the mouse like interfaces, and that's the one handling the touchpad events. D. > Thierry > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cdab218e-9030-4c1d-b780-70702d61f...@gmail.com