CentOS Stream 9 – Common Problem 110 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Third-party kernel modules fail to load with ‘Required key not available’.

Environment & Reproduction

Secure Boot enabled; the module is not signed by an enrolled MOK.

Root Cause Analysis

Kernel enforces module.sig_enforce when Secure Boot is on.

Quick Triage

dmesg | grep -i ‘key|signature’ after the modprobe failure.

Step-by-Step Diagnosis

mokutil –sb-state and mokutil –list-enrolled show key status.

Solution – Primary Fix

Generate a MOK, sign the module, enroll via mokutil –import and reboot to confirm.

Solution – Alternative Approaches

Use DKMS with akmods or kmod-* packages signed by the vendor.

Verification & Acceptance Criteria

modinfo and lsmod show the module loaded after reboot.

Rollback Plan

Unload the module, disable autoload, or boot with Secure Boot off temporarily.

Prevention & Hardening

Bake signed modules into a custom RPM and enroll the MOK via Kickstart.

Related Errors & Cross-Refs

Related: kernel-devel mismatch and akmod build failures.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

shim and mokutil documentation; Red Hat Secure Boot KB.