Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

Hi, I'm having trouble with the Ozmosis bootloader. I've managed to flash my board (Z77-DS3h rev 1.1) with the bootloader and all went fine. I didn't create my BIOS myself but found it on the hackintosh-forum.de and successfully installed El Capitan. Everything works good but can't disable SIP or change any bootloader settings. Have I done anything wrong or is it possible for anyone to mod my BIOS for me with a DSDT and all up to date files? I did try to make a modded BIOS and it went through without errors but i'm still not sure about it.

 

Thanks for any help you can give me guys and p.s,a copy of my current BIOS file is included

attach yor ROM here!!!

Link to comment
Share on other sites

Another quick question if anyone can answer it. I've installed El Capitan and now trying to edit the Defaults.plist file which doesn't exist somehow. How do I create it or should it of been created automatically? 

Here you go. Open cloverconfigurator and make your defaults. Later put Defaults.plist in EFI/Oz and reset NVRAM.

Defaults.plist.zip

Link to comment
Share on other sites

Hi

 

I have couple of questions, I hope someone can help or give some suggestions...

Does Ozmosis able to do kext patching? for example for HD4600 graphics glitch in Clover we use second stage IOGraphicsFamily patch to resolve the issue and it works well. but is there any option in Ozmosis ?

 

Also I am using Clover for more than a year with VBOXHfs.efi and now upgraded to El Capitan still no issues and I haven't replaced it with HFSPlus.efi so can we use Ozmosis with Vboxhfs.efi instead of Hfsplus.efi? sorry if this is a stupid question..as I haven't had much idea about both functionalities..

 

Thak you

Link to comment
Share on other sites

Hi

 

I have couple of questions, I hope someone can help or give some suggestions...

Does Ozmosis able to do kext patching? for example for HD4600 graphics glitch in Clover we use second stage IOGraphicsFamily patch to resolve the issue and it works well. but is there any option in Ozmosis ?

 

Also I am using Clover for more than a year with VBOXHfs.efi and now upgraded to El Capitan still no issues and I haven't replaced it with HFSPlus.efi so can we use Ozmosis with Vboxhfs.efi instead of Hfsplus.efi? sorry if this is a stupid question..as I haven't had much idea about both functionalities..

 

Thak you

 

1. No kext patching yet.

2. Just use HFSPlus. Weird to keep using the old if the 'new' is faster. ;)

  • Like 1
Link to comment
Share on other sites

Thank you Download-Fritz for instant reply,

Ok so no kext patching as I need to use patched kexts if this is the case.. also I am using AppleALC.kext in Clover/Kexts but if we use it in Ozmosis I can add to the same to Bios but , still this kext require Audio id to be injected via plist so how that will work in Ozmosis?

 

Thanks

Link to comment
Share on other sites

Ok I found toledo SSDT edit for Audio layout id 1 given below:

DefinitionBlock ("iASLAZDiXe.aml", "SSDT", 1, "toleda", "amihdas1", 0x00003000)
{
    External (\_SB_.PCI0, DeviceObj)
    External (\_SB_.PCI0.HDAS._ADR)

    Scope (\_SB.PCI0)
    {
        Name (HDAS._STA, Zero)
        Device (HDEF)
        {
            Name (_ADR, 0x001F0003)
            Method (_INI, 0, NotSerialized)
            {
                Store (Zero, \_SB.PCI0.HDAS._ADR)
            }

            Method (_DSM, 4, NotSerialized)
            {
                If (LEqual (Arg2, Zero))
                {
                    Return (Buffer (One)
                    {
                        0x03
                    })
                }

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

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

                    "PinConfigurations", 
                    Buffer (Zero) {}
                })
            }
        }
    }

    Store ("ssdt-ami_100_hdas-hdef_audio_to_hdef-1_v1.0 github.com/toleda", Debug)
}

If I add this code to bios then will audio id 1 inject work?

 

Thank you

Link to comment
Share on other sites

Do you guys are having problem with the last El Capitan update 10.11.04?

 

Here it's freezing, after boot to install update with OZMOSIS 167X-MASS.

 

Already deactivated Nvidia driver, cleared NVRAM with Option+Command+P+R.

Link to comment
Share on other sites

Do you guys are having problem with the last El Capitan update 10.11.04?

 

Here it's freezing, after boot to install update with OZMOSIS 167X-MASS.

 

Already deactivated Nvidia driver, cleared NVRAM with Option+Command+P+R.

Try with SIP disabled

  • Like 1
Link to comment
Share on other sites

@DxF

./gfxutil -i xml -o hex "dev-prop.xml" "dev-prop.hex" && xxd -r -p "dev-prop.hex" > "dev-prop.bin"
  1. Regular efi strings hex format #1 & #2
  2. Just guess, EBL instruction reformat using xxd #3 (scrolldown)
  3. Refer to "Theme.bin", it just plain text

 

Tried all (plain xml / hex strings / xxd) & failed haha (((

Link to comment
Share on other sites

@DxF

./gfxutil -i xml -o hex "dev-prop.xml" "dev-prop.hex" && xxd -r -p "dev-prop.hex" > "dev-prop.bin"
  1. Regular efi strings hex format #1 & #2
  2. Just guess, EBL instruction reformat using xxd #3 (scrolldown)
  3. Refer to "Theme.bin", it just plaint text

 

Tried all (plain xml / hex strings / xxd) & failed haha (((

 

isn't .hex already supposed to be the .bin you look for?

Also, why use the dev-props file anyhow? Imo its very static structure is quite dated...

 

EDIT: Sorry, the .hex file is the hex as strings... forget the first sentence. :)

Link to comment
Share on other sites

Can any one help me please?

 

In my previous post I have mentioned about  toleda HDEF DSDT edit and add the same to Bios for injecting Audio id 1. by only adding above DSDT edit to bios will work or do I need to extract DSDT of my board then patch it with toleda code(I am not sure) then add to bios?

 

Any ideas?

Link to comment
Share on other sites

It is related to Oz only. in your previous post you mentioned about DSDT patch for injecting Audio id 1 /enabling Audio. so my questions is how should I do DSDT patching ? can I use below toleda DSDT patch code for Audio id 1 and add to bios? will it inject Audio id 1?

DefinitionBlock ("iASLAZDiXe.aml", "SSDT", 1, "toleda", "amihdas1", 0x00003000)
{
    External (\_SB_.PCI0, DeviceObj)
    External (\_SB_.PCI0.HDAS._ADR)

    Scope (\_SB.PCI0)
    {
        Name (HDAS._STA, Zero)
        Device (HDEF)
        {
            Name (_ADR, 0x001F0003)
            Method (_INI, 0, NotSerialized)
            {
                Store (Zero, \_SB.PCI0.HDAS._ADR)
            }

            Method (_DSM, 4, NotSerialized)
            {
                If (LEqual (Arg2, Zero))
                {
                    Return (Buffer (One)
                    {
                        0x03
                    })
                }

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

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

                    "PinConfigurations", 
                    Buffer (Zero) {}
                })
            }
        }
    }

    Store ("ssdt-ami_100_hdas-hdef_audio_to_hdef-1_v1.0 github.com/toleda", Debug)
}
Link to comment
Share on other sites

×
×
  • Create New...