Dennis HilkLinux diagnosticsDE

Storage controllers

Silicon Image SiI3132

SiI3132 uses the distinct sata_sil24 controller driver. It should not be grouped with SiI3112 merely because both devices have the Silicon Image vendor identity.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The table maps 1095:3132 to BID_SIL3132 and its two-port implementation. It identifies the controller type, not an enclosure’s connected drives or the exact add-in card brand.

Curated identifiers
pci 1095:3132

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

sata_sil24 handles this family through libata and defines controller-specific port operations. Runtime port enumeration is still needed to know which connections are present and active.

  • sata_sil24 — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

Controller firmware, option ROM and drive firmware can be separate. The reviewed sources do not establish a host-loaded filename for this profile; firmware revision and update policy require the actual controller and OEM identity.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Check the PCI function and bound driver

lspci -nnk -s BDF

Replace BDF with the domain:bus:device.function address. Look for [1095:3132] and Kernel driver in use. sata_sil24 in Kernel modules is only a candidate, not proof of binding.

Inspect visible block-device identities

lsblk -d -o NAME,MODEL,TRAN,HCTL

MODEL describes a block device or a controller-presented logical volume; it is not a PCI-controller identity. HCTL helps distinguish SCSI targets. TRAN can be absent, and this list does not establish the complete physical disk topology.

Read controller and transport messages

sudo journalctl -k -b --no-pager

Elevated access may be needed. Root reads the current boot kernel journal. Associate sata_sil24 messages, port/host identifiers and timeout/reset timestamps with the actual controller. A reset message alone does not prove a bad disk or a firmware defect.

Limitations & related issues

Port-multiplier or external-cable arrangements add topology beyond the PCI controller. A PCI match and a SATA link-up message do not prove every downstream disk is reachable.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.