From: Dominik Kubla <dominik@kubla.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Dominik Kubla <dominik@kubla.de>,
Emmeran Seehuber <rototor@rototor.de>
Subject: Re: PS/2 Mouse does no longer work with kernel 2.6 on a laptop
Date: Fri, 13 Feb 2004 21:20:52 +0100 [thread overview]
Message-ID: <20040213202052.GA1283@intern.kubla.de> (raw)
In-Reply-To: <200402130223.00339.dtor_core@ameritech.net>
On Fri, Feb 13, 2004 at 02:23:00AM -0500, Dmitry Torokhov wrote:
>
> Do you have an active multiplexing controller and does passing i8042.nomux
> option help?
The Debian maintainer released a new package today with the following change
log entry:
* Reenabled INPUT_MOUSEDEV_PSAUX_ENABLE (closes: #232267, #232269).
Now everything works again.
So it looks like this might have been a SNAFU... Unless the other guy
experiencing problems is not using the Debian kernel packages.
Sorry for not passing along that i was using a pre-compiled binary.
Regards,
Dominik
--
BOFH excuse #203:
Write-only-memory subsystem too slow for this machine. Contact your local dealer.
next prev parent reply other threads:[~2004-02-13 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 23:44 PS/2 Mouse does no longer work with kernel 2.6 on a laptop Emmeran Seehuber
2004-02-13 7:03 ` Dominik Kubla
2004-02-13 7:15 ` H. Peter Anvin
2004-02-13 7:23 ` Dmitry Torokhov
2004-02-13 20:20 ` Dominik Kubla [this message]
2004-02-14 9:28 ` Emmeran Seehuber
2004-02-14 17:05 ` Dmitry Torokhov
2004-02-15 14:25 ` Emmeran Seehuber
2004-02-15 15:28 ` Dmitry Torokhov
2004-02-15 19:32 ` Emmeran Seehuber
2004-02-16 13:34 ` Emmeran Seehuber
2004-02-16 14:36 ` Vojtech Pavlik
2004-02-17 6:18 ` Dmitry Torokhov
2004-02-17 23:13 ` Emmeran Seehuber
2004-02-17 23:29 ` Dmitry Torokhov
2004-02-18 0:37 ` Emmeran Seehuber
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=20040213202052.GA1283@intern.kubla.de \
--to=dominik@kubla.de \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rototor@rototor.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.