QAT 4942 Device Node Generation Failure After Driver Installation - /dev/qat_dev* Missing

[yejn123]

Environment - Host OS: Ubuntu 22.04 LTS - Kernel: 5.19.0-46-generic - Driver Version: QAT2.0 L.1.0.0-00001.tar.gz - Container Image: qat_crypto_base (OpenSSL 3.0 + QAT_Engine v2.0) Issue Description After driver installation and successful 'adf_ctl status' showing devices UP: - Missing critical device nodes: /dev/qat_dev0, /dev/qat_dev1, /dev/usdm_drv - Hardware acceleration fails in containers with error: "QAT_HW device not available & QAT_SW not enabled. Using OpenSSL_SW!" Diagnostics - lspci confirms two 4942 devices present - adf_ctl status shows both devices state: UP - Only /dev/qat_adf_ctl and /dev/qat_dev_processes exist Critical Questions 1. Why are device nodes missing despite adf_ctl reporting UP status? 2. Is this a known issue in QAT 2.0 driver for 4942 devices? 3. What udev rules should force node creation? 4. Does QAT 2.0 require different device paths (e.g. /dev/ipu*)?

[DiegoV_Intel]

Hi,

I see you're trying to use QAT_Engine. I'd recommend first to make sure you are able to run the QAT sample code. If the sample code runs, it will confirm the QAT installation was successful and the driver is operational. Once then, you can start adding the next layer (QAT_Engine) to the stack.

You can follow the Getting Started Guide for this initial setup. Running the sample code (cpa_sample_code) is described in the last section.

I noticed you are using the driver version QAT2.0 L.1.0.0-00001. There have been some newer releases since then, so I'd highly suggest you download and use the latest driver available in Intel® QuickAssist Technology Driver for Linux* – HW Version 2.0. Currently, the latest driver is QAT20.L.1.2.30-00090.

Regards,

Diego V.