My third-party nvme driver cannot be automatically loaded at Big Sur startup

[vanir2020]

I have a thunderbolt NVMe RAID Controller.
Need to install the manufacturer's nvme driver (HighPoint NVMe driver).

It works fine on macOS10.15.7,
But when I try to use this card on the new system 11.0。

When I entered the system, I found that the third-party NVMe driver was not loaded, but the system's NVMe driver was loaded.
I plugged in the Thunderbolt device again, and this time the third-party NVMe driver was loaded.

The third-party NVMe driver has been installed correctly. the kext cache is updated successfully.

The problem is that the driver cannot be loaded at startup。
how to fix it?


the Highpoint nvme driver is placed in AuxiliaryKernelExtensions.kc.
and the apple nvme driver is placed in BootKernelExtension.kc,
the system always load drivers in BootKernelExtension first, is it true?

 

[oatman13]

AuxilaryKernelExtensions are loaded by kmd after user-space starts initializing.

BootKernelExtensions are immutable and can only be delivered by Apple. This kernel extension is what is loaded on boot.

In Big Sur it is no longer possible to load a kernel extension at boot-time. Instead they are loaded while daemons are launching as part of the AuxiliaryKernelExtension cache.