Bug 188229 - Installer crashes immediately after reading initrd.img
Summary: Installer crashes immediately after reading initrd.img
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 4
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-07 09:53 UTC by Graham King
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-04-10 18:12:14 UTC

Attachments (Terms of Use)

Description Graham King 2006-04-07 09:53:23 UTC
Description of problem:
Fedora Core 4 installer DVD (x86_64) reboots system immediately after/during
reading initrd.img.

Version-Release number of selected component (if applicable):
Fedora Core 4 (x86_64) from DVD install disk
Motherboard: Asus Pundit-AE3, Chipset: North Bridge SIS 760GX, South Bridge SIS 965L
CPU: AMD Sempron 64Bit 2800 64Bit Socket 754 CPU 333 FSB
Memory: 512Mb DDR 400MHz PC3200
Hard Drive: 40Gb IDE (not-SATA)

How reproducible:
I have tried various install parameters suggested in the install menu, and
various BIOS settings (i.e. disabling SATA support), always with same result.

Comment 1 Chris Lumens 2006-04-07 15:35:23 UTC
Is this better with FC5?

Comment 2 Graham King 2006-04-07 15:39:42 UTC
I'm downloading the ISOs now, and will try FC5 tonight. I was hoping not to use
FC5 just yet, as I'm not really up to sorting out bleeding-edge issues that
no-one else has encountered and documented, but if needs must..

Comment 3 Graham King 2006-04-07 20:09:53 UTC

Tried the 'mediacheck; linux mediacheck' workaround in <a
159026</a> and got all the way through the installation setup.

However, when it came to actually do the installation, it complained that an
existing partition that I had told it to format was in use (?!) and shutdown for

Then, every time I retried, it just frozed at the point of executing /sbin/loader.

Now I'm trying FC5!

Comment 4 Graham King 2006-04-09 09:37:52 UTC
FC5 works fine.

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