Re: Synaptics trouble in 2.5.73

[Peter Osterlund <petero2@telia.com>]

bert hubert <ahu@ds9a.nl> writes:

> Up to 2.5.68 my laptop had no problems with its touchpad but since upgrading
> to 2.5.73, neither gpm nor X see my mouse anymore. 
> 
> >From dmesg:
> 
> Jul  2 20:17:38 snapcount kernel: mice: PS/2 mouse device common for all mice
> Jul  2 20:17:38 snapcount kernel: inport.c: Didn't find InPort mouse at 0x23c
> Jul  2 20:17:38 snapcount kernel: logibm.c: Didn't find Logitech busmouse at 0x23c
> Jul  2 20:17:38 snapcount kernel: pc110pad: I/O area 0x15e0-0x15e4 in use.
> Jul  2 20:17:38 snapcount kernel: input: PC Speaker
> Jul  2 20:17:38 snapcount kernel: i8042.c: Detected active multiplexing controller, rev 1.0.
> Jul  2 20:17:38 snapcount kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
> Jul  2 20:17:38 snapcount kernel: Synaptics Touchpad, model: 1
> Jul  2 20:17:38 snapcount kernel:  Firware: 4.1
> Jul  2 20:17:38 snapcount kernel:  Sensor: 8
> Jul  2 20:17:38 snapcount kernel:  new absolute packet format
> Jul  2 20:17:38 snapcount kernel: input: Synaptics Synaptics TouchPad on isa0060/serio2
> 
> Later on, I get this:
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 4th byte
> Synaptics driver resynced.
> 
> But the mouse still does not work. This is a 'Gericom' laptop, which
> contains mostly SiS parts. Anything I can do to help debug this, just let me
> know.

There have been some reports on the list concerning SiS and keyboard
oddities. (Missing key release events causing endless autorepeat for
example.) Maybe this problem is somehow related.

> I saw mention of special X drivers for this, but the kernel messages appear
> to indicate that the kernel itself is not succeeding in communicating with
> the touchpad.

The kernel messages could very well indicate that the communication
works 99.9% of the time, but you really need the special X driver or
else the touchpad will not work at all in X.

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340