Contribute
Register

X299 - Open Core support

Status
Not open for further replies.
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 )
Btw, all the logs before the picker appears are easily removed. PlatformInfo does not need All the extra (repeated) info/data in: Datahub; PlatfornNVRAM, SMBIOS. Generic covers all the SN UUID you need. See screenshot below.
Regarding the Logo & screen resolution, that sanitiseClearScreen did not do anything for me. I also tried multiple values on "UI" Best I could find was "01". SSDTs are a bit tricky to learn, but it is necessary. I started there but lots of infos are on the net.
.
Good day!
 

Attachments

  • Screen Shot 2019-08-15 at 12.53.10 PM.png
    Screen Shot 2019-08-15 at 12.53.10 PM.png
    98.3 KB · Views: 150
  • Screen Shot 2019-08-15 at 12.53.18 PM.png
    Screen Shot 2019-08-15 at 12.53.18 PM.png
    61.9 KB · Views: 124
Last edited:
So, I can report that thanks to @Ellybz BT is now working. In both Mojave and Catalina, I tested with a BT enabled pair of headphones, which sounded great. No scratchy sound, either. Probably that won't last until I buy a new motherboard, but it was nice to hear sound without the scratchy issues that the Radeon VII has had (driver issues). It would be nice if that was fixed permanently, but we'll see about that.

Really, all I did was disable the ARPT AML file, and then make sure all four of the various BT kexts were set to disabled. I did not load USBinject all because that stopped the system with a "can't ...kext summary" error. I did not load Ellybz's USB kext file. I may enable that later for testing. I did set the quirk setting for XHCIPortLimit to yes, but I'll experiment to see if that's actually correct later also.

Pretty simple fix after all.....thanks, @Ellybz!!!
Ellybz's USB Kext is for my Mobo...Stay away from it. :lol:
 
Match this for correct proportions.

View attachment 421924

For iMessage, Continuity and Handoff, it will work if you bring in the same SN, MLB and UUID.

You can use
Code:
uuidgen
in Terminal to find your UUID. MLB is same as SN except you add 5 random characters to the end of it.

That fixed the proportions/resolution issue. Thanks!

I have the SN, MLB, and UUID already, so I'm good there. Will give it shot after I fix/eliminate all the renaming patches in config.
 
That fixed the proportions/resolution issue. Thanks!

I have the SN, MLB, and UUID already, so I'm good there. Will give it shot after I fix/eliminate all the renaming patches in config.


For others, there is a utility called macserial which seems to do a pretty good job................just google -> acidanthera macserial or - > acidanthera MacInfoPkg.....

Here's an example of how to work it: ./macserial -a | grep -i iMac18,1
 
For others, there is a utility called macserial which seems to do a pretty good job................just google -> acidanthera macserial or - > acidanthera MacInfoPkg.....

Here's an example of how to work it: ./macserial -a | grep -i iMac18,1

Yup, that's what I used to get the MLB and ROM.
 
I removed the patches from config, modified the existing .aml files to compensate, and implemented a SSDT-X299PrimeDeluxe-EC-USBX.aml. Everything seems to be working properly, EXCEPT for one thing:

I'm finding that my USB ports no longer have enough bus power to run my bus-powered USB 3.0 drives. The same drives work on my MacBook Pro just fine, but when I connect to USB 3.0 ports on my Hackintosh most of them don't mount. A couple do, but most will not work. I can see the power light blinking on ones that have a light and I can hear the spin up/down and even clicking on others. None of that happens with my MacBook Pro so I know all the drives are fine.

Issue with the SSDTs? EFI is attached.
 

Attachments

  • EFI.zip
    1.6 MB · Views: 81
In SSDT-EC-USBX.dsl it says "Try NOT to rename EC0, H_EC, etc. to EC. These devices are incompatible with macOS and may break at any time. AppleACPIEC kext must NOT load. See the disable code below."

So why rename EC0>EC at all? Should we just leave that SSDT out AND remove the patch from config?
For Gigabyte X299 users: The only ACPI patches I kept so far ( I will create/replace them with SSDTs )

-FPU_ -> MATH
-TMR_ -> TIMR
-PIC_ -> IPIC
-SMBS._ADR -> XSBU.XADR

Still lots of SSDTs. Will post my updated EFI later.
 
Last edited:
Regarding the Logo & screen resolution, that sanitiseClearScreen did not do anything for me. I also tried multiple values on "UI" Best I could find was "01". SSDTs are a bit tricky to learn, but it is necessary. I started there but lots of infos are on the net.
Before FwRuntimeServices driver was implemented for OC, we used AptioMemoryFix and that took care of the GOP protocol for the logo and screen res for most firmware of boards. Since we have to use FwRuntimeServices driver now, all you need to do is enable ProvideConsoleGOP in UEFI Quirks section to fix the stretching of the log, the res depends on your settings in Misc Boot section of your config.
 
I'm back to square one here. After removing BrcmFirmwareData.kext and BrcmPatchRAM2.kext, and leaving BrcmBluetoothInjector.kext installed, I had BT working in both Mojave and Catalina with both Clover and OC. What I found though is that my USB3 ports were not working correctly. Some portable bus-powered USB HDDs would mount, but a bunch would not. I tried all kinds of USB SSDTs and kexts with no luck getting full USB3 functionality back. This issue appeared in both Catalina with OC and Mojave with Clover (that's all I tested). Not only that, after shutting down the computer, cutting power, and waiting awhile, I came back to find BT no longer worked properly. BT showed up in System Preferences for both Mojave with Clover and Catalina with OC, but I could not get any BT devices to actually connect (they would show, but not connect).

So I decided to put Clover back how it was before with BrcmFirmwareData.kext and BrcmPatchRAM2.kext installed. Started Mojave. BT worked again (devices connect properly right away) and all of my portable bus-powered USB3 drives mount.

So then I decided to try Catalina again. Booted from my OC USB into Catalina. This is with onlyc BrcmBluetoothInjector.kext. BT worked, but my portable bus-powered USB3 drives would not mount. I then installed BrcmFirmwareData.kext and BrcmPatchRAM2.kext on the OC EFI and added to config. Restarted. BT no longer works in Catalina, but all the portable bus-powered USB3 drives do mount.

Isn't that bizarre? Why won't the bus-powered USB3 drives mount without BrcmFirmwareData.kext and BrcmPatchRAM2.kext? And it seems whatever BrcmFirmwareData.kext and BrcmPatchRAM2.kext do gets loaded into some kind of RAM temporarily where only BrcmBluetoothInjector.kext is needed until power is completely cut from the computer or it's off for a while, but eventually BrcmFirmwareData.kext and BrcmPatchRAM2.kext are needed again for BT functionality. But if BrcmFirmwareData.kext and BrcmPatchRAM2.kext are loaded with Catalina with BrcmBluetoothInjector.kext then BT won't work.

Any thoughts on this?

Attaching current EFI and an IOReg from Catalina with OC as bootloader.
 

Attachments

  • Catalina beta 5 OpenCore.ioreg
    14.9 MB · Views: 66
  • EFI.zip
    3.8 MB · Views: 83
Status
Not open for further replies.
Back
Top