Jump to content
xpamamadeus

Ozmosis

6,140 posts in this topic

Recommended Posts

On 10/1/2018 at 12:00 AM, WinstonAce said:

but it's too fast to see what's going on

For me that sounds like at least something is going on... When you boot Mojave with both GPUs without the Aptio Fix, you will get no Verbose Output at all. If there's some Verbose output after performing the previously presented method, it means that we are one step closer to the solution.

 

Have you tried AptioMemoryFix and OsxAptioFixDrv, too?

Share this post


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

ammoune78 

It is very large, it does not fit and a little expensive.

Excuse me, i was meaning the GT710 instead!

 

5 hours ago, TypeThree said:

For me that sounds like at least something is going on... When you boot Mojave with both GPUs without the Aptio Fix, you will get no Verbose Output at all. If there's some Verbose output after performing the previously presented method, it means that we are one step closer to the solution.

 

Have you tried AptioMemoryFix and OsxAptioFixDrv, too?

 

Why with clover no problem, while with Ozmosis the problem appear! Then it appear for other chipsets too, can you see the post that i've linked for Mojave topic?  

Share this post


Link to post
Share on other sites
16 hours ago, WinstonAce said:

GT710 puede ser Kepler o Fermi, asegúrese de que está basado Kepler.

Enviado desde mi SM-G960F utilizando Tapatalk
 

hi.

in the specifications of NVIDIA GeForce GT 710 does not show if it is Kepler or Fermi. Where do I find them? only shows Cuda.

Share this post


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

hi.

in the specifications of NVIDIA GeForce GT 710 does not show if it is Kepler or Fermi. Where do I find them? only shows Cuda.

Only 750 is not Kepler ,all other cards are Kepler in 7xx series。

Share this post


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

Why with clover no problem, while with Ozmosis the problem appear!

Because Clover injects a different AptioFix – at least that's what I think is the issue.

 

In my case I also get the reproducable result that the issue is fixed when I inject OsxAptioFix2Drv. But unless others report about the same result (maybe with different AptioFixes) I can't tell if this is really the solution.

Edited by TypeThree

Share this post


Link to post
Share on other sites
9 hours ago, WinstonAce said:

For me only FixAptioPkg works and only from bios.

Sent from my SM-G960F using Tapatalk
 

 

3 hours ago, TypeThree said:

And now you can boot with both iGPU and dedicated GPU?

Not for me, i injected AptioMemoryFix.efi (ffs) in bios, but it's not give effect, stoped on Apple logo

Share this post


Link to post
Share on other sites

That is actually a big difference because the boot process starts at least...

 

Is the panic nvram related?

 

Have you tried different AptioFix releases?

Share this post


Link to post
Share on other sites

Guys I think after three failures, I would like someone to help me out here!

 

1. Manufacturer: Gigabyte 
2. Model: GA-B75M-HD3 (rev. 1.0) 
3. Chipset: B75 
4. Bios Version: F5 
5. Bios link: http://download.gigabyte.eu /FileList/BIOS/mb_bios_ga-b75m-hd3_f5.exe 
6. OS version As: High Sierra / Mojave 
Awesome site thanks for the help
I tried one from another site,
and all three of mine just hang after I put in the instal usb
 
sonicman66
  •  

Share this post


Link to post
Share on other sites
On 10/4/2018 at 7:49 PM, TypeThree said:

So injecting AptioMemoryFix and using -norelocate as a bootarg changed nothing for you?

I inserted AptiomMemoryFix、OsxAptioFixDrv、OsxAptioFix2Drv、OsxAptioFix3Drv.ffs separately in bios,and add -norelocate to boot-args in ozmosisdefaults,but it doesn't make any sense,still stack on apple logo,no progress bar...

Or you can upload OsxAptioFix2Drv.ffs which you use,I'll check it.THX!

Share this post


Link to post
Share on other sites

This is the driver I used: OsxAptioFix2Drv.efi

 

I did not insert it as ffs into my BIOS and I did not add -norelocate to my defaults.plist boot-args.

I'm just testing, so I enter a UEFI Shell and navigate to the place where OsxAptioFix2Drv is located (in my case EFI --> fs0: cd EFI). Afterwards I manually load OsxAptioFix2Drv through Shell ("load OsxAptioFix2Drv.efi").

If the AptioFix-Load is confirmed, I navigate to my Mojave boot.efi (in my case fs3: cd 375...\System\Library\CoreServices) and start Mojave with the needed options (boot.efi -norelocate -v).

I would recommend to test it this way for everybody. Otherwise you may risk the functionality of your System.

 

In every single case this works for me and I can start Mojave with both iGPU and GPU with fully functional Quicksync and HWEncoding. Different Systems need different AptioFixDrivers, though.

Edited by TypeThree

Share this post


Link to post
Share on other sites
On Sun Oct 07 2018 at 10:04 PM, TypeThree said:

This is the driver I used: OsxAptioFix2Drv.efi

 

I did not insert it as ffs into my BIOS and I did not add -norelocate to my defaults.plist boot-args.

I'm just testing, so I enter a UEFI Shell and navigate to the place where OsxAptioFix2Drv is located (in my case EFI --> fs0: cd EFI). Afterwards I manually load OsxAptioFix2Drv through Shell ("load OsxAptioFix2Drv.efi").

If the AptioFix-Load is confirmed, I navigate to my Mojave boot.efi (in my case fs3: cd 375...\System\Library\CoreServices) and start Mojave with the needed options (boot.efi -norelocate -v).

I would recommend to test it this way for everybody. Otherwise you may risk the functionality of your System.

 

In every single case this works for me and I can start Mojave with both iGPU and GPU with fully functional Quicksync and HWEncoding. Different Systems need different AptioFixDrivers, though.

I tested in shell,but I faild on first step,after load atiofix,I got a blackscreen with backlight...osxaptiofix2drv and aptiomemoryfix got a same result...

Share this post


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

Interesting...

 

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

Nop,I can boot macos through shell,just can not load aptiofix efi.i tried several times,after I type "load aptiofix.efi",some codes flashed,then blackscreen with a Underline flashes in the upper left corner,as I said before,osxaptiofixdrv.osxaptiofix2drv and aptiomemoryfix got a same result...。。。

And also I want to know  what's the deference between loading efi in shell and inserting ffs into bios?

Share this post


Link to post
Share on other sites

Hi guys.
I have no sound in the p8z77m - audio ALC887: in Mojave
1. / Volumes / EFI / Efi / Oz / Darwin / Extensions / Common / AppleALC-OZM.kext, Lilu.kext
2. / Volumes /EFI/Efi/Oz/Acpi/Load/DSDT.aml. SSDT.alm
  in DSDT.aml:
  layout-id: 0x02, 0x00, 0x00, 0x00
I appreciate any help.:(

Share this post


Link to post
Share on other sites

With the latest release of AppleALC, you only need to inject device id in boot-args from OzmosisDefaults: alcid=2, and no more DSDT injection ^_^

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
×