Re: Upgrading a ROM based KEXT
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Cheers, - Dean _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Oct 27, 2006, at 12:27 PM, Michael Smith wrote: On Oct 27, 2006, at 11:20 AM, Satyam Lad wrote: The probe score will always be the same as the info.plist is the same for both the KEXT's. The only difference in both the KEXT (in terms of info.plist) is of "CFBundleVersion" property. The new KEXT has a higher number then the older (ROM) KEXT. This won't achieve your desired goal; version numbers are not considered when matching, only the probe score counts. If you want the kext to win vs. the ROM, you need to ensure the kext has a higher probe score. Actually, that true only if the two kexts have different CFBundleIdentifiers. The way it is *supposed* to work in this case is as Satyam is attempting The kext managmenet system will collect all the versions it can find for any given CFBundleIdentifier and attempt to use the latest version. The fact that it is working as expected on the first reboot tells me that he has it mostly working correctly. The fact the subsequent reboots use the ROM kext indicates that perhaps his newer kext isn't getting included in the kext cache. What happens if you safe boot (hold the shift key down), which bypasses the caches and goes back to scanning for individual kexts. Does it get the newer kext then? This email sent to site_archiver@lists.apple.com
participants (1)
-
Dean Reece