Bug 223231 – Can't install Fedora Core 6 on Adaptec AAR-1210SA SATA HostRAID Controller

Bug 223231 - Can't install Fedora Core 6 on Adaptec AAR-1210SA SATA HostRAID Controller

Summary:	Can't install Fedora Core 6 on Adaptec AAR-1210SA SATA HostRAID Controller

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	6
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Kernel Maintainer List
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-01-18 11:03 EST by Ryan Skadberg
Modified:	2007-11-30 17:11 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-01-18 15:46:22 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ryan Skadberg 2007-01-18 11:03:38 EST

I've been trying unsuccessfully to install FC6 on a Adaptec AAR-1210SA SATA
HostRAID Controller.  When I boot off the CD (IDE), the installer can't find any
valid disks.  I've poked around with lsmod and none of the ATA stuff seems to be
loaded up.

The controller is:

00:0a.0 RAID bus controller: Silicon Image, Inc. Adaptec AAR-1210SA SATA
HostRAID Controller (rev 02) (prog-if 01)
        Subsystem: Adaptec: Unknown device 0240
        Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
        I/O ports at cc00 [size=8]
        I/O ports at d000 [size=4]
        I/O ports at d400 [size=8]
        I/O ports at d800 [size=4]
        I/O ports at dc00 [size=16]
        Memory at dd0c1000 (32-bit, non-prefetchable) [size=512]
        Capabilities: [60] Power Management version 2

I can install FC4 on this machine no problem (though I have heard some rumors
from co-workers that yum updating to latest FC4 kernel breaks this configuration
as well).

Any suggestions are appreciated.  If you need more information, just let me know
what and I will get it all over.

Comment 1 Ryan Skadberg 2007-01-18 15:46:22 EST

I was able to solve this by adding noapic and nolapic to the boot params.

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