Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
xhala_debru

REbuild Extension.mkext after any new kext?

8 posts in this topic

Recommended Posts

Hi all,

 

I've got SL running and, for what I know, all runs fine except for 2 things:

 

1) Diskutil was not able to repair permissions due to something like a lack of receipt.

Of course all of them were all there.

I reinstalled BSD.pkg (don't knowif it's ok to do so) and the error went away.

It does something but I don't know if it does anything.

I'll have to change manually the permissions on a kext and see if SL corrects them.

 

2) Everytime a program, driver or the 10.6.1 installs a kext, I have to rebuild the Extension.mkext in /Extra and in /S/L/etc...

If I don't, the system remains unbootable. (waiting for root device or even stalling just before GUI, with no error message).

I use Chameleon RC3's boot file

Is this normal?

 

Maybe the 2 problems are related?

 

Any idea?

 

Thank you.

 

Xhala

Share this post


Link to post
Share on other sites

hey

 

rebuild the extensions.mkext with kextutility (plus the extensions folder) in /extra after every added kext.

 

in my experience, that's all there is needed. forget about kexthelper and actually, i haven't applied a single change to S/L/E, only to extras.

 

it will help to copy the extensions folder from /Extra (with the new kexts) to the desktop, drag it over kextutility (take the SL ready one from http://www.insanelymac.com/forum/index.php?showtopic=140647) and then copy the Extensions folder mac to /Extra, together with the newly generated extensions.mkext.

 

that did the trick, and always has.

Share this post


Link to post
Share on other sites
hey

 

rebuild the extensions.mkext with kextutility (plus the extensions folder) in /extra after every added kext.

 

in my experience, that's all there is needed. forget about kexthelper and actually, i haven't applied a single change to S/L/E, only to extras.

 

it will help to copy the extensions folder from /Extra (with the new kexts) to the desktop, drag it over kextutility (take the SL ready one from http://www.insanelymac.com/forum/index.php?showtopic=140647) and then copy the Extensions folder mac to /Extra, together with the newly generated extensions.mkext.

 

that did the trick, and always has.

Thanks,

 

I wasn't sure if it was a normal behaviour to have to rebuild mkext or not.

Apparently, it is.

I think it's a pity because these kind of thing was not necessary with Leo.

 

As for the added kext, I had one installed for my Areca raid card and one for littlesnitch.

 

At least one think is forsure, I'll keep a bootable usb Leo HDD to fix things ;)

Share this post


Link to post
Share on other sites

I have noticed that Snow doesnt make a Extensions.mkext like my Leo does.

example: If i delete the Extensions.mkext from Leo the sys creats a new one.

Snow has not made one mkext for me. I have had to make them all myself.

Is my install not 100%? or is it something dumb like timemachine not being set up in Snow.

Share this post


Link to post
Share on other sites

Sorry if this is dumb question,

 

but what's mkext? I know kext is kernal extension and its something like drivers for Windows, but I did notice there is a mkext file that can't be opened with a text editor, just curious what it is.

 

Also, if SL won't automatically rebuild this mkext file on our hackintoshes, what about on a real Mac? because as far as I know, the way we install snow leopard is almost vanilla, just with a different boot loader and a decryptor, maybe a fake EFI.

 

Thanks!

Share this post


Link to post
Share on other sites
I have noticed that Snow doesnt make a Extensions.mkext like my Leo does.

example: If i delete the Extensions.mkext from Leo the sys creats a new one.

Snow has not made one mkext for me. I have had to make them all myself.

Is my install not 100%? or is it something dumb like timemachine not being set up in Snow.

 

Snow Leopard's mkext is no longer in /System/Library but rather in /System/Library/Caches/com.apple.kext.caches/Startup.

 

Just an FYI. You don't need to manually create one, it's automatically recreated with any modification to the Extensions folder.

 

Sorry if this is dumb question,

 

but what's mkext? I know kext is kernal extension and its something like drivers for Windows, but I did notice there is a mkext file that can't be opened with a text editor, just curious what it is.

 

Also, if SL won't automatically rebuild this mkext file on our hackintoshes, what about on a real Mac? because as far as I know, the way we install snow leopard is almost vanilla, just with a different boot loader and a decryptor, maybe a fake EFI.

 

Thanks!

 

The mkext file is simply a cached version of all your kexts in the Extensions folder. The OS uses it for faster loading of your extensions at boot. The file is automatically recreated whenever the Extensions folder is modified. You can also manually rebuild it yourself at boot with the -f flag.

Share this post


Link to post
Share on other sites
Snow Leopard's mkext is no longer in /System/Library but rather in /System/Library/Caches/com.apple.kext.caches/Startup.

 

Just an FYI. You don't need to manually create one, it's automatically recreated with any modification to the Extensions folder.

 

 

 

The mkext file is simply a cached version of all your kexts in the Extensions folder. The OS uses it for faster loading of your extensions at boot. The file is automatically recreated whenever the Extensions folder is modified. You can also manually rebuild it yourself at boot with the -f flag.

Thanks for this info. I have a question on mkext rebuild. Whenever I want to rebuild the mkext, I do the following:

kextcache -v 1 -t -m /Volumes/Chameleon/Extra/Extensions.mkext /Volumes/Chameleon/Extra/Extensions/ /System/Library/Extensions/
kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions/

 

I know that the first one gets executed because I can see the E/E kext get loaded during booting. So is it needed to also load the Extensions.mkext in the caches folder?

Share this post


Link to post
Share on other sites

Well, I put deleberatly wrong permissions on a vanilla kext in /S/L/E and tried to correct the permissions.

No error but not corrections neither.

 

It seems that reinstalling BSD.pkg only clears the "could not correct permissions error", but doesn't help repairing the permissions...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.



×