Skip to content

Supported environments

This page lists the architectures, distributions, operating systems and kernels, and IOMMU configurations on which the current version of the driver can be installed and used. For each item, the extent of verification is also noted. Environments that are not listed here have not been verified.

Legend — ✅ Supported · 🟡 Under verification · ❌ Not supported · 📅 Planned


Architecture

Architecture Status What was verified Remarks
x86_64 ✅ Works All features provided by the driver are available.
arm64, 4K page kernel ✅ Works Operation was confirmed on Ubuntu 24.04 (arm64).
arm64, 16K and 64K page kernels ❌ Not supported The current driver supports only 4K pages.

Driver support status by operating system

Operating system Status What was verified
Ubuntu 22.04 (x86_64) ✅ Operation confirmed
Ubuntu 24.04 (arm64) ✅ Operation confirmed
Ubuntu 24.04, 26.04 (x86_64) 🟡 Under verification: operation verification is being prepared.
Debian 12 (x86_64) 🟡 Under verification: operation verification is being prepared.
RHEL 9 family: Rocky Linux 9, AlmaLinux 9 (x86_64) ✅ Operation confirmed on 9.8
RHEL 8 family (x86_64) 📅 Installability is planned to be verified.
CentOS Stream 9, 10 (x86_64) 📅 Installability is planned to be verified.

Kernel requirements

Requirement Related feature
Page size of 4 KiB The entire driver. It is not built on kernels with other page sizes
CONFIG_HWMON The hwmon interface. If it is disabled, no hwmon device is created. The telemetry in /sys/class/ha/haN/ continues to work

Firmware

The driver decides whether to connect to a device based on the command protocol version that the firmware reports when it boots. This driver's command protocol is v9, and the minimum version required for a connection is v6. The driver connects when the version the firmware reports is v6 or higher. Firmware that reports a version newer than v9 still connects, as long as that version is at least v6. Protocol v9 includes a hardware revision, and this driver does not show that value in sysfs. hw_version is read from PCI configuration space.

Firmware Status Driver behavior
Command protocol v6 or higher ✅ Connects
Command protocol lower than v6 ❌ Refuses to connect when it probes the card. /dev/haN is not created for that card
Firmware lower than 1.0.2 ❌ Not supported. Contact HyperAccel support

Some driver features require a higher firmware version.

Feature Required firmware If the requirement is not met
Firmware update (ha-fw-update) Command protocol v7 or higher The update is refused. The sysfs fw_update_progress is unknown
LED blink (ha-led) Command protocol v8 or higher The command is refused. See ha-led
Temperature, power, and utilization telemetry Telemetry interface (sys_mon) v3 or higher The corresponding telemetry nodes are unknown

Firmware with a command protocol lower than v7 cannot be updated with ha-fw-update. In this case, contact HyperAccel support about the firmware update procedure. Check the running firmware and the command protocol version as follows.

1
2
cat /sys/class/ha/ha*/fw_version
sudo dmesg | grep 'ABI protocol'
Kernel log Meaning
ABI protocol v<N> (driver v9, min v6) The driver connected to firmware whose command protocol is <N>. <N> may be any value of v6 or higher, and the connection stays up when <N> is greater than v9
ABI protocol mismatch: firmware v<N>, driver requires >= v6; refusing probe If it appears when the card is probed, the driver refused to connect. After a reset, it appears together with the post-reset line below
firmware v<version> predates the ABI protocol handshake (needs >= v1.0.2); skipping protocol check The driver connected without being able to check the protocol version
firmware boot not confirmed; skipping ABI protocol check (CSR may be mid-publication) The firmware was not ready when the card was probed, so the driver connected without checking the protocol version
post-reset ABI protocol check FAILED -- device stays bound but its wire ABI is incompatible; unbind it The firmware that rebooted after the reset cannot be used with this driver. The reason is logged in an earlier message for the same card, and the card stays connected

IOMMU

IOMMU configuration Status What was verified
IOMMU off ✅ Works
IOMMU passthrough (iommu=pt) ✅ Works
IOMMU DMA/DMA-FQ (iommu=on) ✅ Works

For how the paths between multiple devices change depending on the IOMMU configuration, see Multiple devices.


See also