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

[izo1]

"hours"?

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

Don't give up man!

20+ hours just trying to get past the install bar.

Thankfully I got into this thread late so people already had it running successfully

Thanks for all your hard work everyone.

 

[kgp]

20+ hours just trying to get past the install bar.

Thankfully I got into this thread late so people already had it running successfully

Thanks for all your hard work everyone.

@izo1 could you please provide your Skylake-X/X299 system specs (mobo, cpu, gpu) in either your profile or signature?

Many thanks in advance,

KGP

 

[Bagi1992]

I redownloaded the installer with the script, I made a fresh installer with terminal but I still can't see the USB in Clover.

Is that correct after make the USB bootable?

Last login: Mon Jan 29 11:01:25 on ttys000
Bagis-iMac:~ bagi1992$ cd /Volumes/USB_VOLUME
-bash: cd: /Volumes/USB_VOLUME: No such file or directory
Bagis-iMac:~ bagi1992$ mkdir .IABootFiles
mkdir: .IABootFiles: File exists
Bagis-iMac:~ bagi1992$ cd .IABootFiles
Bagis-iMac:.IABootFiles bagi1992$ cp /Volumes/USB_VOLUME/System/Library/CoreServices/boot.efi
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
       cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
Bagis-iMac:.IABootFiles bagi1992$

 

[paulotex]

Is that correct after make the USB bootable?

No!

You have to use the real USB name, not "USB_VOLUME". And so you got the error:
"-bash: cd: /Volumes/USB_VOLUME: No such file or directory"

If your USB is called
"Super USB I Like It Very Much"
then you have to use:
cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much

You have to use a "\" before each space.

And your copy command is also wrong, you forgot the isolated dot "." at the end. This means the destination is the current directory. So all together:

cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much
mkdir .IABootFiles
cd  .IABootFiles
cp /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much/System/Library/CoreServices/boot.efi .

 

[kgp]

I redownloaded the installer with the script, I made a fresh installer with terminal but I still can't see the USB in Clover.

Is that correct after make the USB bootable?

Last login: Mon Jan 29 11:01:25 on ttys000
Bagis-iMac:~ bagi1992$ cd /Volumes/USB_VOLUME
-bash: cd: /Volumes/USB_VOLUME: No such file or directory
Bagis-iMac:~ bagi1992$ mkdir .IABootFiles
mkdir: .IABootFiles: File exists
Bagis-iMac:~ bagi1992$ cd .IABootFiles
Bagis-iMac:.IABootFiles bagi1992$ cp /Volumes/USB_VOLUME/System/Library/CoreServices/boot.efi
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
       cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
Bagis-iMac:.IABootFiles bagi1992$

No, of course not. You have to substitute USB_VOLUME by the name of your USB_VOLUME. With the unchanged command, the command will just do nothing as the path you provide is totally wrong. Do you understand what I mean?

Already answered by @paulotex in parallel above. Thanks, man!

 

[izo1]

@izo1 could you please provide your Skylake-X/X299 system specs (mobo, cpu, gpu) in either your profile or signature?

Many thanks in advance,

KGP

Since it was a new system, I just added below.

Thanks!

 

[Bagi1992]

No!

You have to use the real USB name, not "USB_VOLUME". And so you got the error:
"-bash: cd: /Volumes/USB_VOLUME: No such file or directory"

If your USB is called
"Super USB I Like It Very Much"
then you have to use:
cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much

You have to use a "\" before each space.

And your copy command is also wrong, you forgot the isolated dot "." at the end. This means the destination is the current directory. So all together:

cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much
mkdir .IABootFiles
cd  .IABootFiles
cp /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much/System/Library/CoreServices/boot.efi .

The last time I changed it for "Install macOS High Sierra" but It's not enough Sorry guys I don't know anything about coding

So, I guess, I managed it, right?

Last login: Mon Jan 29 11:22:09 on ttys000
Bagis-iMac:~ bagi1992$ cd /Volumes/Install\ macOS\ High\ Sierra
Bagis-iMac:Install macOS High Sierra bagi1992$ mkdir .IABootFiles
mkdir: .IABootFiles: File exists
Bagis-iMac:Install macOS High Sierra bagi1992$ cd .IABootFiles
Bagis-iMac:.IABootFiles bagi1992$ cp /Volumes/Install\ macOS\ High\ Sierra/System/Library/CoreServices/boot.efi .
Bagis-iMac:.IABootFiles bagi1992$

 

[AnaktuvGod]

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.

In regards to the occasional kp'ing, No intensive tasks at all.... simply just let the computer run. I would say it was running for over 24+ but not more than 2 days without panicking. And it seemed to have happened 2x within 1 Hour from the first panic. Same message as I posted and stated before. All typical safe mode bios boot / Mac OS X shut down error popup like a normal crash. Dunno...

Now thing is I need to test it like I said for longer periods of time with ...

A.) Power set to never shut down the entire system (monitor & iX299 Pro)

B.) Power set to never shut down but allow to the monitor to sleep

C.) Power set for monitor and iX299 Pro to sleep.

* This is the name I reference all of our boards contained in this thread. (I just slapped an i in front since most if not all of us is using the iMac Pro 1,1 SMBIOS

I can tell you now it seems to happen mostly upon waking from a sleep state. Every time it crashes I notice the display doesn't wake and I have to hard reboot. Then I get hit with that KP reason and explanation from Mac that I posted.

 

[AnaktuvGod]

@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

I want to note and cancel out the OC theory as I don't overclock...Well at the moment but no overclocking at the moment...7900x and 2400 ram... same $#!+ different toilet.

 

[izo1]

If I take off -v argument to just see Apple logo during boot, Timeout stops working (so it always shows the Clover menu)