From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
Cc: romano@dea.icai.upco.es, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Touchpad does not work anymore
Date: Fri, 1 Apr 2005 12:00:42 -0500 [thread overview]
Message-ID: <d120d5000504010900142bed75@mail.gmail.com> (raw)
In-Reply-To: <20050401164321.GN10278@ens-lyon.fr>
On Apr 1, 2005 11:43 AM, Benoit Boissinot <benoit.boissinot@ens-lyon.org> wrote:
> On Fri, Apr 01, 2005 at 11:28:05AM -0500, Dmitry Torokhov wrote:
> > On Apr 1, 2005 11:14 AM, Benoit Boissinot <bboissin@gmail.com> wrote:
> > > On Mar 31, 2005 8:09 PM, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> > > > > It works, too. Which one is the best one?
> > > > >
> > > >
> > > > Both of them are needed as they address two different problems.
> > > >
> > > I tried to boot with the 2 patches applied (and the patch which solves
> > > noresume) and now touchpad/touchpoint no longer works (with this
> > > kernel or with an older kernel).
> > >
> >
> > Could you be more explicit - it is not recognized at all or it is
> > recognized but mouse pointer does not move or something else? dmesg
> > also might be interesting.
> >
> It is recognized in dmesg (same message as before), but the mouse
> pointer does not move (a `cat /dev/input/mice` doesn't do anything).
>
Should work... The patches come into play only when
suspending/resuming. So you are saying even with an old, unpatched
kernel ALS stopped working, right?
Hmm, that USB mouse - was it there before? I wonder if "usb-handoff"
on the kernel comman line will help.
--
Dmitry
next prev parent reply other threads:[~2005-04-01 17:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 11:03 swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel Romano Giannetti
2005-03-29 13:20 ` Romano Giannetti
2005-03-29 17:02 ` Romano Giannetti
2005-03-29 18:15 ` Pavel Machek
2005-03-31 14:47 ` 2.6.12-rc1 swsusp broken [Was Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel] Romano Giannetti
2005-03-31 15:15 ` Dmitry Torokhov
2005-03-31 15:41 ` Romano Giannetti
2005-03-31 16:50 ` Romano Giannetti
2005-03-31 18:09 ` Dmitry Torokhov
2005-04-01 16:14 ` Benoit Boissinot
2005-04-01 16:28 ` Dmitry Torokhov
2005-04-01 16:43 ` Touchpad does not work anymore Benoit Boissinot
2005-04-01 17:00 ` Dmitry Torokhov [this message]
2005-04-01 17:29 ` Benoit Boissinot
2005-04-05 2:21 ` Benoit Boissinot
2005-03-31 18:29 ` 2.6.12-rc1 swsusp broken [Was Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel] Benoit Boissinot
2005-03-31 22:25 ` noresume breaks next suspend [was Re: 2.6.12-rc1 swsusp broken] Pavel Machek
2005-04-01 0:50 ` Nigel Cunningham
2005-04-01 3:04 ` Nigel Cunningham
2005-04-01 9:45 ` Pavel Machek
[not found] ` <20050525212520.419ee442.akpm@osdl.org>
[not found] ` <20050603094448.GA3218@pern.dea.icai.upco.es>
[not found] ` <20050603105010.GA7300@pern.dea.icai.upco.es>
2005-06-03 12:35 ` swsusp, preempt, input and 2.6.12-rc5-mm2 Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel Romano Giannetti
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=d120d5000504010900142bed75@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=benoit.boissinot@ens-lyon.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=romano@dea.icai.upco.es \
/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