Asus X299 - Support

mgregrs said:

Hey @iso1 (after looong time - in my case)
I knew it, next day ... we will find something or someone helpful ...
and if I remember well, you were 150x times more advanced in ACPI implementantion than me so...
maybe you will be able to help... or maybe for this moment just share 2ssdt:

Can you please share your .aml for your 1st slot 4360CS2 and 7th slot SilverStone card....?
(if it's still the same config as X time ago, where I found your PCI list and these details)
Of course I will try to change what we need for ci2own system, it can be very helpful for us,
especially when I have different system than he and I come back after long time on forum

Click to expand...

Hi

I'm not that good at ACPI (it always goes above my head), but I always try to do it the "right way" with help of others and main focus is always stability and being as real to a Mac as possible.

You can find my current full EFI ZIP for OpenCore here (along with various other users):

That is the only one I use now and I don't use Clover anymore unfortunately.

The ZIP will contain all PCIe slot configurations too.

Hope this helps

izo1 said:

Hi

I'm not that good at ACPI (it always goes above my head), but I always try to do it the "right way" with help of others and main focus is always stability and being as real to a Mac as possible.

You can find my current full EFI ZIP for OpenCore here (along with various other users):

shinoki7/Asus-X299-Hackintosh

Contribute to shinoki7/Asus-X299-Hackintosh development by creating an account on GitHub.

github.com

That is the only one I use now and I don't use Clover anymore unfortunately.

The ZIP will contain all PCIe slot configurations too.

Hope this helps

Click to expand...

Thanks @iso1

So I found your EFI, but quite weird because instead of _DSM method and all package of details like device type, device name, id etc...
you have only:

Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}

Click to expand...

which is something completely new for me
I would like to find some page where I can learn more about that,
because now I feel like baby which can't even walk
and on the same time 'like greezly bear after 1 year of sleep"
I have impression like, all people after KGP inactivity, changed MB
for yours and Prime Deluxe users are gone too.

On the same time, I didn't found anything in .aml files (in your EFI)
about/for your additional USB card what is weird for me at this moment.

Can you say something more about your separation with Clover,
what are your advantages after change?
Do you have any main reason?

PS: Of course it helps, I love to learn something new, to share something
after with others, so Thanks again

Btw youll still the kexts since the ssdt is just cosmetic. I would go with the 94360 if you can so you don’t have to deal with all these kexts and patches, the less kexts the better

mgregrs said:

Thanks @iso1

So I found your EFI, but quite weird because instead of _DSM method and all package of details like device type, device name, id etc...
you have only:

which is something completely new for me
I would like to find some page where I can learn more about that,
because now I feel like baby which can't even walk
and on the same time 'like greezly bear after 1 year of sleep"
I have impression like, all people after KGP inactivity, changed MB
for yours and Prime Deluxe users are gone too.

On the same time, I didn't found anything in .aml files (in your EFI)
about/for your additional USB card what is weird for me at this moment.

Can you say something more about your separation with Clover,
what are your advantages after change?
Do you have any main reason?

PS: Of course it helps, I love to learn something new, to share something
after with others, so Thanks again

Click to expand...

We don’t inject device properties via the SSDT DSM method in OpenCore so that’s why you’re not seeing it in @izo1 ssdts. Also, OpenCore behaves more like a real Mac so SSDT patches will affect all OS. So we use if “Darwin” to avoid renaming devices in Windows.

@izo1 can explain more but if it’s directly OpenCore related it should move to the X299 OpenCore thread

djlild7hina said:

We don’t inject device properties via the SSDT DSM method in OpenCore so that’s why you’re not seeing it in @izo1 ssdts. Also, OpenCore behaves more like a real Mac so SSDT patches will affect all OS. So we use if “Darwin” to avoid renaming devices in Windows.

@izo1 can explain more but if it’s directly OpenCore related it should move to the X299 OpenCore thread

Click to expand...

Thank for info @djlild7hina !
I didn't know what is OpenCore... I just found some info on YT.

About _OSI i found that
"With _OSI, the BIOS provides the string describing an interface, and asks the OS: "YES/NO, are you compatible with this interface?"
So it seems to be something great...
especially OC - it's first time I hear about that,
but now I think it can be genius thing and veeery useful/helpful for our future
Thanks again for info!

mgregrs said:

Thank for info @djlild7hina !
I didn't know what is OpenCore... I just found some info on YT.

About _OSI i found that
"With _OSI, the BIOS provides the string describing an interface, and asks the OS: "YES/NO, are you compatible with this interface?"
So it seems to be something great...
especially OC - it's first time I hear about that,
but now I think it can be genius thing and veeery useful/helpful for our future
Thanks again for info!

Click to expand...

You can read over this guide’s introduction which explains the benefits and quirks of OpenCore

@mgregrs Should i try to buy another Wifi/bluetooth card then? Or you thing we can make this one works?

Also i can do it with .kexts and CAT.

ci2own said:

@mgregrs Should i try to buy another Wifi/bluetooth card then? Or you thing we can make this one works?

Also i can do it with .kexts and CAT.

Click to expand...

All depend of your your choice and financial situation (if you have this CPU I think it will be not a problem )
Of course - if not me/someone like KGP and other advanced user can find a easy solution for this actual card, but it's too much of time if you really need full functionality. These cards are cheap so if I were you... I buy new one BCM94360CD and then you can forget about problems in future because it's the best card (and actual one you can save for 2nd PC or some day in case if 1st one will die or something like that) @djlild7hina had good idea...-much easier and faster way
In few words - If you use everyday OS-X and you need all functions , you want easy config etc.... don't waste time - buy BCM94360CD and be happy owner like all of us with the best choice

PS: ... but this time look carefully on amazon or eBay to find exactly BCM94360CD
not BCM94360CD or BCM94xyzz... in package - exactly this one, even if it cost 15-20€$£ more...

mgregrs said:

All depend of your your choice and financial situation (if you have this CPU I think it will be not a problem )
Of course - if not me/someone like KGP and other advanced user can find a easy solution for this actual card, but it's too much of time if you really need full functionality. These cards are cheap so if I were you... I buy new one BCM94360CD and then you can forget about problems in future because it's the best card (and actual one you can save for 2nd PC or some day in case if 1st one will die or something like that) @djlild7hina had good idea...-much easier and faster way
In few words - If you use everyday OS-X and you need all functions , you want easy config etc.... don't waste time - buy BCM94360CD and be happy owner like all of us with the best choice

Click to expand...

Ok! i'll buy a new wifi/bluetooth card. So is the BCM94360CD the best and more compatible one then? Will it need SSDT patch?

Do i plug the USB Extension Card to add the SSDT? or this card doesn't need it either?

And again many thanks for your help!

ci2own said:

Ok! i'll buy a new wifi/bluetooth card. So is the BCM94360CD the best and more compatible one then? Will it need SSDT patch?

Do i plug the USB Extension Card to add the SSDT? or this card doesn't need it either?

And again many thanks for your help!

Click to expand...

First - this evening you can try to do something with your kexts etc... if it will not work correctly, then after few hours of try you can buy it ...
BCM94360CD - from my knowledge, yes it's most compatible card and fastest on the market (for OS-X... oob)

USB Extension card (or connection with 8-9 pin header to MB) is needed only if you want to use your wireless mouse and keyboard on BIOS, or anywhere "before system boot", because (as I said before)
even without USB Extension card and this little cable, in OS-X you will use your wireless BT hardware without problems

Yes, even with BCM94360CD you can add SSDT for nice cosmetic look in PCI list, but it will work great even without it.
Voila