AR-ARK-FX1 [Arkville 64B Multi-Homed Tertiary Endpoint]
PCI ID 1d6c:1019 · Atomic Rules LLC
| Vendor | Atomic Rules LLC |
|---|---|
| Vendor ID | 1d6c |
| Device ID | 1019 |
| Windows hardware ID | PCI\VEN_1D6C&DEV_1019 |
| Linux modalias | pci:v00001D6Cd00001019 |
| Linux driver | no driver with exact ID |
Frequently asked questions
Which device has PCI ID 1d6c:1019?
PCI ID 1d6c:1019 is “AR-ARK-FX1 [Arkville 64B Multi-Homed Tertiary Endpoint]” made by Atomic Rules LLC (vendor ID 1d6c, device ID 1019).
Which Linux driver supports AR-ARK-FX1 [Arkville 64B Multi-Homed Tertiary Endpoint]?
Linux kernel 6.12 lists no driver for this exact ID. Many devices are still supported through their device class, such as AHCI, NVMe, xHCI or HD Audio controllers; others need a vendor driver. Overview of device classes and their drivers
How do I check whether AR-ARK-FX1 [Arkville 64B Multi-Homed Tertiary Endpoint] is in my computer?
On Linux, lspci -nn | grep -i 1d6c:1019 shows the device if it is present. On Windows, open Device Manager, then Properties → Details → Hardware Ids; it appears as PCI\VEN_1D6C&DEV_1019.
How do I see which driver is currently in use?
lspci -nnk -d 1d6c:1019 lists the device with a “Kernel driver in use” line showing the active driver.
Nearby entries
- 1013 – AR-MAN-U250 [Manitou Class Accelerator for U250]
- 1014 – AR-MAN-U280 [Manitou Class Accelerator for U280]
- 1015 – AR-ARK-BBDEV-FX0 [Arkville 32B DPDK Baseband Device]
- 1016 – AR-ARK-BBDEV-FX1 [Arkville 64B DPDK Baseband Device]
- 1017 – AR-ARK-FX1 [Arkville 64B Multi-Homed Primary Endpoint]
- 1018 – AR-ARK-FX1 [Arkville 64B Multi-Homed Secondary Endpoint]
- 101a – AR-ARK-SRIOV-FX0 [Arkville 32B Primary Physical Function]
- 101b – AR-ARK-SRIOV-FX1 [Arkville 64B Primary Physical Function]
- 101c – AR-ARK-SRIOV-VF [Arkville Virtual Function]
- 101d – AR-ARK-NIC [Arkville ArkNIC Kernel Path Device]
- 101e – AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for Agilex R-Tile]
- 101f – AR-TK242 [2x100GbE Packet Capture Device]