The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Sailer <sailer@sailer.dynip.lugs.ch>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: dtor_core@ameritech.net, linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: Synaptics probe problem on Acer Travelmate 3004WTMi
Date: Mon, 18 Jul 2005 07:54:16 +0200	[thread overview]
Message-ID: <1121666056.3787.1.camel@unreal> (raw)
In-Reply-To: <20050713183804.GA2072@ucw.cz>

On Wed, 2005-07-13 at 20:38 +0200, Vojtech Pavlik wrote:

> Also try the usual options ("i8042.nomux=1" and "usb-handoff"). One or
> both may make the problem disappear.

usb-handoff did it, thanks a lot!

Tom



  reply	other threads:[~2005-07-18  5:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 17:23 Synaptics probe problem on Acer Travelmate 3004WTMi Thomas Sailer
2005-07-13 17:32 ` Dmitry Torokhov
2005-07-13 18:38   ` Vojtech Pavlik
2005-07-18  5:54     ` Thomas Sailer [this message]
2005-07-18  7:14       ` Andrey Panin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1121666056.3787.1.camel@unreal \
    --to=sailer@sailer.dynip.lugs.ch \
    --cc=dtor_core@ameritech.net \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox