Bug 191718 - FC5 CD or DVD image fails with "could not find kernel image: linux"
Summary: FC5 CD or DVD image fails with "could not find kernel image: linux"
Alias: None
Product: Fedora
Classification: Fedora
Component: syslinux   
(Show other bugs)
Version: 5
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Brock Organ
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-15 14:11 UTC by Peter Lemieux
Modified: 2008-05-06 15:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:54:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Peter Lemieux 2006-05-15 14:11:34 UTC
Description of problem:
Cannot install from FC5 CD or DVD images.

Hardware:  Winbook W235 laptop with Intel 855GM graphics and 1280x768 screen

Running either the installation CD or DVD on this machine displays a garbled
background image.  Hitting enter into isolinux returns the error:
     Could not find kernel image: linux
Since all other options require the "linux" initial command, they could not be
run either.  I also tried entering "vmlinuz" directly.  Linux began to boot but
failed with a kernel panic.

Searching for this problem on the Internet reveals that the "could not find
kernel image" command crops up from time to time in a number of distributions
that use isolinux.  Usually the problem is a bad installation image, but that is
not the case here.  The DVD installed properly on a desktop machine, and both
images match their SHA1 summaries.

Also, FC4 installed from DVD onto this machine without incident.

Version-Release number of selected component (if applicable):

How reproducible:
Insert DVD or CD; reboot.  You cannot proceed.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Please add either "isolinux" or "installation" or some such to the list of
components, since this problem applies to none of the current list.

Comment 1 Bug Zapper 2008-04-04 02:52:55 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 2 Bug Zapper 2008-05-06 15:54:04 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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