Bug 445244 - Fedora boot process is hardware dependent
Summary: Fedora boot process is hardware dependent
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 9
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-05 17:49 UTC by Artem S. Tashkinov
Modified: 2009-05-05 21:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-05 21:58:01 UTC


Attachments (Terms of Use)

Description Artem S. Tashkinov 2008-05-05 17:49:32 UTC
Description of problem: initrd (initial ram disk) which Fedora installs during
installation process contains only modules for the current storage
controller(s). Thus if you insert your HDD into another computer then your
Fedora may not boot (most likely will not boot).

I suggest creating a 'generic' initrd which contains modules for most
SCSI/PATA/ATA/USB HDD controllers, so that it is possible to boot your Fedora in
a different environment.

Of course, upon kernel updates this initrd should be updated automatically.

Comment 1 Bug Zapper 2008-05-14 10:40:24 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Jeremy Katz 2009-05-05 21:58:01 UTC
We've switched as of Fedora 10 to building in a lot of the "general" modules.  And after Fedora 11, we will likely be switching to dracut instead of mkinitrd which will do something like this.

So for mkinitrd itself, going to WONTFIX


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