Contribute
Register

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

Status
Not open for further replies.
This looks normal, you have 207 available slide values, so AptioMemoryFix can select any of those.

If you don't get the +++++ line, then that is probably because you are booting the normal 10.13.3 build with iMacPro board-id.

It also just says "boot may fail", thus I guess once the rest of the 10.13.3 (17D2047) installation is properly done it will work without any further issue.
 
@Thireus

I caught it this time. And fyi seems to have happened 2x today.

Anonymous UUID: DC634DD4-2409-FBCD-DA14-0469A37DAD80

Sun Jan 28 22:51:12 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff801996e349): Kernel trap at 0xffffff801998c6b4, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000070000f481328, CR3: 0x000000002fa3e000, CR4: 0x00000000003627e0
RAX: 0x000000007e008003, RBX: 0xffffff801a057320, RCX: 0x00000000000000e2, RDX: 0x0000000000000000
RSP: 0xffffffce5c2bbbf0, RBP: 0xffffffce5c2bbc20, RSI: 0x0000000000000003, RDI: 0xffffff801a0572c0
R8: 0x0000000100000201, R9: 0xffffff801d236036, R10: 0x0000000000000003, R11: 0xffffff8019f70eeb
R12: 0xffffff8019f78896, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffff8019f7887c
RFL: 0x0000000000010046, RIP: 0xffffff801998c6b4, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000070000f481328, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xfffffd000004c270 : 0xffffff801984f606 mach_kernel : _handle_debugger_trap + 0x506
0xfffffd000004c2c0 : 0xffffff801997c744 mach_kernel : _kdp_i386_trap + 0x114
0xfffffd000004c300 : 0xffffff801996e159 mach_kernel : _kernel_trap + 0x5e9
0xfffffd000004c380 : 0xffffff8019801120 mach_kernel : _return_from_trap + 0xe0
0xfffffd000004c3a0 : 0xffffff801984f03c mach_kernel : _panic_trap_to_debugger + 0x25c
0xfffffd000004c4d0 : 0xffffff801984edbc mach_kernel : _panic + 0x5c
0xfffffd000004c530 : 0xffffff801996e349 mach_kernel : _kernel_trap + 0x7d9
0xfffffd000004c6b0 : 0xffffff8019801120 mach_kernel : _return_from_trap + 0xe0
0xfffffd000004c6d0 : 0xffffff801998c6b4 mach_kernel : _xcpm_perf_bias_set + 0x294
0xffffffce5c2bbc20 : 0xffffff801998c9be mach_kernel : _xcpm_init + 0xde
0xffffffce5c2bbc60 : 0xffffff801997ac91 mach_kernel : _acpi_sleep_kernel + 0x471
0xffffffce5c2bbcd0 : 0xffffff7f9bd91fb8 com.apple.driver.AppleACPIPlatform : __ZN23AppleACPIPlatformExpert13sleepPlatformEv + 0x1ee
0xffffffce5c2bbd20 : 0xffffff7f9bd96415 com.apple.driver.AppleACPIPlatform : __ZN12AppleACPICPU7haltCPUEv + 0x75
0xffffffce5c2bbd40 : 0xffffff8019eb03f8 mach_kernel : __Z16IOCPUSleepKernelv + 0x248
0xffffffce5c2bbd90 : 0xffffff8019edddd5 mach_kernel : __ZN14IOPMrootDomain15powerChangeDoneEm + 0x335
0xffffffce5c2bbe00 : 0xffffff8019e7877b mach_kernel : __ZN9IOService8all_doneEv + 0x6fb
0xffffffce5c2bbe50 : 0xffffff8019e75968 mach_kernel : __ZN9IOService23actionPMWorkQueueInvokeEP11IOPMRequestP13IOPMWorkQueue + 0x878
0xffffffce5c2bbeb0 : 0xffffff8019e72993 mach_kernel : __ZN13IOPMWorkQueue17checkRequestQueueEP11queue_entryPb + 0x43
0xffffffce5c2bbef0 : 0xffffff8019e72822 mach_kernel : __ZN13IOPMWorkQueue12checkForWorkEv + 0x82
0xffffffce5c2bbf30 : 0xffffff8019e8ef42 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1e2
0xffffffce5c2bbf70 : 0xffffff8019e8e57c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffffce5c2bbfa0 : 0xffffff80198004f7 mach_kernel : _call_continuation + 0x17
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[C03BFA43-0B1C-3065-BAD7-EAD7EE152F84]@0xffffff7f9bd86000->0xffffff7f9be21fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[8794C760-FDD9-3664-ADED-4A9BBEC6E517]@0xffffff7f9b0e8000
dependency: com.apple.iokit.IOPCIFamily(2.9)[194AA5A0-E772-3515-A771-6DC41FB9A361]@0xffffff7f9a094000
dependency: com.apple.driver.AppleSMC(3.1.9)[C0EDA8D1-B854-3BE7-A2AF-DF27F893962D]@0xffffff7f9b0f1000

BSD process name corresponding to current thread: kernel_task
Boot args: darkwake=1 npci=0x2000 keepsyms=1 debug=0x100

Mac OS version:
17D2047

Kernel version:
Darwin Kernel Version 17.4.0: Tue Dec 19 10:52:05 PST 2017; root:xnu-4570.47.16~1/RELEASE_X86_64
Kernel UUID: 29EF1F85-10C5-3F25-AED6-5529E5948D42
Kernel slide: 0x0000000019400000
Kernel text base: 0xffffff8019600000
__HIB text base: 0xffffff8019500000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)

System uptime in nanoseconds: 1925513498818
last loaded kext at 250000240193: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f9cc1f000, size 69632)
last unloaded kext at 336747181780: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f9cc1f000, size 69632)
loaded kexts:
(none)

EOF
Model: iMacPro1,1, BootROM IMP11.0064.B30, 10 processors, 3.31 GHz, 128 GB, SMC 2.41f1
Graphics: NVIDIA GeForce GTX 1080 Ti, NVIDIA GeForce GTX 1080 Ti, PCIe, 11 GB
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2400 MHz, CRUCIAL, BLS16G4D240FSC.16FBR
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2400 MHz, CRUCIAL, BLS16G4D240FSC.16FBR
Memory Module: BANK 2/DIMM0, 16 GB, DDR4, 2400 MHz, CRUCIAL, BLS16G4D240FSC.16FBR
Memory Module: BANK 3/DIMM0, 16 GB, DDR4, 2400 MHz, CRUCIAL, BLS16G4D240FSC.16FBR
Memory Module: BANK 0/DIMM1, 16 GB, DDR4, 2400 MHz, G-Skill, F4-2400C15-16GVR
Memory Module: BANK 1/DIMM1, 16 GB, DDR4, 2400 MHz, G-Skill, F4-2400C15-16GVR
Memory Module: BANK 2/DIMM1, 16 GB, DDR4, 2400 MHz, G-Skill, F4-2400C15-16GVR
Memory Module: BANK 3/DIMM1, 16 GB, DDR4, 2400 MHz, G-Skill, F4-2400C15-16GVR
Bluetooth: Version 6.0.4f1, 3 services, 26 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
PCI Card: pci144d,a804, NVM Express Controller, AirPort@225,0,0
PCI Card: NVIDIA GeForce GTX 1080 Ti, Display Controller, PCI Slot 6@193,0,0
PCI Card: pci10de,10ef, Audio Device, PCI Slot 6@193,0,1
USB Device: USB 3.0 Bus
USB Device: ASM107x
USB Device: ASM107x
USB Device: AURA Custom Human interface
USB Device: Bluetooth HCI
USB Device: ASM107x
USB Device: Corsair K30A Gaming Keyboard
USB Device: Corsair M95 Gaming Mouse
USB Device: ASM107x
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
Thunderbolt Bus:

View attachment 309253

So, just to confirm, could you give us more detail about the issue? How long has the computer been running? Was there any intensive tasks running? Was there a message displayed when this happened?

I've already reported the issue there: #30 but I'm afraid that it won't help much, as it seems to be clearly related to our specific build.

Notice the following lines:

Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[C03BFA43-0B1C-3065-BAD7-EAD7EE152F84]@0xffffff7f874a6000->0xffffff7f87541fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[8794C760-FDD9-3664-ADED-4A9BBEC6E517]@0xffffff7f861d5000
dependency: com.apple.iokit.IOPCIFamily(2.9)[194AA5A0-E772-3515-A771-6DC41FB9A361]@0xffffff7f85494000
dependency: com.apple.driver.AppleSMC(3.1.9)[C0EDA8D1-B854-3BE7-A2AF-DF27F893962D]@0xffffff7f861de000

I've tried a couple of things recently to revolve it, but I don't have enough uptime to confirm if that worked, I'll let you know if it's the case.

Now the thing is, either it's related to our specific motherboard, or it's related to our Clover config... for that we need confirmation on this thread that people are actually able to run their machine for 24H+ straight without issue.
 
Would it be possible to get a video of this entire guide ? Some of the steps in the guide are confusing.

Would it be possible to get a video of the entire process ? Seems like it'd be a bit easier to see when you move from computer to computer.

I would not know, which of my instructions are confusing. If you just apply what is written there, everything should work as expected.

I personally do not have the time for making movies in addition. I am already in big delay with my parallel X99 thread and guide (which is still on 10.13.2 SA), as this Skylake-X/X299 thread lately calls my entire attention.

I am working nearly 16 hours a day on guide development and support. If I would have a regular job, which is still not the case at present, even the amount of work I am currently investing would be totally impossible.

I really hope on your comprehension.

Best regards,

KGP
 
The installer didn't create a recovery partition. Is it possible to do one?
 
I just can’t get this thing to work. This is sad. I spent a lot of money to build a new rig but it’s becoming a nightmare.

Already spent more than 20 hours and I can’t get the iMac pro version of High Sierra installed

Should I just do a regular vanilla macOS install instead?

"hours"? :lol:

If I remember well, to get my first successful boot it took me several days.

Don't give up man!
 
So, just to confirm, could you give us more detail about the issue? How long has the computer been running? Was there any intensive tasks running? Was there a message displayed when this happened?

I've already reported the issue there: #30 but I'm afraid that it won't help much, as it seems to be clearly related to our specific build.

Notice the following lines:

I've tried a couple of things recently to revolve it, but I don't have enough uptime to confirm if that worked, I'll let you know if it's the case.

Now the thing is, either it's related to our specific motherboard, or it's related to our Clover config... for that we need confirmation on this thread that people are actually able to run their machine for 24H+ straight without issue.

@Thireus, I think it might help to clarify the following:

I am running my build on a 24/7/365 base, i.e. I never turn it off. Everything works flawless and I never face any issues, KP or freezes. I also totally disabled any Sleep/Wake functionality, as Sleep/Wake still does not work flawless since 10.13.2.

Thus, the issues with the Rampage VI indeed might be build related. There might still remain some issues with your BIOS settings, especially with respect to OC. I recommend to further tune your AVX and Core Voltage settings and to stay with stock speeds until your system is rock solid.

It might be also necessary to further tune the Clover settings for this latter board, although I think the issues are rather related to the BIOS settings.

In any case, please let me know if I can help with further ideas or anything else that would help in solving your issues with the Rampage VI.

All the best,

KGP
 
Last edited:
still no 10.3.3 update on my app sote :(
starting to be scared that something is wrong with my config ...

Probably because you're still on a non-macpro1,1 build. Which build are you running?

C.f. #4231 and #4241
 
Last edited:
Hi guys!

I need a little help, yesterday I tried to fresh install 10.3.3 with iMacPro SMBIOS. I just made the installer disk, everything went fine, every step was OK. I disconnected every single SSD, HDD, only attached the USB installer and the final SSD which had Windows 10 previously. The USB installer disk simply doesn't show up in the Clover screen! I tried to reboot many times, but nothing. Anyway I grabbed my previous USB installer disk (10.3.0) and I just installed the system with iMac 17,1 SMBIOS. Then I updated to 10.3.3 via App Store, went fine. Then I tried to change the whole EFI folder for @kgp 's EFI, but oviously I changed the voodootscsync.kext (8 core, 16 thread, I put 15) and generated a new serial and SMUUID. Reboot and nothing. EFI is working, I can choose disk but after that, black screen, then the system shut down. I thought it has to be AptioMemoryFIX.efi problem, (I couldn't crate my own with the script, I attach the terminal message)

Code:
Last login: Sun Jan 28 23:48:50 on ttys000
Attilas-iMac:~ bagi1992$ rm -rf AptioMemFix
Attilas-iMac:~ bagi1992$ git clone https://github.com/Pavo-IM/AptioMemFix
Cloning into 'AptioMemFix'...
remote: Counting objects: 59, done.
remote: Compressing objects: 100% (39/39), done.
remote: Total 59 (delta 22), reused 56 (delta 20), pack-reused 0
Unpacking objects: 100% (59/59), done.
Attilas-iMac:~ bagi1992$ rm -rf ~/Desktop/AptioMemFix/
Attilas-iMac:~ bagi1992$ rm -rf ~/Desktop/AptioFix/
Attilas-iMac:~ bagi1992$ mv AptioMemFix/ ~/Desktop/
Attilas-iMac:~ bagi1992$ chmod +x ~/Desktop/AptioMemFix/AptioMemory_Builder.sh
Attilas-iMac:~ bagi1992$ ~/Desktop/AptioMemFix/AptioMemory_Builder.sh
Build script version 1.2
Missing or incompatible nasm!
Download nasm 2.13.02 from http://www.nasm.us/pub/nasm/releasebuilds/ and install it automatically?
Enter [Y]es to continue: y
Downloading NASM 2.13.02                                               -  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2262k  100 2262k    0     0  1006k      0  0:00:02  0:00:02 --:--:-- 1005k
-Password/
[DONE]
Missing mtoc or mtoc.NEW!
Install prebuilt mtoc and mtoc.NEW automatically?
Enter [Y]es to continue: y
Installing MTOC                                                        |unzip:  cannot find or open external/mtoc-mac64.zip, external/mtoc-mac64.zip.zip or external/mtoc-mac64.zip.ZIP.

so I tried to change for OsxAptioFix3Drv-64.efi. Doesn't work. Then I tried so many various of these efi files but I couldn't find any good. Even with my current system's OsxAptioFixDrv-64.efi + Test2.efi doesn't work on this system. So I don't really have idea now what to do, I can't boot this system with iMacPro SMBIOS, only with iMac 17,1 SMBIOS.

If someone could check my EFI folder, that would be nicely appreciate! I attach my current, working system's EFI too!

The build instructions for AptioMemoryFix.efi are missing mtoc-mac64.zip. You can try the following:

Code:
cd && \
git clone https://github.com/vit9696/AptioFixPkg.git && \
git clone https://github.com/Pavo-IM/AptioMemFix && \
cd AptioFixPkg && \
cp ../AptioMemFix/AptioMemory_Builder.sh . && \
chmod +x AptioMemory_Builder.sh && \
./AptioMemory_Builder.sh
 
@Thireus, I think it might help to clarify the following:

I am running my build on a 24/7/365 base, i.e. I never turn it off. Everything works flawless and I never face any issues, KP or freezes. I also totally disabled any Sleep/Wake functionality, as Sleep/Wake still does not work flawless since 10.13.2.

Thus, the issues with the Rampage VI indeed might be build related. There might still remain some issues with your BIOS settings, especially with respect to OC. I recommend to further tune your AVX and Core Voltage settings.

It might be also necessary to further tune the Clover settings for this latter board, although I think the issues are rather related to the BIOS settings.

In any case, please let me know if I can help with further ideas or anything else that would help in solving your issues with the Rampage VI.

All the best,

KGP

There is very little chance that it's OC-related. Both our KP dumps are similar. I think the issue might be the motherboard itself or a Clover hack we have in common that doesn't fit well.

We haven't even shared the same EFI.

Let's wait for what AnaktuvGod has to say.
 
  • Like
Reactions: kgp
There is very little chance that it's OC-related. Both our KP dumps are similar. I think the issue might be the motherboard itself or a Clover hack we have in common that doesn't fit well.

We haven't even shared the same EFI.

Let's wait for what AnaktuvGod has to say.

Totally fine with me. In any case, I really recommend to both of you to stabilise your systems for stock speeds first and subsequently deal with OC. Just to minimise the variables that could contribute to a destabilisation of your Rampage VI Systems.

Just try to help in solving your issues. Nothing else..
 
Status
Not open for further replies.
Back
Top