Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
xpamamadeus

Ozmosis

5,871 posts in this topic

Recommended Posts

Thank you very much, I will test it, As soon as I get to the computer!

It does not work for me. I do not know what I'm doing wrong. Logs do not create and when loading in the verbose mode nothing displays. 

In shell I put this:

fs0:

CD EFI

bcfg driver add 0 KernextPatcher.efi KernextPatcher

Share this post


Link to post
Share on other sites

Sad but TRUE.. If you have already have Ozmosis in firmware, I can guarantee that will not work for you.
(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage with bcfg.
Take my minimalist setup below as your reference (you can run it from USB drive like me as a test):

.
└── EFI
    ├── KernextPatcher.efi
    ├── KernextPatcher.plist
    ├── KernextPatcherLog.txt
    ├── Oz
    │   ├── Acpi
    │   │   ├── Dump
    │   │   └── Load
    │   │       ├── SSDT-1.aml
    │   │       └── SSDT-2.aml
    │   ├── Darwin
    │   │   └── Extensions
    │   │       └── Common
    │   │           └── FakeSMC.kext
    │   │               └── Contents
    │   │                   ├── Info.plist
    │   │                   └── MacOS
    │   │                       └── FakeSMC
    │   └── theme.bin
    └── Ozmosis.efi

Start shell and type following commands:

# list drivers

bcfg driver dump

Option: 00. Variable: Driver0000
  Desc    - KernextPatcher
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\KernextPatcher.efi
  Optional- N
Option: 01. Variable: Driver0001
  Desc    - Ozmosis
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\Ozmosis.efi
  Optional- N

# remove any existing drivers

bcfg driver rm 0
...

# register drivers

fs0:
cd EFI
bcfg driver add 0 KernextPatcher.efi "KernextPatcher"
bcfg driver add 1 Ozmosis.efi "Ozmosis"

** Need to register KernextPatcher before Ozmosis
** To reorder the sequence: bcfg driver mv 0 1
** If succeed, patcher will create "KernextPatcherLog.txt" log-file

Share this post


Link to post
Share on other sites

Sad but TRUE.. If you have already have Ozmosis in firmware, I can guarantee that will not work for you.

(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage with bcfg.

Take my minimalist setup below as your reference (you can run it from USB drive like me as a test):

.
└── EFI
    ├── KernextPatcher.efi
    ├── KernextPatcher.plist
    ├── KernextPatcherLog.txt
    ├── Oz
    │   ├── Acpi
    │   │   ├── Dump
    │   │   └── Load
    │   │       ├── SSDT-1.aml
    │   │       └── SSDT-2.aml
    │   ├── Darwin
    │   │   └── Extensions
    │   │       └── Common
    │   │           └── FakeSMC.kext
    │   │               └── Contents
    │   │                   ├── Info.plist
    │   │                   └── MacOS
    │   │                       └── FakeSMC
    │   └── theme.bin
    └── Ozmosis.efi

Start shell and type following commands:

# list drivers

bcfg driver dump

Option: 00. Variable: Driver0000
  Desc    - KernextPatcher
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\KernextPatcher.efi
  Optional- N
Option: 01. Variable: Driver0001
  Desc    - Ozmosis
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\Ozmosis.efi
  Optional- N

# remove any existing drivers

bcfg driver rm 0
...

# register drivers

fs0:
cd EFI
bcfg driver add 0 KernextPatcher.efi "KernextPatcher"
bcfg driver add 1 Ozmosis.efi "Ozmosis"

** Need to register KernextPatcher before Ozmosis

** To reorder the sequence: bcfg driver mv 0 1

** If succeed, patcher will create "KernextPatcherLog.txt" log-file

 

OK, I understood. But I was flushing KernextPatcher into the BIOS and it did not work also. Should I KernextPatcher.plist so flush in BIOS to make it work? Or from the BIOS it can’t work at all? Thanks!

Share this post


Link to post
Share on other sites

I think try to change GUID on 11xxx-xxxx-xxxx ... and flash it before ozmosis.efi, maybe then it will be loaded first. try use kext2ffs for kernext.plist as well as ozmosisdefaults.plist

Share this post


Link to post
Share on other sites

 

OK, I understood. But I was flushing KernextPatcher into the BIOS and it did not work also. Should I KernextPatcher.plist so flush in BIOS to make it work? Or from the BIOS it can’t work at all? Thanks!

 

 

You just had to read, nothing more:

If you have already have Ozmosis in firmware, I can guarantee that will not work for you.

(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage (HDD Only) with bcfg.

 

Again this schema explain it:

 

└── EFI

    ├── KernextPatcher.efi

    ├── KernextPatcher.plist

    ├── KernextPatcherLog.txt

    └── Ozmosis.efi

 

And this the only way to use it and not inside the BIOS, to avoid problems after flashing  ^_^ 

 

Share this post


Link to post
Share on other sites

With the new beta 3 my ozmosis no longer detect the high sierra apfs, I have to boot to sierra and select high sierra as a startup disk to boot it. I'm going to try with the new apfs.efi to see what happen.

Share this post


Link to post
Share on other sites

Has anyone found a way to suppress the APFs Driver debug output ?!

 

@cecekpawon just tried out your KernextPatcher for the moment being only with one kernel patch (XCPM on Ivy for HighSierra) and it really works. Great job man I´ll add more patches and report back if something does not work as expected (Patcher added via bfcg Oz in ROM). Thank you very much for this great thing :D 

Share this post


Link to post
Share on other sites

I am not worried about bricking the board, how about you?

 

PpSgWMr.png

 

Latest precompiled binary can be found here.

 

I am also not worried about bricking the board. This one is less functional, but enough for me.

You just had to read, nothing more:

If you have already have Ozmosis in firmware, I can guarantee that will not work for you.

(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage (HDD Only) with bcfg.

 

Again this schema explain it:

 

└── EFI

    ├── KernextPatcher.efi

    ├── KernextPatcher.plist

    ├── KernextPatcherLog.txt

    └── Ozmosis.efi

 

And this the only way to use it and not inside the BIOS, to avoid problems after flashing  ^_^ 

 

It works. Thanks!

post-109325-0-41632100-1499948215_thumb.jpg

Share this post


Link to post
Share on other sites

Greetings.

I am currently "sierra_10.12.5" with the asus P8Z77-M card, i5 processor 3470. NVIDIA GeForce 210 1024 MB graphics. I'm with ozmosis but I do not have "apfs".
 
Last login: Thu Jul 13 09:33:58 on console

iMac-de-Medallo:~ medallo$ sudo disk list

Password:

sudo: disk: command not found

iMac-de-Medallo:~ medallo$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *120.0 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS My Hack Sierra          119.2 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

 

/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                  Apple_HFS RESPALDO                999.9 GB   disk1s2

 

iMac-de-Medallo:~ medallo$

 

Questions:
1. Can I have apfs on "sierra_10.12.5"? Or is it only for 10.13?
2. Is there a final version of apfs or is it better to wait until another one comes out better?
Thank you.
For any help.

Share this post


Link to post
Share on other sites

HI,

 

post-509660-0-96763300-1500019101_thumb.jpg

 

I've this error at boot with Oz.

I've try Pike trick doesn't work for me.

I've try with clover and dropping (not replacing) BGRT solved my issue.

 

is there a way to drop table in Oz ?

 

Fred

 

Share this post


Link to post
Share on other sites

Hi,

 

I've found a soft which do the job for clover can boot without dropping BGRT.

But doesn't work with Oz.

 

https://github.com/Metabolix/HackBGRT

 

 

Fred

 

Fred, c'est une kernel panic liée aux tables acpi!

 

Fred this was ACPI kernel panic related, i suspect DSDT somethings like USB port are not properly injected, or SSDT, but look at the 15,16 line from bottom you'll see IOUSBHost !F and usb . !UCommon.

 

But clearly it is related to ACPI   ^_^

Share this post


Link to post
Share on other sites

Z87 how to solve MATS.aml problem?

 

 

You need to ask davidm71 for that :wink_anim: !

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.

×