Bug 123581
Summary: | FC2 boot CD fails after initrd loaded | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Florian Painke <florian.painke> |
Component: | syslinux | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:03:18 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
Florian Painke
2004-05-19 14:10:46 UTC
OK, perhaps I should add some information on my computer: ASUS P4P800 mainboard (Intel 865PE chipset; onboard audio/lan disabled) P4 2.8 GHz (HyperThreaded(TM)) 2 x 256 MB DDR400 RAM (Dual Channel, whatever) ATi Radeon 7500LE graphics card RealTek RTL8139 NIC Creative SoundBlaster Live! Value Seagate 60 GB harddisk ST360021A primary master Maxtor 40 GB harddisk 2F040J0 primary slave Toshiba DVD-ROM SD-M1712 secondary master Plextor CD-Recorder PX-W4824A secondary slave Hmmm, I tried the following: I have a Mandrake 10 Community installation on my harddisk. I copied the vmlinuz and initrd.img files from the fc2 cd1 over to my local /boot (renaming them to something like *_fc2) and added two entries in my lilo.conf, one with the fc2 kernel vmlinuz and fc2 initrd and one with the mandrake kernel and fc2 initrd. Now, when I use both the kernel and initrd from fc2, again my computer will just reboot. But wehn I use the mandrake kernel with the fc2 initrd, the fc2 installer comes up (unfortunately can't see my cdrom, though). So I guess that the kernel somehow doesn't like my computer. Nad this at a very early stage, since not a single kernel message comes up ... *** This bug has been marked as a duplicate of 121819 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |