Contribute
Register

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

Status
Not open for further replies.
kgp

kgp

Retired
Joined
May 30, 2014
Messages
6,765
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
dk1306 said:
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?
Click to expand...

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

kgp

Retired
Joined
May 30, 2014
Messages
6,765
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
rudey said:
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)))
    }
}
Click to expand...

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?
 
eiriasemrys

eiriasemrys

Joined
Oct 19, 2015
Messages
136
Motherboard
ASUS Sage WS II x299
CPU
i9-7980XE
Graphics
AMD Radeon 6900XT
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
  5. Mac 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.
 
maryhack2018

maryhack2018

Joined
Jan 13, 2018
Messages
30
Motherboard
Gigabyte Aorus Gaming 9
CPU
i9-7920X
Graphics
Vega Frontier
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. Android
  2. iOS
kgp said:
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...
Click to expand...

kgp

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

kgp

Retired
Joined
May 30, 2014
Messages
6,765
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
maryhack2018 said:
kgp

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

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

eiriasemrys

Joined
Oct 19, 2015
Messages
136
Motherboard
ASUS Sage WS II x299
CPU
i9-7980XE
Graphics
AMD Radeon 6900XT
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Mobile Phone
  1. iOS
eiriasemrys said:
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.
Click to expand...

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

kgp

Retired
Joined
May 30, 2014
Messages
6,765
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
eiriasemrys said:
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
Click to expand...

:lol:
 
rauan1

rauan1

Joined
Apr 25, 2016
Messages
208
Motherboard
Gigabyte Z390 Aorus Pro
CPU
i7-9700K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
rauan1 said:
It simply doesn't give me boot screen and comes back to bios config screen. I can see my USB partition in bios though.
You can check D.3.3 steps in the text file:

Rauan:Install MacOS High Sierra iMacRa1$ mkdir .IABootFiles
Rauan:Install MacOS High Sierra iMacRa1$ cd .IABootFiles
Rauan:.IABootFiles iMacRa1$ cp /Volumes/Install\ MacOS\ High\ Sierra/System/Library/CoreServices/boot.efi .
Rauan:.IABootFiles iMacRa1$ ls boot.efi
boot.efi

Can it be something else? I didn't find on my motherboard the option to choose XMP profile, it is not there.

3.) /M.I.T/Advanced Memory Settings/
a.) Extreme Memory Profile (X.M.P): Profile1
Click to expand...

I did follow section D.3.3 word by word and still not able to boot. I suspect that there is something else.
  • I tried two separate USB sticks, where both are detected by BIOS in config screen, but not visible for boot.
  • I tried two separate computers: iMac late 2012 and MacBook late 2013.
  • I tried both ways to create bootable usb: with terminal script (sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction) and with InstallDiskCreator.app
  • I also tried both createInstaller.sh and scripts only to create installer app in applications fodler.
I am sure it is most likely small stupid thing that I am missing or doing wrong, but just can't find it.
 
eiriasemrys

eiriasemrys

Joined
Oct 19, 2015
Messages
136
Motherboard
ASUS Sage WS II x299
CPU
i9-7980XE
Graphics
AMD Radeon 6900XT
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Mobile Phone
  1. iOS
rauan1 said:
I did follow section D.3.3 word by word and still not able to boot. I suspect that there is something else.
  • I tried two separate USB sticks, where both are detected by BIOS in config screen, but not visible for boot.
  • I tried two separate computers: iMac late 2012 and MacBook late 2013.
  • I tried both ways to create bootable usb: with terminal script (sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction) and with InstallDiskCreator.app
  • I also tried both createInstaller.sh and scripts only to create installer app in applications fodler.
I am sure it is most likely small stupid thing that I am missing or doing wrong, but just can't find it.
Click to expand...

Have you looked into the .IABootFiles folder on your USB and confirmed the presence of boot.efi? Must have hidden files showing in finder to do so.
 
rauan1

rauan1

Joined
Apr 25, 2016
Messages
208
Motherboard
Gigabyte Z390 Aorus Pro
CPU
i7-9700K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
eiriasemrys said:
Have you looked into the .IABootFiles folder on your USB and confirmed the presence of boot.efi? Must have hidden files showing in finder to do so.
Click to expand...

This is what I get when I run ls:
Rauan:.IABootFiles iMacRa1$ ls boot.efi
boot.efi

I assumed that this is a prove. Should I check it somehow else?
 
Status
Not open for further replies.
Copyright © 2010 - 2023 tonymacx86 LLC
Top