X299 - Open Core support

[izo1]

Nothing for the ROM parameter under PlatformInfo -> Generic? I think I've filled those out, and there must be something else wrong.....no worries....I'll figure it out.....in due time.....

I'm quite pleased that both Mojave and Catalina boot and work pretty well with not much effort on my part....now comes the hard part....the final 10%......

Thanks for the tip!

No, keep things simple instead of complicating it. It should look like this.

OC lets macOS decide which CPU etc you're using based on the SystemProductName.

In my case, since X299/79xx/99xx CPUs are not even in real Macs, the CPU is "Unknown".

To overcome that, that is the only time you need to switch AUTOMATIC to NO and then add SMBIOS and manually enter other information.

The CPUMask isn't fully working afaik, I am still trying to figure that out.

 

[mm2margaret]

Yes. PM me on what you want/need.

Stork, you are the best!

 

[shael]

@izo1 for someone who said its a big job. you sure are doing a good job at holding this thread together with the proper info. maybe the first post should be edited to link all the OC Docs for reference.

 

[mm2margaret]

Well, here's a good one, this is the author's second guide, an updated one from a previous post: https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/

 

[flmmkr]

flmmkr said:
Ok, so it boots into Catalina, though not all is perfect. Here are the issues:

1. No Bluetooth at all. I have a Dell DW1830/BCM943602BAED card installed for both WiFi and BT. WiFi is working OOB. For BT in Mojave and Catalina with Clover I use BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, and BrcmPatchRAM2 to get it working. Prior to Catalina I did not need BrcmBluetoothInjector.kext, but I could only get BT to work in Catalina with Clover by adding that additional kext. I’ve tried and without that kext and still can’t get BT to work with OpenCore

2. The resolution of my monitors are 2560x1080 (ultra wide monitors). The Apple logo appears stretched even when I put 2560x1080@32 or 2560x1080 or leave blank for Misc/Boot/Resolution.

3. When OC starts (before the picker appears) I get the following:
OCS: No schema for All at 0 index! (11 times)
OCS: No schema for IgnoreForWindows at 1 index!
OCS: No schema for resetLogoStatus at 5 index!
OCS: Failed to parse string field of type 2 (twice)
OCS: No schema for ProvideConsoleControl at 3 index!

4. The OC log txt file left in the EFI shows:
00:000 00:000 OCB: Failed to match a default boot option.
------------------------

Few things..
I don't use any kext for my BT. ( BRCM 4331 ) It's working OOB in Mojave. However, in Catalina, I'm still working on it.
I tried several resolutions ( even 2560x1080@0 ) - OC still complains about it @ boot.
I still get very quick messages @ Failed to parse string or resetLogoStatus ( Different indexes ). Have not resolved this YET. ( Does not affect functionality of MacOS ) .Will keep posted.

EDIT: Have you tried your config OC with Mojave ? ( Catalina is still in Beta )

Ok I just tried a separate Mojave install and BT works with it with OC. So it’s a Catalina issue with OC. BT does work in Catalina with Clover.

 

[Ellybz]

Ok I just tried a separate Mojave install and BT works with it with OC. So it’s a Catalina issue with OC. BT does work in Catalina with Clover.

1- I believe the issue has to do with the ACPI Patches rename vs SSDTs in Catalina.
2- Edit: Still working on the Log issue / Temporary fix is setting Misc/Target to "0"
3- Resolution is resolved by setting it to the actual settings in: about this mac / Display.

 

[flmmkr]

Also your WIFI/BT should work in Catalina exactly as it would under Mojave. Unless you have the Wifi/BT combo where you need to inject a kext.

In that case, use headkaze's repo version that's modified for Catalina:

headkaze/OS-X-BrcmPatchRAM

Broadcom PatchRAM driver for OS X. Contribute to headkaze/OS-X-BrcmPatchRAM development by creating an account on GitHub.

github.com

This will also work for Mojave.

I am using those kexts and still cannot get BT to work in Catalina with OC. When I first tried Catalina with Clover, BT would not work. I found those kexts, tried the the Data and RAM2 kexts (just newer versions of what I was already using) and it still didn’t work. Then I added the Inject kext (so using all 3 kexts) and it worked in both Catalina and Mojave with Clover. With OC and using those 3 kexts, I get BT working Mojave, but not in Catalina public beta 5.

 

[mm2margaret]

So, those kexts don't work in my case with either Mojave or Catalina.

I did spend some dialoging with Pavo over at the other site, and he seemed to be picking up on something Ellybz was talking about:

1. You have renames in the ACPI>Patch in the config and specifically you are renaming PC00 to PCI0, renames should not be done in the config using Patch section, this has been stated over and over in this thread and also stated in the OpenCore documentations.
2. While you are patching the ACPI tables with the rename of PC00 to PCI0 your SSDT Scope is _SB.PCI0.RP19 which is not matching the ACPI table path.
3. You are also doing a device rename of PXSX to ARPT in the SSDT itself.
What I suggest you do is remove all the renames in the ACPI>Patch section and change all your SSDTs to match against the scope of \_SB.PC00.xxx.

He then offered a "fixed" EFI, which didn't work. In my case, loading those kexts do not make BT available, and even with his "fixed" EFI, I still do not have BT available either in Mojave or Catalina.

 

[Ellybz]

@djlild7hina @tonyarnold @izo1
Do you have BT/Wifi working in Catalina with OC?

 

[izo1]

I am using those kexts and still cannot get BT to work in Catalina with OC. When I first tried Catalina with Clover, BT would not work. I found those kexts, tried the the Data and RAM2 kexts (just newer versions of what I was already using) and it still didn’t work. Then I added the Inject kext (so using all 3 kexts) and it worked in both Catalina and Mojave with Clover. With OC and using those 3 kexts, I get BT working Mojave, but not in Catalina public beta 5.

How are you doing your USB map? You need proper USB set up for the internal header.

Is it a kext?

If yes, I recommend opening up all the ports for testing purposes (above 15 limit) by disabling (removing) your current USB patches and or Kexts and SSDTs, then using USBInjectAll.kext, and enabling:

 Kernel > Quirks > XhciPortLimit: YES

temporarily to see if if it works in Catalina. Also post your IOREG with screenshot of XHC.

Also try the attached files.