Overview & identity
The source labels 1c02 as CPT AHCI and assigns a port-control/status quirk. A motherboard sales name or a connected disk model cannot be recovered from this pair alone.
- Curated identifiers
pci 8086:1c02
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
The candidate is ahci with board_ahci_pcs_quirk. This is a controller-specific implementation choice inside the generic AHCI stack, not a separate Intel SSD driver.
ahci— kernel driver/module candidate
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.
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 BDFReplace BDF with the domain:bus:device.function address. Look for [8086:1c02] and Kernel driver in use. ahci in Kernel modules is only a candidate, not proof of binding.
Inspect visible block-device identities
lsblk -d -o NAME,MODEL,TRAN,HCTLMODEL 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-pagerElevated access may be needed. Root reads the current boot kernel journal. Associate ahci 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
An ataN error identifies a libata port/device context that still needs mapping to the physical disk. A CRC/link-reset pattern must not be treated as proof of worn flash or filesystem corruption.
These guides are linked for relevant observations, not as known defects of every device in this family.
- SATA CRC errors and repeated link resets · First documented next step
- ATA uncorrectable sectors and read errors · First documented next step
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.
- Upstream Linux: drivers/ata/ahci.c
Reviewed upstream source
PCI_VDEVICE(INTEL, 0x1c02); line 528 - Upstream Linux: Documentation/driver-api/libata.rst
Project or distribution documentation
SCSI<->ATA translation; line 12