[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with Vaio touchpad



This sounds like the same thing I sent a mail before but for dell
inspiron 600m...  I'm copying an answer I got pretty useful:

00000000000000000000000000000000000000000000000000000000000000000
A. C. Censi 	
to debian-laptop

I have the same problem with an old vintage Sony Vaio PCG-R505JL, From
my research in the kernel lists, it seems that, for 2.6.11 maintainer
selected to disable the hardware double tapping of Alps touchpad, in
favor of doing it by software in the driver, as the kernel message
says.

Unfotunately it does not work well for most people like us, so in new
kernel version 2.6.12, when released, the driver eill return to use
hardware tapping. Until them you can try use the psmouse proto=imps,
as suggested in the Fedora list (as an option to kernel in grub or
lilo if psmouse is in kernel, or as an option to module, in
modprobe,conf). In any way for me it does not worked !?!?

ACC
00000000000000000000000000000000000000000000000000000000000000000

You can find that I guess in the archives...  On posterior mail
exchange ACC indicated 2.6.11 kernel detects the touchpad correctly,
and its tapping is just disabled by kernel in favor of software
drivers (besides some bugs related to touchpad and mouse present), but
on kernel 2.6.12 (not released yet, but I read the 1st rc change_log
and the changes required seem to be there) the tapping for the
correctly detected touchpad will be enabled again (at least that's
what I got)...  To revert touchpad detection to what is detected on
kernel 2.6.10, just modify boot parameter as mentioned by ACC, it may
work as it did for inspiron 600m, or it might not as it didn't for
ACC's Vaio...

Javier.


On 5/23/05, Thadeu Penna <tjpp@if.uff.br> wrote:
> I can confirm the same weird behavior on HP Pavillion zx5820 here.
> I went back to sarge 2.6.8 to get it working fine again. It is a pity
> because I had to recompile alsa since 2.6.8 does not get along with my
> atiixp  soundcard...
> 
> Curt Howland wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi. Up-To-Date Sid on a Vaio PCG-GRT170.
> >
> > I finally tracked down the problem I've had trying to go from kernel
> > 2.6.10 to 2.6.11, which I noticed recently became the "official"
> > latest Debian kernel. Or rather, 2.6.10 is showing up as obsolete
> > today.
> >
> > Anyway, when the "psmouse" module loads in 2.6.10, I get the following
> > message:
> > - -----------
> > ~# modprobe psmouse
> > input: PS/2 Generic Mouse on isa0060/serio1
> > - -----------
> >
> > and everything works just fine. Smooth fine position control, 3-button
> > emulation, copy/paste, strike the touchpad surface and it "clicks"
> > button 1, stuff like that.
> >
> > However, under 2.6.11, the following message comes up:
> > - -----------
> > ~# modprobe psmouse
> > ALPS Touchpad (Glidepoint) detected
> >   Disabling hardware tapping
> > input: AlpsPS/2 ALPS TouchPad on isa0060/serio1
> > - -----------
> >
> > Fine movement is no longer smooth, distance is inconsistent,
> > copy/paste is flaky to say the least, and worst of all there is no
> > "click" when I hit the touchpad with my finger.
> >
> > Is there a way to disable checking, to force "PS/2 Generic"-ness upon
> > the module? Sometimes hardware detection can go too far, it seems.
> >
> > I'm not going to open a trouble ticket on the module until it's
> > obvious there is no way around the detection routine, or I can
> > communicate the action and fix to the kernel packagers.
> >
> > Curt-
> 
> 
> --
>   ___                  _                 .''`.
>    | |_  _. _| _      |_) _ ._ ._  _.   : :'  :
>    | | |(_|(_|(/_|_|  |  (/_| || |(_|   `. `'`
>                      Linux User #50500    `-
> Prof.Adjunto - Instituto de Física  ---Debian-
> Universidade Federal Fluminense     Alpha/i386
> 
> 
> --
> To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 


-- 
Javier-Elias Vasquez-Vivas



Reply to: