Bug 85517 - ps/2 mouse does not work if pluged in after boot
Summary: ps/2 mouse does not work if pluged in after boot
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kudzu
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-03 21:44 UTC by Andy Rysin
Modified: 2014-03-17 02:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-02-04 22:57:53 UTC

Attachments (Terms of Use)

Description Andy Rysin 2003-03-03 21:44:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210

Description of problem:
ps/2 mouse is compiled into the kernel and if not plugged in before booting
linux would not work.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. plug off ps/2 mouse
2. reboot the system
3. try to run kudzu - it'll remove ps/2 from configuration

Actual Results:  no mouse support

Expected Results:  mouse should be detected and picked up

Additional info:

ps/2 mouse should be compiled as a module to fix this

Comment 1 Arjan van de Ven 2003-03-03 21:50:32 UTC
traditionally, ps/2 is not a hotplug-capable bug. Current machines are probably
safe, but you can toast older machines electrically doing ps/2 hotplug.

Comment 2 Andy Rysin 2003-03-03 22:12:13 UTC
well, keeping driver in the kernel will not help saving old machines from being
toasted with ps/2 on the fly connection but will definitely restrict users with
recent hardware to plug it in when they want or can


Comment 3 Arjan van de Ven 2003-03-03 22:15:46 UTC
this also hasn't much to do with in-kernel vs module btw
I've occasionally plugged in keyboards and mice after boot, and that just works.
Yes kudzu gets confused but the kernel side just works.

Comment 4 Bill Nottingham 2005-02-04 22:57:53 UTC
Closing out bugs on older, no longer supported releases. Apologies for any lack
of response. Please attempt to confirm with more recent releases.

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