Ozmosis + El Capitan

It's not a simple question. For installing you have to use Clover installer, for working system you may use Osmosis 1479. Or wait till the Os-Team offers its next version in a few days or weeks..

Gesendet von iPhone mit Tapatalk

There are rumors that the developers are working on a new version, but there is no release date yet.

Installation itself only with clover, after installation and finetune ist finished you can use ozmosis to boot el capitan

Yes, that's possible. But you need to do 2 things that it works:

1.) FakeSMC.kext needs to be put into:

2.) Turn off CSR by setting the NVRAM variable:

So here is the procedure in short:
- Flash Ozmosis 1479 to your BIOS
- Generate El Capitaion BootStick with Clover
- Install El Capitain via Clover Boot Stick
- Boot into El Capitain with Clover Boot Stick
- Add FakeSMC.kext to L/E
- Add all other necessary kexts (LAN, Audio etc.) to L/E
- Turn off CSR via NVRAM
- Now your Hacintosh should boot directly into El Capitaion with Ozmosis, no need for Clover anymore.

The new version of Ozmosis will support FakeSMC.kext to load directly again. So if a new version will be released, you can just flash the new Ozmosis and delete FakeSMC.kext from EFI, or leave it there. Doesn't matter, because Ozmosis always prefers the FakeSMC in EFI, only if there is non it will load it's own.

razor:
You are right, I just wrote the wrong thing, because I was so used to it I changed it in my earlier post.

BTW:
I had problems with using the nvram command to set the csr-active-config, so I put it directly into my defaults.plist on /EFI/Oz.

Since it is a string you don't have to use the %-sign in between.
To check if the setting is used, you can use the terminal command

which should give you the following line back:

This matches the same entry as you would have while using Clover with

@bananarezien here you go: Mod für das Z77-DS3H Rev.1.x
1.X stands for all revisions...

Sorry Folks,

you're right.
The entry in the config.plist must be:

which then leads to the correct value in nvram -p