Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

About .cn, I wont advertise it again here.. :XP

 

Next time try to post your other useful infos for us.. So we know, Oz is successfully inject our D/SSDT / not. If success & didnt load, theres must be wrong with yours..

 

Here my logs with some comments

 

 

 

14:725 00:068 Setting Graphics Mode 0 1920 x 1080
14:752 00:026 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
14:752 00:000 Using AcpiGeneratorMask 0x04 00000100 Darwin
14:784 00:031 Inject SSDT r1  0x03AF 0x43 "APPLE " "tinyPRO " 0x00000001 "INTL" 0x20140926 "SSDT-2.aml" - Success // Found SSDT from \Efi\Oz
14:784 00:000 Remove SSDT r1  0x05CC 0x6E "PmRef " "Cpu0Ist " 0x00003000 "INTL" 0x20051117 - Success // Drop
14:784 00:000 Remove SSDT r1  0x0A92 0xFD "PmRef " "CpuPm   " 0x00003000 "INTL" 0x20051117 - Success // Drop
14:784 00:000 Inject SSDT r1  0x074E 0xC1 "APPLE " "CpuPm   " 0x00018400 "INTL" 0x20140926 "SSDT-1.aml" - Success // Found SSDT from \Efi\Oz
14:784 00:000 Found DMI Anchor 0x000FF040 v2.7 Table Address 0xD6FBA018 Length 0x0EC4 - Success
14:788 00:003 Updated DMI Anchor 0xD66C1000 v2.7 Table Address 0xD66C1020 Length 0x0BE5
14:788 00:000 Found 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args "-v darkwake=0-3Fptal0" (13)
14:788 00:000 Found LoadedImage->LoadOptions "<null string>" (0)
14:788 00:000 LoadedImage->LoadOptions "slide=0" (16)
14:788 00:000 Found Intel HD Graphics 4000 [8086:0162] PciRoot(0x0)/Pci(0x2,0x0) // Found Graphic, inject with default properties
14:788 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "model" = "Intel HD Graphics 4000" (22) - Success
14:788 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "built-in" = 00  (1) - Success
14:788 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "graphic-options" = 0C 00 00 00  (4) - Success
14:788 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "hda-gfx" = "onboard-1" (10) - Success
14:788 00:000 Using Custom AAPL,ig-platform-id 0x01620005 // From config
14:788 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "AAPL,ig-platform-id" = 05 00 62 01  (4) - Success
14:788 00:000 Found Intel Panther Point HDA Controller [8086:1E20] PciRoot(0x0)/Pci(0x1B,0x0) // Found Audio
14:797 00:008 Found \Efi\Oz\Darwin\Extensions\Common\IntelMausiEthernet.kext [plist][x86_64] // Found kext from \Efi\Oz
...
15:278 00:004 Found Darwin Kernel Version 16.0.0: Sat Jul  9 23:23:38 PDT 2016; root:xnu-3777.0.0.0.1~27/RELEASE_X86_64 0xC168B000 Kernelcache
15:278 00:000 Injected Call __ZN12KLDBootstrap20readBooterExtensionsEv Into __ZN12KLDBootstrap23readPrelinkedExtensionsEP10section_64
15:278 00:000 Ignore result from call __ZN12IOUserClient21copyClientEntitlementEP4taskPKc in __ZN6OSKext14loadExecutableEv
15:278 00:000 Injecting IntelMausiEthernet.kext "Driver-2BB9000" 0x2931E bytes // From \Efi\Oz
15:280 00:001 Injecting FakeSMC "Driver-2BE3000" (0xC406E000) 228560 bytes // From ROM
15:280 00:000 Warning DisableVoodooHda TRUE // From config, skip default properties

 

 

 

Defaults.plist snippets

 

 

 

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
<dict>
  <key>AAPL,ig-platform-id</key>
  <integer>23199749</integer>
  <key>DisableIntelInjection</key>
  <false/>
  <key>DisableNvidiaInjection</key>
  <true/>
  <key>DisableVoodooHda</key>
  <true/>
  ...
</dict>

 

 

 

"tinyPRO" aka "SSDT-2.aml" snippets

 

 

 

External (_SB_.PCI0, DeviceObj)
External (HDEF, DeviceObj)

Scope (\)
{
    Scope (_SB)
    {
        Scope (PCI0)
        {
            Scope (HDEF)
            {
                Method (_DSM, 4, NotSerialized)
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03
                        })
                    }

                    Return (Package (0x08)
                    {
                        "layout-id",
                        Buffer (0x04)
                        {
                             0x01, 0x00, 0x00, 0x00
                        },

                        "PinConfigurations",
                        Buffer (Zero) {},
                        "MaximumBootBeepVolume",
                        Buffer (One)
                        {
                             0x40
                        },

                        "hda-gfx",
                        Buffer (0x0A)
                        {
                            "onboard-1"
                        }
                    })
                }
            }
        }
    }
}

 

 

 

I download from ASUS website & DIY extract DSDT binary, and found there are already _SB.PCI0.HDEF _DSM method. Delete / replace with yours.

 

 

 

Scope (_SB.PCI0.HDEF)
{
    Method (_DSM, 4, Serialized)  // _DSM: Device-Specific Method
    {
        Name (_T_0, Zero)  // _T_x: Emitted by ASL Compiler
        If (LEqual (Arg0, ToUUID ("c5c5d98d-360e-43af-b7c1-3ede8f669ad3")))
        {
            ADBG ("Audio Player call")
            While (One)
            {
                Store (Arg2, _T_0) /* \_SB_.PCI0.HDEF._DSM._T_0 */
                If (LEqual (_T_0, Zero))
                {
                    If (LEqual (Arg1, Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                             /* . */
                        })
                    }
                    Else
                    {
                        Return (Buffer (One)
                        {
                             0x00                                             /* . */
                        })
                    }
                }
                Else
                {
                    If (LEqual (_T_0, One))
                    {
                        If (LEqual (DerefOf (Index (Arg3, Zero)), Zero))
                        {
                            ADBG ("Audio not active")
                            Store (Zero, VBOK) /* \VBOK */
                        }
                        Else
                        {
                            ADBG ("Audio is active")
                            Store (One, VBOK) /* \VBOK */
                        }
                    }
                }

                Break
            }

            Return (Zero)
        }
        Else
        {
            Return (Buffer (One)
            {
                 0x00                                             /* . */
            })
        }
    }
}

 

 

Link to comment
Share on other sites

This is a brand new ROM then?

The Version of FakeSMC is confusing...

Would be interesting to see if my package from July 2016 would work if you put it into /EFI/Oz/Darwin/Extensions/Common

Link to comment
Share on other sites

Hi all,

 

first of all, this is my setup:

 

Intel i7 3770

QUO Aos MoBo (Ozmosis 1669M)

16GB Kingston RAM

Gigabyte GTX 660 3GB

Samsung EVO 850 SSD (Windows)

Samsung EVO 840 SSD (OS X El Capitan)

 

 

So, I'm having a strange problem with Windows 10. I can only get Win 10 to boot if I use the original QUO BIOS. If I switch to Ozmosis 1669, Windows 10 will not boot (just a black screen without mouse cursor or anything, none of the key combinations do anything, and Alt-Ctrl-Del will just reboot the machine). I've installed all the latest drivers in Win 10 and tried Ozmosis 1669 again. No change. I've tried several different BIOS settings, safe boot on/off, integrated graphics on/off etc. I've also tried having nothing but the Windows SSD connected to the MoBo. Nothing works. 

 

Now for the really weird part. I've had Windows 10 running on this machine before. No changes in hardware, no changes in software. I upgraded my Win 7 Home to Win 10 some months ago, and it worked fine. I didn't like Win 10, so I went back to Win 7. No problems at all. Now I try doing the same thing and no dice. With Ozmosis 1669 the Win 10 upgrade i completes up the point of the first reboot, and it just gets stuck. I've tried this maybe a dozen times already, and it simply will not work. Then I swapped to the original QUO BIOS, and Win 10 installs and works normally. Now of course using the QUO BIOS is not an option, since I can't use OS X with it. Windows 7 Works just fine with Ozmosis, and so does El Capitan. The only thing that doesn't work is Windows 10.

 

I have a sneaking suspicion that the last time I tried Windows 10, I may have had Ozmosis 1479 installed, but I'm not sure. The problem is that to my knowledge 1479 does not support El Capitan. I've never had to modify Ozmosis in any way, and I don't even know how to. It's always worked like a charm without any tweaking.

 

So I've concluded that either something drastic has changed in Windows 10 in the past few months or there is some fundamental difference between Ozmosis 1479 and 1669 that prevents Windows 10 from booting. Any ideas what that something could be?

 

I'd like to have El Capitan and Windows 10 running side by side, but right now I'm only able to use El Capitan and Windows 7.

 

Link to comment
Share on other sites

Msg from developer, maybe you need to update your bios :)

 Woohoo, that did it. This bios was not on the github list, so I didn't even know there was a newer version available. Now Win 10 works. I still need to troubleshoot the El Capitan 10.11.6 update issue, but that's another story and from what I've gathered so far it requires some tweaking.

 

Anyway, thanks a lot.

  • Like 1
Link to comment
Share on other sites

I have updated my firmware utilizing UEFITool 0.21.5 and have successfully flashed my bios using a USB thumb drive created with rufus and installing DOS on it.

 

I can go into the bios setup and make changes. However, I never get the Ozmosis splash screen and I always get a Boot0ss error with the modified firmware.  If I reflash the firmware with a non-modified version I can again boot to the MacOS drive.

 

Can someone take a look at my file and see if I've missed something? I have tried to keep it to the minimum as all the necessary kexts, such as FakeSMC, I have installed in the EFI partition to make updating easier for me.

 

Many thanks in advance for any assistance you can provide.

 

 

 

EDIT:  Forgot to add attachment.  Modified firmware file can be found here:  

https://dl.dropboxusercontent.com/u/77750421/Z170v3.rom

Link to comment
Share on other sites

I have updated my firmware utilizing UEFITool 0.21.5 and have successfully flashed my bios using a USB thumb drive created with rufus and installing DOS on it.

 

I can go into the bios setup and make changes. However, I never get the Ozmosis splash screen and I always get a Boot0ss error with the modified firmware.  If I reflash the firmware with a non-modified version I can again boot to the MacOS drive.

 

Can someone take a look at my file and see if I've missed something? I have tried to keep it to the minimum as all the necessary kexts, such as FakeSMC, I have installed in the EFI partition to make updating easier for me.

 

Many thanks in advance for any assistance you can provide.

 

 

 

EDIT:  Forgot to add attachment.  Modified firmware file can be found here:  

https://dl.dropboxusercontent.com/u/77750421/Z170v3.rom

 

Missing some essential part in your rom:

At least, OzTheme, OzDefault, FakeSmc.

 

Fred 

Link to comment
Share on other sites

Missing some essential part in your rom:

At least, OzTheme, OzDefault, FakeSmc.

 

Fred 

Fred,

 

Thanks for taking a look, I will see if I can find OzTheme and OzDefault and insert them.  As for FakeSMC, I've put that in the EFI partition as I don't want to update the firmware every time a new version comes out.

 

Fernando

Link to comment
Share on other sites

Missing some essential part in your rom:

At least, OzTheme, OzDefault, FakeSmc.

 

Fred 

I took a look at the ozmosis rom that I was extracting files from and I found the OzmosisDefaults and FakeSMC, but was not able to find the theme.  I placed the two files I found on my firmware image and flashed the bios but I still get the boot0ss error. 

 

Any ideas what is going on? As soon as I flash the original firmware back I am able to boot normally.

Link to comment
Share on other sites

I took a look at the ozmosis rom that I was extracting files from and I found the OzmosisDefaults and FakeSMC, but was not able to find the theme.  I placed the two files I found on my firmware image and flashed the bios but I still get the boot0ss error. 

 

Any ideas what is going on? As soon as I flash the original firmware back I am able to boot normally.

Wait a support for skylake .Or use Ozmosis via bcfg. Dont replace partitiondxe and FAT with enhancedfat.

Link to comment
Share on other sites

Wait a support for skylake .Or use Ozmosis via bcfg. Dont replace partitiondxe and enhancedfat with FAT.

Unfortunately I can't even get into bcfg as it goes directly to a boot0ss error.   Guess I'll have to wait for Skylake support.  Thank you.

Link to comment
Share on other sites

Hi guys!

I have big problem with ALC887 and all USB port to be working!

Yes, i need help please. When the HDEF is in SSDT, then it work, but the problem with SSDT is when it's shutting down or in restart it takes long time to do it and USB ports work. Back to patched DSDT with all devices, Some USB's ports don't work with and without USB injection in DSDT or SSDT, and sound also and no audio kext work at all! And the devices injected in DSDT or SSDT with DTGP method and DSM aren't listed in PCI devices at System Information in OS X.

Please anyone to help me, thanks!

Link to comment
Share on other sites

boot0ss is part of a legacy bootloader like chameleon. Which means u r booting legacy using the CSM...

When using the normal firmware I boot using Clover in UEFI mode.   I set the firmware to the same settings as with Clover, UEFI only, OS set to Other.  Any suggestions on how to check how it's getting into legacy mode?

Link to comment
Share on other sites

When using the normal firmware I boot using Clover in UEFI mode.   I set the firmware to the same settings as with Clover, UEFI only, OS set to Other.  Any suggestions on how to check how it's getting into legacy mode?

 

Could imagine you installed Clover with legacy boot files (yes, you can boot Clover via UEFI and still have legacy files installed).

Why do you set OS to Other OS? If you want true UEFI booting, make sure you are using Protective MBR (clean GPT) rather than Hybrid MBR and have no bootcode in the MBR region (such as boot0ss or whatever errors for you). No CSM, and preferably "Win8" boot mode

And no, I will make a step-by-step guide, please research...

 

I'd be interested in seeing how this works. Do you mind making this mod for the Z77pro3(AsRock)?

This board has got its bios patched for it to run without the CPUpowermanagements kext I think thats important to be aware of.

 

First google and if none is found, ask here: http://www.insanelymac.com/forum/topic/303569-ozmosis-modded-bios-repository/

  • Like 1
Link to comment
Share on other sites

good day,

 

i read through all the contents from this topic, yes 212 pages....

 

so now i can make an Oz for my P8Z77-V Pro, so far so good. such like intel 82579v, lsi raid....

 

but seems still no solution to input DSDT to Oz for ASUS motherboard, am i right?

 

thanks and have a nice day.

Link to comment
Share on other sites

good day,

 

i read through all the contents from this topic, yes 212 pages....

 

so now i can make an Oz for my P8Z77-V Pro, so far so good. such like intel 82579v, lsi raid....

 

but seems still no solution to input DSDT to Oz for ASUS motherboard, am i right?

 

thanks and have a nice day.

Hi, what do you mean? 

You can put your DSDT into ESP/Quo/Darwin/Acpi so system can load id, but you have to edit and fix it 

Link to comment
Share on other sites

×
×
  • Create New...