Bug 1062 - Installer hangs on 486dx-33 at "Loading initrd.img...."
Installer hangs on 486dx-33 at "Loading initrd.img...."
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-02-07 13:16 EST by rivers
Modified: 2014-03-19 07:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-25 21:02:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rivers 1999-02-07 13:16:20 EST
I'm trying to install on a Gateway 2000, 486dx-33 16meg with
builtin (on the motherboard) VGA and IDE controllers.

Initially, all I got after pressing return at
   Loading initrd.img....Boot failed

After disabling the "128K Cache" (it's not clear exactly
what that is) - I was able to get past that.  Now, I get:

   Loading initrd.img.....
and a hang.  I've waited overnight to ensure it was actually
a system hang.

Furthermore, I've made several floppies - to guarantee that
the floppy was OK - and went as far as physically changing
the floppy drive.

I'm guessing it's hanging during a probe of some kind... but
I don't know how to determine that.

I've disabled everything in the machine, it has no serial or
printer ports enabled... and... I've removed all cards.
This is basically a processor, 16 meg of memory, a keyboard
and VGA card, floppy and IDE controller.

As I'm in Raleigh - I'd be happy to stop by with the machine
for a demonstration.
Comment 1 Matt Wilson 1999-03-13 16:25:59 EST
Could you please try the boot.img from
ftp://rawhide.redhat.com/i386/images.  If that boots then your
computer will be supported in the next release.
Comment 2 Matt Wilson 1999-03-25 21:02:59 EST
Closing bug from lack of activity

Note You need to log in before you can comment on or make changes to this bug.