Is it possible to configure OpenCanopy for ultra widescreen resolutions, such as 3440x1440? My boot picker is stretched really wide.
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
I figured I'd post here before reverting to 0.6.0.
I run a single Xeon as a media server w/4x8tb drives in RAID5 by SoftRAID. Everything worked fine with all the 0.5.x and 0.6.0 releases of OpenCore. Yesterday I updated OC to 0.6.1 and today I got a message from SoftRAID (see below) that it thinks I'm running with SecureBoot (a T2 chip), which obviously isn't the case.
I've never enabled any Security Settings in Recovery Mode, so this must be an OC implementation w/0.6.1. Can anyone provide any insight to managing this in 0.6.1, otherwise I'm going to revert to 0.6.0.
I run a single Xeon as a media server w/4x8tb drives in RAID5 by SoftRAID. Everything worked fine with all the 0.5.x and 0.6.0 releases of OpenCore. Yesterday I updated OC to 0.6.1 and today I got a message from SoftRAID (see below) that it thinks I'm running with SecureBoot (a T2 chip), which obviously isn't the case.
I've never enabled any Security Settings in Recovery Mode, so this must be an OC implementation w/0.6.1. Can anyone provide any insight to managing this in 0.6.1, otherwise I'm going to revert to 0.6.0.
Attachments
When updating to a newer version always consult with the relevant OC manual, because there might be new parameters introduced. Also there is an
ocvalidate utility for checking the configuration against the current release.In your case there is a
SecureBootModel parameter introduced, which you will have to set as disabled.0.6.1 added a few options about Secure Boot. Did you config them properly accordingly?
I posted my 0.6.1 package at here
You may try it.
Absolutely. I’m quite busy at the moment, but I will update the wiki as soon as I can.
I'm using DisplayPort on a Vega 64. 3440x1440 works fine once booted, just the boot picker is stretched.
@startergo Thanks. Here is the file.... Interesting once in debug I could only boot into Catalina... my normal production config.plist too...
@startergo also here are the two drives after boot that appear in apple boot menu with native boot graft card...
Attachments
May be you can run debug mode to check which resolutions are detected. Then manually assign a better resolution for the boot picker (if 3440x1440 is not on the list).
Seems like it.
strings /System/Library/CoreServices/boot.efi.*.im4m | sort -u | sed -E '/^.{1,7}$/d'
Code:"Apple X86 Secure Boot Root CA - G11 2T8012Mac-TssLive-ManifestKeyGlobal-RevB-DataCenter1 xmH4smoln. ',X)QNPh 170323023206Z 170323214243Z0_1;09 7$Xbuks\ Apple Inc.1 }NT\rLg$c
There's a tool to open it:
which requires you build this first:
GitHub - tihmstar/img4tool: A tool for manipulating IMG4, IM4M and IM4P files
A tool for manipulating IMG4, IM4M and IM4P files. Contribute to tihmstar/img4tool development by creating an account on GitHub.github.com
but I don't know what any of it means.
GitHub - tihmstar/libgeneral: general stuff for projects
general stuff for projects. Contribute to tihmstar/libgeneral development by creating an account on GitHub.
Thank you very much for the detailed informations...
Last edited:
It seems the default config.plist relies on boot-args for HWAccel & Catalina booting rather than the hybridization method with Device Properties for the GPU. Is there a reason for doing so performance wise or is it just easier to implement?
Device properties injection does not work yet properly in BigSur. A PCIE bridge has to be created through SSDT. In Mojave and Catalina it is the preferred way and leaving the boot arguments NVRAM variable as short as possible.
I have the same issue with my Vega 64 over displayport and hdmi on my 21:9 monitor. Running the debug version of OpenCore showed it wasn't detecting the 3440x1440 resolution. I tried forcing the resolution but lost my video output. I've chosen to accept it and use my secondary 2560x1440 monitor as my boot display since it displays correctly.
Thank you very much for your work at OC incl. HW Acc. I try your folder (I use before a handmade one by myself 0.5.9) and it worked fine. There is a "small anomaly" at boot:
I turn on the Mac and if I use "AQ==" I see a small Apple logo (that indicates that the OS uses a native resolution of my LG) and when the WindowManager loads the LoginScreen I see a resulution of 1920x800 (a quarter of my native 3840x1600 from my LG 38WK95C-W via DisplayPort). If I then login I see for a short time of 1 1/2 seconds in the top left corner the login screen picture of 1920x800 while the WindowManager is switch the rsulution to 3840x1600 and reload the normal Desktop Screen.
At the moment I use now "Ag==" and the complete boot is in 1920x800 - after Login the resolution is switched to 3840x1600.
Looks weird but is not harmful
MacPro5,1 Dual 3,46 Ghz, Sapphire Radeon RX 570 Nitro+ (Slot 1)
I have it working with my opencore install but had to convert my bootcamp install from legacy to UEFI. I used the method here. https://www.windowscentral.com/how-convert-mbr-disk-gpt-move-bios-uefi-windows-10 The advantage is if you allready have a bootcamp disk with a lot of stuff on it and you dont want to start from scratch you can do the MBR to GPT conversion and not have to install windows 10 from scratch and all your games etc but it does have to be on its own drive not a shared partition with Mac OS. The conversion has to be done before you install Opencore so you can boot into the bootcamp drive to be able to do the conversion running windows, once you convert you won't be able to boot into windows until you then install opencore and then Opencore bootloader will see the windows drive and so will Catalina under system prefs startup disk. I did get an error the first time I tried the conversion but it worked on the second try. It may be easier to just install windows 10 from scratch in UEFI only and then Opencore will be able to boot into windows.
Please provide logging file from the debug OC version. Example setup for the log file:
OpenCore on the Mac Pro
forums.macrumors.com
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
This is the macOS support, not UEFI GOP support (which OpenCore use to show the boot screen).