Re: Synaptics Touchpad workaround for strange behavior after Syncloss (With Patch). (fwd)

[Gunter Königsmann]

Strike! Helps.

No more warnings, no more bad clicks, and a *real* smooth movement.

Never thought, a touchpad can work *this* well... ;-)

Anyway, I still get those 4 lines  on leaving X, but don't know, if it is
an error of the kernel, anyway, and doesn't do anything bad exept of
warning me:

atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).


Yours,

	Gunter.

-- 
Nasrudin called at a large house to collect for charity.  The servant said
"My master is out."  Nasrudin replied, "Tell your master that next time he
goes out, he should not leave his face at the window.  Someone might steal it."

---------- Forwarded message ----------
From: Dmitry Torokhov <dtor_core@xxxxxxxxxxxxx>
Date: Sun, 11 Jan 2004 10:34:54 -0500
To: Gunter Königsmann <gunter.koenigsmann@xxxxxx>
Delivered-To: GMX delivery to gunter.koenigsmann@xxxxxx
Cc: linux-kernel@xxxxxxxxxxxxxxx, Vojtech Pavlik <vojtech@xxxxxxx>,
     Peter Berg Larsen <pebl@xxxxxxxxxx>
Subject: Re: Synaptics Touchpad workaround for strange behavior after Sync
    loss (With Patch).

On Sunday 11 January 2004 09:22 am, Vojtech Pavlik wrote:
> On Sun, Jan 11, 2004 at 01:52:46PM +0100, Peter Berg Larsen wrote:
> > On Sun, 11 Jan 2004, Gunter Königsmann wrote:
> > > Hmmm... Now I get an "Reverted to legacy aux mode" after about
> > > every third resync of the driver, and sometimes odd and sometimes
> > > even numbers of sync losses...
> >
> > How often is that? X/minute. I do not expect many "reverted .."
> > messages, but if there is, then I believe the mux ver 1.1 has added
> > some extra error codes that we se as a revert.
>
> Or the BIOS powermanagement is touching the controller in a way the MUX
> mode doesn't like ...

Does booting with i8042.i8042_nomux=1 help? That should keep the MUX in
legacy mode. (well, depending on the kernel version it's either i8042.nomux
or i8042.i8042_nomux, -mm1 and my patches use former, in 2.6.1 vanilla uses
later form).

Dmitry

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/