Depending on the system there a lot of different patch sets for both metal and no metal systems. Check the OCLP online docs for details.I thought the post install patches were for HD4000, not HD3000(?)
Depending on the system there a lot of different patch sets for both metal and no metal systems. Check the OCLP online docs for details.I thought the post install patches were for HD4000, not HD3000(?)
thank you guys,Best method is to make a clean install, and then use Migration Assistant af first boot.
You want to use wired keyboard and mouse initially.the paired Bluetooth Mouse and the USB keyboard worked well
Great, thanks! Weirdly enough, after trying to boot for a few times more, it suddenly worked with both the USB keyboard and the bluetooth mouse.You want to use wired keyboard and mouse initially.
Present the most basic hardware config while getting it patched.
FYI there is a Lilu fix that was just released today for OCLPThis is an ongoing issue with Lilu:
Lilu dev: @ failed to obtain model information, retrying... · Issue #1903 · acidanthera/bugtracker
Mac Pro 5,1 Opencore REL-076-2021-12-06 OCLP 0.3.3 and Montery 12.1 Sometimes I get the Lilu dev: @ failed to obtain model information, retrying... error when booting. I have bootpicker enabled and...github.com
I can see still same version 0.3.3, shold I just re-download this version and try to create and install new build on the internal Fusion drive?FYI there is a Lilu fix that was just released today for OCLP
not sure if it fixes your exact issue but worth looking into and trying out
Yes, this fix will work. In fact, we discussed it here two days ago:FYI there is a Lilu fix that was just released today for OCLP
not sure if it fixes your exact issue but worth looking into and trying out
Did you get it updated? still having the same issues...This happens to me with monotonous regularity when installing OTA to an external SSD with 512 GB. I have noted that the current 12.1 is a release candidate, not the final production version. I've decided to wait until the production version is released, maybe next week. Will try OTA first, if that fails will do a clean install.
I personally download OCLP using git and then when updates come I do a git pull and use the CLI version of OCLPI can see still same version 0.3.3, shold I just re-download this version and try to create and install new build on the internal Fusion drive?
Great. Please, whats the steps if I am currently on 0.3.3? Just download and run the app (0.3.4) from internal HDD, create new build and install it on internal HDD?The proposed fix is in the most current _034 NIGHTLY.
Yep.Great. Please, whats the steps if I am currently on 0.3.3? Just download and run the app (0.3.4) from internal HDD, create new build and install it on internal HDD?
I can see v 0.3.4 but I dont know how to download it :-D I am able download only version 0.3.3Yep.
Just an update regarding installation to an external SSD. So on my Imac 13,1, it isn't automatic, meaning if I don't manually select the correct boot picker during installation reboots, the process will just error out/hang on a black screen. I've spotted a few Youtube comments stating the same issue. Here is the workaround in case it helps anyone else:It should be automatic.
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30715101
How is the external SSD connected? The screen should go black - just wait a few minutes and it should continue.
Maybe change the background color to something special - not white or black or gray - so you know when OpenCore has started.
For example, without OpenCore, I use the following command to set the background color to a light orange color (see it in the Apple Startup Manager by holding the option key):
Code:source "/Volumes/Work/Programming/ThunderboltProjects/Other/OSXOLVED/gfxutil.sh" setnvramhex 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:DefaultBackgroundColor 7f7fff80
And in the OpenCore config.plist, I use a light blue color:
Which was converted from hex like this:Code:<key>DefaultBackgroundColor</key> <data>/39/AA==</data>
xxd -p -r <<< ff7f7f00 | base64
And converted to hex like this:
base64 -d <<< /39/AA== | xxd -p
The four bytes are the blue, green, red components (the last byte is unused I think).
So whenever I reboot, I know when OpenCore is booting.
It will say "Macintosh HD" for the update from 12.0.1 to 12.1 but during the installation of 12.0.1, there will be a "macOS Installer" item. Anyway, it should be automatically selected and booted by OCLP.
I noticed the same thing when booting to an external SSD. It takes almost 4 minutes compared to 1 with Big Sur. There are some users stating boot times of 30+ minutes, so I guess it could be worse. It looks like a Monterey bugHi guys,
2011 iMac 27" with OCLP 0.3.3 and non-metal patch (Monterey 12.1). Extremely long boot time - Apple logo and progress bar take approx. 3 min 40 s to finally enter the login screen. This is caused by OCLP? Or is the any other culprit? I did a clean install of macOS Monterey 12.1, I have Fusion drive (240 GB SSD + 1 TB HDD) - I installed the OCPL build to SSD when asked. Also I added 4 GB (2x 2 GB) of additional memory recently - now I have 8 + 8 + 2 + 2 (20 GB in all 4 slots). Is there anything I could try to speed up the boot little bit? Thanks.
?Read this: https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/SOURCE.md Consult the CHANGELOG, first.I can see v 0.3.4 but I dont know how to download it :-D I am able download only version 0.3.3
Did you get it updated? still having the same issues...
When a new macOS update comes out, do you mean a beta or a public release? The reason I ask is that public macOS releases are, by definition, waaay more reliable than macOS betas. Lately the public macOS releases are generally followed by a new OCLP release to go with it.or do I need to wait until it's been vetted and repackaged for OCP somehow?
It's not kext editing, it's a patch you need to add to opencore config.plist (kernel --> patch, section).Found this
https://www.tonymacx86.com/threads/how-to-fix-aquantia-10-gb-ethernet-for-big-sur.305261/page-6
at post #54 a guy manages to fix that by my kext editing knowledge is exactly zero.