DAHDI Not Loading

Home » Asterisk Users » DAHDI Not Loading
Asterisk Users 7 Comments

Hi

I took a UEFI image of CentOS 7.7, (dahdi runs on the image). copied that to a physical disk with dd, booted the image and dahdi does not start.

doing service dahdi restart says “could not insert dahdi module – the required key is not found.”

How do I get dahdi to be happy ?
it is “NOT” possible to disable UEFI on my hardware. Kernel is 3.10.0-1062.12.el7

I saw something about needing to SIGN the dahdi modules. How do I do that ?
If that is the solution.

Thanks

Jerry

7 thoughts on - DAHDI Not Loading

  • I’d rather not have to do that step. I “desire” to make the image and copy to the physical disk with dd and have everything set to go. Not take further time and “recompile” things.

    How do I do that?

    Jerry

  • If you are using your package manager to install Asterisk & Dahdi, then I would not suggest that you compile.

    Doug

    —

  • You can leave UEFI on, but should be able to disable secure boot in your BIOS.

    If you are unable to disable UEFI secure boot, then you will need to generate a machine owner key pair, and enroll the public parts on the machines where you want to load DAHDI modules you sign with the private part.

    See:
    https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Administration_Guide/sect-signing-kernel-modules-for-secure-boot.html

    Regards, Shaun

    —

  • HI All,

    I tried removing the dahdi directory – re-extracting from source and recompile. Did not help. Still getting the error. I am installing from source.

    Thoughts ?

    Jerry

  • Pretty sure Shaun Ruffell nailed it. It sounds like you have secure boot enabled (systems designed to run Windows, which is just about everything but a build-it-yourself PC, will enable this by default). This can usually be turned off the the BIOS. The alternative is to get the module properly signed, which involves doing things beyond my personal experience. If secure boot is on, then simply recompiling the module will not help.

    Fedora is set up so that if you run a vanilla install, it can boot with secure boot (all the modules that come from Fedora kernel repos are signed), but if you add your own module, it won’t be signed unless you do it, which means it won’t load if secure boot is enabled.

    –Greg