iMac Pro X299 - Live the Future now with macOS 10.14 Mojave [Successful Build/Extended Guide]

[kgp]

sorry, the last screenshot had a bad resolution

Same KP as before.

I cannot find anything suspicious in your BIOS settings or EFI-Folder. You still did not disable EIST, but it cannot be the source for the KP though.

Did you try to use boot flag npci=0x2000 or disable above 4G decoding? However, the KP seems anyway CPU related.

Are you booting with the correct EFI-Folder? During Boot Splash Screen press F8 and select the drive with the appropriate EFI-Folder. Just to be at the save side.

 

[Maywitt]

I cannot find anything suspicious in your BIOS settings or EFI-Folder. You still did not disable EIST, but it cannot be the source for the KP though.

Did you try to use boot flag npci=0x2000 or disable above 4G decoding? However, the KP seems anyway CPU related.

Are you booting with the correct EFI-Folder? During Boot Splash Screen press F8 and select the drive with the appropriate EFI-Folder. Just to be at the save side.

npci=0x2000: same KP.

+ EIST was disabled: same KP

I've only one EFI-Partition on my USB Flash Drive. In USB port 2.0 or 3.1 .

I have try make a screenshot from the boot-process. Unfortunately, I don't know any way to log the boot process. And a screenshot from Clover before the Mainscreen.

EDIT: Disable "Above 4G..." is on this MB not possible - Bios Q-Code "d4".

 

[kgp]

npci=0x2000: same KP.

+ EIST was disabled: same KP

I've only one EFI-Partition on my USB Flash Drive. In USB port 2.0 or 3.1 .

I have try make a screenshot from the boot-process. Unfortunately, I don't know any way to log the boot process. And a screenshot from Clover before the Mainscreen.

EDIT: Disable "Above 4G..." is on this MB not possible - Bios Q-Code "d4".

But you might also have a system disk with an EFI-Folder and likely also other disks with EFI-Folders? Thus, if you would not boot by default with the EFI-Folder on your USB Flash Drive but instead with any other EFI-Folder on any other disk, all your modifications performed in the EFI-Folder on your USB Flash Drive would remain without any effect.
Do you know what I mean?

Therefore, press F8 during the BIOS Splash Screen, select the USB Flash Drive in the BIOS boot menu to boot from its EFI-Folder and finally select the macOS Installer partition on your USB Flash Drive in the Clover boot menu to start the MacOS Installation.

BIOS Boot menu (F8) and Clover boot menu are not the same thing.

Given your actual BIOS settings, you boot your system each time with the EFI-Folder on Patriot Memory PMAP without any additional F8 interaction. Is this actually your macOS Flash drive installer and adequate EFI-Folder?

Honestly your KP information looks like if TSCAdjustReset.kext would not be present or simply ignored.

 

[perfecto245]

https://github.com/KGP/XHC-USB-Kext-Library

You will find fully implemented and truncated 15-port kexts for the Asus X299 Prime-A.

Awesome! Thanks! so do I just add this usb kext to the EFI folder, and disable the 3 new patch parameters in the config.plist? or do they have to run along with the kext? are all my ports going to work as is ?

Thanks mate

 

[kgp]

Awesome! Thanks! so do I just add this usb kext to the EFI folder, and disable the 3 new patch parameters in the config.plist? or do they have to run along with the kext? are all my ports going to work as is ?

Thanks mate

If you want to use all ports, you need to implement the fully implemented kext and enable all 3 USB port limit patches, with the drawback that your system will not be anymore vanilla, because you will have to modify the 3 USB port limit patches before or immediately after each macOS update.

If you want to have a vanilla system, disable the 3 USB port limit patches and use the truncated 15-port kext instead, with the drawback that one internal USB3.0 heather and one external USB2.0 back-panel connector will be non-functional.

Clear enough?

 

[Maywitt]

But you might also have a system disk with an EFI-Folder and likely also other disks with EFI-Folders? Thus, if you would not boot by default with the EFI-Folder on your USB Flash Drive but instead with any other EFI-Folder on any other disk, all your modifications performed in the EFI-Folder on your USB Flash Drive would remain without any effect.
Do you know what I mean?

Therefore, press F8 during the BIOS Splash Screen, select the USB Flash Drive in the BIOS boot menu to boot from its EFI-Folder and finally select the macOS Installer partition on your USB Flash Drive in the Clover boot menu to start the MacOS Installation.

BIOS Boot menu (F8) and Clover boot menu are not the same thing.

Given your actual BIOS settings, you boot your system each time with the EFI-Folder on Patriot Memory PMAP without any additional F8 interaction. Is this actually your macOS Flash drive installer and adequate EFI-Folder?

Patriot Memory PMAP is my USB Flash Drive. The second drive inside is the EVO 970 1TB - fresh and empty.

And how can I load to force the TSCAdjustReset.kext ?

I tested my system in the last minutes with an other USB Flash Drive (create with UniBeast, change the EFI) - same KP.

 

[kgp]

Patriot Memory PMAP is my USB Flash Drive. The second drive inside is the EVO 970 1TB - fresh and empty.

And how can I load to force the TSCAdjustReset.kext ?

I tested my system in the last minutes with an other USB Flash Drive (create with UniBeast, change the EFI) - same KP.

You should not create your USB Flash Drive with UniBeast but exactly follow and apply the individual steps outlined in my guide for the macOS USB Flash Drive Installer creation. No need to use UniBeast at all.

 

[Maywitt]

You should not create your USB Flash Drive with UniBeast but exactly follow and apply the individual steps outlined in my guide for the macOS USB Flash Drive Installer creation. No need to use UniBeast at all.

My first USB (Patriot Memory) was created after your instruction. the second USB was a desperate attempt.

 

[kgp]

My first USB (Patriot Memory) was created after your instruction. the second USB was a desperate attempt.

Well, maybe the other two guys can help you further. Apparently, they are successfully running the Deluxe II already but likely with different CPUs? I cannot find anything else suspicious in your EFI-Folder and BIOS configuration that could prevent your system from boot. You are using the actual firmware version for the Deluxe II?

The weird thing is that you even confirmed by yourself that everything was working until you removed the NVMe with the windows installation.

@mcity: it was my first step: I've install win 10 1803 without problems on a EVO 970 1TB M2 in Slot M2_3. No errors. Then I remove the M2_Disk. Since then I've the problems with the OSX install.

Why did you remove the EVO 970 at all? Interestingly, the EVO 970 is still configured as one of your boot drives in your BIOS. My question now is, if the EVO 970 still contains your windows installation, which drive is the destination for your macOS Installation? Apparently there is no other drive connected to your system that could be the destination of your macOS Installation.

Further questions: Did you perform an UEFI or Legacy installation of Windows? Did you disconnect all other drives then the destination drive for your widows installation before performing the windows installation? Finally did you reformat the EVO 970 with HFS+ and a GUID table, if the drive previously contained a windows installation?

 

[Maywitt]

Well, maybe the other two guys can help you further. Apparently, they are successfully running the Deluxe II already but likely with different CPUs? I cannot find anything else suspicious in your EFI-Folder and BIOS configuration that could prevent your system from boot. You are using the actual firmware version for the Deluxe II?

The weird thing is that you even confirmed by yourself that everything was working until you removed the NVMe with the windows installation.



Why did you remove the EVO 970 at all? Interestingly, the EVO 970 is still configured as one of your boot drives in your BIOS. My question now is, if the EVO 970 contains your windows installation, which drive is the destination for your macOS Installation. Apparently there is no other drive connected to your system that could be the destination of your macOS Installation.

oh sorry, it's a misunderstanding: at the first I install a win10 OS - it's was my test of a absolute new system. Win10 run perfectly and without errors.I thought the windows hard disk disturbs the MAcOS installation. I remove the NVMe with Windows and insert an empty NVMe for MacOS. You know the rest...