public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Chen-Becker <derek@chen-becker.org>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Troubleshooting PS/2 mouse in 2.6.5
Date: Mon, 26 Apr 2004 11:53:56 -0600	[thread overview]
Message-ID: <408D4CB4.4070901@chen-becker.org> (raw)

Hi,
     I'm upgrading my workstation from 2.4.22 to 2.6.5 and everything is 
working great except for /dev/input/mice: it doesn't appear to be 
producing anything, even if I cat it. I've checked and both dmesg and 
/proc/bus/input/devices show the mouse handler loaded and show the mouse 
as recognized. I've tried disabling ACPI because I saw it mentioned when 
I googled, but that didn't help. I've also tried loading the event 
handler module and I get nothing there either. I have another PC with 
2.6.5 working fine with the same mouse. Both are hooked up to the same 
KVM, would that have anything to do with it? Does anyone know where I 
could look to get more detail on what's happening?

Thanks,

Derek

-- 
+---------------------------------------------------------------+
| Derek Chen-Becker                                             |
| derek@chen-becker.org                                         |
| http://chen-becker.org                                        |
|                                                               |
| PGP key available on request or from public key servers       |
| ID: 21A7FB53                                                  |
| Fngrprnt: 209A 77CA A4F9 E716 E20C  6348 B657 77EC 21A7 FB53  |
+---------------------------------------------------------------+

             reply	other threads:[~2004-04-26 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 17:53 Derek Chen-Becker [this message]
2004-04-27  5:49 ` Troubleshooting PS/2 mouse in 2.6.5 Kim Holviala
2004-04-27 13:49   ` Derek Chen-Becker
2004-04-27 14:06     ` Derek Chen-Becker
2004-06-02 23:44       ` Vojtech Pavlik

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=408D4CB4.4070901@chen-becker.org \
    --to=derek@chen-becker.org \
    --cc=linux-kernel@vger.kernel.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