Bug 445244

Summary:	Fedora boot process is hardware dependent
Product:	[Fedora] Fedora	Reporter:	Artem S. Tashkinov <aros>
Component:	mkinitrd	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	9	CC:	dcantrell, wtogami, yaneti
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-05 21:58:01 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 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