Bug 60977
Summary: | USB mouse not detected by X if not present at boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Sean O'Connell <sean> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | teg |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-05-01 18:57:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sean O'Connell
2002-03-11 05:35:18 UTC
I filed it under kudzu, but maybe initscripts might have been more appropo. As a follow up to this, I have not been able to get the modules.conf setup to work reliably. Alas, only the hackish way of doing the mod- probles in /etc/X11/prefdm has worked consistently for me. Is this working due to a race condition? Probably the best way to handle this is to have hotplug kick the X server so that it reopens the mouse device. But could you do that in such a way as to not kill a current xsession? That is really what prompted this.. I hate to have to do a ctrl+alt+bksp just use my hotpluggable mouse. The prefdm hack works (I cannot explain why, per se). The other thing that would be nice would be a userland mouse abstraction daemon (a la .. dare I say it .. FreeBSD's moused, which back in my bsd days would allow me to share focus between usb mouse and on board mouse). I was never able to get gpm under linux to do what moused could do under FreeBSD. Not an issue for hotplug. You could have a X configuration with multiple devices in it, both active, if you want to and anaconda wants - it shouldn't break anything. Deferring to a future release. The real "right" answer is to use the new input layer stuff from 2.5 (lets you use ps2 and usb both from a combined input mutex similar to how usb mice work already) I think we've come up with a solution that will make this case work. cool. i am curious to hear what you came up with. Time tracking values updated |