[CentOS] Getting SATA Controller working

I have an SIIG SC-SA4011 (V1.0) SATA controller that doesn't appear to come
up. The system has CentOS 6.5 installed on it, and everything on it works,
except for this one controller - the other SATA controller, a RocketRAID
1640 works fine. lspci lists the offending controller:

$> lspci
[... snip ...]
04:01.0 Mass storage controller: Silicon Image, Inc. SiI 3114
[SATALink/SATARaid] Serial ATA Controller (rev 02)

When I look in dmesg though, I see this:
pci 0000:04:01.0: no compatible bridge window for [io  0x4800-0x4807]
pci 0000:04:01.0: can't reserve [io  0x4800-0x4807]
pci 0000:04:01.0: no compatible bridge window for [io  0x4400-0x4403]
pci 0000:04:01.0: can't reserve [io  0x4400-0x4403]
pci 0000:04:01.0: no compatible bridge window for [io  0x4000-0x4007]
pci 0000:04:01.0: can't reserve [io  0x4000-0x4007]
pci 0000:04:01.0: no compatible bridge window for [io  0x3800-0x3803]
pci 0000:04:01.0: can't reserve [io  0x3800-0x3803]
pci 0000:04:01.0: no compatible bridge window for [io  0x3400-0x340f]
pci 0000:04:01.0: can't reserve [io  0x3400-0x340f]

and:

pci 0000:04:01.0: BAR 4: assigned [io  0xa000-0xa00f]
pci 0000:04:01.0: BAR 4: error updating (0x00a001 != 0x002001)
pci 0000:04:01.0: BAR 4: set to [io  0xa000-0xa00f] (PCI address
[0xa000-0xa00f]
pci 0000:04:01.0: BAR 0: assigned [io  0xa010-0xa017]
pci 0000:04:01.0: BAR 0: error updating (0x00a011 != 0x002011)
pci 0000:04:01.0: BAR 0: set to [io  0xa010-0xa017] (PCI address
[0xa010-0xa017]
pci 0000:04:01.0: BAR 2: assigned [io  0xa018-0xa01f]
pci 0000:04:01.0: BAR 2: error updating (0x00a019 != 0x002019)
pci 0000:04:01.0: BAR 2: set to [io  0xa018-0xa01f] (PCI address
[0xa018-0xa01f]
pci 0000:04:01.0: BAR 1: assigned [io  0xa020-0xa023]
pci 0000:04:01.0: BAR 1: error updating (0x00a021 != 0x002021)
pci 0000:04:01.0: BAR 1: set to [io  0xa020-0xa023] (PCI address
[0xa020-0xa023]
pci 0000:04:01.0: BAR 3: assigned [io  0xa024-0xa027]
pci 0000:04:01.0: BAR 3: error updating (0x00a025 != 0x002025)
pci 0000:04:01.0: BAR 3: set to [io  0xa024-0xa027] (PCI address
[0xa024-0xa027]

Any suggestions on how I can get this controller up and running or is it
too old to work with?