Description of problem:
FC6 does not find the harddisk, fc6test3 does find the harddisk.
fc6 does load ata_piix which does not work, fc6test3 loads the correct
ahci-module and therefore detects the harddrive.
System is a Toshiba Tecra S3 laptop with a sata-harddisk and intel-chipset.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to instal fc6 release
Not fixed in fc7test1.
Not fixed in f7test2.
Created attachment 151234 [details]
Anaconda Crash dump from f7t3
I tried to instal f7test3. Anaconda crashes while searching for existing
fedora installations. It dumps a debug-log into the dialog and asks to report a
bug against anaconda. I'm quite sure it'y my long-time-bug 215016 as anaconda
does not see the harddisk.
If I boot f7t3 install dvd with kernel parameter noprobe, the problem can be fixed.
When manually selecting the drivers, the driver ahci has to be loaded first,
that brings up the harddisk. Second the driver ata_piix has to be loaded, to get
access to the optival drive.
Perhaps it`s an anaconda and no kernel bug ?
Tested on 2007-04-09s Rawhide. Loading the wrong drivers by Anaconda can be
fixed by starting with noprobe and loading the drivers manually. Sadly the
installed systems does not boot and crahes while starting.
No changes in 2007-04-17 rawhide.
can you attach the lspci -n output please?
Created attachment 153050 [details]
sure, comes at once.
Ubuntu 7 has similar problems.
*** Bug 231273 has been marked as a duplicate of this bug. ***
Tested f4t3 because of kernel 2.6.21 but no change.
no change with kernel 3142
Given the presence of a workaround, moving to target.
Which workaround ?
I just tried to install todays rawhide via pxe. The bug is not fixed.
Anaconda does not see the harddisk.
Booting with noprobe and manually loading ahci and ata_piix (order
matters) gets the harddisk online but installs a non-bootable system.
This bit me upgrading to F7. I managed to install FC6 by changing VTs and doing
rmmod ata_piix/insmod ahci, but under F7 something's holding a reference to the
DVD drive, so I can't rmmod ata_piix.
This is on a Toshiba Tecra S3, with no BIOS option to enable/disable AHCI. I
haven't tried noprobe as an option yet.
Unlike comment #4, I don't have to load ata_piix; ahci works for both drives.
Actually, I do have to load ata_piix, but noprobe worked for me.
I could install F7 on a Toshiba Tecra S3 130 by booting with noprobe and
manually loading ahci first and ata_piix second.
After that system work without problems.
Still there in F7 release and Rawhide 2007-06-15.
Comment #18 -> comment #5 still applies to my machine.
Still there in rawhide-2007-07-24.
Still there in F8Test1.
Still there in F8Test2.
Tejun Heo from Kernel-Bugzilla says, it`s a distribution-error due to wrong
module loading order.
I tested F8test2 with noprobe and manually loaded the modules. The installation
works, but produces a non booting system.
Tejun is wrong.
Module loading is non-deterministic, thanks to the kernel-mandated use of udev.
If drivers cannot cope with this, they are broken.
Thanks for your comment. I reopened the bug in bugzilla.kernel.org
------- Comment #17 from firstname.lastname@example.org 2007-09-18 21:48 -------
The controller has two interfaces - compatible IDE interface and an AHCI one.
The IDE interface can be driven by ata_piix while the AHCI interface can be
driven by ahci. If ata_piix is loaded first, it grabs the device; otherwise,
This is a special case. IIRC, in all other cases, dual mode controllers can be
put into one of either mode and that is determined either by BIOS or PCI
quirks, so no driver contention there. Only ICH6s use the same PCI ID for both
IDE and AHCI modes and those two drivers differ in capability.
Drivers are coping quite well but they can't cope beyond hardware restrictions.
One solution I can think of is to conditionalize out those duplicate PCI IDs
>from ata_piix if CONFIG_SATA_AHCI is 'y' or 'm' but I'm afraid that would just
end up upsetting more users. Things have been this way for a very long time
Distros can comment out duplicate PCI IDs from ata_piix if making module
loading order deterministic is difficult.
Robert, can you cc Bill Nottingham here?
It is in F8 as well.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Jeff Garzik upstreamed a fix on 04.04.2008 into the kernel. With the
installation-media based on a rebased kernel.rpm I call test, if the fix works.
With Fedora 9 Beta the ich6-driver is still broken.
Still broken in F9 preview. Anaconda does not see any hdds.
The kernel in the preview was built on April 10 and should have the fix
mentioned in comment 29.
Maybe Jeff can answers this. Is this patch included in 2.6.25 oder scheduled for
a later kernel ?
Posted by Tejun: http://marc.info/?l=linux-ide&m=120651487507202&w=2
Included by Jeff: http://marc.info/?l=linux-ide&m=120729493203454&w=2
Still broken in F9 Preview.
was merged in 2.6.26; I think this is the real fix.
Booting the installer with 'blacklist=ata_piix' may help you.
The optical drives depends on ata_piix.
Doh. So, what you'd have to do is to boot with 'blacklist=ata_piix', and then go
to driver selection and try and load the driver later after ahci loads.
Yes, that works. I always booted via pxe and did a network-install.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Fixed in F10 Snap 2 due to kernel 2.6.27. Thanks to all.