RHEL7 systems with FIPS enabled producing "modprobe: ERROR: could not insert ..." / "modprobe: FATAL: Module ... not found" messages

Solution Verified - Updated -

Issue

  • After enabling FIPS, the following ERROR messages are printed during boot and seen in the journal

    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'camellia_aesni_avx_x86_64': No such device
    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'camellia_aesni_avx2': No such device
    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'cast6_avx_x86_64': No such device
    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'serpent_avx_x86_64': No such device
    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'serpent_avx2': No such device
    dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'twofish_avx_x86_64': No such device
    
  • After enabling FIPS, the following FATAL messages are printed during boot and seen in the journal

    dracut-pre-trigger[252]: modprobe: FATAL: Module sha1 not found.
    dracut-pre-trigger[252]: modprobe: FATAL: Module sha256 not found.
    

Environment

  • Red Hat Enterprise Linux 7
  • Red hat Enterprise Linux 8
  • FIPS compliance mode

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content