Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 14 Sonoma on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
TheShortTimer said:
Previously I was using Catalina - which also has sleep issues and was hoping to escape them by leapfrogging to Sonoma. Would I have to reinstall Catalina and then use OCLP to install Ventura or can I do this from Sonoma? Thanks again.
Click to expand...
Do you recall which version of Catalina you were running at that point? The last version was 10.15.7. This may be significant because it contained, for the rMBP10,1 and some other models anyway, a firmware update.

If you want to check whether the firmware is up to date on your Mac I highly recommend using SilentKnight - if you don't have it here's the link to the download selection page: https://eclecticlight.co/lockrattler-systhist/
 
  • Like
Reactions: TheShortTimer, K two and deeveedee
ChrisOSX said:
However, if I select my model, MacbookPro6,2, it selects those by default. So by logic, permissions get changed damn near everywhere.
Click to expand...
... but not sleep image permissions. It is usually best to "Build and Install Open Core" on the target Mac (in your case MBP6,2) and allow OCLP to auto-detect SMBIOS and self-configure. Then manually uncheck the AMFI and LV check boxes.

EDIT: SIP, AMFI and Library Validation do have other "file permission" impacts as you observed. I've been running my MBP6,2 with AMFI and Library Validation disabled fully enabled since OCLP 0.6.8 and all is good. I have my iGPU disabled, but that's because of a problem that (for me) pre-dates OCLP. Note that others here have reported problems with switching between iGPU and dGPU after using OCLP for unsupported macOS.

EDIT2: the sleep issue with the external monitor is interesting. I haven't done much sleep / wake testing with an external monitor connected to my MBP6,2. There is an Acidanthera kext called WhateverGreen.kext that attempts to resolve graphics issues (very popular with hackintosh users and is being used by OCLP on some Mac Models). OCLP does not inject WhateverGreen.kext for the MBP6,2. It might be worth your time to review this kext. Also note that I don't test my real MBP6,2 much any more, because I prefer my emulated MBP6,2 (Dell laptop). If I get some time, I'll revisit testing with my real MBP6,2 to see if I can duplicate some of the issues you reported.
 
Last edited:
deeveedee said:
... but not sleep image permissions. It is usually best to "Build and Install Open Core" on the target Mac (in your case MBP6,2) and allow OCLP to auto-detect SMBIOS and self-configure. Then manually uncheck the AMFI and LV check boxes.

EDIT: SIP, AMFI and Library Validation do have other "file permission" impacts as you observed. I've been running my MBP6,2 with AMFI and Library Validation disabled since OCLP 0.6.8 and all is good. I have my iGPU disabled, but that's because of a problem that (for me) pre-dates OCLP. Note that others here have reported problems with switching between iGPU and dGPU after using OCLP for unsupported macOS.

EDIT2: the sleep issue with the external monitor is interesting. I haven't done much sleep / wake testing with an external monitor connected to my MBP6,2. There is an Acidanthera kext called WhateverGreen.kext that attempts to resolve graphics issues (very popular with hackintosh users and is being used by OCLP on some Mac Models). OCLP does not inject WhateverGreen.kext for the MBP6,2. It might be worth your time to review this kext. Also note that I don't test my real MBP6,2 much any more, because I prefer my emulated MBP6,2 (Dell laptop). If I get some time, I'll revisit testing with my real MBP6,2 to see if I can duplicate some of the issues you reported.
Click to expand...
The only addition I make is allow task for pid (for TotalFinder). The rest is auto chosen for a reason. 👍✌️
 
  • Like
Reactions: deeveedee
@ChrisOSX I had a typo in my previous post and have corrected it. I meant that I have been running with AMFI and Library Validation fully ENABLED (boxes unchecked in OCLP GUI) since OCLP 0.6.8 (not disabled). Thanks for your thorough replies.
 
******* said:
Yes, it does at installation. As I said before, I would love an option not to install the root patches during installation.
Click to expand...
Interesting. Have you found that you are unable to use MA as the last step of a macOS install when macOS installer is built with OCLP? In other words, if you build the macOS installer with OCLP, are you still able to perform MA as the last step of the macOS install when prompted?

EDIT: The reason I ask is that I don't believe I have had any problem with MA when I use a macOS installer built with OCLP (as long as I perform MA as the last step of the macOS install when prompted by the macOS installer).
 
deeveedee said:
Interesting. Have you found that you are unable to use MA as the last step of a macOS install when macOS installer is built with OCLP? In other words, if you build the macOS installer with OCLP, are you still able to perform MA as the last step of the macOS install when prompted?

EDIT: The reason I ask is that I don't believe I have had any problem with MA when I use a macOS installer built with OCLP (as long as I perform MA as the last step of the macOS install when prompted by the macOS installer).
Click to expand...
Nop. The last time I saw that was in Monterey. In Ventura and Sonoma, even during the last step of installation Migration Assistantant dont work. Al least, for me.
 
  • Like
Reactions: deeveedee
ChrisOSX said:
Depending on what you select in the security tab can determine what permissions are set.

If I leave the default "Host Model", Disable Library Validation and Disable AMFI remain unselected.

However, if I select my model, MacbookPro6,2, it selects those by default. So by logic, permissions get changed damn near everywhere.

---
Anyways, it appears after some troubleshooting, having my external connected monitor turned on while it goes to sleep causes the black screen and possible loginwindow / window server errors. So maybe some USB mapping tinkering is in order. Time will tell.
Click to expand...
Running High Sierra and OCLP on the same disk is not recommended. :eek:
 
  • Like
Reactions: perez987, ChrisOSX, davidlv and 1 other person
******* said:
Nop. The last time I saw that was in Monterey. In Ventura and Sonoma, even during the last step of installation Migration Assistantant dont work. Al least, for me.
Click to expand...
I thought I took better notes, but apparently not. I don't remember whether my last full macOS installs were performed with OCLP-built macOS installer or "raw" installer download from Apple. I will need to test again. Thanks.

@******* Your response made me realize that we probably need to follow some loose guidelines for minimal info included when posting requests for assistance. Requests for help should probably include the following:
  • OCLP Version Number (and if not release OCLP build, the date source was downloaded from GitHub and python version used to build OCLP)
  • macOS Version Number
  • Clean macOS install, macOS upgrade (and from the previous macOS version) or macOS install over a previous install?
  • Was macOS installer downloaded from Apple or built with OCLP?
  • If a macOS upgrade, was upgrade performed via OTA or via macOS installer over the previous macOS?
  • Was "Build and Install Open Core" performed on the target Mac or on a different Mac?
  • Target SMBIOS Model
  • AMFI and Library Validation enabled or disabled
 
Last edited:
  • Like
Reactions: olad, hvds, 0134168 and 1 other person
ChrisOSX said:
Good thing they're on separate disks then ;)
Click to expand...
Yeah, a separate disk is good indeed for HS. I had it installed in a different Volume and it constantly issued "Incompatible disk" error messages.
BTW, when you can find the time, could you update the links in your signature, now that the nightly is for version 1.2.0 and the release is 1.1.0?
 
Question, I am able to select open core to show the boot picker on startup without having the option key held every time. The issue seems to be, that Open core wants to boot my native install over Monterey by default instead of Sonoma, and the Open core boot loader is on the Sonoma drive since Monterey doesn't need it to run on this iMac. How do I set Sonoma as the default open core selection?
 
  • Like
Reactions: K two
Can´t find info on what the withdrawn downgrade of 3802 metal Para-virt plugin in OCLP1.1.0 now means for i.e. Kepler.
Had the 1.0.1 and also latest nightlies of 1.1.0 running without hiccups on cMPs with GT630/640.
Any hint where to find it (explanation also welcome!).
 
Last edited:
MacinMan said:
Question, I am able to select open core to show the boot picker on startup without having the option key held every time. The issue seems to be, that Open core wants to boot my native install over Monterey by default instead of Sonoma, and the Open core boot loader is on the Sonoma drive since Monterey doesn't need it to run on this iMac. How do I set Sonoma as the default open core selection?
Click to expand...
Have you tried the ctrl key while in the OCLP boot picker? It should show the cycle-arrow symbol and when you pick and boot the OS of your choice, it should set it as default. Same as in the Apple boot-picker.
 
  • Like
Reactions: K two and deeveedee
Even with official 1.1.0 Photos crashes at startup on MBP8,2. Still monitoring if it gets rid of the abnormal huge usage of kernel_task process. Thanks to devs!
 
Larsvonhier said:
Have you tried the ctrl key while in the OCLP boot picker? It should show the cycle-arrow symbol and when you pick and boot the OS of your choice, it should set it as default. Same as in the Apple boot-picker.
Click to expand...
I did, and it didn't remember the Sonoma drive within the open core picker. Next time I rebooted, it defaulted to Monterey again as the selected drive to boot from within Open core. Do they do that on purpose because Monterey is natively supported so if the unsupported OS has issues, you at least get into a supported OS?
 
MacinMan said:
Question, I am able to select open core to show the boot picker on startup without having the option key held every time. The issue seems to be, that Open core wants to boot my native install over Monterey by default instead of Sonoma, and the Open core boot loader is on the Sonoma drive since Monterey doesn't need it to run on this iMac. How do I set Sonoma as the default open core selection?
Click to expand...
Press the Control key as you choose the EFI icon. (As explained in the OCLP instructions you neglected to read before posting that question, which is why the "A" dev always gets peeved.)
 
  • Like
Reactions: K two
Rats !!!

Late 2009 iMac (10,1) is running Sonoma 14.0 (23A344) without any real issues. I am always just hoping, that the very minimal graphic gremlins, keep improving with each OCLP release.

So, ....I updated OCLP from v1.0.1 to v1.1.0, on a Late 2009 iMac (10,1), installing it to the booting SSD EFI, and then applying post install patches and NOW:

Photos continually crashes when launching?

Anyone else? ...should I revert the OCLP install from v1.1.0 back to 1.0.1?
 
  • Like
Reactions: hvds
davidlv said:
Press the Control key as you choose the EFI icon. (As explained in the OCLP instructions you neglected to read before posting that question, which is why the "A" dev always gets peeved.)
Click to expand...
I'm a bit confused here, I didn't hit the control key before selecting EFI, no, but it remembers the EFI selection without it in the apple boot picker, it's in the open core picker my selection isn't remembered, even with control.
 
MacinMan said:
I'm a bit confused here, I didn't hit the control key before selecting EFI, no, but it remembers the EFI selection without it in the apple boot picker, it's in the open core picker my selection isn't remembered, even with control.
Click to expand...
Not before selecting the EFI icon per se, but after the EFI icon appears and as you select it with a mouse etc. and hit the enter key. That works on my iMac 15,1 which also has Monterey installed on an external disk. Given the 15,1 iMac is not supported by Monterey as your iMac is.
 
BuffyzDead said:
Rats !!!

Late 2009 iMac (10,1) is running Sonoma 14.0 (23A344) without any real issues. I am always just hoping, that the very minimal graphic gremlins, keep improving with each OCLP release.

So, ....I updated OCLP from v1.0.1 to v1.1.0, on a Late 2009 iMac (10,1), installing it to the booting SSD EFI, and then applying post install patches and NOW:

Photos continually crashes when launching?

Anyone else? ...should I revert the OCLP install from v1.1.0 back to 1.0.1?
Click to expand...
Might be something needs to be set in the OCLP Settings (preferences) before the Build and Install step. Have you looked carefully in there? Edit: for something different than in your previous install?
 
Last edited:
  • Like
Reactions: K two
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back