I am attempting to install RH 7 on an older HP Vectra Pentium 75 machine
that does not have any USB controllers, USB devices, etc.
While anaconda is loading it confirms whether there is a USB controller or
not. In my case it acknowledges that there is no USB controller and
continues on until it starts a search for a USB mouse. At this point it
does not find a USB mouse and it locks up.......never to move forward or
give me an error message or anything.
Alt+F2 reports: sh-2.04# _
Alt+F3 reports: * looking for USB mouse...
Alt+F4 reports: <6>raid5 personality registered
Is there any work around to this?
I would suspect that this problem is being encountered by many others as
RH is being toyed with on lots of older machines.
Your help is appreciated.
Please try booting into the installer with the 'nousb' option, like
and tell us if that helps.
I tried your suggestion and still am experiencing a lock up. The halt is
happening in the same spot. However Alt+F3 no longer reports "* looking for USB
mouse", instead it hangs one line ahead "* going to insmod ext3.o (path is
NULL)". All other F+ Keys report what is stated in the original message.
hmmm ... I am not seeing this problem in a similar system (P166, no usb devices)
... how much memory does your machine have ...? were you trying to start the
install in text mode or GUI mode ...? The place where you are reporting the hang
is where the installer loads into 'stage 2' and presents the "welcome to red
hat" screen ... I would be interested to know if this behavior occurs for you:
* in text mode
* explicitly specifying how much memory the machine has
Thank you for your continued support.
The issue has been resolved. I was installing in text mode, which seemed to not
be the issue. The culprit was incompatible memory simms. I was trying to run 54
megs of memory in pairs from 3 different manufacturers (6 total simms).
To get beyond my troubles I reduced the memory to 4 identical simms of 4 megs
each. At that stage everything worked fine. After installation I loaded
additional memory only to find that the machine wouldn't accept it.
You can chalk it up to memory hardware incompatibility.
Again, thanks for your help.
glad to know you were able to resolve the issue ... thanks for your report! :)