Jump to content
xpamamadeus

Ozmosis

5,903 posts in this topic

Recommended Posts

What are you up to, boy? Do the windows device id serve?

Hi all,

 

I'm back, i need more SATA's Model, Vendors and Device ID's with specific IOName from IORegistryExplorer, as for exemple: 9 Series - Intel - pci8086,8c82.

This will help me to add them onto the InjectorKext to be more compatible.

 

Cordially, ammoune78!


 

Hi murvold!

 

Your DSDT will be ready for tomorrow if everything goes well.

Share this post


Link to post
Share on other sites
Advertisement

What are you up to, boy? Do the windows device id serve?

 

Take a look at the previous posts! 

 

Because some motherboards does not shows the right SATA's model or shows orange disk or shows Generic SATA Device, and some can't boot because of InjectorKext doesn't have there proper ID's, even if DSDT or SSDT is patched.
 
In adition to that, the InjectorKext plist file extracted from QUO rom can't help you, because of it's executable that can not be modified! 
 
That's why i've builded an updated one with more SATA's ID and Models, but i still need more for X79, Z97, and other chipsets etc....
 
I already taked permission for that and for who can't read previous posts, to create an new topic that can contain updates only: an Read only Topic! 
 
To leave this one for support and discussions.
Edited by ammoune78

Share this post


Link to post
Share on other sites

Hi all,

 

I'm back, i need more SATA's Model, Vendors and Device ID's with specific IOName from IORegistryExplorer, as for exemple: 9 Series - Intel - pci8086,8c82.

This will help me to add them onto the InjectorKext to be more compatible.

 

How can I find in IORegistryExplorer what you need? 

Share this post


Link to post
Share on other sites

Another doubt, some news about the Aptio V and the new boards Z170 and Z270 ??

 

Take a look at the previous posts! 

 

Because some motherboards does not shows the right SATA's model or shows orange disk or shows Generic SATA Device, and some can't boot because of InjectorKext doesn't have there proper ID's, even if DSDT or SSDT is patched.
 
In adition to that, the InjectorKext plist file extracted from QUO rom can't help you, because of it's executable that can not be modified! 
 
That's why i've builded an updated one with more SATA's ID and Models, but i still need more for X79, Z97, and other chipsets etc....
 
I already taked permission for that and for who can't read previous posts, to create an new topic that can contain updates only: an Read only Topic! 
 
To leave this one for support and discussions.

 

Share this post


Link to post
Share on other sites

How can I find in IORegistryExplorer what you need? 

 

Quite simple, just open IORegistryExplorer and go to SAT0 or SAT1 or SATA and it's done, follow this ScreenShot:

 

post-334538-0-10700200-1486332993_thumb.png

Share this post


Link to post
Share on other sites

Another doubt, some news about the Aptio V and the new boards Z170 and Z270 ??

 

I don't think it can be done, CORE_DXE has a smaller size and the ROM space can't be free! Secondly the ROM is protected, it need to be unlocked to go flash it with SPI Flasher!

I hope I can help a little bit. here is my screen from the: GA-Z77N-WiFI

 

attachicon.gifBildschirmfoto 2017-02-05 um 23.27.33.png

 

Thanks CrazyCreator for your fast reply, your Mobo has the 1e03 ID and the QUO one in InjectorKext has the 1e02!

 

But I still have a doubt, you may have to find it under windows or ubuntu live dvd to be sure. Because in the ScreenShot you've posted there's two ID one from QUO and the other from the board I think.

Share this post


Link to post
Share on other sites

when in ubuntu what is the line for the terminal again?

 

Once in Ubuntu, open Terminal and type: lspci -nn 

 

You will see something like this: 00:1f.2 SATA controller [0106]: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller [8086:1d02] (rev 06), copy it and that's all.

 

This is just an exemple taken from X79 board, but yours will show Z77 or 7 Series!

Edited by ammoune78

Share this post


Link to post
Share on other sites

And to patch kernel/kexts? :rolleyes:

 

Everything possible in Ozmosis. :)

 

Meanwhile seems to internal only.

 

I dont have aptio-V, but to work with spi-programmer we need to remove the capsule header first before flashing it. With smaller CORE_DXE size it should be an advantage for user to get more free spaces without compressing it first.

post-1101532-0-40415200-1486366406_thumb.png

Share this post


Link to post
Share on other sites

@ammoune78

here is the terminal output:

ubuntu@ubuntu:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
00:1c.5 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 [8086:1e1a] (rev c4)
00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8]
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] [1002:aa58]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
05:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
ubuntu@ubuntu:~$

Share this post


Link to post
Share on other sites

Meanwhile seems to internal only.

 

I dont have aptio-V, but to work with spi-programmer we need to remove the capsule header first before flashing it. With smaller CORE_DXE size it should be an advantage for user to get more free spaces without compressing it first.

 

I don't think so for GIGABYTE boards, because firstable they don't have a capsule header, but it need CodeRush  :yes:  mind to break the security, secondable the DXE_CORE has 58 Kb, and in Volume 02 there was only 1 Kb of free space!

 

The question is what should be deleted from Rom file to leave more free space? 

 

@ammoune78

here is the terminal output:

ubuntu@ubuntu:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
00:1c.5 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 [8086:1e1a] (rev c4)
00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8]
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] [1002:aa58]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
05:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
ubuntu@ubuntu:~$

 

Yeah, the Device ID is [1e02], but I don't know why the [1e03] appear as Device ID in your IOReg  :whistle:, maybe it's the SATA II port? Anyway, as you use the iMac SMBios you can enter those Device ID's to your injected properties in the DSDT ^_^ ! 

Share this post


Link to post
Share on other sites

Im prefer to compress some module rather than delete it. Use mmtool to get full report of each module size & use uefitool to check whether the current module is already compressed / not.

 

Yes that's was I meant, because I did not pay attention by writing "delete", because I never delete modules from my Bios, except those who comes after NetworkStackSetupScreen. There's module name under Setup.ffs that can be Compressed from 2.1 MB to 455KB. And in Z270 chipset Bios, PartitionDxe and Fat module are already there, I hope if Ozmosis can work on it. 

Share this post


Link to post
Share on other sites

Yeah, the Device ID is [1e02], but I don't know why the [1e03] appear as Device ID in your IOReg  :whistle:, maybe it's the SATA II port? Anyway, as you use the iMac SMBios you can enter those Device ID's to your injected properties in the DSDT ^_^ ! 

 

My DSDT ist patched a little bit. but I think I understand not really what you say to me. 

 

Am I to enter the Device-ID, or do you think I have entered the ID?

Share this post


Link to post
Share on other sites

My DSDT ist patched a little bit. but I think I understand not really what you say to me. 

 

Am I to enter the Device-ID, or do you think I have entered the ID?

 

Your board have the same Device ID of the QUO board, so no need to add it into InjectorKext because it's already there.
 
But if you look at your IORegistryExplorer posted yesterday, you will see 2 Device IDs:
 
1e02: the right one
and
1e03: it's this one that I not understand why it's there.
 
If I try to understand why, and because your lspci -nn did not show it, it's related to your DSDT because it not have a patch for SATA.
 

If in case that your DSDT has no SATA patch, so this is why i told you that you need to inject Devices to your DSDT with Device ID's from the given lspci -nn result. This is if you use iMac SMBios, because you will not have kernel panic if Device ID's was injected to DSDT.

 

The system will be more stable if detailed informations are in the DSDT with the help of kexts, and this is my understanding related to my experience with OS X!

 

 

 

 

 

 

 

 

@ Murvold!

 

Here's your Patched DSDT, SSDT is inside it:  DSDT-Patched.aml.zip

Edited by ammoune78

Share this post


Link to post
Share on other sites

Hi ammoune78, please help me made ozm rom for x79-up4 rev1.1

 

Hi cxdee, here's your X79UP4-F7 Rev1.1 Rom and OzmosisDefaults with MacPro6.1 but you need to put your 5 last MAC address digits for iCloud to work!

 

 

 

OzmosisDefaults.plist.zip

Share this post


Link to post
Share on other sites

I don't think so for GIGABYTE boards, because firstable they don't have a capsule header, but it need CodeRush  :yes:  mind to break the security, secondable the DXE_CORE has 58 Kb, and in Volume 02 there was only 1 Kb of free space!

 

The question is what should be deleted from Rom file to leave more free space? 

 

Yeah, the Device ID is [1e02], but I don't know why the [1e03] appear as Device ID in your IOReg  :whistle:, maybe it's the SATA II port? Anyway, as you use the iMac SMBios you can enter those Device ID's to your injected properties in the DSDT ^_^ ! I donk think space is an issue as I can inset Oz and other kext files...the only issue is it won't accept hfsplus.ffs it shows error. without hfsplus it won't work right??

I don't think it is a space issue..I can insert OZ and other kext files...but can't insert hfsplus.ffs... it throws some error...have tested on two different sky lake boards but same error.

Share this post


Link to post
Share on other sites

I don't think it is a space issue..I can insert OZ and other kext files...but can't insert hfsplus.ffs... it throws some error...have tested on two different sky lake boards but same error.

Which kind of error? 

What program are you using? 

MMtool throw a strange error when you don't have enough room 

Share this post


Link to post
Share on other sites

I don't think it is a space issue..I can insert OZ and other kext files...but can't insert hfsplus.ffs... it throws some error...have tested on two different sky lake boards but same error.

 

If you did not understand I can repeat  :D :

I don't think is for:

1- GIGABYTE boards don't have a capsule header for UEFI, and it was replied for cecekpawon: I dont have aptio-V, but to work with spi-programmer we need to remove the capsule header first before flashing it.

2- Even if you put all Ozmosis stuffs and I already did it, and even if you have SPI - Programmer, you still need to break the security of the bios!

If you reached all the steps, the final one is the hard one: breaking security ;) .

Share this post


Link to post
Share on other sites

@ ammoune78

I was refereeing to the space availability in ROM which you have mentioned above...you may right in other aspects...I am not disputing that.. :) 

Yeah need to break security!!! I think CodeRush can do it..

 

I am using MMTool but this error is not because of space issue..I have tried to insert hfsplus.ffs first but still same error..I have attached image..

erro.jpg

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 partha.slg123
      Hackintosh High Sierra 10.13.3 USB Installer Boot Into USB DIrectly Enter Exit Option Menu. Clover Boot Menu Not Showing. Plz Help .................
       

       
      My System Specification :

      CPU : Core i5 6400
      MB : Asus H110M-CS
      RAM : 8GB DDR 4
      HDD : WD 1TB For Windows And WD 500 GB For Hackintosh
      Bootloader : Clover
    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
    • By cvad
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
    • By MacNB
      Recently transition from ###### to Clover.
      All work great on my raging Dell530 (with Quad-core Xeon E5450).
      I can triple boot Snow-Leopard, Mavericks or Yosemite.
      Really love the way clover does dynamic patching.
       
      Decided to add a second drive that had the original Dell-installed Windows Vista.
       
      Question for the community: Is it even possible to boot legacy Vista on the second drive using Clover ?
       
      I ask because I cannot. I have searched and all topics discuss UEFI boot which is OK for Win7 and up.
      Vista does not support UEFI boot.
      And this good old Dell only has BIOS.
       
      Clover GUI lists two new partitions after the Recovery HD partition.
      The last one is called "Boot Windows from OS" (screenshot0):
       
      When I hit enter, the screen clears to black and Clover windows badge is displayed but does not boot.
      If I hit enter again, I see the Clover GUI again.
       
      It just will not boot Vista.
       
      Disk details are as shown:
      OSX-YS-Pro:~ MacNB$ diskutil list /dev/disk0    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *1.0 TB     disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:                  Apple_HFS OSX-SL                  803.3 GB   disk0s2    3:                  Apple_HFS OSX-MV                  153.3 GB   disk0s3    4:                  Apple_HFS OSX-YS                  42.4 GB    disk0s4    5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5 /dev/disk1    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:     FDisk_partition_scheme                        *750.2 GB   disk1    1:                 DOS_FAT_16 DellUtility             74.0 MB    disk1s1    2:               Windows_NTFS RECOVERY                10.7 GB    disk1s2    3:               Windows_NTFS OS                      739.3 GB   disk1s3 OSX-YS-Pro:~ MacNB$ OSX-YS-Pro:~ MacNB$ sudo fdisk440 /dev/disk1 Password: Disk: /dev/disk1 geometry: 91201/255/63 [1465149168 sectors] Signature: 0xAA55          Starting       Ending  #: id  cyl  hd sec -  cyl  hd sec [     start -       size] ------------------------------------------------------------------------  1: 06    0   1   1 -    8 254  63 [        63 -     144522] DOS > 32MB    2: 07    9  13   5 - 1023 254  63 [    145408 -   20971520] NTFS         *3: 07 1023 254  63 - 1023 254  63 [  21116928 - 1444028416] NTFS          4: 00    0   0   0 -    0   0   0 [         0 -          0] unused       OSX-YS-Pro:~ MacNB$    FDISK shows that the 3rd partition is ACTIVE on the Vista drive (disk1).
       
      Clover is installed on EFI partition on the OS X drive (disk0).
       
      Config.plist attached.
      debug.log attached.
       
      If I boot from a Chameleon USB-stick, I can select the OS partition and it boots, but Clover does not.
       
      Edit: I can boot Vista via the BIOS by hitting F12 and selecting the vista hdd.
      screenshot0.bmp
      MacNB-debug.log.zip
      MacNB-config.plist.zip
      MacNB-530-Generic.zip
    • By Soeren_DK
      Hi there.
      I'm new to this site but not totally new to hack. I've had a hack since 10.4 and the latest version I ran was 10.9, not totally fixed but it worked to what I needed. Now I want to make the machine run as good as it can. I can see there has been a lot of changes/upgrades/new solutions since I installed my hack and I have a hard time to catch up.  
      I've been able to boot and install macOSX and now I need the POST installation.
      I tried to install the clover EFI boot loader with these settings:
       
      and found the DSDT.aml and SSDT-0.aml from HERE
      found the apfs.efi
      and placed it in EFI -> EFI -> CLOVER -> driver64
      and these kext in here:

       
       
      But when I boot it up this is the first bootscreen I have. No partions, no mouse control, no nothing.

      if I exit clover this screen appear.

      and now everything works. 
       
      What is wrong?
      Cheers
      Soren
×