Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

pmcnano
pmcnano
Posted
Posted

Nope, just for personal use & not to redistribute it.. I did a mistakes for sharing here without proper licenses. Enjoy brother 

 

Well thanks!

 

PS. I'm still unable to load AppleALC from BIOS. I mean, it loads but it just doesn't work

post-120132-0-13145500-1465991840_thumb.png

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

@pmcnano seem theres new pattern must to zeroout to get codecs working. Goto their official thread & follow the link. Also they have new beta for 10.12 to test, I didnt try. Old version just give me hang right before login screen.

 

@bs0d yes & thanks for the heartattack, maybe other friends here will re share it after done testing. Current patch supposed to work with prev ver. But I cant test it. My 10.11 was tampered by this garbage.

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

@cecekpawon not sure I'm following. By "new pattern" you mean for Sierra? It has never worked for me from bios. I have it in /EFI and works perfectly. Inject it to bios and I got nothing. I already used your script to integrate the plists etc.

 

Btw @cecekpawon if you want a suggestion, It would be a nice feature asking which GUID # you want for the converted FFS. I was going to use it to create my AppleALC ffs but I was already using the GUID #. I went ahead and edited the old script (Pavo's) and created it.

 

@crusher I will try it, I don't understand what would the difference be though. Thanks

06:128 00:001 Injecting FakeSMC "Driver-39E6000" (0x2961E000) 118644 bytes
06:128 00:000 Injecting CPUSensors "Driver-3A03000" (0x2963B000) 46688 bytes
06:129 00:001 Injecting Super I/O Family "Driver-3A0F000" (0x29647000) 94460 bytes
06:131 00:001 Injecting GPUSensors "Driver-3A27000" (0x2965F000) 137976 bytes
06:132 00:001 Injecting IntelMausiEthernet.Rev-2.1.0d0 "Driver-3A49000" (0x29681000) 163953 bytes
06:133 00:000 Injecting FakePCIID.Rev-1.2.3 "Driver-3A72000" (0x296AA000) 53335 bytes
06:133 00:000 Injecting FakePCIID_XHCIMux.Rev-1.2.3 "Driver-3A80000" (0x296B8000) 50405 bytes
06:134 00:001 Injecting AppleALC.Rev-1.0.12 "Driver-3A8D000" (0x296C5000) 397153 bytes
Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

@pmcnano Would like retake alook but im on phone right now far from my ps2 keyboard so tomorrow will do. Im not sure about "GUID #" I just follow the old guide, downloading last example from THEKING & use mmtool as a weapon, uefitool sometimes from hack.
Since you have: Injecting ... (0x...) yes I believe it run from rom. And if you prev able to run this kext & got sound working from EFI, I dont think you need new pattern what I mentioned before. It should just go. Ex for old pattern for my alc892:
Find: 8319D411 (in 10.12 become: 8A19D411)
Replace: 00000000
@mathew2005 for now please do pm someone buddy, not with my pc right now, sorry..

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

Is there any way to inject an audio ID using Oz? I can't figure out how to use AppleALC

 

I use ssdt to inject audio prop

 

 

 

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

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

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

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

 

 

Link to comment
Share on other sites
Tusskan
Tusskan
Posted
Posted

After do some more tests with permissions, I decide to republish this patched ver ov Oz (1.03.167X-MASS RELEASE) which allowed me to boot with injected kexts (from rom / efi folder like usual) into 10.11 installer & 10.12 installed. Please use with caution until new official ver released.

Out of curiosity, How did you manage to debug it? And did you patch it.?

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

Quick question:

 

With 1479, I didn't need the following section in my Defaults.plist

    <key>BootEntryTemplate</key>
    <string>$label</string>
    <key>DarwinDiskTemplate</key>
    <string>$label</string>
    <key>DarwinRecoveryDiskTemplate</key>
    <string>$label ($platform.$major.$minor)</string>
    <key>DarwinCoreStorageTemplate</key>
    <string>$label</string>
    <key>AndroidDiskTemplate</key>
    <string>$label</string>
    <key>AndroidDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string>
    <key>LinuxDiskTemplate</key>
    <string>$label $build</string>
    <key>LinuxDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>
    <key>LinuxRescueDiskTemplate</key>
    <string>$label Rescue</string>
    <key>LinuxRescueOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>

Yesterday, I updated to 167xMASS and I had a moment of panic reusing my old Defaults.plist: no OSX volumes present at all in the boot menu... :wacko: until I extracted and modified the OzmosisDefaults in the modded ROM I use (pre-made for my board on the German forum).

 

Any explanations...?

 

Thanks,

 

Patrice

Link to comment
Share on other sites
bs0d
bs0d
Posted
Posted

Quick question:

 

With 1479, I didn't need the following section in my Defaults.plist

    <key>BootEntryTemplate</key>
    <string>$label</string>
    <key>DarwinDiskTemplate</key>
    <string>$label</string>
    <key>DarwinRecoveryDiskTemplate</key>
    <string>$label ($platform.$major.$minor)</string>
    <key>DarwinCoreStorageTemplate</key>
    <string>$label</string>
    <key>AndroidDiskTemplate</key>
    <string>$label</string>
    <key>AndroidDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string>
    <key>LinuxDiskTemplate</key>
    <string>$label $build</string>
    <key>LinuxDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>
    <key>LinuxRescueDiskTemplate</key>
    <string>$label Rescue</string>
    <key>LinuxRescueOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>

Yesterday, I updated to 167xMASS and I had a moment of panic reusing my old Defaults.plist: no OSX volumes present at all in the boot menu... :wacko: until I extracted and modified the OzmosisDefaults in the modded ROM I use (pre-made for my board on the German forum).

 

Any explanations...?

 

Thanks,

 

Patrice

 

the price of progress, giving the user more control over the boot options produced for various operating systems it supports.

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

the price of progress, giving the user more control over the boot options produced for various operating systems it supports.

Thanks... Confirming what I've found in the meantime.

 

Read this on Hackintosh-Forum.de about someone not seeing his Fusion Drive (sorry Google Translation):

 

"Can you please the currently used Defaults.plist upload times and / or check as the entry under <key> Defaults: 1F8E0C02-58A9-4E34-AE22-2B63745FA101 </ key> looks like? From OZ1669 should look as follows:

source

      <Key> Defaults: 1F8E0C02-58A9-4E34-AE22-2B63745FA101 </ key> 
      <Dict> 
      <Key> AndroidDiskOptionTemplate </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ androidboot.hardware = android_x86 ro SRC = $ path </ string> 
      <Key> AndroidDiskTemplate </ key> 
      <String> $ label </ string> 
      <Key> Boot Entry Template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Core Storage Template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Disk template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Recovery Disk template </ key> 
      <String> $ label ($ platform. $ Major. $ Minor) </ string> 
      <Key> Linux Disk option template </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ ro </ string> 
      <Key> Linux disk template </ key> 
      <String> $ label $ build </ string> 
      <Key> Linux Rescue Disk template </ key> 
      <String> $ label Rescue </ string> 
      <Key> Linux Rescue option template </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ ro </ string> 
      </ Dict>

If that looks different to you or entries in the templates are missing then this would explain why the fusion drive volume group does not appear there."

Link to comment
Share on other sites
MattsCreative
MattsCreative
Posted
Posted

After do some more tests with permissions, I decide to republish this patched ver ov Oz (1.03.167X-MASS RELEASE) which allowed me to boot with injected kexts (from rom / efi folder like usual) into 10.11 installer & 10.12 installed. Please use with caution until new official ver released.

great job 

Link to comment
Share on other sites
davidm71
davidm71
Posted
Posted

Can u guys in the know summerize what discoveries have been made thus far? I read that there were issues with OZ resolving proper boot order when a Windows partition is present. Has this been fixed?

 

Thank you very much,

 

Respect.

Link to comment
Share on other sites
bs0d
bs0d
Posted
Posted

Thanks... Confirming what I've found in the meantime.

 

Read this on Hackintosh-Forum.de about someone not seeing his Fusion Drive (sorry Google Translation):

 

"Can you please the currently used Defaults.plist upload times and / or check as the entry under <key> Defaults: 1F8E0C02-58A9-4E34-AE22-2B63745FA101 </ key> looks like? From OZ1669 should look as follows:

source

      <Key> Defaults: 1F8E0C02-58A9-4E34-AE22-2B63745FA101 </ key> 
      <Dict> 
      <Key> AndroidDiskOptionTemplate </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ androidboot.hardware = android_x86 ro SRC = $ path </ string> 
      <Key> AndroidDiskTemplate </ key> 
      <String> $ label </ string> 
      <Key> Boot Entry Template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Core Storage Template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Disk template </ key> 
      <String> $ label </ string> 
      <Key> Darwin Recovery Disk template </ key> 
      <String> $ label ($ platform. $ Major. $ Minor) </ string> 
      <Key> Linux Disk option template </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ ro </ string> 
      <Key> Linux disk template </ key> 
      <String> $ label $ build </ string> 
      <Key> Linux Rescue Disk template </ key> 
      <String> $ label Rescue </ string> 
      <Key> Linux Rescue option template </ key> 
      <String> initrd = $ initfs root = UUID = uuid $ ro </ string> 
      </ Dict>

If that looks different to you or entries in the templates are missing then this would explain why the fusion drive volume group does not appear there."

ok this is bad .. use lower case for the elements such as <String> should be <string> and <Key> should be <key> ... also </ string> should be </string> and </ key> should be </key> etc etc

Link to comment
Share on other sites
brousseau6933
brousseau6933
Posted
Posted

ok this is bad .. use lower case for the elements such as <String> should be <string> and <Key> should be <key> ... also </ string> should be </string> and </ key> should be </key> etc etc

Sorry, Google Translation is the culprit. Should have been:

Source Code

    <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
    	<dict>
    		<key>AndroidDiskOptionTemplate</key>
    		<string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string>
    		<key>AndroidDiskTemplate</key>
    		<string>$label</string>
    		<key>BootEntryTemplate</key>
    		<string>$label</string>
    		<key>DarwinCoreStorageTemplate</key>
    		<string>$label</string>
    		<key>DarwinDiskTemplate</key>
    		<string>$label</string>
    		<key>DarwinRecoveryDiskTemplate</key>
    		<string>$label ($platform.$major.$minor)</string>
    		<key>LinuxDiskOptionTemplate</key>
    		<string>initrd=$initfs root=UUID=$uuid ro</string>
    		<key>LinuxDiskTemplate</key>
    		<string>$label $build</string>
    		<key>LinuxRescueDiskTemplate</key>
    		<string>$label Rescue</string>
    		<key>LinuxRescueOptionTemplate</key>
    		<string>initrd=$initfs root=UUID=$uuid ro</string>
    	</dict>

Can u guys in the know summerize what discoveries have been made thus far? I read that there were issues with OZ resolving proper boot order when a Windows partition is present. Has this been fixed?

 

Thank you very much,

 

Respect.

When I boot on my Windows 10 drive, the boot order of my other OSX USB and recovery partitions got messed up yes...

 

But, my main Yosemite (also first SATA connection) remains first and default.

 

For mixed OSX/Windows drives, I don't know...

Link to comment
Share on other sites
BALDY_MAN
BALDY_MAN
Posted
Posted

Hi all 

i would be greatful if someone could be so kind as to  take a look at my modified  bios for me as it is my first attempt at doing it

and ive be out of the hackintosh building for a while

                                                                                Best Regards

                                                                                                   Baldyman

Ozmosis Sabertooth x79-ASUS 4801. CAP folder.zip

Link to comment
Share on other sites
xrnc
xrnc
Posted
Posted

In following the guide in the OP of this thread in an attempt to create a bios for an Asus H97M-E/CSM I run into a consistent 2k oversize.

 

It seems that people generating custom bios for folks on the german hackintosh-forum.de site are running into the same thing, the one I downloaded for this board from crusher there is showing the same issue.

 

The factory bios is 8192 kb, after putting everything into MMTool per the guide here, deleting FileSystem and compressing CORE_DXE, MMTool spits out a bios file that is 8194kb.

 

I have a AFUDOS capable of flashing the board with /GAN, just can't generate a properly sized bios.

 

Am I missing something obvious?

 

Here's the link to the current factory bios...

 

http://dlcdnet.asus.com/pub/ASUS/mb/LGA1150/H97M-E/H97M-E-ASUS-2702.zip

 

Not sure if it helps, but I took the original and the one generated by crusher, also assumingly with MMTool since it came out the same size as mine, and diff'd them, but don't know what I might be looking for...

 

http://pastebin.com/RKQYyLfy

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