Installation and setup¶
This page covers installing the driver and checking that it is in an operational state. You check the supported environments for the driver, install it from the deb package and check the result, and then configure device permissions, containers, and module parameters as needed.
Installation and verification sequence¶
| Step | Task | Page |
|---|---|---|
| 1 | Check whether the architecture, distribution, operating system kernel, and firmware are within the minimum supported range | Supported environments |
| 2 | Install the driver from the deb package | Installation |
| 3 | Check the module load, device probe status, device nodes, and telemetry | Verifying the installation |
For the list of installed files, see Installed files. How to upgrade to a new version or remove the driver is described in Upgrading and removal.
What to decide after setup¶
| Item | Default state | Where to change it |
|---|---|---|
| Whether the module loads automatically at boot | The installation creates /etc/modules-load.d/ha.conf and leaves this enabled |
Automatic loading at boot |
| Device node permissions | A udev rule opens /dev/haN to all local users (0666), and also makes the debug node bypass_range_check writable by all users |
Restricting access |
| Checking the CDI spec for containers | The driver package does not create a CDI spec. ha-container-toolkit, which is part of hyperaccel-lpu, creates and updates it |
Container support |
| Module parameters | The installation does not set any parameters. If there is no options file created earlier, all parameters have their default values | Configuring and using parameters |
| Monitoring method | Telemetry can be read through sysfs and hwmon without any additional configuration | Collecting telemetry with Prometheus, Building a card health check |