Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

Hello, buddy,
First of all, Hardware is:
CPU: INTEL I7-4790
Motherboard: Gigabyte Z97N-WIFI
Graphics card: AMD WX5100
BOOTLOADER: Ozmosis
SMBIOS: iMac15.1
The problem is: when the HD4600 is turned on,although use 32 Memory and 128 DVMT in Bios settings, it can't boot 10.14, it is stuck in the Apple logo, no progress bar. When the HD4600 is turned off, the WX5100 can boot 10.14 normally.
How should I do?
THX!

Remove completely the WX5100, then boot to OS X with apfsdriverloader in the rom, and try to add bcfg boot entry to your installed drive


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

50 minutes ago, ammoune78 said:


Remove completely the WX5100, then boot to OS X with apfsdriverloader in the rom, and try to add bcfg boot entry to your installed drive


Sent from my iPhone using Tapatalk

Hey,thx for reply!

Unfortunately,I tried,it's useless,forgot to tell u,there is apfsdriverloader in my rom,

and it can boot to 10.13.6 with apfs and almost everything works normal and smooth,

only boot to 10.14,can not turn on the HD4600,unless turn off it in bios settings!

I think it may not be caused by wx5100,

Do U use DSDT,SSDT or some kexts for HD4600?and what's ur ig-platformid?

Can u show these for me?

Thx!

Edited by taoarch
Link to comment
Share on other sites

I did some testing with latest Lilu + AppleALC which start to ignore my "layout-id" and forced me to inject "alc-layout-id" property to getting back my sound. Later I know that latest AppleALC doesnt like and treat us like real mac with overridden 'firmware-vendor' by Oz with Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102->FirmwareVendor='Apple'. Changing / deleting those value fix my problem.

  • Like 3
  • Thanks 2
Link to comment
Share on other sites

On 8/14/2018 at 5:34 PM, taoarch said:

Hey,thx for reply!

Unfortunately,I tried,it's useless,forgot to tell u,there is apfsdriverloader in my rom,

and it can boot to 10.13.6 with apfs and almost everything works normal and smooth,

only boot to 10.14,can not turn on the HD4600,unless turn off it in bios settings!

I think it may not be caused by wx5100,

Do U use DSDT,SSDT or some kexts for HD4600?and what's ur ig-platformid?

Can u show these for me?

Thx!

 

ig-platform-id in OzmosisDefaults is:

Quote

		<key>AAPL,ig-platform-id</key>
		<integer>220332035</integer>

 

You can now use the WhateverGreen kext, if you can't boot to Mojave, and nothing magical here, in SSDT/DSDT, just use the HD4600 patch. But, if without the WX5100 card installed, it's a problem!

Link to comment
Share on other sites

China's d1ves has developed doz can be compatible with 1151, I already in B250, Z270, Z370 can work, at present in Asrock, Gigabyte, Asus run very well, but this doz firmware requires KEY.PO key authorization, Create Series.po file in Efi:/efi folder, brush into Doz firmware to start get Series.po, this file is authorization file, need to use SERIES.PO to convert Key.po, then put Efi:/efi, restart activation doz,Unfortunately, each PC motherboard must be a separate key, otherwise it will not work

212598558_2018-08-176_19_39.png.4d05087041d003a20c404bd7f1f06348.png1883934471_2018-08-176_20_29.thumb.png.bc374c425c24ccdfdfe1256f3b5caad3.png

key.po

series.po

  • Like 1
Link to comment
Share on other sites

oh,it's archived,if you want to use it,sent your key to me with email or put here,i will give the key for you....

 

To be honest, compatibility is not very good, practicability is not very good, operability is not very good, personal entertainment works, difficult to ascend the hall of elegance.

 

good luck

 

:)

 

god bless you

  • Like 2
Link to comment
Share on other sites

x_0 thats dangerous question. OpenOz is stand for OpenCore & Ozmosis (have tried OxCxOxZ, Ozopen, etc which is bad), assumed they are both had some identical keys to store the datas, and nothing more, for SEO things you know. If no, then nothing to be destroy with this app. Welcome back @STLVNUB (your nick is very hard to mention man).

Link to comment
Share on other sites

Id like to help but cant with details, tired sorry. Latest workaround published by TypeThree is to disable Oz internal patches and use kernextpatcher with clover patch datas. If you know wheres the correct address to applying the patches, you may use kernextpatcher as a helper there, but seems you are trying to avoid it. Oz & Clover had some slightly different way to applying patches, but with same results.

Link to comment
Share on other sites

ozmosis xmax with kernel patches work for me with 10.13.6 on apfs

but 10.14 doesn't start

are this the correct patches?


 

    <key>Comment</key>
    <string>KbepMoja-EXT</string>
    <key>Disabled</key>
    <false/>
    <key>Find</key>
    <data>6K8AAADrBeg=</data>
    <key>MatchOS</key>
    <string>10.14</string>
    <key>Replace</key>
    <data>6K8AAACQkOg=</data>



    <key>Comment</key>
    <string>KbepHSMoja-SIP</string>
    <key>Disabled</key>
    <false/>
    <key>Find</key>
    <data>w0iF23RpSIsDSInf/1AoSA==</data>
    <key>MatchOS</key>
    <string>10.13,10.14</string>
    <key>Replace</key>
    <data>w0iF2+sSSIsDSInf/1AoSA==</data>

 

Link to comment
Share on other sites

For me it works just normal... I can't say what the problem is and why Mojave refuses to boot for some people when iGPU and dedicated GPU are activated.

 

I had that problem in the beginning and the only way I could start Mojave with both GPUs, was when I had Mojave as the first boot priority, entered the BIOS and exited it again without saving (the behaviour doesn't make sence to me).

Then I reset my BIOS to defaults and ever since that day I can start Mojave completely normal with both GPUs activated.

 

Maybe somebody has a clue what this might be about...

Edited by TypeThree
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

Hi

any way to stop Oz from injecting this device-properties?

 

<dict>
    <key>AFGLowPowerState</key>
    <data>AQAAAA==</data>
    <key>MaximumBootBeepVolume</key>
    <string>s</string>
    <key>PinConfigurations</key>
    <data>MEERAWARAQEQkYEBIJGgkEBAIQFQEUUB</data>
    <key>hda-gfx</key>
    <data>b25ib2FyZC0xAA==</data>
    <key>layout-id</key>
    <data>AgAAAA==</data>
    <key>platformFamily</key>
    <data>AA==</data>
</dict>

 

Link to comment
Share on other sites

16 hours ago, WinstonAce said:

Hi

any way to stop Oz from injecting this device-properties?

 


<dict>
    <key>AFGLowPowerState</key>
    <data>AQAAAA==</data>
    <key>MaximumBootBeepVolume</key>
    <string>s</string>
    <key>PinConfigurations</key>
    <data>MEERAWARAQEQkYEBIJGgkEBAIQFQEUUB</data>
    <key>hda-gfx</key>
    <data>b25ib2FyZC0xAA==</data>
    <key>layout-id</key>
    <data>AgAAAA==</data>
    <key>platformFamily</key>
    <data>AA==</data>
</dict>

 

Register these properties in DSDT

SSDT-1.aml.zip

Edited by korlione2009
Link to comment
Share on other sites

On 8/26/2018 at 5:50 AM, TypeThree said:

For me it works just normal... I can't say what the problem is and why Mojave refuses to boot for some people when iGPU and dedicated GPU are activated.

 

I had that problem in the beginning and the only way I could start Mojave with both GPUs, was when I had Mojave as the first boot priority, entered the BIOS and exited it again without saving (the behaviour doesn't make sence to me).

Then I reset my BIOS to defaults and ever since that day I can start Mojave completely normal with both GPUs activated.

 

Maybe somebody has a clue what this might be about...

This is a way to solve hd4600 which could not boot Mojave under HD4600,but not perfect for me!

First,I must set 32m&128m in bios settings.

Then,I must enter the BIOS and exit it without saving everytime.

Last,every boot or reboot,lt will panic with usb,I have patch in kernextpatcher,and in High Sierra,everything is ok!

I don't know why...

Edited by taoarch
  • Thanks 1
Link to comment
Share on other sites

This is a way to solve hd4600 which could not boot Mojave under HD4600,but not perfect for me!
First,I must set 32m&128m in bios settings.
Then,I must enter the BIOS and exit it without saving everytime.
Last,every boot or reboot,lt will panic with usb,I have patch in kernextpatcher,and in High Sierra,everything is ok!
I don't know why...

I think a patch is needed here, to solve this problem. I did a request for it, on Mojave topic, but still no answer, especially when clover do the job, sadly Oz need that patch!


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

2 hours ago, ammoune78 said:


I think a patch is needed here, to solve this problem. I did a request for it, on Mojave topic, but still no answer, especially when clover do the job, sadly Oz need that patch!


Sent from my iPhone using Tapatalk

Can you show the topic for me? I can't find either!THX

Edited by taoarch
Link to comment
Share on other sites

×
×
  • Create New...