Many thanks for looking into this for us!Lol.Well I figured out what tool you needed, then asked if it was reasonable to consider making it and was told it basically existed.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Interesting. I have two instances of OC from after that commit that show each other. Perhaps the reason is that one is on a CD...
Most definitely. Thanks.
Just a pet thing with detecting that one setting. Would allow scripted bless to check whether it would take or not. Nothing particularly critical though.
Editing a post from another thread, it just struck me OpenCore might me helpful.
An interesting issue with an AMD R9 280X with 2x MiniDP and 1x HDMI running multiple 4K screens in Big Sur.
I run two Samsung UR59C 4K monitors and additionally a Toshiba 4K TV off this computer just to make sure the GPU dies a dignified death before I switch to some modern AMD GPU in the near future. It is a Powercolor R9 280X with latest Powercolor BIOS (I run it switched to stock, although I do have this same BIOS with UEFI for native boot screens, not really useful nowadays as Big Sur is only available through OpenCore anyway).
My initial setup was monitors only via DP ports (#1, #2, the default DP mode is v1.2 as set through the OSD menu). On startup, they gave me a strange kind of mirroring on login screen: DP #2 displayed the login screen in 2560x1440 and DP #1 showed the same content, but brutally downscaled to 1280x720 with only the width expanded to full screen, black bars above and below the content. Once logged in, they switch to expanded desktops and I was able to set #2 to 2560x1440, however in 30 Hz only. #1 stays in 1280x720.
Rebooted with the TV connected via HDMI and - lo an behold - while there is still mirroring and DP #1 stays at 1280x720, suddenly DP #2 and HDMI are 2560x1440@60 Hz. I log in and push all screens to 4K, which resulted in the TV (HDMI) in 4K30, DP #2 in 4K60 and DP#1 still at 1280x720 no matter how I played with the display settings prefpane.
Rebooted again and back to login screen, now the DP#1 is still fugly 1280*720 with black bars, DP#2 is 4K60, HDMI is 4K30, all screens are mirrored. I compared the OSD settings of both monitors and started to change them one by one. Surprise! Once the DP#1 was downgraded to DisplayPort ver 1.1, it displayed a nice 2560x1440@60 Hz and the other displays mirrored no more.
And then I switched DP#1 back to DisplayPort ver 1.2 and... 4K60 on both MiniDP-connected displays and 4K30 on the TV.
So now my procedure on every startup is to wait for login screen, enter the menu of the left (my DP#1) monitor to downgrade to DisplayPort ver 1.1, click again to switch back to DisplayPort ver 1.2 and I have my triple-4K setup running.
That's in MacOS.
The point is, I do not need to do anything like this in Windows I run from the other SSD on the same computer, using the same GPU with the same BIOS. The three screens go double 4K60 + 4K30 just by themselves. I want it in MacOS.
Now - the display that has the wrong resolution (DP#1) is the same display that shows the OC boot picker and Apple logo on startup. As I started digging through the Internet to find some information, I started to suspect it may have something to do with the EDID and incorrect data passed between the display and computer in the early stage of boot in this particular scenario. I've found how to extract EDID from a running system using
P.s.: the unexpected result of my tinkering is that the displays themselves do not play any audio anymore. Two DisplayPort audio devices are detected by MacOS, however the analog audio connectors on both displays are silent, no matter how loud I crank them up. HDMI audio works no problem.
An interesting issue with an AMD R9 280X with 2x MiniDP and 1x HDMI running multiple 4K screens in Big Sur.
I run two Samsung UR59C 4K monitors and additionally a Toshiba 4K TV off this computer just to make sure the GPU dies a dignified death before I switch to some modern AMD GPU in the near future. It is a Powercolor R9 280X with latest Powercolor BIOS (I run it switched to stock, although I do have this same BIOS with UEFI for native boot screens, not really useful nowadays as Big Sur is only available through OpenCore anyway).
My initial setup was monitors only via DP ports (#1, #2, the default DP mode is v1.2 as set through the OSD menu). On startup, they gave me a strange kind of mirroring on login screen: DP #2 displayed the login screen in 2560x1440 and DP #1 showed the same content, but brutally downscaled to 1280x720 with only the width expanded to full screen, black bars above and below the content. Once logged in, they switch to expanded desktops and I was able to set #2 to 2560x1440, however in 30 Hz only. #1 stays in 1280x720.
Rebooted with the TV connected via HDMI and - lo an behold - while there is still mirroring and DP #1 stays at 1280x720, suddenly DP #2 and HDMI are 2560x1440@60 Hz. I log in and push all screens to 4K, which resulted in the TV (HDMI) in 4K30, DP #2 in 4K60 and DP#1 still at 1280x720 no matter how I played with the display settings prefpane.
Rebooted again and back to login screen, now the DP#1 is still fugly 1280*720 with black bars, DP#2 is 4K60, HDMI is 4K30, all screens are mirrored. I compared the OSD settings of both monitors and started to change them one by one. Surprise! Once the DP#1 was downgraded to DisplayPort ver 1.1, it displayed a nice 2560x1440@60 Hz and the other displays mirrored no more.
And then I switched DP#1 back to DisplayPort ver 1.2 and... 4K60 on both MiniDP-connected displays and 4K30 on the TV.
So now my procedure on every startup is to wait for login screen, enter the menu of the left (my DP#1) monitor to downgrade to DisplayPort ver 1.1, click again to switch back to DisplayPort ver 1.2 and I have my triple-4K setup running.
That's in MacOS.
The point is, I do not need to do anything like this in Windows I run from the other SSD on the same computer, using the same GPU with the same BIOS. The three screens go double 4K60 + 4K30 just by themselves. I want it in MacOS.
Now - the display that has the wrong resolution (DP#1) is the same display that shows the OC boot picker and Apple logo on startup. As I started digging through the Internet to find some information, I started to suspect it may have something to do with the EDID and incorrect data passed between the display and computer in the early stage of boot in this particular scenario. I've found how to extract EDID from a running system using
sudo ioreg -l | grep IODisplayEDID and a hint to put it into OC config.plist. I am not sure this would help. Asking does not harm, however - how do I edit my config to include EDID information for all three displays attached? Or perhaps there is another way to hardcode the initial resolution into a config file so Mac OS displays properly on login screen (an subsequently)?P.s.: the unexpected result of my tinkering is that the displays themselves do not play any audio anymore. Two DisplayPort audio devices are detected by MacOS, however the analog audio connectors on both displays are silent, no matter how loud I crank them up. HDMI audio works no problem.
Oh sorry, you meant within the OS? If so, I believe the information is not simply in a runtime accessible NVRAM variable, for instance. I think someone (@joevt ??) would have to write a small program to use UEFI runtime services to locate and call FwGetCurrent of OC_FIRMWARE_RUNTIME_PROTOCOL.
Hello,
I just installed the newest OC version with BigSur (11.5.2) on my 5,1. However upon selecting BigSur in the boot screen and after the loading bar is done I get a black screen.
I attached the SSD to my MacBook via USB and there everything works fine, I see the login screen.
Any ideas what might cause this?
On old OC+Catalina everything worked fine. I have a 5700 XT via display port.
I successfully installed and validated all the needed kexts including latebloom...
EDIT:
Booting my old Catalina SSD from the fresh OC works fine, I don't get a black screen, just from BigSur...
EDIT 2:
I figured it works via HDMI, it seems to be a display port issue with BigSur... any ideas why???
EDIT 3:
OK - the solution was to add the boot arg `agdpmod=pikera` because of my NAVI GPU.
I just installed the newest OC version with BigSur (11.5.2) on my 5,1. However upon selecting BigSur in the boot screen and after the loading bar is done I get a black screen.
I attached the SSD to my MacBook via USB and there everything works fine, I see the login screen.
Any ideas what might cause this?
On old OC+Catalina everything worked fine. I have a 5700 XT via display port.
I successfully installed and validated all the needed kexts including latebloom...
EDIT:
Booting my old Catalina SSD from the fresh OC works fine, I don't get a black screen, just from BigSur...
EDIT 2:
I figured it works via HDMI, it seems to be a display port issue with BigSur... any ideas why???
EDIT 3:
OK - the solution was to add the boot arg `agdpmod=pikera` because of my NAVI GPU.
Last edited:
For some reason I don't really want to boot windows 10. I don't understand. The Windows 10 logo appears and nothing happens. He hadn't had a problem with him before. I've been using Opencore for a long time. What is the solution? I'm on Opencore 0.7.2.
Thank!
Thank!
Is anyone aware of changes in OpenCanopy that may cause the graphical picker to stop working as of OpenCore 0.7.3? With the pre-existent config.plist and both old and updated OpenCanopy binaries, all I get is the text-only picker. I've had four successful warm boots (no failures), but no graphical picker. I would assume some new config.plist key is required?
UEFI drivers are added differently in 0.7.3. The first post will be updated shortly.
The guide has been updated to OpenCore version 0.7.3.
A notable change is how UEFI drivers are added. See "Updating OpenCore" in Part 3.
Thanks to the hard work of @Bmju, this version of OC includes a driver for booting Linux natively (without GRUB). The procedure in the guide (which is also for booting Linux natively) will now be greatly simplified!
A notable change is how UEFI drivers are added. See "Updating OpenCore" in Part 3.
Thanks to the hard work of @Bmju, this version of OC includes a driver for booting Linux natively (without GRUB). The procedure in the guide (which is also for booting Linux natively) will now be greatly simplified!
Auto-eject changes?
Has anyone experienced auto-eject of external devices after installing OpenCore 0.7.3? It has already happened to me four or five times when I dismiss the screensaver (in my case, a black screen). Any ideas?
Has anyone experienced auto-eject of external devices after installing OpenCore 0.7.3? It has already happened to me four or five times when I dismiss the screensaver (in my case, a black screen). Any ideas?
Yes, it is turned on. But it was the same under OC 0.7.2 and it didn't behave this way.
EDIT: Actually, I think my Mac can now go to sleep. It hasn't done so in years. Has anything changed with 0.7.3?
Last edited:
I have a HighPoint 7101a with 4 NVME drives installed. The 1st has OS Mojave the 2+3 is set up as a raid 0 (scratch disc) and what I was thinking of doing is installing OS Catalina onto the 4th drive?
So leaving Mojave only on the 1st and having Catalina on the 4th drive.
So, would it be possible to install Catalina on the 4th SSD using Opencore?
So leaving Mojave only on the 1st and having Catalina on the 4th drive.
So, would it be possible to install Catalina on the 4th SSD using Opencore?
I noticed when I had downloaded Martin's EFI Folder from the link on page 1 a couple of hour's ago this morning that I had a text boot picker until I made this change.
Martin's =
<key>Drivers</key>
<array>
<dict>
<key>Path</key>
<string>OpenRuntime.efi</string>
<key>Enabled</key>
<true/>
<key>Arguments</key>
<string></string>
</dict>
<dict>
<key>Path</key>
<string>OpenCanopy.efi</string>
<key>Enabled</key>
<false/>
<key>Arguments</key>
<string></string>
</dict>
</array>
after I'd changed it to
<key>Drivers</key>
<array>
<dict>
<key>Path</key>
<string>OpenRuntime.efi</string>
<key>Enabled</key>
<true/>
<key>Arguments</key>
<string></string>
</dict>
<dict>
<key>Path</key>
<string>OpenCanopy.efi</string>
<key>Enabled</key>
<true/>
<key>Arguments</key>
<string></string>
</dict>
</array>
after that change (opencanopy ...enabled was set to false, I changed that and set it to true).I got the graphical boot picker back.
Last edited:
Working fine for me, have you updated properly the new 0.7.3
Drivers plist configuration? See:OC 0.7.3 upgrade (#115) · axivo/opencore@491600c
* Updated Latebloom to 0.20 version * Updated OcBinaryData files * Updated drivers format * Updated properties * Updated sofware versions
github.com
The auto-eject issue corrected itself after the eleventh successful boot. I have no idea what might have caused it.
EDIT: By "eleventh" I meant the eleventh successful warm boot in a row yesterday, after sloppily installing OC 0.7.3 for the first time, not that the auto-eject issue happened in all first ten boots. It only happened in the tenth.
EDIT: By "eleventh" I meant the eleventh successful warm boot in a row yesterday, after sloppily installing OC 0.7.3 for the first time, not that the auto-eject issue happened in all first ten boots. It only happened in the tenth.
Last edited:
Garbage collection in NVram? If it happens again triple reset nvram and check it.
Monterey Beta 6 OCLP v0.2.5 seems to work good on my MacBook Pro 2010 NVDIA 330M GPU.
Does anyone know how to get the Mini-Display port to work?
Thanks!
Does anyone know how to get the Mini-Display port to work?
Thanks!