AsRock X299 Creator

[oli.mathieu]

Yes the patch doesn't mach so I adapted the SSDTs to PC00 but I made a huge mistake on SSDT-EC-DMAC : I forgot to do that with SSDT-EC-DMAC : so here is the new SSDT-DMAC

Sorry but I see only one difference : PC00 instead of PCI0.... what else did you do ?

 

[Loloflatsix]

Sorry but I see only one difference : PC00 instead of PCI0.... what else did you do ?

Yes your are right, not easy : I didn't pay attention to the start of the scope.

    Scope (_SB)
    {
        Device (PC00)
        {
            Name (_HID, EisaId ("PNP0A08"))  // _HID: Hardware ID
            Name (_CID, EisaId ("PNP0A03"))  // _CID: Compatible ID
            Name (_ADR, Zero)  // _ADR: Address
            Method (^BN00, 0, NotSerialized)
            {
                Return (Zero)
            }

            Method (_BBN, 0, NotSerialized)  // _BBN: BIOS Bus Number
            {
                Return (BN00 ())
            }

            Scope (\_SB.PC00.LPC0)
            {

 

[oli.mathieu]

Yes your are right, not easy : I didn't pay attention to the start of the scope.

    Scope (_SB)
    {
        Device (PC00)
        {
            Name (_HID, EisaId ("PNP0A08"))  // _HID: Hardware ID
            Name (_CID, EisaId ("PNP0A03"))  // _CID: Compatible ID
            Name (_ADR, Zero)  // _ADR: Address
            Method (^BN00, 0, NotSerialized)
            {
                Return (Zero)
            }

            Method (_BBN, 0, NotSerialized)  // _BBN: BIOS Bus Number
            {
                Return (BN00 ())
            }

            Scope (\_SB.PC00.LPC0)
            {

bravo

 

[S1lla]

yo

Yes with iMacPro SMBIOS it works better : that means we need to define MacPro 7.1 in the info.plist properties of USB.kext

The "Model" query can be deleted completely afterwards it will not matter which SMBIos is in use.

 

[Ellybz]

@oli.mathieu @mbi7
Just catching this conversation, ( Maybe it was already resolved/discussed )
Another option to disable the internal bluetooth and force OSx to use the external dongle.( Other than Bios )
Open terminal and type:

sudo nvram bluetoothHostControllerSwitchBehavior=always

Press enter, enter password, enter & REBOOT.
If you remove your USB dongle, OSX will use again the internal.

To undo the changes:
undo sudo nvram -d bluetoothHostControllerSwitchBehavior
Press enter, enter password, enter & REBOOT.
Done.

 

[mbi7]

@oli.mathieu @mbi7
Another option to disable the internal bluetooth and force OSx to use the external dongle.( Other than Bios )
Open terminal and type:
sudo nvram bluetoothHostControllerSwitchBehavior=always
Press enter, enter password, enter & REBOOT.

THANK YOU, this works! I always wondered how to get OS X to specify priority for a different bluetooth controller. (On this motherboard, disabling bluetooth in bios doesn't seem to help, OS X still sees it).

 

[mbi7]

sudo nvram bluetoothHostControllerSwitchBehavior=always

@Ellybz - well I spoke too soon, I was able to get this to work once, but in the process of trying to get my Wacom driver working (cleared my preferences folder), this won't "stick" in nvram after an immediate reboot anymore... nvram -p will show it after I set it, but it will not be present after reboot.

Any ideas on how to set it in a clover config or boot argument?

 

[Ellybz]

@Ellybz - well I spoke too soon, I was able to get this to work once, but in the process of trying to get my Wacom driver working (cleared my preferences folder), this won't "stick" in nvram after an immediate reboot anymore... nvram -p will show it after I set it, but it will not be present after reboot.

Any ideas on how to set it in a clover config or boot argument?

I forgot to mention that Native NVRAM is required. I might be mistaken but I don't think NVRAM is supported on your GAZ170. Most X299 boards support native NVRAM. Not sure about the X299 AsRock Creator.
Not using clover, so not sure I can help you much. Have tried with AptioMemoryFix64 instead of EmuVariable64?
That might do the trick.

 

[mbi7]

I forgot to mention that Native NVRAM is required.

Ya, This is with the x299 creator, not sure why it worked one time if nvram isn't working on this platform yet. Hmm. We are using fwruntime instead of aptio on this board, I'll look into other options.

If only there was a way to run it as a launchctl unload/load ...

 

[Ellybz]

Ya, This is with the x299 creator, not sure why it worked one time if nvram isn't working on this platform yet. Hmm. We are using fwruntime instead of aptio on this board, I'll look into other options.

If only there was a way to run it as a launchctl unload/load ...

Here's your other option. Get the bugger off the ship . (Only 2 screws )