Red Hat Bugzilla – Bug 244616
Installing OS fails on ATI/AMD SB700 chipset with AHCI mode
Last modified: 2007-11-30 17:12:07 EST
+++ This bug was initially created as a clone of Bug #244156 +++
Description of problem: cannot find hard disk device while setting the SATA
mode to AHCI mode in system BIOS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.the onchip SATA mode to AHCI mode
cannot find AHCI driver
find the AHCI driver for hard disk
This patch will be included in the linux kernel from version 2.6.22
-- Additional comment from email@example.com on 2007-06-14 03:58 EST --
Created an attachment (id=156964)
patch: add the AHCI device ID
-- Additional comment from firstname.lastname@example.org on 2007-06-14 09:47 EST --
-- Additional comment from email@example.com on 2007-06-14 09:51 EST --
Asked AMD to send a SB700 reference board for the SB700 back ports.
-- Additional comment from firstname.lastname@example.org on 2007-06-14 13:44 EST --
Is this a bug or new hardware enablement?
-- Additional comment from email@example.com on 2007-06-14 13:54 EST --
(In reply to comment #5)
> Is this a bug or new hardware enablement?
Feature Request-- new hw enablement.
I have this same issue with my Thinkpad T61. The device should be supported by
the ahci driver, but it is not found at boot. This applies to the install
process and to booting after installation is complete. The problem is still
present in kernel-22.214.171.124-41.fc7.
Lenovo (by Intel) / 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [SATA
Should I file a separate bug or is this OK?
Seperate bug please - differing hardware, and assign it to firstname.lastname@example.org
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.
The information contained herein indicates this is resolved from kernel 2.6.22
so I am closing. If I have erred, please accept my profuse apologies and re-open
and I will attempt to assist in its resolution.
yep, you may close this bug, and I find FC8 Test 2 contains this patch.