Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

davidm71
davidm71
Posted
Posted

Hi,

 

Trying to get Voodoo to recognize my audio which is ALC898 on a Gigabyte Z87 UD5h board. On the last version of OZ I could put in HDEF audio dsdt edits and boot without issue no OZ stops on 'Credential Manager ....' error or KPs even with this  minimal DSDT:

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20100331
 *
 * Disassembly of iASLGdJz8M.aml, Sun Dec 13 23:07:49 2015
 *
 *
 * Original Table Header:
 *     Signature        "DSDT"
 *     Length           0x0000013F (319)
 *     Revision         0x02
 *     Checksum         0x03
 *     OEM ID           "ALASKA"
 *     OEM Table ID     "A M I"
 *     OEM Revision     0x000000F9 (249)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20100331 (537920305)
 */
DefinitionBlock ("iASLGdJz8M.aml", "DSDT", 2, "ALASKA", "A M I", 0x000000F9)
{
    Method (DTGP, 5, NotSerialized)
    {
        If (LEqual (Arg0, Buffer (0x10)
                {
                    /* 0000 */    0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, 
                    /* 0008 */    0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B
                }))
        {
            If (LEqual (Arg1, One))
            {
                If (LEqual (Arg2, Zero))
                {
                    Store (Buffer (One)
                        {
                            0x03
                        }, Arg4)
                    Return (One)
                }

                If (LEqual (Arg2, One))
                {
                    Return (One)
                }
            }
        }

        Store (Buffer (One)
            {
                0x00
            }, Arg4)
        Return (Zero)
    }

    Scope (_SB)
    {
        Device (PCI0)
        {
            Device (HDEF)
            {
                Name (_ADR, 0x001B0000)
                OperationRegion (HDAR, PCI_Config, 0x4C, 0x10)
                Field (HDAR, WordAcc, NoLock, Preserve)
                {
                    DCKA,   1, 
                            Offset (0x01), 
                    DCKM,   1, 
                        ,   6, 
                    DCKS,   1, 
                            Offset (0x08), 
                            Offset (0x09), 
                    PMEE,   1, 
                        ,   6, 
                    PMES,   1
                }

                Method (_PRW, 0, NotSerialized)
                {
                    Return (Package (0x02)
                    {
                        0x0D, 
                        0x05
                    })
                }

                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x08)
                        {
                            "codec-id", 
                            Buffer (0x04)
                            {
                                0x98, 0x08, 0xEC, 0x10
                            }, 

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

                            "device-type", 
                            Buffer (0x12)
                            {
                                "Realtek ALC898"
                            }, 

                            "PinConfigurations", 
                            Buffer (Zero) {}
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
        }
    }
}
Link to comment
Share on other sites
HBP
HBP
Posted
Posted

I have rechecked, and it is ANY legacy boot loaders, linux works fine, OS X works fine, but windows and all the other boot loaders of OS X (like clover) fail to get serialized and added to the list. I am stuck at 894M until this problem is resolved.

machine in question is:

GA-Z87X-UD5 TH, I7-4770K, 16 GIG DDR3, nvidia GTX 660, 250 GB SSD, 1500 gb sata (Fusion Drive)

 

HBP

ok, so when I update my OZ to 1669M a oddball thing happens. I lose the ability to boot from windows and Clover( my backup boot loader ) should OZ take a Dive.  what settings am I missing?  all the other settings seem Great and stable on my system in my Sig.

 

HBP

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

I have rechecked, and it is ANY legacy boot loaders, linux works fine, OS X works fine, but windows and all the other boot loaders of OS X (like clover) fail to get serialized and added to the list. I am stuck at 894M until this problem is resolved.

machine in question is:

GA-Z87X-UD5 TH, I7-4770K, 16 GIG DDR3, nvidia GTX 660, 250 GB SSD, 1500 gb sata (Fusion Drive)

 

HBP

Ozmosis is a UEFI Platform Manager,  if you want to boot your machine in legacy mode don't use/load it and use instead whatever, legacy "bootloader" you want. 

  • Like 1
Link to comment
Share on other sites
davidm71
davidm71
Posted
Posted

ok, so when I update my OZ to 1669M a oddball thing happens. I lose the ability to boot from windows and Clover( my backup boot loader ) should OZ take a Dive. what settings am I missing? all the other settings seem Great and stable on my system in my Sig.

 

HBP

I have the Z87 UD5H gigabyte board and no issues using clover 3330 as a backup bootloader and booting Windows. Make sure your OS X efi drive is on port 0 as ozmosis uses port 0 and make sure you don't have clover defaults file on that efi partition. If you want post your bios for a look..

Link to comment
Share on other sites
Aigors
Aigors
Posted
Posted

I don't either

Maybe he upograded from 10.10.2 to something else ..

Mine it's a fresh el capitan installation 

I thought it was my english knoweldge so poor to don't uderstand :D 

Link to comment
Share on other sites
Aigors
Aigors
Posted
Posted

I think is a typo, he meant 10.11.2

Stil don't uderstand, i'm from Italy, my english it's not so good to understand all the chat and way to say.

4400 support has been ended  after 10,10.2? 

Link to comment
Share on other sites
anowzic
anowzic
Posted
Posted

Hi folks! Do you know a reliable method to activate iMessage for 11.1.2/Ozmosis 1669m?

Actually, it was working out of the box, but I changed the SSDT to iMac 13,1 from MacPro 3,1, and it needs to be reactivated.

This is not related to Ozmosis, please do your research and if failing, post in the appropiate sub-forum.

Okay, the reason I'm asking it here, is that every single "how to fix iMessage" post over the Internet is for Clover or Chimera, but no mention of Ozmosis anywhere. Please be kind and dispell the darkness of my ignorance. Or at least help me to get going.
Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

I don't see how that relates to SSDT.

For Ozmosis, all you would need to do is edit the Defaults.plist

 

Hint: If all you did is change the Syetm Definition maybe you should change the serial # so it looks like an iMac serial #, same applies for ROM

  • Like 1
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted

Okay, the reason I'm asking it here, is that every single "how to fix iMessage" post over the Internet is for Clover or Chimera, but no mention of Ozmosis anywhere. Please be kind and dispell the darkness of my ignorance. Or at least help me to get going.

 

Hi,

 

You just need as said IronManJFF to change that in your Defaults.plist with valid values   :yes:

 

BaseBoardSerial in Oz Defaults.plist = MLB in RTVariables Clover Config.plist.

HardwareAddress in Oz Defaults.plist = ROM in RTVariables Clover Config.plist.

 

Fred

  • Like 2
Link to comment
Share on other sites
HBP
HBP
Posted
Posted

Ozmosis is a UEFI Platform Manager,  if you want to boot your machine in legacy mode don't use/load it and use instead whatever, legacy "bootloader" you want. 

 

thank you for your input, but there seems to be a misunderstanding as to what I am trying to explain, so I will take 2 pictures to explain it.

 

IMG_4319 is 894M   ozmosis

IMG_4320 is 1699M ozmosis

 

As you can see, All the other drives are not visible. no DVD drives, no windows partitions nothing, even though P1 is a windows 7 Pro disk.

 

It has it's UEFI entry like it's s'posed to right under the P0 device, and with 894M it works correctly with the fusion drive, with 1699M is does not.

 

this is the BIOS boot list, not the hermit crab guy, so it should include ALL boot options...

 

 

HBP

post-7000-0-34779000-1450128051_thumb.jpg

post-7000-0-78787600-1450128093_thumb.jpg

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

thank you for your input, but there seems to be a misunderstanding as to what I am trying to explain, so I will take 2 pictures to explain it.

 

As you can see, All the other drives are not visible. no DVD drives, no windows partitions nothing, even though P1 is a windows 7 Pro disk.

 

It has it's UEFI entry like it's s'posed to right under the P0 device, and with 894M it works correctly with the fusion drive, with 1699M is does not.

 

this is the BIOS boot list, not the hermit crab guy, so it should include ALL boot options...

 

 

HBP

1. In BIOS settings enable Legacy Boot.

2. READ THIS so you know what/how to setup your stuff especial this part:

 

DisableBootEntriesFilter || BOOLEAN || Disables filtering of firmware generated boot entries

By default Ozmosis remove all useless firmware boot entries c r a p.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...