Hello,
Currently running a reinstall on a previously flawless MacBook Pro 11,3 (15" 2014) because of apparent bugs in Opencore 1.1.0. The underlying issue is that opencore changed the native resolution on this macbook to something like 2580xWhatever during boot and then no other monitors work. Had been running Ventura on it for a while without issue.
There's 25 minutes remaining on this install but other attempts have resulted in everything from kernel panic during install to no change, still problematic resolution or spinning login. Have tried to remove kexts without success. Simply by upgrading from 0.6.7 to 1.1.0, I turned a rock-solid daily driver into a brick.
Does Opencore 1.2.0 address this problem? Looking at the release notes, I don't see any reference to the issue and there is apparently no reasonable way to get the attention of the developers. Maybe like Apple, they need to pause new features to address bugs.
Alternatively, is there a way to make it stop using this crazy resolution on boot? Seems like a command line option for the kernel (coming from a Linux background, like an argument to grub like --keep-normal-resolution).
Currently running a reinstall on a previously flawless MacBook Pro 11,3 (15" 2014) because of apparent bugs in Opencore 1.1.0. The underlying issue is that opencore changed the native resolution on this macbook to something like 2580xWhatever during boot and then no other monitors work. Had been running Ventura on it for a while without issue.
There's 25 minutes remaining on this install but other attempts have resulted in everything from kernel panic during install to no change, still problematic resolution or spinning login. Have tried to remove kexts without success. Simply by upgrading from 0.6.7 to 1.1.0, I turned a rock-solid daily driver into a brick.
Does Opencore 1.2.0 address this problem? Looking at the release notes, I don't see any reference to the issue and there is apparently no reasonable way to get the attention of the developers. Maybe like Apple, they need to pause new features to address bugs.
Alternatively, is there a way to make it stop using this crazy resolution on boot? Seems like a command line option for the kernel (coming from a Linux background, like an argument to grub like --keep-normal-resolution).
