- Joined
- Apr 16, 2017
- Messages
- 418
- Motherboard
- Gigabyte X299 WU-8
- CPU
- i9-7980XE
- Graphics
- RX 580
- Mobile Phone
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.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 )
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
Last edited: