Bug 117479

Summary: mouse do not wotk with kernel 2.6.3-1.118
Product: [Fedora] Fedora Reporter: Fernando <ftorresg1>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
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: 2006-02-21 19:01:48 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:
Attachments:
Description Flags
XFree86 log file none

Description Fernando 2004-03-04 13:36:29 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217

Description of problem:
When I boot with this version of kernel, the mouse is not detected. 
I run Linux inside VMWare 4

Version-Release number of selected component (if applicable):
XFree86 4.3.0-62 , kernel-2.6.3-1.118

How reproducible:
Always

Steps to Reproduce:
1. Boot VMWare
2. Start X Windows

Actual Results:  X Windows do not start.

Expected Results:  X Windows is started

Additional info:
Comment 1 Fernando 2004-03-04 13:38:04 UTC 
Created attachment 98291 [details]
XFree86 log file

this is the log file in wich is show the error message
Comment 2 Miloslav Trmac 2004-03-04 14:09:39 UTC 

*** This bug has been marked as a duplicate of 116092 ***
Comment 3 Jeff Gillivan 2004-03-28 21:26:47 UTC 
check bug report 119277 for possible solution
Comment 4 Fernando 2004-03-29 08:26:59 UTC 
If I cange /dev/psaux to /dev/input/mice it works.

Thanks a lot.
Comment 5 Mike A. Harris 2004-03-29 21:28:18 UTC 
Reopening and closing as dupe of master bug dupe for this issue,
bug alias "mouse-psaux".

*** This bug has been marked as a duplicate of 116118 ***
Comment 6 Red Hat Bugzilla 2006-02-21 19:01:48 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.