Jump to content
15 posts in this topic

Recommended Posts

I'd be really thankful if someone with some knowledge about kexts could explain why some kexts only work in /S/L/E/ and not if loaded by a bootloader e.g. from an EFI Partition.

 

It shouldn't be about dependencies because they should all be satisfied as soon as the system loads the rest of the kext from the system drive or am I wrong about this?

Has this question been asked a million times before? Then at least tell me that...

 

well....... sadly the osx86 community has fallen pretty hard,

edit- funny while i was typing this i noticed taruga is looking at this topic.

the kexts have dependencies that are needed to load them, and the boot on root string will cause them to boot before their dependencies and therefore not work.

well....... sadly the osx86 community has fallen pretty hard,

edit- funny while i was typing this i noticed taruga is looking at this topic.

the kexts have dependencies that are needed to load them, and the boot on root string will cause them to boot before their dependencies and therefore not work.

 

Thx for the answer!

 

So one had to put all the dependencies on the efi partition too? Would that work? I'd really like the idea of having an untouched system partition without any added or modified kexts, plists et cetera...

Thx for the answer!

 

So one had to put all the dependencies on the efi partition too? Would that work? I'd really like the idea of having an untouched system partition without any added or modified kexts, plists et cetera...

 

It will work until apple releases an update of the kexts, then it will cause a problem

 

Taruga should know about this and the OSvKernlib.kext lol

It will work until apple releases an update of the kexts, then it will cause a problem

 

Hmm :( , that's not exactly the idea of the whole efi partition thing...

 

Is this just with some SL kexts, or was this problem already there with leopard?

It's good to minimize hackintosh stuff in S/L/E, but keeping a 'virgin' partition? That adds so little to the setup.

 

 

the goal is not to have to replace any retail kexts with you own, but have them load over from extra/extensions/

so that system updates don't crash.

 

any third party kexts should have no issues being loaded in S/L/E

leopard.

 

Well then... I'll get used to it.

 

Thanks for clearing that up.

 

the goal is not to have to replace any retail kexts with you own, but have them load over from extra/extensions/

so that system updates don't crash.

 

any third party kexts should have no issues being loaded in S/L/E

 

Thanks again. Thats what I thougth. I just have skge and VoodooHDA in S/L/E so I should be fine with any upcoming updates...

 

What about fakesmc. Is it update-proof? I remember having read something in netkas' blog that dsmos will have to be updated as soon as 10.6.1 is out to work with it... Is this also the case with fakesmc?

Well then... I'll get used to it.

 

Thanks for clearing that up.

 

 

 

Thanks again. Thats what I thougth. I just have skge and VoodooHDA in S/L/E so I should be fine with any upcoming updates...

 

What about fakesmc. Is it update-proof? I remember having read something in netkas' blog that dsmos will have to be updated as soon as 10.6.1 is out to work with it... Is this also the case with fakesmc?

 

If you have been hackintoshing for a while, then you know by now that us hackintoshers will never get to some magic point where we can just put together a system that is guaranteed update proof. On my Leopard system I used a Boot123 USB drive that got me through a few point revisions, but even it failed my by 10.5.8.

 

Apple will always throw us some loop that makes upgrading hard without a patch, or a new dsdt, or a new dsmos, or a new bootloader. Personally I never upgrade until I look here on the forum and see what breaks.....

I'd be really thankful if someone with some knowledge about kexts could explain why some kexts only work in /S/L/E/ and not if loaded by a bootloader e.g. from an EFI Partition.

 

It shouldn't be about dependencies because they should all be satisfied as soon as the system loads the rest of the kext from the system drive or am I wrong about this?

 

use Kext Utility ...

Here is a little script I made to create my mkext for both i386 and x86_64. Edit it to fit your /E/E location. I'll be modifying it to make it more automatic this is just a quick draft.

 

 

mkextcreatorV0.2.sh.zip

mkextcreator.sh.zip

Here is a little script I made to create my mkext for both i386 and x86_64. Edit it to fit your /E/E location. I'll be modifying it to make it more automatic this is just a quick draft.

 

 

mkextcreatorV0.2.sh.zip

mkextcreator.sh.zip

Good Attempt but this will still not work for Raid Helper Partitions

×
×
  • Create New...