Jump to content
xpamamadeus

Ozmosis

6,187 posts in this topic

Recommended Posts

Loading via bcfg it's not enough, driver should be initialized properly, "jumpstart like". This method is fast and simple.

 

 

Whats all this talk about "jumpstarting" the driver? The only issue I ever had was Ozmosis menu acting up on my system. Was that ever fixed?

 

Thanks

Share this post


Link to post
Share on other sites
Advertisement

Well, no it does not. It will load if added via EFI Shell and bcfg driver ADD but it won't connect to any device so even if the driver is loaded nothing will happen unless you connect it to a proper device (use the connect command to attach it to a given device) and that's where jumpstart comes into place. Jumpstart typically means that a driver will be started even if no devices are associated with it it will connect to suitable Devices if they are available. UEFI Drivers which are placed inside of the ROM will load if you fire up your Machine and they will load before the drives are initialised to make sure the Filesystems are recognised.  Drivers which are added via bcfg depend on a fully initialised and readable Disk to load them. In Case of the APFS Driver it will be loaded but as a Filesystem driver it won't attach to anything since the drives have already been scanned and attached...

 

If you boot into the (u)EFI Shell you might be able to attach the driver to a drive with the connect or reconnect Command both will trigger a scan of the device Tree which automatically will connect APFS but this thing has to be repeated every time you boot up your PC in order to connect APFS...

Share this post


Link to post
Share on other sites

Well, no it does not. It will load if added via EFI Shell and bcfg driver ADD but it won't connect to any device so even if the driver is loaded nothing will happen unless you connect it to a proper device (use the connect command to attach it to a given device) and that's where jumpstart comes into place. Jumpstart typically means that a driver will be started even if no devices are associated with it it will connect to suitable Devices if they are available. UEFI Drivers which are placed inside of the ROM will load if you fire up your Machine and they will load before the drives are initialised to make sure the Filesystems are recognised.  Drivers which are added via bcfg depend on a fully initialised and readable Disk to load them. In Case of the APFS Driver it will be loaded but as a Filesystem driver it won't attach to anything since the drives have already been scanned and attached...

 

If you boot into the (u)EFI Shell you might be able to attach the driver to a drive with the connect or reconnect Command both will trigger a scan of the device Tree which automatically will connect APFS but this thing has to be repeated every time you boot up your PC in order to connect APFS...

Very interesting. I think I understand. Your saying that by the time the apfs driver loads from firmware the drives or partitions have been assigned to another driver. In that case are there any uefi system calls or block io protocols that can be loaded in a custom driver that loads the apfs driver and auto connects the drive for you?

Share this post


Link to post
Share on other sites

Maybe the best way is to load both apfs & Ozmosis from disk with correct order:

bcfg driver add 0 apfs.efi "apfs"
bcfg driver add 1 Ozmosis.efi "Ozmosis"

Or create a driver to load apfs.efi from disk before Ozmosis, after screen fully initialized (optional to block text output while loading apfs.efi by overriding EFI_TEXT_STRING).
Please..

Share this post


Link to post
Share on other sites

in GM INSTALLTION:

EFIPayloads:

 - IM101.88Z.00CF.B00.1708080133
 - IM111.88Z.0037.B00.1708080241
 - IM112.88Z.005B.B00.1708080439
 - IM121.88Z.004D.B00.1708080012
 - IM131.88Z.010F.B00.1708080805
 - IM141.88Z.0123.B00.1708211404
 - IM142.88Z.0123.B00.1708211454
 - IM143.88Z.0123.B00.1708211454
 - IM144.88Z.0183.B00.1708080656
 - IM151.88Z.0211.B00.1708080656
 - IM161.88Z.0212.B00.1708080033
 - IM162.88Z.0212.B00.1708080033
 - IM171.88Z.0110.B00.1708080012
 - IM181.88Z.0151.B00.1708080034
 - IM183.88Z.0151.B00.1708080034
 - MB101.88Z.0154.B00.1708080122
 - MB61.88Z.00CB.B00.1708080203
 - MB71.88Z.003D.B00.1708080317
 - MB81.88Z.0168.B00.1708080033
 - MB91.88Z.0159.B00.1708080011
 - MBA31.88Z.0067.B00.1708080355
 - MBA41.88Z.007B.B00.1708072159
 - MBA51.88Z.00F4.B00.1708080803
 - MBA61.88Z.0103.B00.1708080653
 - MBA71.88Z.0171.B00.1708072210
 - MBP101.88Z.00F2.B00.1708080809
 - MBP102.88Z.010B.B00.1708080805
 - MBP111.88Z.0142.B00.1708080655
 - MBP112.88Z.0142.B00.1708080655
 - MBP114.88Z.0177.B00.1708080033
 - MBP121.88Z.0171.B00.1708080033
 - MBP131.88Z.0212.B00.1708080127
 - MBP132.88Z.0233.B00.1708080034
 - MBP133.88Z.0233.B00.1708080034
 - MBP141.88Z.0167.B00.1708080034
 - MBP142.88Z.0167.B00.1708080034
 - MBP143.88Z.0167.B00.1708080129
 - MBP61.88Z.005A.B00.1708072217
 - MBP71.88Z.003D.B00.1708080058
 - MBP81.88Z.004D.B00.1708080655
 - MBP91.88Z.00D7.B00.1708080744
 - MM41.88Z.0045.B00.1708072325
 - MM51.88Z.007B.B00.1708080744
 - MM61.88Z.010B.B00.1708080649
 - MM71.88Z.0224.B00.1708080033
 - MP61.88Z.0120.B00.1708080652


SMCJSONs:

 - Mac-031B6874CF7F642A: 2.14f24
 - Mac-189A3D4F975D5FFC: 2.16f68
 - Mac-27ADBB7B4CEE8E61: 2.15f7
 - Mac-2BD1B31983FE1663: 2.19f12
 - Mac-35C1E88140C3E6CF: 2.12f143
 - Mac-35C5E08120C7EEAF: 2.24f32
 - Mac-3CBD00234E554E41: 2.18f15
 - Mac-42FD25EABCABB274: 2.22f16
 - Mac-473D31EABEB93F9B: 2.36f97
 - Mac-65CE76090165799A: 2.33f10
 - Mac-66E35819EE2D0D05: 2.37f20
 - Mac-77EB7D7DAF985301: 2.17f7
 - Mac-7DF21CB3ED6977E5: 2.13f15
 - Mac-81E3E92DD6088272: 2.21f92
 - Mac-937CB26E2E02BB01: 2.27f2
 - Mac-9AE82516C7C6B903: 2.35f105
 - Mac-9F18E312C5C2BF0B: 2.26f2
 - Mac-A369DDC4E67F1C45: 2.31f36
 - Mac-A5C67F76ED83108C: 2.38f7
 - Mac-B809C3757DA9BB8D: 2.34f2
 - Mac-BE0E8AC46FE800CC: 2.25f87
 - Mac-DB15BD556843C820: 2.33f10
 - Mac-E43C1C25D4880AD6: 2.28f7
 - Mac-F60DEB81FF30ACF6: 2.20f18
 - Mac-FA842E06C61E91C5: 2.23f11
 - Mac-FFE5EF870D7BA81A: 2.32f20


FirmwareFeatures(Mask):

 - IM144.88Z.0183.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf00fe137
 - IM151.88Z.0211.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf80fe137
 - IM171.88Z.0110.B00.1708080012: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - IM181.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - IM183.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MB101.88Z.0154.B00.1708080122: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MB91.88Z.0159.B00.1708080011: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MBP131.88Z.0212.B00.1708080127: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP132.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP133.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MBP141.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP142.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP143.88Z.0167.B00.1708080129: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MP61.88Z.0120.B00.1708080652: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe80fe136

in my real macbook pro with GM

 

MBP133

 

$nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

$nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures >%f5%0f%fd

 

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask ?%ff%1f%ff

 

FF:0xFD0FF53E

FFM:0xFF1FFF3F
 
??????????????????????
=.=

Share this post


Link to post
Share on other sites

Maybe the best way is to load both apfs & Ozmosis from disk with correct order:

 

bcfg driver add 0 apfs.efi "apfs"
bcfg driver add 1 Ozmosis.efi "Ozmosis"
Or create a driver to load apfs.efi from disk before Ozmosis, after screen fully initialized (optional to block text output while loading apfs.efi by overriding EFI_TEXT_STRING).

Please..

I think i can make that happen and prepare a driver that first loads afps.efi and then ozmosis.efi in that order both from disk. Making them load from a firmware volume however is a little more tricky. For one you would have to somehow nuder both files so they dont auto load when inside the firmware. Wonder if telling genffs theyre efi_applications is enough to cripple that. Then you load both files both files manually in the driver from firmware should work.

Share this post


Link to post
Share on other sites

I've done some progress..

I took the german ozmosis bios for my board and applied MATS fix, replaced the original ssdt and dsdt with my own and also added some kext: Lilu, WhateverGreen, AppleIntelE1000e, USBInjector and AppleALC.

I also replaced SMCEmulator and its sensors with FakeSMC.

 

Now I got an error message in UefiTool: "PE32 image wit invalid DOS signature" on some of the new kexts. 

Can someone look at this bios before I flash it ?

 

https://www.dropbox.com/s/nnj554bfd1xm78x/Z87XUD4H-10b-Sierra_personalMod.rom.zip?dl=0

Share this post


Link to post
Share on other sites

I've done some progress..

I took the german ozmosis bios for my board and applied MATS fix, replaced the original ssdt and dsdt with my own and also added some kext: Lilu, WhateverGreen, AppleIntelE1000e, USBInjector and AppleALC.

I also replaced SMCEmulator and its sensors with FakeSMC.

 

Now I got an error message in UefiTool: "PE32 image wit invalid DOS signature" on some of the new kexts. 

Can someone look at this bios before I flash it ?

 

https://www.dropbox.com/s/nnj554bfd1xm78x/Z87XUD4H-10b-Sierra_personalMod.rom.zip?dl=0

attach kexts here and I can compress for you...

Share this post


Link to post
Share on other sites

greetings.

I'm sorry, but I don't understand a lot of things because it's my turn to translate.
I'm at 10.12.6.
For 10.13 what do I need to add and what do I need to remove from my bios with ozmosis?
or is it better to wait until the definite ozmosis comes out for 10.13?
Thanks for any help.

post-433991-0-06085100-1506106048_thumb.png

Share this post


Link to post
Share on other sites

I extract the "bootloader" from VM,i inseart it into Z97-D3H,but it not work,some bigone teach me,pl

 

 

new.zip

 

 

 

 

the MacMiscDxe looks like ozmosis

 

 

someone teach me,help me

 

 

:(

 

 

@cecekpawon

@crusher.

Edited by craike

Share this post


Link to post
Share on other sites

Dont know what to say. Are you trying to load MacMiscDxe along with Ozmosis, or? But why? How can they read your config, based on what? Ozmosis will set everything you needs to boot OSX (assumed like MacMiscDxe from Hopper, except "VmwPkg/MacMiscDxe/ApfsHelper.c"). Is that open-source? I never use vmware, sorry.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
    • By cvad
      Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
×