Red Hat Bugzilla – Bug 192387
FC5 not finding Intel Ultra ATA drive during install. (FC4 did)
Last modified: 2008-01-19 23:39:28 EST
Description of problem:
Fedora Core 5 installer is not finding the hard disk on an IBM R52 Thinkpad,
running Windows XP, installing into VMWare Workstation. The installer prompts
for a device driver. I tried Intel ata_piix, as the closest choice.
Fedora Core 4 installed just fine, multiple times.
Version-Release number of selected component (if applicable):
Source of distribution, DVD in the book, "Fedora 5 ... Bible" by Christopher Negus
Five out of five tries.
Steps to Reproduce:
1. Reboot with install DVD.
2. Next past the the two language prompts
3. Then you'll see "..can't find drive..."
Can't find hard drive.
Silently finds hard drive.
Numberous web notes about linux having problems finding Ultra ATA dirves and
SATA drives. But FC4 found it just fine...
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen