public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Koschewski <marc@osknowledge.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Marc Koschewski <marc@osknowledge.org>,
	Ed Tomlinson <tomlins@cam.org>,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org
Subject: Re: psmouse unusable in -mm series (was: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine)
Date: Fri, 25 Nov 2005 14:53:33 +0100	[thread overview]
Message-ID: <20051125135332.GC6728@stiffy.osknowledge.org> (raw)
In-Reply-To: <200511242124.00127.rjw@sisk.pl>

* Rafael J. Wysocki <rjw@sisk.pl> [2005-11-24 21:23:59 +0100]:

> On Thursday, 24 of November 2005 13:44, Marc Koschewski wrote:
> }-- snip --{
> > > It looks like you are seeing a different bug.  The one opened for debian user space
> > > covers mousedev not being loaded if the kernel is 2.6.15, which leads to no /dev/input
> > > 
> > 
> > That's what I think, thus the report on LKLM. But noone but me seems to
> > be trapped into it until... :/
> 
> FWIW, my touchpad doesn't work with -rc2-mm1 too (usually I use a USB mouse,
> so I didn't notice before).  Here's what dmesg says about it:
> 
> Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
> input: SynPS/2 Synaptics TouchPad as /class/input/input2
> 
> The box is an Asus L5D (x86-64).

That's what 2.6.15-rc2 reports for my input devices:

stiffy:/var/cache/apt/archives# dmesg | grep input
input: AT Translated Set 2 keyboard as /class/input/input0
input: PC Speaker as /class/input/input1
input: ImPS/2 Generic Wheel Mouse as /class/input/input2
drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

Regards,
	Marc

      parent reply	other threads:[~2005-11-25 13:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 18:29 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine Marc Koschewski
2005-11-18 19:28 ` Hugh Dickins
2005-11-19  0:31   ` Marc Koschewski
2005-11-19  3:07 ` Dmitry Torokhov
2005-11-20 17:14   ` Marc Koschewski
2005-11-22  3:43     ` Dmitry Torokhov
2005-11-22 10:14       ` Marc Koschewski
2005-11-23 19:57       ` psmouse unusable in -mm series (was: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine) Marc Koschewski
2005-11-24  2:29         ` Ed Tomlinson
2005-11-24  4:41           ` Dmitry Torokhov
2005-11-24  8:41           ` Marc Koschewski
2005-11-24 12:17             ` Ed Tomlinson
2005-11-24 12:44               ` Marc Koschewski
2005-11-24 20:23                 ` Rafael J. Wysocki
2005-11-24 21:20                   ` Rafael J. Wysocki
2005-11-25  8:22                     ` Vojtech Pavlik
2005-11-25 13:50                       ` Marc Koschewski
2005-11-25 21:16                       ` Rafael J. Wysocki
2005-11-25 21:41                         ` Dmitry Torokhov
2005-11-26  3:54                     ` Dmitry Torokhov
2005-11-26  4:50                       ` Dmitry Torokhov
2005-11-26 17:28                         ` Rafael J. Wysocki
2005-11-28  6:01                           ` Dmitry Torokhov
2005-11-25 13:53                   ` Marc Koschewski [this message]

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=20051125135332.GC6728@stiffy.osknowledge.org \
    --to=marc@osknowledge.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tomlins@cam.org \
    /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