Bug 1920 - generic kernel image doesn't work on UX
generic kernel image doesn't work on UX
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: aboot (Show other bugs)
6.0
alpha Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-03-31 18:02 EST by Richard D. Payne
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-05-30 17:51:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Richard D. Payne 1999-03-31 18:02:41 EST
I'm trying to install on a 164UX (Ruffian) machine. the
kernel image (/images/generic.gz) worked fine on the LX,
but on the UX it hangs.

It loads MILO w/o any trouble, I insert the kernel disk,
pass MILO the boot info, it starts reading from the floppy,
it finds the kernel image, starts uncompressing it, it
prints two lines of '#', on the third line we get 1 '#' and
that's it. Floppy light stays on but nothing ever happens.
We left the machine overnight to see if anything happened,
nothing.
Comment 1 Cristian Gafton 1999-03-31 19:16:59 EST
From rth:

I was fairly certain that Ruffian had a lame MILO that was
limited in the size kernel it could load, and that a generic
kernel was too big. I was fairly certain that Ruffian had a lame MILO
that was limited in the size kernel it could load, and that a generic
kernel was too big.
Comment 2 Richard D. Payne 1999-04-06 10:13:59 EDT
The ruffian MILO and ldmilo from gatekeeper.dec.com (The Jay Hacked
version) seems to work w/o any trouble. I've upgraded two machine
from 5.2 to 5.9 using that MILO and ldmilo.exe.
Comment 3 Jeff Johnson 1999-05-30 17:51:59 EDT
This appears solved. Please reopen if not.

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