Contribute
Register

How to build your own iMac Pro [Successful Build/Extended Guide]

Status
Not open for further replies.

kgp

Retired
Joined
May 30, 2014
Messages
6,783
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
got it, sorry for my peanut-sized brain but why do we need the aml anyway? for me it seems to work properly without that

If you feel that you don't need the SSDT-X299-iMacPro.aml, don't use it ;).. it just implements the respective PCI device drivers.. e.g., does HDAU work with your GTX 980 without the SSDT-X299-iMacPro.aml, after removing NvidiaGraphicsFixup.kext from your EFI-Folder, which in fact is obsolete when using SMBIOS iMac Pro1,1? ;) Does your rig properly sleep and wake without the SSDT-X299-iMacPro.aml? Obviously you don't use a TBEX 3 with your Asus X299 TUF Mark 1, do you?
 
Joined
Jan 20, 2011
Messages
92
Motherboard
Asus X299 TUF Mark 1
CPU
i7-7800X
Graphics
NITRO+ RX 590 8G G5 SE
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
  4. Mac Pro
Classic Mac
  1. iMac
Mobile Phone
  1. Android
  2. iOS
If you feel that you don't need the SSDT-X299-iMacPro.aml, don't use it ;).. it just implements the respective PCI device drivers.. e.g., does HDAU work with your GTX 980 without the SSDT-X299-iMacPro.aml, after removing NvidiaGraphicsFixup.kext from your EFI-Folder, which in fact is obsolete when using SMBIOS iMac Pro1,1? ;) Does your rig properly sleep and wake without the SSDT-X299-iMacPro.aml? Obviously you don't use a TBEX 3 with your Asus X299 TUF Mark 1, do you?
thanks you, you're right don't have NvidiaGraphicsFixup.kext anymore also don't use HDAU, have an Audio Interface. I have a very minimal setup with one NVME m2 as macos system drive, one graphics card, Revodrive 3 x2 :) with windows and another 2tb ssd for workparts(ausio data, footage). SO did I got it right, when I download X299-iMacPro.aml(untouched) it is adopted to your rig and if some PCI device isn't working properly on my end I have to adjust/adopt it, right?
 
Joined
Jul 25, 2012
Messages
38
Motherboard
Asus Prime X299 Deluxe
CPU
I9 7900X
Graphics
MSI GeForce GTX 1080 SEA HAWK EK X
Ok got a weird one, I have been playing around with the AML files a lot and I just noticed when I apply the SSDT-XOSI.aml to my patched directory, I get strange behaviors on some of my devices in windows 10.

For example in pic-slot 6 I have an Asus 10gb Nic installed, this works great under macOS and used to work in windows before I added the SSDT-XOSI.aml to my patched directory.

I researched the file and it looks like it doesn't account for the latest builds of windows 10, it cuts off at windows 2015, the latest build of windows 10 is window 2017 as documented by Microsoft here in their "How to Identify the Windows Version in ACPI by Using _OSI" document found here, http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx.

I went ahead and added the latest builds to my SSDT-XOSI.aml but Windows 10 is still having issues recognizing all of my PCI devices. I am wondering if anyone else is having similar issues with their Windows 10 installs. I have a few programs I have to use in windows and I use my 10gb Nic to transfer 100's of gbs a day so I need to get it back up and going, just not sure where else to look. Here is a copy/paste of my current SSDT-XOSI.aml.
Code:
/*
 * Intel ACPI Component Architecture
 * AML/ASL+ Disassembler version 20160422-64(RM)
 * Copyright (c) 2000 - 2016 Intel Corporation
 *
 * Disassembling to non-symbolic legacy ASL operators
 *
 * Disassembly of iASLIX82MI.aml, Tue Feb 13 17:58:48 2018
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x000000CC (204)
 *     Revision         0x01
 *     Checksum         0xC5
 *     OEM ID           "mfc88"
 *     OEM Table ID     "XOSI"
 *     OEM Revision     0x00000000 (0)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20160422 (538313762)
 */
DefinitionBlock ("", "SSDT", 1, "mfc88", "XOSI", 0x00000000)
{
    Method (XOSI, 1, NotSerialized)
    {
        Store (Package (0x10)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2015",
                "Windows 2016",
                "Windows 2017"
            }, Local0)
        Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}
 
Last edited:

kgp

Retired
Joined
May 30, 2014
Messages
6,783
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
thanks you, you're right don't have NvidiaGraphicsFixup.kext anymore also don't use HDAU, have an Audio Interface. I have a very minimal setup with one NVME m2 as macos system drive, one graphics card, Revodrive 3 x2 :) with windows and another 2tb ssd for workparts(ausio data, footage). SO did I got it right, when I download X299-iMacPro.aml(untouched) it is adopted to your rig and if some PCI device isn't working properly on my end I have to adjust/adopt it, right?

Yes, you have to adopt the SSDT-X299-iMacPro.aml in any case.. Drop the implementation of devices you do not use. Adopt the implementation of devices you use. Add implementation of devices not yet implement. A wrong or not suitable SSDT-X299-iMacPro.aml can be worse than not having any.. ;)
 

kgp

Retired
Joined
May 30, 2014
Messages
6,783
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Ok got a weird one, I have been playing around with the AML files a lot and I just noticed when I apply the SSDT-XOSI.aml to my patched directory, I get strange behaviors on some of my devices in windows 10.

For example in pic-slot 6 I have an Asus 10gb Nic installed, this works great under macOS and used to work in windows before I added the SSDT-XOSI.aml to my patched directory.

I researched the file and it looks like it doesn't account for the latest builds of windows 10, it cuts off at windows 2015, the latest build of windows 10 is window 2017 as documented by Microsoft here in their "How to Identify the Windows Version in ACPI by Using _OSI" document found here, http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx.

I went ahead and added the latest builds to my SSDT-XOSI.aml but Windows 10 is still having issues recognizing all of my PCI devices. I am wondering if anyone else is having similar issues with their Windows 10 installs. I have a few programs I have to use in windows and I use my 10gb Nic to transfer 100's of gbs a day so I need to get it back up and going, just not sure where else to look. Here is a copy/paste of my current SSDT-XOSI.aml.
Code:
/*
 * Intel ACPI Component Architecture
 * AML/ASL+ Disassembler version 20160422-64(RM)
 * Copyright (c) 2000 - 2016 Intel Corporation
 *
 * Disassembling to non-symbolic legacy ASL operators
 *
 * Disassembly of iASLIX82MI.aml, Tue Feb 13 17:58:48 2018
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x000000CC (204)
 *     Revision         0x01
 *     Checksum         0xC5
 *     OEM ID           "mfc88"
 *     OEM Table ID     "XOSI"
 *     OEM Revision     0x00000000 (0)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20160422 (538313762)
 */
DefinitionBlock ("", "SSDT", 1, "mfc88", "XOSI", 0x00000000)
{
    Method (XOSI, 1, NotSerialized)
    {
        Store (Package (0x10)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2015",
                "Windows 2016",
                "Windows 2017"
            }, Local0)
        Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}

I don't understand how anything you do under OSX can affect your Windows 10 partition on a dual boot system. Do I simply misunderstand what you are trying to transmit above?
 
Joined
Oct 19, 2015
Messages
129
Motherboard
ASUS Prime X299 Deluxe
CPU
i9-7980XE
Graphics
Vega FE
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
Hey All,

I was doing a fresh install on my 2 x299 systems. Both are identical to the system in my profile. I flashed both bios, I set all the bios settings in accordance with the guide, synced the bios settings on both ASUS Deluxes. The first machine, everything installed fine, the second machine, I get allocation errors 100% of the time when trying to install. I recreating the install USB on another flash drive, same deal. All drives booted on that machine have allocation errors. I even tried swapping the SSD from the working system into the non working system, and same deal, allocation error on boot. If I place the install USB on the working system, I can boot into installer. On the other system, allocation errors. There should be no difference, its the exact same hardware. Am I missing something?

I tried switching the AptioMemoryFix.efi to OsxAptioFix3Drv-64.efi, but nothing changes, same allocation error (Error loading kernel cache (0x9)).

System 1: (No Allocation Errors)
7980XE
ASUS Deluxe (Flashed)
GTX Titan X (Maxwell)
32GB Corsair RAM
NVMe Samsung SSD

System 2: (Allocation Errors, no matter what drive)
7980XE
ASUS Deluxe (Flashed)(Loaded same bios settings from System 1)
GTX Titan X (Maxwell)
32GB Corsair RAM
NVMe Samsung SSD

I am going to try flashing the bios and clearing cmos.
 
Joined
Jan 13, 2018
Messages
22
Motherboard
Gigabyte Aorus Gaming 9
CPU
i9-7920X
Graphics
Vega Frontier Edition
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. Android
  2. iOS
I do not understand the question.. What does NVMe and SSD TRIM support has to do with an applications? What you apply is a kext patch...

kgp

I mean that if I install an application in macOS that makes the TRIM enabler. Then would the patch be necessary?
 

kgp

Retired
Joined
May 30, 2014
Messages
6,783
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
kgp

I mean that if I install an application in macOS that makes the TRIM enabler. Then would the patch be necessary?

Is there any app able to do this, which would also automatically load on login? I guess the kextpatch is the simplest way to do it anyway..
 
Joined
Oct 19, 2015
Messages
129
Motherboard
ASUS Prime X299 Deluxe
CPU
i9-7980XE
Graphics
Vega FE
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
Hey All,

I was doing a fresh install on my 2 x299 systems. Both are identical to the system in my profile. I flashed both bios, I set all the bios settings in accordance with the guide, synced the bios settings on both ASUS Deluxes. [...]

I tried switching the AptioMemoryFix.efi to OsxAptioFix3Drv-64.efi, but nothing changes, same allocation error (Error loading kernel cache (0x9)).

System 1: (No Allocation Errors)
7980XE
ASUS Deluxe (Flashed)
GTX Titan X (Maxwell)
32GB Corsair RAM
NVMe Samsung SSD

System 2: (Allocation Errors, no matter what drive)
7980XE
ASUS Deluxe (Flashed)(Loaded same bios settings from System 1)
GTX Titan X (Maxwell)
32GB Corsair RAM
NVMe Samsung SSD

I am going to try flashing the bios and clearing cmos.

Solved my own problem, flashed back the the bios to previous ver. then refreshed to KGPs current X299.CAP. No more allocation issues. Install running smoothly. Conspiracy OVER. :D
 
  • Like
Reactions: kgp

kgp

Retired
Joined
May 30, 2014
Messages
6,783
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Solved my own problem, flashed back the the bios to previous ver. then refreshed to KGPs current X299.CAP. No more allocation issues. Install running smoothly. Conspiracy OVER. :D

:lol:
 
Status
Not open for further replies.
Top