Bug 112858
Summary: | fedora core kernels cannot boot from S-ATA disk on ICH5 controller | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Hornby <alex> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2 | CC: | kajtzu, pfrields |
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: | 2005-01-11 22:46:38 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
Alex Hornby
2004-01-04 11:48:10 UTC
Looks similar to bug #110543. Same problem with fedora core 2 kernels. The initrd mechanisms for loading scsi disk ( necessary for libata ) and libata are not working. I had to build a custom kernel with SCSI, SCSI disk and libata in kernel ( _not_ as modules ) to get it to boot. I've tried the latest FC2 fedora kernel updates - they still have this problem. How about attempting to build the mkinitrd image manually? I noticed that sometimes not all the sata modules get included in the initrd image. Try using the regular, modular kernel and create the initrd image with: mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix /boot/initrd.img-2.6.7-1.492 2.6.7-1.492 Excellent - thanks Kaj. Rebuilding the initrd meant that I could use the stock fedora core 2 kernels. Hopefully fedora core 3 will include the ata_piix modules by default in initrd. Its fairly common hardware :) Kay: Do you have any idea on how to run that command in rescue mode? mkinitrd wants /lib/modules/version-nbr as input, whereas I built modules in a different library!!!!! I do not see if mkinitrd can redirect input.... Alex: In the mean time I suggest not to use mkinitrd at all (it makes no difference to think about including a module in the kernel, as to do it with mkinitrd). Another good reason: no source is available... > Another good reason: no source is available...
????????
mkinitrd itself is shell script.. you have the source, Manfredo. Hmmm I think I stumbled on the problem (and fix) in bug #129745. :) Sorry... Its easier to say stupid things, than to accept you said them... is this fixed in the current releases ? Yes, its fixed in FC3. |