Bug 161284
Summary: | PS/2 mouse not detected upon X startup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Phil Staub <phils> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | nadeem.riaz, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-05 01:14:25 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
Phil Staub
2005-06-22 00:41:19 UTC
I upgraded from FC2 to FC4, and have nearly the exact same problem. The mouse wheel refuses to work when the mouse is pluggedi nto the PS/2 port, but works fine when its in the USB port. Same mouse. I suspect a hardware dependency somewhere in the chipset driver. Installing FC4 on my laptop works fine with the same mouse (in PS/2 mode). Also, I tried buying a PS/2 to USB adapter to convert the mouse output of my KVM switch to USB to plug into the problematic tower, and in that configuration even plugging it into the USB port doesn't work. The only thing I've found that works is to plug the USB connector of the mouse directly into the tower's USB input. In the event that the specific chipset is significant, my mainboard is an Intel D845GEBV2. At one time I knew what the chipset was, but I can't recall any more. For the time being, I've switched back to FC3. 8-( I have a similar problem. Just upgraded a Dell Optiplex GX1 (500Mz) from FC2 to FC4. Everything went smoothly with the 2.6.11-1.1369_FC4 kernel and the PC operated just fine. However, when yum upgraded to 2.6.14-1.1367_FC4 the mouse disappeared and the keyboard became very sluggish. The mouse is PS2 and a standard keyboard behind a KVM switch. The mouse seems to be absent prior to X starting. However, sometimes the mouse will appear on boot or can be made to start but only works for short periods of time. Rebooting with the 2.6.11-1.1369 kernel brings everything back into operation. (In reply to comment #3) > I have a similar problem. Just upgraded a Dell Optiplex GX1 (500Mz) from FC2 to > FC4. Everything went smoothly with the 2.6.11-1.1369_FC4 kernel and the PC > operated just fine. > > However, when yum upgraded to 2.6.14-1.1637_FC4 the mouse disappeared and the > keyboard became very sluggish. The mouse is PS2 and a standard keyboard behind a > KVM switch. The mouse seems to be absent prior to X starting. However, sometimes > the mouse will appear on boot or can be made to start but only works for short > periods of time. Rebooting with the 2.6.11-1.1369 kernel brings everything back > into operation. Sorry about the repeat of comment #4. Was just trying to make a correction and got the whole thing again. However, some additional information. First I noticed that when booting with the 14-1.1637 kernel, the led of the optical mouse begins flashing consistently during the kernel initialization process. This is well before X starts. (Normally the led will only come on when the mouse is moved.) It is as if the 14-1 kernel is constantly polling the mouse. Second, I forced the installation of the 13-1.1532 kernel and booted with that. It seems to work just fine so far. Will let it run overnight to be sure. Interestingly, the 14-1.1637 kernel seems to run just fine on my IBM T-21 laptop. Are there any serio/input/mouse layer messages in dmesg after booting, or after experiencing mouse loss? What does cat /proc/bus/input/devices show This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. |