Ever tried shift command 4 and space when making screenshots? Instead of cropping images later on.Still using my 11-inch Early 2015 MBA with Sonoma installed
installed using OCLP 0.4.0n and running with no apparent issues.
Ever tried shift command 4 and space when making screenshots? Instead of cropping images later on.Still using my 11-inch Early 2015 MBA with Sonoma installed
installed using OCLP 0.4.0n and running with no apparent issues.
Hello RogueB, thank you for your report. Very useful for me.iMac 13,2 (late 2012):
Installed Sonoma 14.4 beta3 OTA over beta 2 version. Applied OCLP 1.4.0n from 2.13.24.
Everything functions correctly, including iPhotos.
MacBook Pro 5,2 17* C2D 3.02 MGz (Penryn), 1TB SSD :
Applied OCLP 1.4.0n while booted in Ventura, then booted into Sonoma Volume.
Sonoma 14.beta2, installed via USB thumb drive, boots to login screen, but is inaccessible since neither internal keyboard/trackpad nor wired keyboard/mouse are functional (the latter routed through external USB hub) . Can’t login to check functionality. Resetting SMC or NVRAM made no difference.
Booted back to Ventura volume and noted, that after installing OCLP 1.4.0n from 2.13.24, I could no longer login using internal keyboard. I had to use wired keyboard, routed via external USB hub, in order to login. Previously that was only necessary after installing Sonoma variants. I also reapplied patches, but process failed at “rebuilding cache” stage. I took screen shot of the section of OCLP install log, since copy/paste did not function. Patching process stopped due to problems with “missing” USB IO functions.
Reinstalled Ventura via thumb-drive to overwrite the patches, then removed contents of the EFI partition. Reinstalled OCLP to the drive and applied patches, but results were the same. Patching stopped at “rebuilding cache” stage. Resetting SMC or NVRAM made no difference.
Monterey volume remains unaffected by OCLP Version change and boots without issues.
Attached are a screen shout of OCLP output log and , for reference, a screen shot of disk utility mapping the SSD drive on the MacBook Pro.
Hope this may be of help.
I have found that if you try upgrading to the 14.4 then you will run into these issues. At least I have. If you go to the Mr. Macintosh web site and download MacOS 14.3.1 then go to Dortania page on GitHub and download the latest OCLP 1.3.0 you should be okay.That's the main reason I am considering going to sonoma on my mid 2010 MacBook Pro. However if the keyboard and trackpad going to cause fits, Monterrey will suit just fine for several more years.
No I haven't. Thanks for the tip!Ever tried shift command 4 and space when making screenshots? Instead of cropping images later on.
MBP5,2: coming closer to a working machine.Hello RogueB, thank you for your report. Very useful for me.
Regarding MBP 5,2 my results are similar. I first assumed the gradually dying charging circuitry of that machine might be the culprit.
I started with installing 14.4b2 over 14.3 from a USB installer to the internal disk. Using OCLP EFI 1.4.0n from 240213. USB-hub connected keyboard+mouse worked, though not immediately, this time it needed a few unplug/plugins of the hub's USB cable.
Then it proceeded to the login screen. As in your case, external keyboard/mouse were unresponsive. The optical mouse's red LED on the bottom side was off, though the hub's control LED was on. After playing with the USB connectors for quite a while, keyboard/mouse became responsive so I could log in and start the post-install patches. But I made a mistake by not plugging in the Ethernet cable and that failed. The SSD in the end had the undesired Data - Data - ... structure.
Further attempts on re-running the USB installer failed as keyboard/mouse were unresponsive also for the installer.
Now I took the internal MBP5,2 SSD out. Doing further attempts. Connected it to MBP11,1 to erase it and write again the EFI.
Can someone help me here?
Unfortunately, OCLP 1.4 did not solve the problem with WiFi on the iMac at the end of 2013,
not on Beta2 and not on Beta3.
.
I reinstalled OCLP 1.4 specifically for this and also checked the IOSkywalkFamily.kext to
see whether it was the new 1.1.0 and everything was there.
Otherwise, the nVidia graphics as well as Ethernet Lan and Bluetooth
were all successfully patched except for WLAN.
A wonderful and inexpensive alternative is Energiza (https://appgineers.de/energiza).Then, purchase this extremely cost effective utility; AlDente.
It will preserve and extend the life of your new battery.
There is a Discord dedicated to OCLP support.
It's the only way to give feedback.
I have tried everything you wrote several times without success.Establish a cable connection to the Internet and then try out the root patches again, then the WiFi patch should also work. If necessary, connect to the network via a USB cable to your iPhone! (Stay away from macOs betas!)
The Paradise: https://discord.com/invite/rqdPgH8xSNA wonderful and inexpensive alternative is Energiza (https://appgineers.de/energiza).
I've been using it myself since the beta because my original battery also was swollen and I don't want to have this problem with the new third-party battery.
View attachment 2349930
Yes, but WHERE EXACTLY? There are several sub-areas.
View attachment 2349929
I often see screenshots of the system with macOS Sonoma here - where can I find this view (pic 1), because I only know the view as shown in pic 2...🤔
Picture 1
View attachment 2349946
Picture 2
View attachment 2349945
0xCUB3/About-This-HackGitHubhttps://github.com › About-This-Hack.I often see screenshots of the system with macOS Sonoma here - where can I find this view (pic 1), because I only know the view as shown in
The Paradise: https://discord.com/invite/rqdPgH8xSN
The Paradise is where concerns are posted, from the OCLP readme -No offense, but I asked where exactly (which subfolder/category) problems can be reported to the developers. You had sent me the link to the server. pls see pic again
MBP5,2 upgraded OTA to 14.4b3 from b2. Using OCLP from source, latest.MBP5,2: coming closer to a working machine.
Without knowing if this might have (had) an effect, made an OCLP 140n from source, used it for EFI.
Starting the USB installer (which actually resides on the now reinstalled internal SSD) remained tricky. The LED for the optical sensor at the bottom of the mouse kept going off soon after installer started, and not back on. What helped in the end was plugging the USB hub out of the connector on the MBP and immediately plugging back into another of those three USB connectors. That triggered something to power the mouse again.
During the reboots when installing, the LED went on and off again, but during the last three reboots it went off only briefly then back on. So the mouse/keyboard were on for the login!
Just finished the root patches (with the OCLP from source). After reboot internal trackpad/keyboard work (and external as well). Writing now from Safari on that machine.
Next will be OTA installation of 14.4b3.
Thanks, developers!
The Paradise is where concerns are posted, from the OCLP readme -
Support
This project is offered on an AS-IS basis, we do not guarantee support for any issues that may arise. However, there is a community server with other passionate users and developers that can aid you:
Reading the docs is essential.
- OpenCore Patcher Paradise Discord Server
- Keep in mind that the Discord server is maintained by the community, so we ask everyone to be respectful.
Not there, only via the Paradise, as stated within the docs and on Discord. 🧐I think we are talking at cross purposes or I don't understand your statement because I am not a native English speaker.
My point is not that I have general problems etc., but that I can give feedback on development, i.e. if something doesn't work.
And as I said, there are different subcategories on the Discord server for OCLP and it's not clear - not only to me - when to post in which subcategory (please have a look at the picture in the attachment)❗️
For example, the fact that the Photos app always crashes on MacBooks with only one integrated graphics card when you click on Memories or want to edit photos taken in portrait mode is not mentioned anywhere in the OCLP issues on GitHub.
View attachment 2350054
Where else can a user get the attention of developers? Certainly not on a MR thread. The Paradise is intended to gather information, not dispense it. As noisy it may seem, the usefulness of the Paradise can only be measured by the quality of the effort supported.Discord is a scatter-shot unstructured mess. I check it out periodically, and, sure enough, it's even worse than the last time I looked. I don't hang around there, have better things to do than try to trick it into doing something it clearly wasn't designed to do, i.e. provide useful IT information for adults.
I'd say Dortania's success with OCLP is not a lot to do with their presence on cringe-inducing Discord. Which, in a way, makes it even more impressive!As noisy it may seem, the usefulness of the Paradise can only be measured by the quality of the effort supported.
Is your dlstain for Discord in general or for the Paradise specifically? And why would developers direct users there if it wasn't useful? 🤷♂️I'd say Dortania's success with OCLP is not a lot to do with their presence on cringe-inducing Discord. Which, in a way, makes it even more impressive!
As somebody with a mid 2010 MBP, 14.3.1 works well. I get Window server issues like before, but I'm thinking it still has something to do with my external monitor/sleep 🤷♂️ I only use a external mouse (Logitech M705), but the trackpad has never not worked for me.That's the main reason I am considering going to sonoma on my mid 2010 MacBook Pro. However if the keyboard and trackpad going to cause fits, Monterrey will suit just fine for several more years.