Jump to content
5 posts in this topic

Recommended Posts

Hello,

 

It's my first topic there yet I want you to be attentive to my problem. Thanks in advance for your help:

 

So here is where I'm stuck. My friend provided me with custom packed Extensions.mkext file for /Extra folder. It was made for GA-EP35-DS4 mobo and I have GA-EP45-DS4 and wan't to customize it a little bit. Here is the list of kexts that reside inside Extensions.mkext:

 

AHCIPortinjector.kext

EvOreboot.kext

fakesmc.kext

IOAHCIBlockStorageInjector.kext

 

And I need to put HDAEnabler.kext, LegacyHDA.kext, RealtekRTL81xx.kext in it. I unpacked Extensions.mkext using kext utility to /Extra/Extensions using the same utility packed a new Extensions.mkext file which is initially smaller in size than a provided one. And tried to boot.

 

At the boot I got the following error:

 

4/8/11 8:48:28 AM kernel ACPI_SMC_PlatformPlugin::registerLPCDriver - failed to locate SMC driver

 

And can't pass through this place.

 

What I can't understand is that why it doesn't not boot with kexts unpacked?

 

I have no other options to try as to pack the needed kexts together with provided ones and see if it will boot this way.

 

What do you think on this problem, have you experienced it yourself?

 

 

Edit: I were able to pack my own Extensions.mkext with the use of MKext Tool. Here you are able to select in which way to pack either in i386 or x86_64

 

Best Regards,

Ruslan

so what I've already tried is to pack a new Extensions.mkext including the kexts I need. And it doesn't boot either it boots only with Extensions.mkext my friend provided to me. It seems like magic however i believe there is no magic in OSX86 world and I'm missing some knowledge. Here is the screen shot of Kext Utility:

 

screenshotjxf.png

 

Uploaded with ImageShack.us

 

 

It writes that it "Found i386 (arch) only kext(s)" and I want to boot in 32Bit mode to check if it'll work this way. Currently I'm booting in 64 Bit.

 

Ruslan

My understanding is that the mkext file only contains the portion of the kexts required for booting (Info plist and executable) and not all information is transformed back to a original-like kext when unpacked. So, basically, not all the info is there to create a valid mkext file again. Some kexts may need to be "rebuilt" manually to undergo another kextcache process. I'll need to do some tests to verify this theory, but that's my guess.

 

An example would be kexts with Plugins. Those plugins get extracted individually and will end up outside their original parent kext. So, they would need to be added back in manually.

 

I would opt for getting the original kexts from your friend and add your set. Actually, those 4 kexts are rather common and can be found anywhere on the net, so there's no need to rely only on those from your friend.

 

What version of fakesmc.kext are you using and does it have any plugins? I figure it's probably the older v2.1 that doesn't have any plugins.

 

MAJ

Thanks for your reply MAJ,

 

I'm really into this problem now. And I know that it architecture related in some way as I was able to boot in 32 Bit with my packed Extensions.mkext

Only RealtekRTL81xx.kext doesn't work so I'm going to expand mkext and put this kext in /System/Library/Extensions where it worked.

 

I think you are right it reassembles the kexts in some other way so I can't boot with them. And actually it makes them only 32 Bit loadable. But I'm using 64 Bit kext utility app ver. 2.4.2

 

So I guess it could be able to load and pack the kexts in 64 Bit.

 

Ruslan

 

oh and I'm using ver. 2.0 of fakesmc and I don't know how to check if it has any plugins or not.

Hey, thanks all for your help it is really encouraging. And I fixed it:

 

I were able to pack my own Extensions.mkext with the use of MKext Tool. Here you are able to select in which way to pack either in i386 or x86_64

 

Best Regards,

Ruslan Yusipov

×
×
  • Create New...