Overview & identity
1b21:0612 is the checked shared-family entry. Adjacent ASM1061/1062 revision and RAID-labelled IDs are different entries and are not silently included in this exact match.
- Curated identifiers
pci 1b21:0612
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 ahci table chooses board_ahci_43bit_dma. That DMA addressing variant is an implementation detail of this controller path, not an instruction to change the IOMMU or disable platform protection.
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 [1b21:0612] 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
A controller’s PCIe lane path can limit aggregate transfers across SATA ports. Individual drive model and negotiated SATA speed remain separate evidence from the host-controller identity.
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(ASMEDIA, 0x0612); line 1529 - Upstream Linux: include/linux/pci_ids.h
Reviewed upstream source
PCI_VENDOR_ID_ASMEDIA; line 2595 - Upstream Linux: Documentation/driver-api/libata.rst
Project or distribution documentation
SCSI<->ATA translation; line 12