To chime in again... Yes, this one happened to me too early on. I should have mentioned it. I ended up using a simple script to "sudo cp -R" the kext from the build location to /System/Library/Extensions/ and that had the side effect of setting the owner and group to root:wheel which seems to be how they need to be set. This was also the easiest location for the system to pick up subordinate dependancies too. -Mike On Friday, February 14, 2003, at 10:40 AM, Stiphane Sudre wrote: On Friday, February 14, 2003, at 03:55 PM, Peter Lovell wrote: Hi Eric, Mike's suggestion is a good one. I'll also suggest that you go back to your build process and check that carefully. I've had several occasions where I was able to build the kext with warnings but no errors and it wouldn't load. Just for completeness, also check the plist and other packaging things (ownership, permissions, etc etc). It could be that they were OK in the old build folder but haven't been recreated correctly. I would expect these to at least give you an error upon kextload, but you never know. Another potential cause I once faced. Not building the Kext with the root account prevented my kernel from working. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.