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

[alexmenn]

Hmm.. seems you just copied all SSDTs without any adaptations. Those which are compliant with onboard devices work. But all others fail. Also you use SSDTs you should not use at all because you do not have such devices: e.g. SSDT-X99-X540-T1.aml, SSDT-X99-TB3HP.aml, SSDT-X99-P2EI0G-2T.aml, SSDT-X99-ACQU.aml..

Then you use two Vega SSDTs at the same time: i.e. SSDT-X99-Vega-Fontier.aml and SSDT-X99-Vega64.aml, which is simply a no go by definition . In addition you use the RadeonVegaLowFansSpeed.kext, which is not meant to be used in line with any Vega SSDT.

Either use SSDT-X99-Vega64.aml and remove the power table implementation, if you are not content with the implemented OC settings, or just use RadeonVegaLowFansSpeed.kext, if you think that this is the better approach.

However, never use two Vega SSDTs or any kext in addition. Following your PCI snapshot, in consequence none of the Vega SSDTs is loaded at boot. Just use one with the correct ACPI path and ACPI replacements for your system and slot configuration or just use the kext only, or neither use any Vega SSDT nor Vega kext at all.

Some final advise: It is better not to use any SSDT instead of implementing SSDTs which are not needed or not properly adopted.

I hope this helps somewhat, my friend..

Ok , I will fix it.

Any clue about bluetooth problems?

These are my ssdt now. What do you mean with "remove the power table implementation"? I simply deleted all SSDT you mean and RadeonVegaLowFansSpeed.kext, is ok now?

 

[kgp]

Ok , I will fix it.

Any clue about bluetooth problems?

These are my ssdt now. What do you mean with "remove the power table implementation"? I simply deleted all SSDT you mean and RadeonVegaLowFansSpeed.kext, is ok now?View attachment 385353

Use the Vega64-SSDT attached, as it does not implement any load table. But you have to adopt its ACPI path and and ACPI replacements to your system and slot configuration in concordance with your ACPI table information available from IOREG. This small guideline might help you in doing the latter. BTW.. you need to do this for all SSDTs implemented. Always verify and confirm a proper SSDT implementation by means of loaded PCI drivers (section "PCI" of Apple's system report) and implement devices in your ACPI table (IOREG). Do a stepwise implementation of each respective SSDTs and always check if everything under IROEG and "PCI"is implemented as defined within the SSDT. Otherwise modify your SSDT in concordance with your IOREG information.

If despite the small guideline you do not know at all what to do, better don't use any SSDT.

The funny thing is, that at least the ARPT SSDT seems properly implemented and the respective driver also successfully loaded under section "PCI" of Apple's system report. Thus the SSDT is certainly not the problem for your BT issues. However, you know that to make the bluetooth part of your adapter work at all, you need to connect the respective USB cable to some working USB2.0 connector/header. You are using the 15-port kext for the ASUS X99-A II, thus check if the HS port of the USB2.0 connector/header the USB cable currently is connected with, is also part of the truncated kext and if the respective USB2.0 connector/header is functional at all.

 

[alexmenn]

Oh okay. The bluetooth is connected to the same usb header 2.0 of mobo I used in 10.13.6 SU and not its not working. I've checked your guide, and this header works with your kexts. Im using USB1314 with bluetooth.

So weird...

BTW, how can you see gpu idle in 46 degrees while I see 86 allways? something must be wrong with the gpusensors.kext

With the SSDT-x99-vega64.aml all my vega64 fans are very loud. I think I have to fix aml first following your guide.

 

[kgp]

Oh okay. The bluetooth is connected to the same usb header 2.0 of mobo I used in 10.13.6 SU and not its not working. I've checked your guide, and this header works with your kexts. Im using USB1314 with bluetooth.

So weird... View attachment 385356

And you also changed USB connector numbers of HS13 and HS14 to 255? They are 0 by default in the kext for the most general case.

The reason why BT does not work in your case in my opinion is USB related. The ARPT PCI driver is properly loaded, thus the SSDT should not be the source of your issues.

 

[alexmenn]

And you also changed USB connector numbers of HS13 and HS14 to 255? They are 0 by default in the kext for the most general case.

The reason why BT does not work in your case in my opinion is USB related. The ARPT PCI driver is properly loaded, thus the SSDT should not be the source of your issues.

Let me try. My mobo is the same as yours, so, any sense. I have my vega64 in first PCI slot.

 

[kgp]

Let me try. My mobo is the same as yours, so, any sense. I have my vega64 in first PCI slot.

View attachment 385357

Upload an IOREG.save of your system without any SSDT and Whatevergreen in your EFI-Folder at boot. The ACPI table on some X99-A II ports is flipped between PCIEX16_1 and PCIEX16_4

Anyway, if the default ACPI path and ACPI replacements in the default Vega SSDT are valid for Slot-1 of your motherboard, the GFX0 and HDAU PCI drivers also should be properly implemented and loaded under "PCI", which given your former PCI snapshot was definitely not the case.

Should look like such

and not such

if the Vega SSDT has been properly adopted and implemented.

 

[kgp]

BTW, how can you see gpu idle in 46 degrees while I see 86 allways? something must be wrong with the gpusensors.kext

With the SSDT-x99-vega64.aml all my vega64 fans are very loud. I think I have to fix aml first following your guide.

First we have to ensure that SSDT-x99-vega64.aml is properly implemented on your system. Then you can implement in the SSDT a load table generated with VGTab that fulfils your needs and requirements. Without any load table your GPU performance and fan behaviour will be factory default!

Concerning the 86 deg C you constantly see under iStatMenus, it might well be that the device-ID of your GPU is not yet considered in the source code for the gpusensors.kext. If you tell me your GPU device-ID, I can implement the latter in the source code and provide you with a new gpusensors.kext that also works with your GPU. No problem.Until then you can also check your GPU temps under Heaven or Valley. These values should be roughly accurate in any case, but carefully observe GPU temps when performing Heaven or Valley benchmarks until we are sure about your GPU IDLE temps!

 

[alexmenn]

First we have to ensure that SSDT-x99-vega64.aml is properly implemented on your system. Then you can implement in the SSDT a load table generated with VGTab that fulfils your needs and requirements. Without any load table your GPU performance and fan behaviour will be factory default!

Concerning the 86 deg C you constantly see under iStatMenus, it might well be that the device-ID of your GPU is not yet considered in the source code for the gpusensors.kext. If you tell me your GPU device-ID, I can implement the latter in the source code and provide you with a new gpusensors.kext that also works with your GPU. No problem.Until then you can also check your GPU temps under Heaven or Valley. These values should be roughly accurate in any case, but carefully observe GPU temps when performing Heaven or Valley benchmarks until we are sure about your GPU IDLE temps!

Ok thx! here you are my device id!

Modelo de chipset: Radeon RX Vega 64
Tipo: GPU
Bus: PCIe
Anchura de canal PCIe: x16
VRAM (dinámica, máx.): 8176 MB
Fabricante: AMD (0x1002)
ID del dispositivo: 0x687f
ID de la revisión: 0x00c1

Ive done some checks. If I boot to 10.13.6 from my backup, bluetooth doesnt work too. It worked with gtx 1080 connected, not with vega 64. I think is a pci bandwith problem, could be? I've tried to move the combo to full-size pci instead of mini-pci in mobo but then mac doesnt detect it.

Let me restart without ssdt and without whatevergreen and Ill come back with results.

 

[alexmenn]

@kgp here you are my ioreg after boot without ssdt and without whatevergreen (only hdmi works, I think its ok if I boot without whatevergreen)

 

[kgp]

Ok thx! here you are my device id!

Modelo de chipset: Radeon RX Vega 64
Tipo: GPU
Bus: PCIe
Anchura de canal PCIe: x16
VRAM (dinámica, máx.): 8176 MB
Fabricante: AMD (0x1002)
ID del dispositivo: 0x687f
ID de la revisión: 0x00c1

View attachment 385385
Ive done some checks. If I boot to 10.13.6 from my backup, bluetooth doesnt work too. It worked with gtx 1080 connected, not with vega 64. I think is a pci bandwith problem, could be? I've tried to move the combo to full-size pci instead of mini-pci in mobo but then mac doesnt detect it.

Let me restart without ssdt and without whatevergreen and Ill come back with results.

In order to use the fully implemented XHC USB kext KGP-iMacPro-ASUS-X99AII-XHCI.kext, you must enable the USB port limit patches in your config.plist.

BTW.. I hope you are also using the 10.14.3 X99 EFI-Folder distribution with the correct USB port limit patches implement. They are disabled by default.

I would not know how the change from Nvidia to Vega could affect your BT functionality.

To start without SSDTs and without Whatevergreen is a good approach. If you could upload a an IOREG.save of such configuration as mentioned above, I definitely could see many things clearer and provide further help.

Your GPU device-ID seems to be 0x687f. Let me check on that the gpusensor.kext source code and come back to you.