Contribute
Register

X299 - Open Core support

Status
Not open for further replies.
Pavo said:
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.
Click to expand...

@Pavo So nice to see you post over here.......I regularly view discord and enjoy your comments there.......

So, it appears to me that the most challenging part of Open Core is the boot picker. It seems like it's the one feature that needs more development, and the current options seem somewhat limited. Can another booting menu be used with Open Core? Is there more development planned?
 
mm2margaret said:
@Pavo So nice to see you post over here.......I regularly view discord and enjoy your comments there.......

So, it appears to me that the most challenging part of Opencore is the boot picker. It seems like it's the one feature that needs more development, and the current options seem somewhat limited. Can another booting menu be used with Opencore? Is there more development planned?
Click to expand...
OpenCore devs have added a feature to allow 3rd party boot-picker interfaces but that would require you to develop that yourself. The reason it is a little more difficult that Clover is because of the secure options that OC has built-in. They are try to make it secure from the ground up which is amazing in my opinion. I agree the docs are very vague on the config settings but that where we as users have to test and test different options to get it right. OpenCore is very new and will get better to understand as the community helps provide feedback and or creates guides, apps to automate things for it.
 
flmmkr said:
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.
Click to expand...

I have found some inconsistencies that resulted in my having OC installed on two separate USB drives. And when I've found an issue that seems odd, or like you, not understandable even after a reboot, I will shut the computer down entirely. Then I will boot using the other USB drive to see if that makes a difference. It's also good to have a second backup boot drive anyway.

But perhaps a better approach would be to file your issue on this site: https://github.com/acidanthera/bugtracker/issues
You might find some guidance there, and it might be a bug.
 
Pavo said:
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.
Click to expand...
Thanks for your Input. It was actually this way but Apple Logo is still stretched during first part of the Boot. attached is my EFI ( No SN, UUID ). Very happy with everything else so far. Any suggestion?
 

Attachments

  • EFI Ellybz OC GA.zip
    1.9 MB · Views: 74
Last edited:
flmmkr said:
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.
Click to expand...
Without looking at your IOReg, I'd say you need to verify your protocol settings in your Custom USB Kext. HS/SS Ports ( 3/ 0 /255 )Does it load properly? I have no idea if you've already done that but this is where I would start.
 
Ellybz said:
Thanks for your Input. It was actually this way but Apple Logo is till stretched during first part of the Boot. attached is my EFI ( No SN, UUID ). Any suggestion?
Click to expand...
ACPI>Quirks you have resetLogoStatus it should be ResetLogoStatus.
Misc>Boot Try leaving ConsoleBehaviourOs and ConsoleBehaviourUi blank and change Resolution to Max.
UEFI>Quirks you have ProvideConsoleControl, needs to be removed because it was removed from the config along time ago.

Thats about all I see beside all the renames you have in ACPI>Patch section that should not be used. They simply are not needed. But that doesn't have anything to do with Apple boot logo.
 
Pavo said:
ACPI>Quirks you have resetLogoStatus it should be ResetLogoStatus.
Misc>Boot Try leaving ConsoleBehaviourOs and ConsoleBehaviourUi blank and change Resolution to Max.
UEFI>Quirks you have ProvideConsoleControl, needs to be removed because it was removed from the config along time ago.

Thats about all I see beside all the renames you have in ACPI>Patch section that should not be used. They simply are not needed. But that doesn't have anything to do with Apple boot logo.
Click to expand...
I'll try that & report back. :)
Edit: I changed all settings based per your recommandation, Apple Logo is still stretched ( x2 ) during first part of the boot.
I'll keep looking. Thanks.
 

Attachments

  • Screen Shot 2019-08-15 at 5.57.45 PM.png
    Screen Shot 2019-08-15 at 5.57.45 PM.png
    139 KB · Views: 118
Last edited:
Ellybz said:
I did not miss it. I also tried it, same thing. A thought ...I'm gonna try later with DP port instead of HDMI / Other monitor. ..Have to run errands. Thanks though :thumbup:
Click to expand...
Oh sorry to hear it didn’t work.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top