Description of problem:
While trying to install FC2 on an IBM x330, neither ServeRaid nor
Adaptec SCSI are detected. Modules can't be inserted into the kernel.
The output of lspci is similar to this:

00:00.0 Host bridge: ServerWorks CMIC-LE (rev 0a)
00:00.1 Host bridge: ServerWorks CMIC-LE (rev 0a)
00:00.2 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
00:00.3 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 06)
00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:0a.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 51)
00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04)

while on kernel 2.4, it looks like this:

00:00.0 Host bridge: ServerWorks CMIC-LE (rev 0a)
00:00.1 Host bridge: ServerWorks CMIC-LE (rev 0a)
00:00.2 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
00:00.3 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 06)
00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:0a.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 51)
00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04)
01:03.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02)
01:06.0 RAID bus controller: IBM ServeRAID Controller

anything on PCI 01 can't be seen under the 2.6 kernel that ships with
the FC2 installer.

How reproducible:

Always

Steps to Reproduce:
1. Boot up from either FC2-i386-disc1.iso or boot.iso
2. Choose install

  
Actual results:

No hard drives are detected. Further investigation shows that the SCSI
hardware is not detected.

Expected results:

Adaptec AIC-7892P U160/m and IBM ServeRAID Controller should be
visible in lspci output.

Additional info:

While browsing for this bug in bugzilla, I found none which matches my
description; however, it seemed to me that there are multiple bugs
which have already been reported which might have the same etiology,
but the reporters hadn't realized that it was a problem with the
kernel PCI drivers.