Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154509 - sata ahci - disks not found
Summary: sata ahci - disks not found
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: David Milburn
QA Contact: Brian Brock
URL: http://www.supermicro.com/products/sy...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-12 10:34 UTC by cervajs
Modified: 2009-07-30 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-30 16:29:40 UTC


Attachments (Terms of Use)

Description cervajs 2005-04-12 10:34:29 UTC
Description of problem:
when installing rhel4, anaconda does not detect sata disks
motherboard have Intel E7221 (Copper River) chipset ICH6R 
bios set to AHCI mode

fc4test2 install is ok
maybe libata 1.7 vs 1.10 problem

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. get motherboard with intel ICH6R chipset
2. set ide mode to AHCI in bios
3. install RHEL4
  
Actual results:
RHEL4(anaconda) does not detect disks

Expected results:
RHEL4(anaconda) can detect disks

Additional info:
AHCI is needed for NCQ a sata hotplug
my PC http://www.supermicro.com/products/system/1U/5014/SYS-5014C-T.cfm

Comment 1 Jeremy Katz 2005-04-12 15:32:07 UTC
Can you try the U1 beta?

Comment 2 cervajs 2005-04-12 16:30:04 UTC
where can i download U1 beta? 


Comment 3 cervajs 2005-04-13 10:31:49 UTC
can you send me boot.iso? thanks

Comment 4 David Milburn 2009-07-30 16:29:40 UTC
RHEL4 U8 installation should recognize the disks, please re-open if necessary.


Note You need to log in before you can comment on or make changes to this bug.