Kernel panics and kexts are related?

expand collapsive

The device gets a kernel panic after it upgraded to Big Sur. I get it after rebooting and entering the FV2 passoword

All Replies

  • Hexnode

    Catherine George

    Moderator

    Happy to help,

    Kernel panics often occurred in our Beta testing environment for macOS Big Sur. However, a specific KEXT loaded by an application and its incompatibility with Big Sur caused the device to misbehave.

    Verify if your software is running a Kernel Extension and check its compatibility statement with Big Sur.

    Kindly reach out to the Hexnode Community for further queries.

    Catherine George
    Hexnode UEM

  • Participant

    yfke

    Participant

    Is there anything with kernel extensions and macOS Big Sur?
    I have some kernel extension approved via policies. Its perfect with Catalina. On big sur it prompts the user to allow the kernel extensions to be installed following reboot.
    Should I replace kernel extensions policy with system extensions to approve these KEXTs? I understand system extensions and replacing kernel extensions on big sur.

  • Hexnode

    Catherine George

    Moderator

    Hello @yfke,

    Welcome to Hexnode Connect,

    Kernel Extensions policies are still supported on Mac. However, unlike its previous versions, macOS Big Sur requires these KEXTs to have additional configuration settings to continue working. For example, whether you enable the User Override option on the policy, the user should approve it and restart the device to load it successfully.

    Big Sur does not automatically convert Kernel Extensions to System Extensions. So, if your applications or software load a Kernel Extension for its functioning, they should probably be supporting System Extensions too by now. In that case, you may approve them using the System Extensions policy. Otherwise, for loading a Kernel Extension, the user should approve it and restart the device. This is how it works on macOS Big Sur.

    Hope I was able to throw some insights into your question,.

    Catherine George
    Hexnode UEM

  • Participant

    Kim Morgan

    Participant

    macOS Big Sur seems to have too many issues with kexts. We had undergone this phase. And I understand we are not just the ones to have suffered.
    I recommend you follow these steps. That’s hhow we recovered the device.

    • Disable SIP in recovery mode.
    • Reboot the device.
    • On the terminal, run:
      sudo kextunload.
      sudo rm -rf extensions
      sudo kmutil clear-staging
    • Reboot the device.
    • Enable SIP.