Bug 39710 - RedHat Wolverine Beta3 CD#1 errors out during attempted auto boot
RedHat Wolverine Beta3 CD#1 errors out during attempted auto boot
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
ia64 Linux
high Severity high
: ---
: ---
Assigned To: Brent Fox
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-05-08 15:28 EDT by Bryan Leopard
Modified: 2005-10-31 17:00 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-24 17:59:51 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 Bryan Leopard 2001-05-08 15:28:42 EDT
When I have the first cd in the cdrom drive on boot of the titan, I 
receive the following error:

Launching auto boot image: I\Boot\bootia64
elilo.c (line 98): cannot find a loader for H?
<<ERROR>>
Trying failsafe kernel once
elilo.c(line 98): cannot find a loader for vmlinux
<<ERROR>>

The only way to start the install is by using the efi shell to access the 
cd and typing elilo.efi
Comment 1 Brent Fox 2001-05-08 17:41:03 EDT
Bill, have we seen this problem before?
Comment 2 Bill Nottingham 2001-05-08 17:51:42 EDT
There was a bug in the bootloader in regards to arguments passed to it,
but that seems to imply something else was wrong.
Comment 3 Bill Nottingham 2001-05-08 18:15:02 EDT
(arch fixed)

We need to reproduce this inhouse.
Comment 4 Brent Fox 2001-05-14 22:13:13 EDT
So what's the status of this, Bill?  Can I help in any way?
Comment 5 Bill Nottingham 2001-05-14 22:16:15 EDT
Try reproducing this on the compaq box with the current tree.
Comment 6 Brent Fox 2001-05-22 14:16:31 EDT
I was able to reproduce this when the path was set wrong...that may be the cause
of the whole problem.
Comment 7 Bill Nottingham 2001-05-22 16:14:53 EDT
Yup, it appeared the firmware was only setting the path to *one* of the MS-DOS
partitions. Seems like a firmware bug.
Comment 8 Bill Nottingham 2001-05-24 17:59:45 EDT
There is also a current elilo problem where, when invoked from a boot
entry, it can fail if there is (for instance) a floppy in the drive.
Comment 9 Bill Nottingham 2001-05-29 13:32:41 EDT
If it's the elilo problem, it's a dup of 42222; the path problem would
have to be a firmware bug, though.

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