Jump to content
xpamamadeus

Ozmosis

6,140 posts in this topic

Recommended Posts

Thank you..
the solution was to remove from OzmosisDefaults.plist, the line: "FirmwareVendor" "Apple":frantics:

Yes, and the other one, consist to add alcid=2 or your preferred and remove patch from dsdt or ssdt according to the latest AppleALC documentation!
It was just an information for knowledge


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
Advertisement
On 10/12/2018 at 3:01 AM, ammoune78 said:


Yes, and the other one, consist to add alcid=2 or your preferred and remove patch from dsdt or ssdt according to the latest AppleALC documentation!
It was just an information for knowledge emoji846.png


Sent from my iPhone using Tapatalk

It work also audio via HDMI with HD4600 ?

I can get audio from analog only with mojave...

Share this post


Link to post
Share on other sites
It work also audio via HDMI with HD4600 ?
I can get audio from analog only with mojave...


It should, but i didn’t tested it yet, i can try and report back later today!


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
18 hours ago, ammoune78 said:

 


It should, but i didn’t tested it yet, i can try and report back later today!


Sent from my iPhone using Tapatalk

 

Solved :thumbsup_anim:

 

Missed out that WhateverGreen now is needed also for IGPU.....

 

 

Share this post


Link to post
Share on other sites
On Tue Oct 09 2018 at 7:28 AM, TypeThree said:

Interesting...

 

Also BlackScreen when you use bcfg driver add... and do a reboot aftwards?

Though my test,I think maybe @ammoune78 is right,10.14.1beta1 can normally boot without any change in bios,with igpu and dgpu.I tried almost every macos vesion except 10.14.1beta2.So I think this issue maybe not caused by aptiomemory.

Share this post


Link to post
Share on other sites

If your guideline is not "never touch a running system", please do an NVRam and BIOS Setting reset and test again. 

 

If everything still works perfectly afterwards, you may be right. I'm gonna test 10.14.1beta1, too...

Share this post


Link to post
Share on other sites

Excuse me @mosconi , I didn't had time to reply, and yes, WathEverGreen replaced IntelGraphicsFixUp, so it was the magical solution.

 

@taoarch and @TypeThree:

I can boot normally to Mojave, with just choosing Mojave HD in the Boot Override on the Bios Settings, and without altering any Bios Option.

The result:

- Booting every Apple OS normally ^_^

- Booting Mojave from Boot Override on the Bios Settings, and keeping them as they are  ^_^

Share this post


Link to post
Share on other sites
6 hours ago, ammoune78 said:

Excuse me @mosconi , I didn't had time to reply, and yes, WathEverGreen replaced IntelGraphicsFixUp, so it was the magical solution.

 

@taoarch and @TypeThree:

I can boot normally to Mojave, with just choosing Mojave HD in the Boot Override on the Bios Settings, and without altering any Bios Option.

The result:

- Booting every Apple OS normally ^_^

- Booting Mojave from Boot Override on the Bios Settings, and keeping them as they are  ^_^

Magic!This is working for me under 10.13.6 and 10.14.1beta3 normally boot or reboot,but not 10.14...

Share this post


Link to post
Share on other sites
6 hours ago, taoarch said:

Magic!This is working for me under 10.13.6 and 10.14.1beta3 normally boot or reboot,but not 10.14...

 

I can boot 10.14 with both graphics card IGPU/DGPU, I already confirmed it, after @TypeThree had posted that solution! And, for me, I only reboot with same settings on bios, and choose Mojave HD from Boot Override menu on my GIGABYTE board! Did you used WhatEverGreen? Did you used Ozmosis Mojave support by @TypeThree?

Share this post


Link to post
Share on other sites
57 minutes ago, ammoune78 said:

 

I can boot 10.14 with both graphics card IGPU/DGPU, I already confirmed it, after @TypeThree had posted that solution! And, for me, I only reboot with same settings on bios, and choose Mojave HD from Boot Override menu on my GIGABYTE board! Did you used WhatEverGreen? Did you used Ozmosis Mojave support by @TypeThree?

As I just said,according to your methods,I can boot 10.14.1beta3 with IGPU AND DGPU,

and I use wgatevergreen and ozmosis with Mojave support,but it doesn't work for 10.14 release edition。

And when I used 10.14.1beta1 before to test,  I only need to set dvmt to 32m and 128m in bios, it can boot normally.but but it doesn't work for 10.14.1beta3!

What a magical bug!

Edited by taoarch

Share this post


Link to post
Share on other sites
As I just said,according to your methods,I can boot 10.14.1beta3 with IGPU AND DGPU,
and I use wgatevergreen and ozmosis with Mojave support,but it doesn't work for 10.14 release edition。
And when I used 10.14.1beta1 before to test,  I only need to set dvmt to 32m and 128m in bios, it can boot normally.but but it doesn't work for 10.14.1beta3!
What a magical bug!

I did not set dvmt to 32 and 128
The thing that works for me is boot override
This magical is working for me but not for you as i can see


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Boot override is a very useful solution, but I found that in order to successfully boot Mojave, it should be saved and restarted after selecting the system item in Boot override. The computer must have a restart process to be successful. For this reason, I chose to change dmvt. Of course, this is not the only option.

Share this post


Link to post
Share on other sites
14 hours ago, taoarch said:
Boot override is a very useful solution, but I found that in order to successfully boot Mojave, it should be saved and restarted after selecting the system item in Boot override. The computer must have a restart process to be successful. For this reason, I chose to change dmvt. Of course, this is not the only option.


Hm, maybe because different manufacturer for boards, but because i use for each os one selected drive while others are disabled from sata interface settings with profil settings in the bios, when i restart to choose Mojave profile i select its boot override and it works directly! But this is an alternative solution, that touches only haswell systems with Ozmosis!
Other chipsets have pretty same problem using clover, but they have a patch, except damned haswell.


Sent from my iPhone using Tapatalk

Edited by ammoune78

Share this post


Link to post
Share on other sites

Hi Friends, it's been a long time i'm not posting, but i have little time.
One my friend ask me for an hackintosh, but i'm very ignorant about latest developments 

, could someone advice me for a mobo, cpu and graphics card that are compatible with ozmosis? 

Many thanks 

Share this post


Link to post
Share on other sites
3 hours ago, Aigors said:

Hi Friends, it's been a long time i'm not posting, but i have little time.
One my friend ask me for an hackintosh, but i'm very ignorant about latest developments 

, could someone advice me for a mobo, cpu and graphics card that are compatible with ozmosis? 

Many thanks 

Hi.. I have ASUS P8Z77-m - i5 3470 - NVIDIA GeForce GT 710 2047 MB - iMac (27-inch, Late 2012)- SSD 120G - Mojave Ozmosis

get them.

Share this post


Link to post
Share on other sites

Hi all,

just want to let you know, that I successfully installed Mojave on my hackintosh with intel hd4600 igpu only.

I updated Ozmosis to the xmax version and added the KernextPatcher.ffs into the rom.

For loading ApfsDriverLoader-64.efi and OsxAptioFixDrv-64.efi and to select the boot entries I used my enhanced rEFInd.

But I have to set igpu memory to 32M, any higher value stucks at the apple logo. 

 

Share this post


Link to post
Share on other sites

Is there a nvram variable that could be used to disable injection of SMCEmulator.kext from firmware (could not find any on the Wiki)?

I have an issue with Mojave 10.14.1 and 10.13.6SU on my QUO board and I would like to test something without that kext being injected from firmware.

Edited by IronManJFF

Share this post


Link to post
Share on other sites

AFAIK SMCEmulator.kext is simply a renamed FakeSMC and nowadays pretty old (version 1300 or something like that). I wouldn't recommend using SMCEmulator, instead you should use VirtualSMC (MMIO support) or FakeSMC.

 

I don't think that there's a way to disable Kexts from loading that are in the firmware (except breaking kext injection on purpose :D), only if there's a kext with the same identifiers on the EFI it will be loaded instead of the one from FV. Ozmosis uses FV as a fallback in most cases.

Share this post


Link to post
Share on other sites

There was a nvram variable to prevent VooDooHDA injection, so I thought may be there was a undocumented one for SMCemulator.

Thanks for clarification, will try to override with EFI

Share this post


Link to post
Share on other sites

Yes, because some VoodooHDA features are part of Ozmosis.efi itself, it's like a collaboration between VoodooHDA and Ozmosis (DeviceProperty Injection etc.). But as far as I am concerned Ozm doesn't have an effect on SMCEmulator itself, I could be wrong here though.

Share this post


Link to post
Share on other sites
21 hours ago, TypeThree said:

Yes, because some VoodooHDA features are part of Ozmosis.efi itself, it's like a collaboration between VoodooHDA and Ozmosis (DeviceProperty Injection etc.). But as far as I am concerned Ozm doesn't have an effect on SMCEmulator itself, I could be wrong here though.

Hey!

Is there any progress in booting Mojave with hd4600?

I can boot it with "override", but I must repeat this step in bios every time I start, so I switch to clover.lol!

Share this post


Link to post
Share on other sites

I can't guarantee anything yet. As previously mentioned it can help to use a normal AptioFix and disable Ozm internal AptioFix by using -norelocate flag in some cases.

Edited by TypeThree

Share this post


Link to post
Share on other sites

IQSV

If I boot from the boot menu, then after the appearance of the apple, it will immediately restart. But if I am loading from Hermit Shell, as in the screenshot, the system is loading. Thought that a problem with Darboot. Already removed it from the BIOS. The problem is not in it. I now wonder why it loads from Shell, and if I add an entry to the boot menu, then no. Any ideas? AptioFix and -norelocate does not work. IMG_20181113_115609.jpg

Edited by Jakushevich

Share this post


Link to post
Share on other sites

Hi all.

 

Just today, I read for the first time about this Osmosis system.  Just curious, if I wanted to give this a go, am I limited to ancient hardware like the z77 chipset based boards or are there now modern motherboards that work?

 

thanks in advance!

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 ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • 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
×