Bug 49766 - Selecting wrong mouse makes keyboard not work
Summary: Selecting wrong mouse makes keyboard not work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-23 19:21 UTC by Anders Carlsson
Modified: 2007-04-18 16:35 UTC (History)
0 users

Clone Of:
Last Closed: 2001-07-27 01:46:55 UTC

Attachments (Terms of Use)

Description Anders Carlsson 2001-07-23 19:21:56 UTC
During the installation I made a mistake and selected that my mouse was of
type PS/2 instead of USB which is the correct type. 

When I later started X the mouse wouldn't work, nothing strange about that
since I chose the wrong type. What's strange is that the keyboard didn't work.

I rebooted and ran XConfigurator, and when XConfigurator starts X to check
the configuration I got the same thing. Neither the mouse nor the keyboard
worked. When X exited and I got back to XConfigurator I found that the
keyboard didn't work even _after_ X exited.

Seems like X is trying to detect the PS/2 mouse and screws up the keyboard
by sending some weird data to it or something.

Comment 1 Glen Foster 2001-07-23 21:18:28 UTC
This defect is considered SHOULD-FIX for Fairfax.

Comment 2 Mike A. Harris 2001-07-27 01:46:49 UTC
What mouse (brand/model) do you have?  Also, what keyboard do you have?
Is your keyboard PS/2, AT, or USB?

This problem is sufficiently bizarre IMHO that I need much more detailed
information.  Can you create an X server log by running X configurator,
and then attaching /var/log/XFree*.log (all of em) to this report?

Please attach your configuration file as well, and a copy of your
/var/log/messages (trimmed if necessary to be <= 200k or so, we just
want the bottom of it preferably with kernel boot messages).

Also, are you using a Red Hat binary kernel, or a home built kernel?

Comment 3 Mike A. Harris 2001-09-02 04:58:43 UTC
Closing bug due to lack of information.

Note You need to log in before you can comment on or make changes to this bug.