Marvell 88SE9130 on ClearOS 5.2 (CentOS)

[Oblong Cheese]

Hi all,

I just bought myself one of these and put it into my ClearOS machine. This is what I see from lspci:

[root@gateway ~]# lspci -d 1b4b:9123 -vvv
01:00.0 SATA controller: Unknown device 1b4b:9123 (rev 11) (prog-if 01 [AHCI 1.0])
	Subsystem: Unknown device 1b4b:9123
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 50
	Region 0: I/O ports at c480 [size=8]
	Region 1: I/O ports at c400 [size=4]
	Region 2: I/O ports at cc00 [size=8]
	Region 3: I/O ports at c880 [size=4]
	Region 4: I/O ports at c800 [size=16]
	Region 5: Memory at fe8ef800 (32-bit, non-prefetchable) [size=2K]
	Expansion ROM at fe8f0000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
		Address: fee00000  Data: 4032
	Capabilities: [70] Express Legacy Endpoint IRQ 0
		Device: Supported: MaxPayload 512 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <1us, L1 <8us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed unknown, Width x1, ASPM L0s L1, Port 0
		Link: Latency L0s <512ns, L1 <64us
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x1

Question is: it appears to detect and work fine, however it states 'unknown device' - should I be worried about this? I am going to attach two 1Tb disks for a RAID0, and although I will have backups, I don't particularly want my entire RAID to disappear one day because CentOS has decided it doesn't like the card anymore.

How can I tell what kernel modules have been loaded for this (if any) or if there is a better one available?

Edit: With a 2Tb WD20EARS disk connected I can see a /dev/sdb and its size is reported correctly. I guess the next step is to format it and mount it and see how things go!

Thank-you

[antari]

"Unknown device" probably just means that lspci doesn't have that PCI ID in its little list (/usr/share/misc/pci.ids on my system) of them. Shouldn't affect function at all.

As for it not showing the kernel module/driver in use... that's weird, anything from lspci -v and more verbose shows what is in use for me. Tried adding -k to try and force it?

[Oblong Cheese]

lspci doesn't have a -k argument on my system.

[Quadbox]

Originally Posted by Oblong Cheese

lspci doesn't have a -k argument on my system.

Weird... what version of pciutils/libpci?

[antari]

A quick google suggests ClearOS 5.2 uses pciutils 2.2.3, although I could be wrong. The option to show kernel module in use was added in pciutils 2.2.9, and the current version is 3.1.x (don't know exact version).

/lib/modules/$(uname -r)/modules.pcimap
Has a list of modules for specific PCI devices... the format is pretty self-explanatory. It doesn't have any info for drivers compiled into the kernel, just modules.

Best bet would be to track down a repo/rpm for updated pciutils/libpci, or compile from source.

My guess for the driver would be ahci. Which kernel are you running?

[Oblong Cheese]

Yes, the pciutils is version 2.2.3 and the kernel is 2.6.18-194.8.1.v5.

The box is going to become a network gateway but at present I am setting up the RAID etc disks in it.

There are several package updates available for the system but I can't keep network connectivity long enough to download them. One NIC is setup as ppp0 and the other is for what will become the LAN interface; when I connect the LAN interface to my existing ADSL router and manually specify that as the default route it works for a time but then the route is deleted from the routing table after a few minutes. I'm not sure why or how to make it stick.

In any case the SATA controller is working, I have transferred about 800Gb to and from an mdadm RAID0 which is currently connected to it. Hopefully when I get it online I can perform the system updates and install a new pciutils.

[Oblong Cheese]

It's been online for a while now and performing an update of the PCI IDs results in a correct listing for the device in lspci.