ADC Home > Reference Library > Technical Q&As > Darwin > Hardware & Drivers >
|
Q: My KEXT loads when I hot-plug my device, so why won't it load at boot time? A: There are a couple of reasons why this could be happening. First,
a boot time KEXT other than your own may be matching to your device, namely a
KEXT with its A common example of this is a composite USB device with a vendor-specific driver. The Apple composite class driver will match at boot time. (The composite class driver has to be a boot time KEXT because it is needed to boot from Mass Storage class devices.) As a result, the vendor-specific driver will not load. But, if the device is hot-plugged, all eligible drivers will then compete for the device and the vendor-specific driver will be a better match than the composite class driver. The
solution is to set the Another
possible cause is that boot time KEXT loading does stricter version and dependency
checking starting in Mac OS X 10.1. Verify that the
Even after changing the MODULE_VERSION in Project Builder, it may be necessary
to 'Clean' your project or even delete your build folder in the Finder
before recompiling because Project Builder caches some of this information.For more information about loading KEXTs at boot time, please see the Loading Kernel Extensions at Boot Time document. [Jan 15, 2004] |
|