Red Hat Bugzilla – Bug 59925
install fail on mouse device
Last modified: 2007-04-18 12:40:26 EDT
Description of Problem:
install fails at final step complaining can't create /dev/mouse
Version-Release number of selected component (if applicable):
at end of each attempted install
Steps to Reproduce:
1. IDE CD install 7.1 distribution, expert nofb lowres
2. auto partition
attached file system requested to be logged with bugzilla
Created attachment 45779 [details]
traceback from install
What type of install was this and what sort of mouse did you select to be
install type: custom, install everything
mouse type: ps/2 2 button, emulate 3 buttons YES
And it's completely reproducible (ie if you run the install again does it
continue to happen)?
Also, you might try not using expert since expert provides very little differing
From email --
Brian Marshall <email@example.com>
[Bug 59925] Changed Status - install fail on mouse device
20 Feb 2002 09:38:31 +0800
Thanks for your new comments.
Now I have more serious trouble, the install is hanging up part way through
at random positions while installing the packages, so I can't get back to
the end again at the moment to further reproduce the mouse problem.
The reason I'm using expert mode is that if I use standard mode, the GUI
goes mostly black early in the process, with buttons highlighting yellow as
you float over them with the mouse). I've found that if I use expert mode
that this does not happen (that part is definitely 100% reproducible).
Can you advise if linear mode should be used for a Seagate ST15150N SCSI
This is sound a lot like you have a bad CD or a dodgy CD-ROM drive. You might
try booting with 'linux ide=nodma nofb lowres'. Expert mode has nothing to do
at all with the X setup, so that just sounds even more like CD problems. As to
linear mode, you generally want linear unless your drive is more than about 7
years old, which is why we finally removed the check box in Red Hat Linux 7.2
Closing due to inactivity, please reopen if you contine to have problems.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.