Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

Thanks. I got windows to boot with the 894 and vanilla dsdt this morning before work. Wonder do you recall what variable you changed in the dsdt? Anyhow from now on I'll probably keep the dsdt edits in bios to a minimum and limit it to hdef edits if at all and load the dsdt straight from the hard drive. Anyhow while playing around with Clover I noticed they have one efi driver called AmiAptioFix. Is this a concern with osmosis at all if using ami bioses?

 

Thanks

 

Edit: You were right! It was the DSDT! Probably the renaming device name patch was at fault.  Wish I knew exactly which edits were at fault though to get it as close to vanilla install as possible.

Link to comment
Share on other sites

Was wondering if this is correct for my Defaults.plist file:

 

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
        <dict>
<key>UserInterface</key>
                <string>%01</string>
</dict>
 
Want to set the GUI as the default bios option.
 
Thanks
or this :
 
<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
        <dict>
<key>UserInterface</key>
                <true/>
</dict>
  • Like 1
Link to comment
Share on other sites

Its same like 7 series.

New gui its diferend module.

there are CoolGUIDxe in 8 series and i think thats a new gui,

i will try to integrate it but i dont think that will be soo simple as only integrate module..

 

integrated it but nothign happened,dont know how to start it :D

maybe if i replace old one with new one.

Dont know why new z87 even have this old theme file inside...

 

 

Ever figure out how to swap GUI from  newer motherboard into older model like from Z97 to Z87 for example?

Link to comment
Share on other sites

Hi, during some hacking i discover one weird thing, i have a complete network boot server that serve uefi based machine, copy ozmosis.efi into directory where i serve efi file, i can view ozmosis screen, but after i can't anything.

For what you know, how can send via newtwork others thing like filesystem fakesmc and so on? 

Link to comment
Share on other sites

Thanks. I got windows to boot with the 894 and vanilla dsdt this morning before work. Wonder do you recall what variable you changed in the dsdt? Anyhow from now on I'll probably keep the dsdt edits in bios to a minimum and limit it to hdef edits if at all and load the dsdt straight from the hard drive. Anyhow while playing around with Clover I noticed they have one efi driver called AmiAptioFix. Is this a concern with osmosis at all if using ami bioses?

 

Thanks

 

Edit: You were right! It was the DSDT! Probably the renaming device name patch was at fault.  Wish I knew exactly which edits were at fault though to get it as close to vanilla install as possible.

When you patch your DSDT let the name of your SAT0 and SAT1 device unchanged, you can still add a _DSM method to SAT0 device - it doesn't matter. You should be able to load windows than.

It took me three days of bios flashing and testing while adding patch by patch to BIOS DSDT. I found out since than that most mainboards are concerned when you install a patched DSDT with SAT0 changed to SATA into bios. When you still want to use SATA device name in your bios DSDT you have to change the name of SAT0 to SATA inside of your bios SSDTs and windows will load again normally.

 

Good luck 

 

Was wondering if this is correct for my Defaults.plist file:

 

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
        <dict>
<key>UserInterface</key>
                <string>%01</string>
</dict>
 
Want to set the GUI as the default bios option.
 
Thanks
or this :
 
<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
        <dict>
<key>UserInterface</key>
                <true/>
</dict>

 

 

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
        <dict>
<key>UserInterface</key>
                <true/>
</dict>
 
is the right one for boolean variables in .plist
Link to comment
Share on other sites

here detailed instructions with video:

 

http://www.insanelymac.com/forum/topic/301407-guide-insert-ozmosis-into-uefi-bios/?hl=%20ozmosis

 

or you can use OZMTool from terminal, it is a great tool and saves a lot of manual work but I would to recommend to do it once manually so you can understand what you need to do to get osmosis inside the bios and what all the modules are for.

 

when using non gigabyte board usually you have to disable MSR lock with PMPatch or newer version UEFI Patch otherwise you have to use patched AppleCPUPowerManagement.kext to be able to boot OS X and to use speedstep and turboboost functions further.

 

Good luck!

 

Many thanks. I completely destroyed this machine with Clover, had to reinstall Win7-64 (non-UEFI this time). Haven't bothered reinstalling Mac OS X as of this date.

Link to comment
Share on other sites

Many thanks. I completely destroyed this machine with Clover, had to reinstall Win7-64 (non-UEFI this time). Haven't bothered reinstalling Mac OS X as of this date.

Keep in mind that ESP ( Efi System Partiton ) will be located on the first HDD, if you install win7 in uefi mode and after you will install Osx, ESP wil be located in osx disk if you will use two phisical disks 

Link to comment
Share on other sites

Hi! All about GA-Z77-DS3H I have two HDD, first only OS X, second Windows 8 UEFI and 10.10.4 beta. Can not do that boot from first, all time booting Windows. Try change priority boot in BIOS menu, but without success, changes do not save.  Try through shell.("bcfg boot dump" and than " bcfg boot rm...") It delete, but after reboot again is. Please help me find solution. 

And else one: where find utility MMtol for OS X, in topic links unworking.

Thanks

Link to comment
Share on other sites

Thanks. But how make priority boot from HDD with only OS X ???

On your bios settings put your Only UEFI and first boot is boot name of your partition of OS X eg Hackintosh HD or whatever...

AHCI-Mode : Enabled
XHCI-Mode : Auto
XHCI-Hand Off : Enabled
EHCI-Hand Off : Enabled
vt-D f : Disable
Wake On Lan : Disable
Secure Boot : Disable
CPU EIST : Disable
Internal Processor Graphics : Disable
DVMT Total Memory Size : MAX
Intel Speedstep: Disabled
Link to comment
Share on other sites

I am do it, after F10\Save, but after reboot again "Windows Boot Manager" is first and load windows

Open terminal and write or copy paste this command:

 

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableBootEntriesFilter=%01
Link to comment
Share on other sites

 

Open terminal and write or copy paste this command:

 

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableBootEntriesFilter=%01

No success... I don not understand why changes in boot menu not save, other changes in bios menu nice saves

Link to comment
Share on other sites

No success... I don not understand why changes in boot menu not save, other changes in bios menu nice saves

 

Open System Preferences then Startup Disk select the OSX install reboot when asked to do so. It should now do what you want this thing defaults to windows no matter what else you do and this is the only way I ever found to do it for OSX default boot.

Link to comment
Share on other sites

Open System Preferences then Startup Disk select the OSX install reboot when asked to do so. It should now do what you want this thing defaults to windows no matter what else you do and this is the only way I ever found to do it for OSX default boot.

 

already did it.... no success

Link to comment
Share on other sites

All same no success :(

OSX Load only through F12 or GUI by click mouse and choose OS X partition. Default  automaticly load windows. Also reseted nvram too. May something wrong with nvram? If  the same situation in other users everythings is fine, than I have problems with nvram.

Link to comment
Share on other sites

use voodoo, keep in bios with disabler.kext...

 

Ok you now have VoodooHDA in your ROM.

 

|185|PartitionDxe   |1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609|00818313|0018CC|DRVR|
|186|HfsPlus        |4CF484CD-135F-4FDC-BAFB-1AA104B48D36|00819BDF|00379C|DRVR|
|187|EnhancedFat    |961578FE-B6B7-44C3-AF35-6BC705CD2B1F|0081D37B|003451|DRVR|
|188|OzmosisDefaults|99F2839C-57C3-411E-ABC3-ADE5267D960D|008207CC|0007B0|DRVR|
|189|Ozmosis        |AAE65279-0761-41D1-BA13-4A3C1383603F|00820F7C|030B56|DRVR|
|190|OzmosisBlackThe|AC255206-DCF9-4837-8353-72BBBC0AC849|00851AD2|02F692|FRFM|
|191|SmcEmulatorKext|DADE1001-1B31-4FE4-8557-26FCEFC78275|00881164|0133A3|FRFM|
|192|DisablerKext   |DADE1002-1B31-4FE4-8557-26FCEFC78275|00894507|00323B|FRFM|
|193|InjectorKext   |DADE1003-1B31-4FE4-8557-26FCEFC78275|00897742|00023F|FRFM|
|194|CpuSensorsKext |DADE1006-1B31-4FE4-8557-26FCEFC78275|00897981|0078D7|FRFM|
|195|LpcSensorsKext |DADE1007-1B31-4FE4-8557-26FCEFC78275|0089F258|00EC10|FRFM|
|196|GpuSensorsKext |DADE1008-1B31-4FE4-8557-26FCEFC78275|008ADE68|01A285|FRFM|
|197|VoodooHdaKext  |DADE1009-1B31-4FE4-8557-26FCEFC78275|008C80ED|027367|FRFM|
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...