Jump to content

TypeThree

Members
  • Content count

    65
  • Joined

  • Last visited

About TypeThree

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. TypeThree

    Ozmosis

    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.
  2. TypeThree

    Ozmosis

    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.
  3. TypeThree

    Ozmosis

    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.
  4. TypeThree

    Ozmosis

    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...
  5. TypeThree

    Ozmosis

    @medallo Take a look at this post: https://www.insanelymac.com/forum/topic/291655-ozmosis/?do=findComment&comment=2630256 Btw: You don't have to use AppleALC-Ozm.kext anymore, just use the normal release...
  6. TypeThree

    Ozmosis

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

    Ozmosis

    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.
  8. TypeThree

    Ozmosis

    That is actually a big difference because the boot process starts at least... Is the panic nvram related? Have you tried different AptioFix releases?
  9. TypeThree

    Ozmosis

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

    Ozmosis

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

    Ozmosis

    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.
  12. TypeThree

    Ozmosis

    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?
  13. TypeThree

    Ozmosis

    For testing I'd load AptioFix through Shell with "load OsxAptioFix2drv" (after navigating to the right directory) and afterwards start the boot.efi by navigating to the right one and entering "boot.efi -norelocate -v". Please try that for me. You can also test different AptioFixDrivers.
  14. TypeThree

    Ozmosis

    The problem is located somewhere different, I'm tracking the issue at the moment. The first anomaly is that the issue appears even before the startup process of Mojave. Another particularity is that different boards and hardware configurations seem to have the issue to different extends. Quiet magically some people don't even have the issue. I have periods of time where I have no issue at all and then suddenly, even if nothing seems to have changed, I can only enter Mojave with both GPUs by using the "BIOS trick". Finally, it is confirmed that both iGPU and dedicated GPU can work together in Mojave (with Ozmosis) even when tools like Whatevergreen aren't even used. This all leads me to the conclusion that it's highly unlikely that we are facing a macOS driver issue. The problem appears way to early which points in the direction of a UEFI driver issue, uppermost register- or memory issue – AptioFix. Fortunately the Ozmosis internal AptioFix can be disabled by using the -norelocate boot-argument. At the moment it looks like the issue can be resolved by using -norelocate and loading the OsxAptioFix2Drv instead (AptioMemoryFix lead to NVRam issues during my tests). Braveheart testers are welcome!
  15. TypeThree

    Ozmosis

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