Before you installed Big Sur on this iMac, did this iMac run the last native OS for it (maybe El Capitan or high sierra?) and receive all security updates? If not your firmware probably isn’t up to date which can cause problems.I think it's transparent.
Screenshot attached. Do you confirm?
Regards,
Mario
Hi, I'm new to this forum.
I'm trying to reuse an old iMac 9,1 (late 2009).
I have upgraded RAM (8G) and Disk (SSD) and I was able to installed BigSur 11.6.5 using Opencore Legacy Installer.
But I'm feeling that the graphics are not working properly.Some Video applications present video all in green. When hovering on the docker, I have no icons animation.
Can anyone point me how can I check if the graphics is properly installed?
Thanks in advance for any help.
Just to advise that in OCLP 0.44 the above bug has not been fixed, so when you upgrade to 0.44 you need again to delete the specific IOName line in device properties and reboot in order to get Intel Power Gadget (and any other affected apps) to work.So, I installed the OCLP EFI to an empty USB. I opened config.plist and deleted the IOName patch. Saved it and then restarted and booted off this modified USB EFI.
Intel Power Gadget installs and works fine. Also I checked the IORegistryExplorer and now the IOName entry is correctly shown as "string".
I tested sleep/wake and it is working. However, I believe that maybe Deep sleep is not working. This is because when I wake up the iMac, it wakes up very fast whilst I remember it used to delay a little... Is there a way to check if deep sleep is actually working?
I don't have Big Sur installed. But OCLP 0.4.4 verbose/Monterey/426.0.0.0.0/MBP10,2 work flawlessly for me.Has anyone else seen any problems with OC verbose logging on a MacBookPro10,2 (or I guess any other similar system) when updated to bios version 426.0.0.0.0? (Specifically, the last log line repeats and then everything hangs.) Or can report that OC verbose logging is working fine for them, on that combination? I'm actually beginning to suspect an actual Aapl EFI bug of some description (since it seems to apply on multiple versions of OC, going back to at least 0.5.something; and to multiple, including very bare, configs), but looking for more evidence.
Make sure you've installed the latest Catalina security update before going to Big Sur or Monterey. The last sec update for Catalina included a firmware update, and it's the only way to get it.The Wife´s is still in High Sierra.
Since I need to upgrade the OS, could/should go to BigSur or "stay" Catalina?
(Document and some browse).
I don't think, there were any MBPs that were supported by Mojave, but not by Catalina.Actually, maybe Mojave was the last supported macOS for those machines? 🤔
Thanks,Make sure you've installed the latest Catalina security update before going to Big Sur or Monterey. The last sec update for Catalina included a firmware update, and it's the only way to get it.
Actually, maybe Mojave was the last supported macOS for those machines? 🤔
11.6.7 (beta or RC) has been issued, see Discord / updates.Has Apple issued a beta for 11.6.7, or is 11.6.6 'final' for Big Sur?
11.6.7 (beta or RC) has been issued, see Discord / updates.
See MrMacintosh for the InstallAssistant.pkg which is already available for 11.6.7b, as it is for 12.5b.
Thanks,
The problem from Catalina is the "Chrome and Brave crash".
Also, MicrosofT365, needs 10.15 or Higher!
Creating a BS instalation disk, with 045, now....