fedora3 does not see my ata raid card....

[K.C. Chan]

lspci says:

02:0a.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 03)
Subsystem: Triones Technologies, Inc. HPT370 UDMA100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 120 (2000ns min, 2000ns max)
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at dfe0 [size=8]
Region 1: I/O ports at dfac [size=4]
Region 2: I/O ports at dfa0 [size=8]
Region 3: I/O ports at dfa8 [size=4]
Region 4: I/O ports at d800 [size=256]
Expansion ROM at feae0000 [size=128K]

Any idea how to check the module for it. Current kernel is the stock kernel from RedHat: "2.6.11-1.35_FC3". Thks in advance.

[Stuart Browne]

Generally, I believe the 'CONFIG_BLK_DEV_HPT366=y' needs to be set, which means it's compiled into the kernel, not as a module.

By the looks of all posts I've read, even though it say's 'Unknown mass storage controller:', it is actually known and supported.

Do you have disks and a configured container on that controller's interfaces?

[K.C. Chan]

Yes I have disks. The total disks are 3, 1 primary two residing on the ata raid card. The primary is the OS. I re-install the systems, but left the disks on the ata raid card alone. Since the container is configured at the BIOS; I would think it should be left in-tack. Now, I having problems with it. On redhat 9, I would mount it using /dev/ataraid/. Now I am not sure where it is located?

[Stuart Browne]

Can you attach the output of the 'dmesg' command so we can have a read through it.