Bug 182147
Summary: | FC5T3 i386 won't boot on Emachines T5026 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stanton Finley <stantonfinley> |
Component: | syslinux | Assignee: | Peter Jones <pjones> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | fulko.hew |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-27 09:13:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Stanton Finley
2006-02-20 19:54:23 UTC
I am having the same symptoms on my Compal Cl-50 laptop (that has been running Fedora Core 4-3-2-1 fine). After researching these symptoms on the isolinux mailing list (http://syslinux.zytor.com/archives/): "Unknown keyword in config file", and "Could not findkernel image" there seem to be many people having similar symptoms on their non-Fedora systems too. There are many comments about being BIOS related, but I could not find any definitive answer, because none of the responses described what the BIOS problem might be. One person suggested a workaround that he found for his system, and that worked for me on test 3. ...When you enter 'linux' during the install bootstrap time, it sort of activates macros in Isolinux's config file that effectively causes Isolinux to invoke: /isolinux/vmlinuz initrd=/isolinux/initrd.img By entering this manually at the 'boot:' prompt, I could still boot off of both the CD and DVD distribution media, and continue the installation process. (Of course I had anaconda fail and create a stack trace many times, and had other issues, but at least I could boot the installation process.) As the originator of this bug I can confirms that entering "/isolinux/vmlinuz initrd=/isolinux/initrd.img" at the boot prompt does in fact initiate the boot and allows me to proceed with the installation without incident on my Emachines T5026 using the FC5 test 3 DVD. |