Ozmosis

[cecekpawon]

Ozmosis ppl,

 

Here quick test files for BootChime project https://github.com/Goldfish64/AudioPkg to play with.

 

Kudos

Chime.zip

[obus]

bump

Edited December 24, 2018 by obus

[elviejo]

 

Ozmosis ppl,

 

Here quick test files for BootChime project https://github.com/Goldfish64/AudioPkg to play with.

 

Kudos

Chime.zip

How to integrate it on ROM?.

[cecekpawon]

I guess you will need AudioDxe.ffs and BootChimeDxe.ffs, which not provided by developer yet.

Go extract file in attachment to test (warning: i have not test my self, please use at your own risk).

 

As I mentioned above, BootChimeDxe will have super size to embed, since they have default sound inside binary.

And Im too lazy to reapply my previously diffs.

 

[!] Also experienced boot hang with my Aptiofix with latest commit, could be caused by overridden ExitBS in BootChimeDxe, not sure here.

 

* I have made a new driver to work with AudioDxe here which similar to BootChimeDxe, I think ;)))

 

FIRMWARE.Fv.zip

[poof86]

I'm not able to install Mojave while using my i7-4790k HD4600 iGPU. I have WhateverGreen and Lilu with my XMAX Ozmosis, but still stuck at the apple logo when I start the Mojave installation from USB. Using my High Sierra installation works fine still even after the BIOS Flash Update

 

Here are a few questions that I can't seem to find the answers to, maybe you pro's can help me out:

 

- Is HD4600 supported by Mojave Hackintosh? Or do I need to wait for a fix?

- In what cases should I Enable "DisableIntelInjection" and/or "DisableNvidaInjection"? (I normally have a GTX 960 as secondary DGPU with webdrivers and my iGPU as primary)

- I'm using SMBIOS iMac15,1 that matches my CPU, Does this mean power management is covered natively?

 

And the most important question before I try installing Mojave again:

 

- Would it work to install Mojave using a DGPU (and disabling iGPU) and after installation go back to my iGPU?

 

Any help is super appreciated

[ammoune78]

On 1/10/2019 at 2:44 AM, poof86 said:

I'm not able to install Mojave while using my i7-4790k HD4600 iGPU. I have WhateverGreen and Lilu with my XMAX Ozmosis, but still stuck at the apple logo when I start the Mojave installation from USB. Using my High Sierra installation works fine still even after the BIOS Flash Update

 

Here are a few questions that I can't seem to find the answers to, maybe you pro's can help me out:

 

- Is HD4600 supported by Mojave Hackintosh? Or do I need to wait for a fix?

- In what cases should I Enable "DisableIntelInjection" and/or "DisableNvidaInjection"? (I normally have a GTX 960 as secondary DGPU with webdrivers and my iGPU as primary)

- I'm using SMBIOS iMac15,1 that matches my CPU, Does this mean power management is covered natively?

 

And the most important question before I try installing Mojave again:

 

- Would it work to install Mojave using a DGPU (and disabling iGPU) and after installation go back to my iGPU?

 

Any help is super appreciated

 

 

On 8/25/2018 at 10:50 PM, 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...

 

 

 

[firefly_can_fly]

Hey guy, glad to be back. 

Does anyone use AMD cards like: 

MSI Radeon RX 580 GAMING X 4G

Sapphire PCI-Ex Radeon RX 580 Nitro+ 4GB GDDR5 (256bit) (1411/7000) (DVI, 2 x HDMI, 2 x DisplayPort) (11265-07-20G)

 

With Oz? 

Currently, I have gtx 1050ti, so I guess this would be a good GPU boost up.

[ammoune78]

2 hours ago, firefly_can_fly said:

Hey guy, glad to be back. 

Does anyone use AMD cards like: 

MSI Radeon RX 580 GAMING X 4G

Sapphire PCI-Ex Radeon RX 580 Nitro+ 4GB GDDR5 (256bit) (1411/7000) (DVI, 2 x HDMI, 2 x DisplayPort) (11265-07-20G)

 

With Oz? 

Currently, I have gtx 1050ti, so I guess this would be a good GPU boost up.

 

It will work Out Of The Box 

[BALDY_MAN]

HI ALL. 

          I have modified a copy of the Z97PD3.F8b-XMAX.rom. by adding the KernextPatcher_XMAX.plist to the bois .

          and i have managed to update to 10.14.4 Beta (18E174f) i seems to work ok. except it boots up a bit slow. some usb Ports and HDMI not working   sleep will restart

          could someone be so kind and check my Send me file please .

Send me Grahams-iMac.zip

[TypeThree]

Thank for your feedback! Did you try to use this Plist for Kext-Injection with 10.14.4? https://www.hackintosh-forum.de/forum/thread/37862-macos-mojave-ozmosis-beta-oz167x-xmax/?postID=484508#post484508

Edited February 4, 2019 by TypeThree

[BALDY_MAN]

heres a copy of the bios i moddified. i havent time to try and recreate what i did at the moment. the bios and file are from the german site. im now running.10.14.4 Beta (18E184e)KernextPatcher Log.txt file from efi folder

modded bios folder.zip

KenextPatcherLog folder.zip

CHANGES: IM NO LONGER USING THIS BIOS

as it was to problematic for me IE couldnt use apps and programs i have reverted back to past bios and 10.14.3

Edited February 6, 2019 by BALDY_MAN
added file

[TypeThree]

The Log looks good, thanks for your testing!

[Morc]

Hello guys! I am a bit interested again after some time in Ozmosis. Do i have to build it myself or someone will send me a modded for my Z97-HD3? And are there some things changed from the time I was experimenting with it last time(november 2016)? I would be happy if i was not needed to reinstall macOS and could use my existing macOS(10.13) installation.

[BALDY_MAN]

4 hours ago, Morc said:

Hello guys! I am a bit interested again after some time in Ozmosis. Do i have to build it myself or someone will send me a modded for my Z97-HD3? And are there some things changed from the time I was experimenting with it last time(november 2016)? I would be happy if i was not needed to reinstall macOS and could use my existing macOS(10.13) installation.

 you will need the app UEFITOOL  Motherboard bios. And (Kext2Ffs tool. to convert  kext you need to ffs file to add to your bios) and some 0mosis files the is a  how to on this site 

[witjojo]

Hello Guys,

 

I have installed the following Rom Z97D3H.F9-XMAX-ROM. Previously, I had Z97D3H.F9-Sierra-ROM.

However, I have removed DarBoot because Legacy Boot does not work with it. DarBoot makes the APFS entries (UEFI) in the boot menu, but probably removes the legacy entries. Maybe that can be changed? And I do not need OzmosisHFTheme, so I removed it too.

Sierra and Mojave work without problems. But Yosemite and El Capitan do not start anymore.

Whereby I assume that it is the KeenextPatcher. Because when I start Yosemite or El Capitan no KernextPatcherLog.txt file is created. At Sierra and Mojave, this is created, and the systems also start.

 

I copied the FakeSMC to S / L / E on Yosemite, changed rights and updated Kext Cache.

Yosemite starts now. But no sound and no network. Kext under /Efi/OZ/Darwin/Extensions/Common will not load.

The second NVME SSD is not recognized. The KextsToPatch entries are probably not loaded from the KernextPatcher.plist. Or the KernextPatcher.plist will not be executed at all. Does the KernextPatcher not work with the old systems?

Furthermore, I can not update from Mojave 10.14.2 to 10.14.3. He simply aborts the update and restarts.

 

 

Can someone please look at that and help me? Attached my files and Sorry for my bad English.

 

 

 

 

bootlog_Yosemite.txt

kextstat_Yosemite.txt

Defaults.plist

KernextPatcher.plist

Edited February 7, 2019 by witjojo

[cecekpawon]

Hello,

 

After you are able to boot into your Yosemite (by putting required kexts to S/L/E), still no KernextPatcherLog.txt on your \EFI folder? Have you tried another log option? https://github.com/cecekpawon/UEFTW/wiki/Howto-Driver-Log

 

I know its lame, KernextPatcher (or other driver by me) will delete your old log file and create a new one during boot. Which mean, once you are unable to reach the desktop and reset your pc, you will lost the last log file.

 

From your bootlog, latest Lilu will not allowed you to use their plugins when you set Firmware Vendor to "Apple". Try to change to "Eppla" or something else.

 

Maybe KernextPatcher are failed to read current booted system version. Try to rename "MatchOS" to "#MatchOS" to disable OS version filter.

 

** During testing please keep FakeSMC or other mandatory kexts on S/L/E to allow you to reach the desktop.

[witjojo]

Thanks cecekpawon - i will test this

[witjojo]

8 hours ago, cecekpawon said:

After you are able to boot into your Yosemite (by putting required kexts to S/L/E), still no KernextPatcherLog.txt on your \EFI folder? Have you tried another log option? https://github.com/cecekpawon/UEFTW/wiki/Howto-Driver-Log

 

I do not know exactly how to do that?

 

8 hours ago, cecekpawon said:

I know its lame, KernextPatcher (or other driver by me) will delete your old log file and create a new one during boot. Which mean, once you are unable to reach the desktop and reset your pc, you will lost the last log file.

 

I know about it. I then boot into Windows there I have access to the EFI partition. There is no KernextPatcherLog.txt

 

8 hours ago, cecekpawon said:

From your bootlog, latest Lilu will not allowed you to use their plugins when you set Firmware Vendor to "Apple". Try to change to "Eppla" or something else.

 

Yes maybe, but the other kext have to load, like AppleALC.kext, IntelMausiWthernet.kext, USBInjectAll.kext.

 

8 hours ago, cecekpawon said:

Maybe KernextPatcher are failed to read current booted system version. Try to rename "MatchOS" to "#MatchOS" to disable OS version filter.

 

I did that, but no change.

 

Perhaps the driver is incompatible with the older OS versions? And can something be changed there?

Or do you have any other ideas to test it out?

 

[cecekpawon]

@witjojo

 

*) Theres another options to save the log besides SaveLogToFile (SaveLogToDeviceTree / SaveLogToNvram) that you can get it later from OS.
**) The driver will create a log file on first ESP found, in case you have more than one ESP installed. Or on same directory as driver was loaded from disk.
***) You are correct (1), it will create a log file when you are booting to Windows.
****) You are correct (2), you still have another kexts (IntelMausi etc) to load from EFI folder. And from your log, Ozmosis already done injecting em all flawlessly. KernextPatcher seems failed to patch the kernel for you.
*****) Sadly, I dont another OS / machine to do some test for you, only me here with 1 and only pc + macos ver. Perhaps someone can help you. The thing that you might want to try is to load the driver from ESP (with bcfg / DBounce) instead of FV as comparison.

[uglyJoe]

This commit by vit9696 helps me out with Clover not injecting kext from efi.

I didn't test this with Ozmosis and KernextPatcher, but it should work like that:

		<dict>
			<key>Comment</key>
			<string>KBEMojaKxldUnmap</string>
			<key>Disabled</key>
			<false/>
			<key>Find</key>
			<data>AA+FsgEAAEg=</data>
			<key>MatchOS</key>
			<string>10.14</string>
			<key>Replace</key>
			<data>AJDpsgEAAEg=</data>
		</dict>

 

[uglyJoe]

Just did some tests and it seems to be working

 _____ _____ _____ _____ _____
|| U ||| E ||| F ||| T ||| W ||  https://github.com/cecekpawon/UEFTW
||___|||___|||___|||___|||___||  KernextPatcher (r#NaN | 2018-04-21 15:39:05)
|/___\|/___\|/___\|/___\|/___\|  On 2019-02-10 12:48:12

00:100 (00:100) | Running from: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,DF9F014D-E07B-4CAE-A8B2-0B80F9F06600,0x28,0x64000)EFI\BOOT\drivers_x64\KernextPatcher.efi
00:100 (00:000) | SelfDirPath = EFI\BOOT\drivers_x64
00:107 (00:007) | Get Plist from: NVRAM ... Not Found
00:107 (00:000) | Get Plist from: ESP: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,DF9F014D-E07B-4CAE-A8B2-0B80F9F06600,0x28,0x64000)EFI\BOOT\drivers_x64\KernextPatcher.plist ... Success
00:107 (00:000) | Parsing plist: ... Success
00:107 (00:000) | KernelToPatch: 8 requested
00:107 (00:000) |  - [00]: KbepMLMav-EXT | MatchOS: 10.8,10.9 | Len: 11 | C6E830000000EB084889DF -> C6E83000000090904889DF
00:107 (00:000) |  - [01]: KbepYosECSieHS-EXT | MatchOS: 10.10-10.13 | Len: 8 | E825000000EB05E8 -> E8250000009090E8
00:107 (00:000) |  - [02]: KbepMoja-EXT | MatchOS: 10.14 | Len: 8 | E8AF000000EB05E8 -> E8AF0000009090E8
00:107 (00:000) |  - [03]: KbepEC-SIP | MatchOS: 10.11 | Len: 16 | C34885DB7470488B034889DFFF502848 -> C34885DBEB12488B034889DFFF502848
00:107 (00:000) |  - [04]: KbepSie-SIP | MatchOS: 10.12 | Len: 16 | C34885DB7471488B034889DFFF502848 -> C34885DBEB12488B034889DFFF502848
00:107 (00:000) |  - [05]: KbepHSMoja-SIP | MatchOS: 10.13,10.14 | Len: 16 | C34885DB7469488B034889DFFF502848 -> C34885DBEB12488B034889DFFF502848
00:107 (00:000) |  - [06]: KbepMoja14.4-SIP | MatchOS: 10.14.4-10.14.6 | Len: 18 | 4885C0746C4889C3488B004889DFFF502848 -> 4885C0EB154889C3488B004889DFFF502848
00:107 (00:000) |  - [07]: KBEMojaKxldUnmap | MatchOS: 10.14 | Len: 8 | 000F85B201000048 -> 0090E9B201000048
05:347 (05:239) | AllocatePages: Got RelocBase (0x9BEF4000) + valid KernelData (0x9C0F4000)
05:580 (00:233) | Found Booter (OS: 10.12 | Ver: 361.220.1)
05:580 (00:000) | Booter Path: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,0E24B55C-AC2B-4CBF-AADF-3A13409A3DDD,0x64028,0x1D161920)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A7131E144323EF30A4144E40632F276A)\\System\Library\CoreServices\boot.efi
05:599 (00:019) | OSVersion: 10.14.3 | BuildVersion: 18D109
05:599 (00:000) | KernelAndKextPatcherInit: Start
05:599 (00:000) | ScreenInfo: Base 0xE0000000 Width 2560 Height 1440 RowBytes 0x2800
05:599 (00:000) | RelocBase = 9BEF4000
05:604 (00:004) | Found BootArgs at 0x9F405000
05:604 (00:000) | Found 64Bit kernel at 0x9C0F4000
05:606 (00:001) | Loaded Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 | VersionMajor: 18 | VersionMinor: 2 | Revision: 0
05:606 (00:000) | Cached: Yes
05:606 (00:000) | KernelAndKextPatcherInit: End
05:606 (00:000) | Filtering KernelPatches:
05:606 (00:000) |  - [00]: KbepMLMav-EXT | [MatchOS: 10.8,10.9 | MatchBuild: All] | Allowed: No
05:606 (00:000) |  - [01]: KbepYosECSieHS-EXT | [MatchOS: 10.10-10.13 | MatchBuild: All] | Allowed: No
05:606 (00:000) |  - [02]: KbepMoja-EXT | [MatchOS: 10.14 | MatchBuild: All] | Allowed: Yes
05:606 (00:000) |  - [03]: KbepEC-SIP | [MatchOS: 10.11 | MatchBuild: All] | Allowed: No
05:606 (00:000) |  - [04]: KbepSie-SIP | [MatchOS: 10.12 | MatchBuild: All] | Allowed: No
05:606 (00:000) |  - [05]: KbepHSMoja-SIP | [MatchOS: 10.13,10.14 | MatchBuild: All] | Allowed: Yes
05:606 (00:000) |  - [06]: KbepMoja14.4-SIP | [MatchOS: 10.14.4-10.14.6 | MatchBuild: All] | Allowed: No
05:606 (00:000) |  - [07]: KBEMojaKxldUnmap | [MatchOS: 10.14 | MatchBuild: All] | Allowed: Yes
05:606 (00:000) | Kernel patches to process: 3
05:606 (00:000) | KernelUserPatch: Start
05:606 (00:000) | - KbepMoja-EXT | Success: 1 replaces done
05:635 (00:029) | - KbepHSMoja-SIP | Success: 1 replaces done
05:663 (00:027) | - KBEMojaKxldUnmap | Success: 1 replaces done
05:711 (00:047) | KernelUserPatch: End
05:711 (00:000) | KernextPatcher: End

[uglyJoe]

I removed Ozmosis and all other stuff from my ROM and put it into the ESP.

For booting Mojave 10.14.3 with the Intel HD4600, I tested nearly all possible combinations with the different Aptio fixes.

• OsxAptioFixDrv don't need the '-norelocate' boot argument
• All other drivers need the '-norelocate' argument to work
• '-norelocate' doesn't work from nvram or defaults.plist (I added it as a boot option with refind)

With Clover AptioMemoryFix, OsxAptioFix3Drv and OsxAptioFix2Drv are working fine.

With Ozmosis and loaded by refind:

• AptioMemoryFix dosn't work
• OsxAptioFix3Drv dosn't work
• OsxAptioFix2Drv works with '-norelocate' but there is no boot.log, etc
• OsxAptioFixDrv works but only if it was written to the ESP after the ozmosis file.

To make sure that the drivers are loading in the correct order, 'cd' to efi\boot\drivers_x64 and type 'ls'.

OsxAptioFixDrv should list after Ozmosis, if not you can solve this with  'mv OsxAptioFixDrv.efi OsxAptioFixDrv.ife' and 'mv OsxAptioFixDrv.ife OsxAptioFixDrv.efi'

00:678 00:193 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,DF9F014D-E07B-4CAE-A8B2-0B80F9F06600,0x28,0x64000)/EFI\BOOT\drivers_x64\OsxAptioFixDrv-64.efi
01:672 00:993 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,0E24B55C-AC2B-4CBF-AADF-3A13409A3DDD,0x64028,0x1D161920)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A7131E144323EF30A4144E40632F276A)/\System\Library\CoreServices\boot.efi
01:672 00:000 Found Current Graphics Mode 0 2560 x 1440
01:724 00:051 Setting Graphics Mode 0 2560 x 1440
01:776 00:051 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
01:776 00:000 Using AcpiGeneratorMask 0x04 00000100 Darwin
01:777 00:001 Found DMI Anchor 0xDCF3D498 v2.7 Table Address 0xDCD5A018 Length 0x0C54 - Success
01:778 00:001 Updated DMI Anchor 0xD7BC1000 v2.7 Table Address 0xD7BC1020 Length 0x092E
01:778 00:000 Found 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args "igfxskipdp=3F-49ptal0" (12)
01:778 00:000 Found LoadedImage->LoadOptions "\\System\Library\CoreServices\boot.efi " (80)
01:778 00:000 LoadedImage->LoadOptions "\\System\Library\CoreServices\boot.efi  slide=0" (96)
01:778 00:000 Found Intel HD Graphics 4600 [8086:0412] PciRoot(0x0)/Pci(0x2,0x0)
01:778 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "model" = "Intel HD Graphics 4600" (22) - Success
01:778 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "built-in" = 00  (1) - Success
01:778 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "graphic-options" = 0C 00 00 00  (4) - Success
01:778 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "hda-gfx" = "onboard-1" (10) - Success
01:778 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "AAPL,ig-platform-id" = 03 00 22 0D  (4) - Success

Sadly, this isn't working from the ROM. So please: Make Ozmosis open source to make Ozmosis great again.

 

[cecekpawon]

Kudos,

 

1 hour ago, uglyJoe said:

01:778 00:000 Found 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args "igfxskipdp=3F-49ptal0" (12)

 

I think you have broken boot-args there that may causing Oz to read that string improperly, it should be "igfxskipdp=3" right? Have you tried to manually restoring those value with something like "igfxskipdp=3 -norelocate slide=N"?

[uglyJoe]

Yes, I am aware of this but I think, this is only a cosmetic error because at the end of the log I get:

02:195 00:006 Shrinking Kernel Memory Map 0xA80 (56) -> 0x690 (35)
02:196 00:000 Found BootArgs 0x9F471000 Version 0x2 Revision 0x0
02:196 00:000 CommandLine "slide=0 igfxskipdp=3"
02:196 00:000 EfiMode             0x40 (64) DebugMode 0x0 Flags 0x49 01001001 (RebootOnPanic | CSRActiveConfig | BlackTheme)

Edit:

I also tried to add '-norelocate' via nvram but it only works if I pass it directly to the boot.efi

I can see the difference because if the option kicks in, the progress bar appears a short time before it crashed.

If not, it's simply stuck at the Apple logo

:tidE

 

By the way, there you can see that Ozmosis adds the slide option by it self.

If I put a custom slide value, I got it twice in the CommandLine -> "slide=0 igfxskipdp=3 -norelocate slide=N".

For this reason I have done some tests with a patched Ozmosis that stops adding any options.

And to be sure, I added some custom entries to my refind.conf, where I added all arguments as an option passed to boot.efi.

 

Edited February 14, 2019 by uglyJoe

[uglyJoe]

And something I forget to ask:

 

nvram -p

OsxAptioFixDrv-RelocBase	%00%d0%8a%bc%00%00%00%00  
OsxAptioFixDrv-RelocBase	%00%90%8b%bc%00%00%00%00
OsxAptioFixDrv-RelocBase	%00`%90%bc%00%00%00%00
OsxAptioFixDrv-RelocBase	%00P%8d%bc%00%00%00%00
OsxAptioFixDrv-RelocBase	%00%b0%b0%bc%00%00%00%00

Why are these values different on each boot?

 

 

00:678 00:193 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,DF9F014D-E07B-4CAE-A8B2-0B80F9F06600,0x28,0x64000)/EFI\BOOT\drivers_x64\OsxAptioFixDrv-64.efi
01:672 00:993 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,0E24B55C-AC2B-4CBF-AADF-3A13409A3DDD,0x64028,0x1D161920)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A7131E144323EF30A4144E40632F276A)/\System\Library\CoreServices\boot.efi

If we could find a way to make this happens from inside the bios and in the same order - the HD4600 would be back to the game  

Edited February 14, 2019 by uglyJoe