From: Vojtech Pavlik <vojtech@suse.cz>
To: Take Vos <Take.Vos@binary-magic.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: PS/2 keyboard and mouse not available/working/weird
Date: Tue, 22 Oct 2002 16:34:53 +0200 [thread overview]
Message-ID: <20021022163453.A22665@ucw.cz> (raw)
In-Reply-To: <200210221603.54816.Take.Vos@binary-magic.com>; from Take.Vos@binary-magic.com on Tue, Oct 22, 2002 at 04:03:49PM +0200
On Tue, Oct 22, 2002 at 04:03:49PM +0200, Take Vos wrote:
> I just upgraded to 2.5.44 from 2.5.43.
>
> In 2.5.43 I had a small PS/2 mouse problem, as it din't see my wart but only
> my scratch pad.
Known bug, still trying to find out why this happens. Any chance your
notebook has an IBM touchpad?
> In 2.5.44 both my PS/2 mice are not available, neither is my keyboard,
> although after sufficient keystrokes, sometimes 5, sometimes more, the
> keyboard is found, this is with Xfree.
Interesting.
> Here is some relevant dmesg information.
> --snip--
> drivers/usb/core/usb.c: registered new driver hid
> drivers/usb/input/hid-core.c: v2.0:USB HID core driver
> drivers/usb/core/usb.c: registered new driver usbscanner
> drivers/usb/image/scanner.c: 0.4.6:USB Scanner Driver
> register interface 'mouse' with class 'input
> mice: PS/2 mouse device common for all mice
> register interface 'joystick' with class 'input
> register interface 'event' with class 'input
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> --snip--
> MTRR: setting reg 3
> atkbd.c: Unknown key (set 0, scancode 0xf0, on isa0060/serio0) pressed.
> atkbd.c: Unknown key (set 0, scancode 0x4b, on isa0060/serio0) pressed.
> atkbd.c: Unknown key (set 0, scancode 0x43, on isa0060/serio0) pressed.
> atkbd.c: Unknown key (set 0, scancode 0xf0, on isa0060/serio0) pressed.
> atkbd.c: Unknown key (set 0, scancode 0x43, on isa0060/serio0) pressed.
> input: AT Set 2 keyboard on isa0060/serio0
>
Very interesting.
> The last time I booted in 2.5.44 the keyboard was found after about 20
> keystrokes but was useless as it produced weird escape sequences instead of
> normal characters, this was without XFree (to check if it had something to do
> with that).
Can you try with #define DEBUG in i8042.c?
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-22 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:03 Take Vos
2002-10-22 14:34 ` Vojtech Pavlik [this message]
2002-10-23 7:43 ` Take Vos
2002-12-12 19:36 ` Take Vos
2002-12-13 12:53 ` Bas Vermeulen
2002-10-22 14:37 ` Michael Dreher
2002-10-22 18:13 ` 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=20021022163453.A22665@ucw.cz \
--to=vojtech@suse.cz \
--cc=Take.Vos@binary-magic.com \
--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
Powered by JetHome