macOS 14 Sonoma on Unsupported Macs Thread

[MacFoxG4]

Successfully updated my MBP 9,2 to 14.8.1. Sonoma runs really well on here. Only issue I have is that I can’t access my iCloud storage. I clicked the link in Finder to go to the iCloud page in Settings and the Settings app starts up, but it just takes me to a blank page with my name at the top.

EDIT: Signing out of my Apple ID in the Settings app and then signing back in again solved the issue.

 

[carnwath]

Successfully updated my MBP 9,2 to 14.8.1. Sonoma runs really well on here. Only issue I have is that I can’t access my iCloud storage. I clicked the link in Finder to go to the iCloud page in Settings and the Settings app starts up, but it just takes me to a blank page with my name at the top.

EDIT: Signing out of my Apple ID in the Settings app and then signing back in again solved the issue.

Up to 14.8.1 on a MBP 9,2 here too and going well.

 

[paridedamessina]

deleted

 

[K two]

Late to the party.

 

[xboxbml]

Late to the party.
View attachment 2571060

Never too late...

 

[basslik]

Late to the party.
View attachment 2571060

Why not create a new container and tryout Sequoia?

 

[next_cube]

Upgrade OTA (OCLP 2.4.1) to 14.8.1 on a Mac Mini 2014, MBP 15" 2015 and MBA 2017.

 

[Daniel Pascoal]

[I posted this on Sequoia thread, will leave it here too in case it helps anyone]

Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

 

[basslik]

[I posted this on Sequoia thread, will leave it here too in case it helps anyone]

Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

INTERESTING.

i have three containers, with Monterey, Sonoma, and Sequoia. It boots up the last MacOS version I was using.

I have it setup with a 5 second delay to give me enough time to choose an OS.

 

[xboxbml]

[I posted this on Sequoia thread, will leave it here too in case it helps anyone]

Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

Nice job!

 

[dwnldr]

Hello, friends!
I'm just here to say that the iMac 18.3 (5K 27", 2017 with Radeon PRO 8GB) works INCOMPARABLY better with Sonoma 14.8.1+OCLP than previous native versions! I simply have no words and no understanding of how this is even possible... (nice games from Apple...) The last OS I was happy with was "Catalina." I returned to it several times and "stuck" with it until application support for this OS dropped... From that moment on, I had given up on my (for me) still well-equipped iMac. I'm not a heavy user of unsupported versions (I check them out sporadically), but now I can't say anything else but THANK YOU to the developers for their work!

Of course, the question now is how Sequoia would perform on this device?

 

[JimmyT72]

[I posted this on Sequoia thread, will leave it here too in case it helps anyone]

Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

Daniel,
How do I 'disable Spotlight on every volume....' ?
I have a Macair 5,2 with two volumes. Sequoia on one and Sonoma on the other.
Thanks in advance, Jim