site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com The solution is to either: a) $ sudo touch /System/Library/Extensions $ sudo reboot or b) manually rebuild the cache using kextcache(8) $ sudo kextcache -e - Kevin On May 11, 2005, at 10:29 AM, Ramble Leon wrote: I have two G5, one is 1.6G UP, another is 1.8G DP, I've made my own kernel and put xnu/BUILD/dst/* in a pkg, by install the package, the mach_kernel will be copied to /mach_kernel, kexts and frameworks will be copied to /System/Library/Extensions & Frameworks. I installed the package in both my G5, the 1.6UP is working fine, the 1.8DP is also bootable, but the booting kernel is not my kernel. Although I check the /mach_kernel in both machines by md5, they are exactly same kernel, but uname of these two machines are different, uname output of the 1.8DP is information of the old kernel. Even I removed the old one and reboot, still the same result. Where is the REAL kernel in the 1.8DP G5? How can I replace it? Anybody can help me a little bit? Thanks. _______________________________________________ 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... Mac OS X pre-links the mach_kernel and Extensions, and the results are cached in the /System/Library/Extensions.mkext. The system will only regenerate this cache if it notices that the /System/Library/ Extensions directory is newer than the mach_kernel. My guess is that you copied them over in such a way that the mach_kernel still has a newer mtime than the Extensions directory, and therefore the old uname is still cached in the mkext. This email sent to site_archiver@lists.apple.com