Asus X299 - Support

[dolgarrenan]

1) Yes
2) Yes
3) No -- never needed an SSDT for TB recognition with High Sierra & the original x299 Deluxe.
4) Yes (interestingly, even shows that the drivers loaded).
5) I fixed the 10G card issue, by installing the drivers from Multibeast.

Right now my only workaround is to boot to either Windows or Mojave desktop, and do a 'Restart'. I only need to do this for Mojave use --- TB3 devices work perfect in Windows even after a cold boot.

I'll have a look, keep you posted!

 

[mcity]

Yeah, but very difficult to get low latency ram at 3600.

A lot of applications tend to favor higher MHz.

I use this calculator and it seems that for my purposes the 3600 would be a better option.

Ram Latency Calculator

If anyone has any more insight would appreciate it.

3600 mhz @ CL 16 is my choice. Why RGB?

 

[Beezanteeum]

Don't you want to say that their laptops USED TO BE the best there was? Have you heard of flexgate and the butterfly keyboard problems on their Macbook Pro laptops?

…Not to mention thermal throttling on i9 based MacBook Pro

 

[dolgarrenan]

Here it is, give it a go @KevinAGI

 

[dolgarrenan]

1) Yes
2) Yes
3) No -- never needed an SSDT for TB recognition with High Sierra & the original x299 Deluxe.
4) Yes (interestingly, even shows that the drivers loaded).
5) I fixed the 10G card issue, by installing the drivers from Multibeast.

Right now my only workaround is to boot to either Windows or Mojave desktop, and do a 'Restart'. I only need to do this for Mojave use --- TB3 devices work perfect in Windows even after a cold boot.

No patches on DSDT section plus almost nothing is being loaded. Check @kgp thread and Github to find proper EFI files and such

 

[izo1]

3600 mhz @ CL 16 is my choice. Why RGB?

3600 at CL16 for 16GB sticks is prettyyyyy pricey

RGB because...it’s faster? Just kidding

 

[KevinAGI]

Here it is, give it a go @KevinAGI

Thanks that works and now I need to know why. It was very close to the one I rolled myself but not quite.
Where did the Device (DCLK) come from?
After your method statement you have an if statement. What does this do exactly?
The "name" buffer was different than what I had originally, where did I miss this?

If you want to just point me to some documentation that works to.

Thanks
Kevin

 

[dolgarrenan]

Where did the Device (DCLK) come from?

The device is not present in under the ACPI provided by Apple, I haven't had the chance to dig into a MacPro5,1 to check how the system states the device under the tree, but since there is nothing, we can just create it!
If you look under device RP08 in DSDT, you'll notice there is a device called D07E with address 0xff, this device needs to be "disabled" by means of ACPI patching, thus the "zero" scope value for D07E.

After your method statement you have an if statement. What does this do exactly?

Just another way of calling the DSM method

The "name" buffer was different than what I had originally, where did I miss this?

You didn't, information is scarce about ACPI table patching (there is no general guide unfortunately) so we need to push it a little by adding relevant or wanted information to the table so it can be shown properly o as we want.

If you want to just point me to some documentation that works to.

I wish there was more info about this elsewhere.. I'm afraid all the knowledge I have acquired has been through years of trial and error. One of the best sources of info about patching and such is @RehabMan, most things I know are through "experiments" I have done based on his work and other stuff I find around.
He has a very good guide on laptop patching that englobes many aspects of ACPI patching, I'd start there.

@kgp has done tons of work in this matter too, so his post is like a little big guide

Glad I could help!

 

[KevinAGI]

The device is not present in under the ACPI provided by Apple, I haven't had the chance to dig into a MacPro5,1 to check how the system states the device under the tree, but since there is nothing, we can just create it!
If you look under device RP08 in DSDT, you'll notice there is a device called D07E with address 0xff, this device needs to be "disabled" by means of ACPI patching, thus the "zero" scope value for D07E.

Just another way of calling the DSM method

You didn't, information is scarce about ACPI table patching (there is no general guide unfortunately) so we need to push it a little by adding relevant or wanted information to the table so it can be shown properly o as we want.

I wish there was more info about this elsewhere.. I'm afraid all the knowledge I have acquired has been through years of trial and error. One of the best sources of info about patching and such is @RehabMan, most things I know are through "experiments" I have done based on his work and other stuff I find around.
He has a very good guide on laptop patching that englobes many aspects of ACPI patching, I'd start there.

@kgp has done tons of work in this matter too, so his post is like a little big guide

Glad I could help!

Thanks for the info. I to have been using @RehabMan , @kgp and @shilohh 's examples to modify and fix SSDT's for my builds. It's the uncommon cards I use that have always given me trouble. Going for my Areca Raid card next, then on to my X299 build. I would love to join you guys in Mojave, but alas I need Cuda to do my job.

Kevin

 

[BluewaterVA]

KGP says to use Bios 1503 for installation of High Sierra on Asus X299. I have upgraded to Bios 1704 prior to wanting to Hackintosh.

Am I doomed? Can I get a reliable Hackintosh on 1704?

Any advice? Please, thank you!