Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

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

  • Like 1
Link to comment
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.
Link to comment
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

 

Link to comment
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   ^_^

Link to comment
Share on other sites

 

So is it my case ? not sure because I can boot without KP when I use HackBGRT without dropping BGRT.

Even if I made a TABLE replacing OEm ID, etc... and inject it I've KP.

 

I think the trouble is the moment Oz or Clover get adresse of image.

I read many thing in linux forum about this UEFI bug.

 

For exemple this link : https://github.com/torvalds/linux/blob/master/drivers/firmware/efi/efi-bgrt.cThanks Crusher

[000h 0000   4]                    Signature : "BGRT"    [Boot Graphics Resource Table]
[004h 0004   4]                 Table Length : 00000038
[008h 0008   1]                     Revision : 00
[009h 0009   1]                     Checksum : 86
[00Ah 0010   6]                       Oem ID : " mi "
[010h 0016   8]                 Oem Table ID : ""
[018h 0024   4]                 Oem Revision : 01072009
[01Ch 0028   4]              Asl Compiler ID : "AMI "
[020h 0032   4]        Asl Compiler Revision : 00010013
 
[024h 0036   2]                      Version : 0001
[026h 0038   1]                       Status : 01
[027h 0039   1]                   Image Type : 00
[028h 0040   8]                Image Address : 00000000C50FC018
[030h 0048   4]                Image OffsetX : 000001B6
[034h 0052   4]                Image OffsetY : 000000BB
 

Fred

Link to comment
Share on other sites

So is it my case ? not sure because I can boot without KP when I use HackBGRT without dropping BGRT.

Even if I made a TABLE replacing OEm ID, etc... and inject it I've KP.

 

I think the trouble is the moment Oz or Clover get adresse of image.

I read many thing in linux forum about this UEFI bug.

 

For exemple this link : https://github.com/torvalds/linux/blob/master/drivers/firmware/efi/efi-bgrt.cThanks Crusher

[000h 0000   4]                    Signature : "BGRT"    [Boot Graphics Resource Table]
[004h 0004   4]                 Table Length : 00000038
[008h 0008   1]                     Revision : 00
[009h 0009   1]                     Checksum : 86
[00Ah 0010   6]                       Oem ID : " mi "
[010h 0016   8]                 Oem Table ID : ""
[018h 0024   4]                 Oem Revision : 01072009
[01Ch 0028   4]              Asl Compiler ID : "AMI "
[020h 0032   4]        Asl Compiler Revision : 00010013
 
[024h 0036   2]                      Version : 0001
[026h 0038   1]                       Status : 01
[027h 0039   1]                   Image Type : 00
[028h 0040   8]                Image Address : 00000000C50FC018
[030h 0048   4]                Image OffsetX : 000001B6
[034h 0052   4]                Image OffsetY : 000000BB
 

Fred

 

 

You were right davidm71, I install Sierra and it's ok

It's not Oz or Clover Issue

 

Fred

Link to comment
Share on other sites

Compiler ID? Where is the tool / link? help me

Pull your tables with Clover by pressing F4 and Maciasl to examine the structure and follow the instructions I wrote earlier.

Link to comment
Share on other sites

  • 2 weeks later...

As Ozmosis development is EOL or I prefer STALLED.

 

Anybody here interested in continuing Ozmosis Development?

Ozmosis was not meant to be open and it will remain like that.

 

Open Core was meant to be open but due various reasons like lack of time and/or developers at this moment is on hold until main developer decide what to do.

Link to comment
Share on other sites

×
×
  • Create New...