Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Set the OC_ATTR_USE_FLAVOUR_ICON bit in PickerAtrributes?
Bonjour,

Well no, when I said I missed something.
It's done and it works perfectly, thanks. 👍 😉

03073410.png
 
Last edited:
I hope my mid-2014 rMBP will still be officially supported on Mac OS 12, but if not I’ll be interested to see how unofficial support progresses.

I hope that the Big Sur GPU compatibility fixes for 2011 iMacs can extend to Mac OS 12.
 
With EasyFind or FindAnyFile, keyword(s) - dosdude1 and dd1 will find the Launch Daemons. Right clicking on the two Control Panes removes them. Patch Updater in Utility ƒ can be deleted. 😎
Those two Daemons are the culprits, that's right. But removing the control panel extensions did not remove their files, they kept doing their now useless tasks and crashing. So it might still be considered helpful to remove them manually...
 
  • Like
Reactions: K two
The AppleInternal bit definitely breaks all Big Sur OTA updates, but not updates for anything else (ie. Safari, etc). This is because when the AppleInternal bit is set, the process involved in Big Sur OTAs switches to using an internal server (which has no DNS entry on public DNS), and since that server is not publicly available, it fails. (Redirecting it back to the normal server works fine.) However, things like Safari use a different update mechanism, and they're not affected. Catalina and lower aren't affected either, as they exclusively use the other mechanism - only Big Sur OTAs are broken (whether deltas or the full 12GB downloads that I like to call the "full bundle", for lack of a better term).

I'll check authenticated root/0x800 later, but I doubt it'll change anything. That bit's probably just a red herring with the real cause being broken seal.

@dhinakg Okay, so I now gather that the deal with unauthenticated root 0x800 is not so much that it automatically breaks incremental updates, as that it makes it too easy to break the seal on the OS, perhaps inadvertently, and then obv. you won't get an incremental update, at least not next update. Does that sound about right? (If so, that closes the issue - or rather resolves all my confusions, anyway - thanks! :) )
 
  • Like
Reactions: K two
Those two Daemons are the culprits, that's right. But removing the control panel extensions did not remove their files, they kept doing their now useless tasks and crashing. So it might still be considered helpful to remove them manually...

KnockKnock v.2.3.0 was useful, too in the quest.
 
KnockKnock v.2.3.0 was useful, too in the quest.
Somewhere in the depth of all the posts here there was this „clean installation„ recommendation. It is a fairy tail that one can survive several dozens or system software updates starting at 10.8 or before and end up in the very same state as doing a clean installation with the latest 11.4.

This has not been true with Solaris or Linux (had never a really compelling upgrade story) and it has never been true with macOS. Somewhere on the road you will always hit an unseen block and on the long run you waste more time with repairing than saved before by omitting the full backup, install, restore cycle. And doing the backup/restore cylce is always a good practise. You do not want to figure it out the first time in your life after a nasty hardware crash.
 
  • Like
Reactions: hvds and K two
Somewhere in the depth of all the posts here there was this „clean installation„ recommendation. It is a fairy tail that one can survive several dozens or system software updates starting at 10.8 or before and end up in the very same state as doing a clean installation with the latest 11.4.

This has not been true with Solaris or Linux (had never a really compelling upgrade story) and it has never been true with macOS. Somewhere on the road you will always hit an unseen block and on the long run you waste more time with repairing than saved before by omitting the full backup, install, restore cycle. And doing the backup/restore cylce is always a good practise. You do not want to figure it out the first time in your life after a nasty hardware crash.
So far, haven't had that problem on any of the unsupported Macs. But will keep it in mind, thanks. 11.5b1 OTA works great after the purge, no weird processes running. CPU temp lower than 11.4 or 11.3.1, as well.

Started with a clean install of 11.2.3, used Migration Assistant from 10.5.7 19H1306 Time Machine back-up. The dosdude1 items entered via TM. 🧐
 
  • Like
Reactions: Ausdauersportler
@dhinakg Okay, so I now gather that the deal with unauthenticated root 0x800 is not so much that it automatically breaks incremental updates, as that it makes it too easy to break the seal on the OS, perhaps inadvertently, and then obv. you won't get an incremental update, at least not next update. Does that sound about right? (If so, that closes the issue - or rather resolves all my confusions, anyway - thanks! :) )
Yup. You should be able to check the seal with diskutil info.
 
  • Love
Reactions: Bmju
  • Like
Reactions: mwidjaya and K two
Successful installation of BigSur 11.5 beta 2 on iMac 13,2 (late 2012) with 1TB fusion drive.

Method: BKN's microptacher 0.5.1


Successful installation of Big Sur 11.5 beta 2 on Macbook Pro 5,2 (mid 2009) with Samsung Evo SSD.

See post https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29914333 for details. Note one change, the OCLP disk picker (instance just before booting into desktop) no longer shows two Macintosh HD disks; disks are now displayed with accurate descriptive.

Method: OCLP 0.6.0

Thank you to all developers.

Hope this post is of help.
 

Attachments

  • Screenshot 2021-06-02 at 21.14.58.png
    Screenshot 2021-06-02 at 21.14.58.png
    65.5 KB · Views: 80
  • Screen Shot 2021-06-03 at 14.15.40.png
    Screen Shot 2021-06-03 at 14.15.40.png
    85.1 KB · Views: 81
  • Screen Shot 2021-06-03 at 14.16.19.png
    Screen Shot 2021-06-03 at 14.16.19.png
    21.7 KB · Views: 73
Last edited:
cMP mid 2012 5,1 BS 11.5 Beta 2 updated with OCLP_0.1.6 only had froze at last state, reboot "power button pressed, waited 15 seconds then turn back on".
 

Attachments

  • cMP Mid 2012 5,1 BS-11.5 Beta2 with OCLP_0.1.6.png
    cMP Mid 2012 5,1 BS-11.5 Beta2 with OCLP_0.1.6.png
    1.9 MB · Views: 80
I would bet a substantial chunk of money on the 2015-2017 Airs remaining supported.
Yes, should be ok.

I think there is some correlation with how apple classify products as vintage and obsolete.


Once tagged as obsolete, newest OS support is likely dropped as well.
 
A very harsh cut-off if it eventuates would seem to suggest that Mac OS 12 could be the last Mac OS to run on Intel Macs.
I'd doubt that, and I don't agree with the article on the cutoff for Intel Macs and OS 12. While looking at it from firmware updates is interesting, I choose to look at how Apple has traditionally handled what machines survive every summer. Usually anything that isn't a Mac Pro tower gets six years of OS support from when the machine was launched, give or take a year. Mac Pro towers usually gets 8 years.

The oldest supported OS 11 machines are 2013 models, including my wife's 2013 MacBook Air. Even I was a little surprised it survived for Big Sur but it's still within Apple's normal OS timelines at 6 +/- 1 years. It won't get OS 12 and considering it will be 8 years old later this year, this is expected.

I think the Haswell architecture will be retired which means 2013 and 2014 Macbook airs, 2013 and 2014 MacBook Pros and 2013 and 2014 iMacs will all be retired. A question mark will be the mid-2015 iMac, which is Haswell and only available between May and October of that year before it was replaced by Broadwell and Skylake designs depending on the model (21.5 vs 27). The mid-2015 iMac could easily get the axe since it would still fall into the 6 +/- 1 year guide.

Lastly, the 2013 Mac Pro (Ivy Lake) was being sold right up until the end of 2019, not even two years ago. That means that the 2013 Mac Pro still would survive for OS 12, and there are still a lot of them in production workflows around the world. And I could see them still getting active updates until 2027, six years from now. Assuming that the Late-2019 Mac Pro gets 8 years of support, Intel OS support could easily go out until 2029 and could be longer if Apple refreshes the machine with faster Intel architecture as is currently rumored.

Yes, Apple has cut off machines earlier in their life cycle before (PowerPC->Intel comes to mind) but I can't see Apple doing it to their best content creator customers, some of which literally paid $15K-$50K+ for these machines.
 
  • Like
Reactions: Hombre53
I’m not saying it’s what I want to happen or think will happen but if Apple does drop support very aggressively with Mac OS 12 it would signal it being the last release for Intel but they would extend security updates for much longer than normal say e.g. 5-7 years rather than 3.

Apple won’t want 2013 machines to get security updates till 2026-2028. A lot of businesses, institutions, government etc. will not allow machines to be used once no longer getting security updates, so if Mac OS 12 is the last Intel release it is in Apple’s interests to drop support for as many machines as possible to encourage many upgrades to Apple Silicon in a couple of years time.

I would like to see several more years of Mac OS updates for Intel Macs and a more gradual dropping of support.

I would be disappointed if my mid-2014 rMBP didn’t get Mac OS 12. I’m hoping to hang onto it for a little while yet while Apple Silicon matures. Though having said that I’m still running High Sierra and will probably reluctantly move to Mojave soon.
 
if Mac OS 12 is the last Intel release
Not going to happen. It is not in their pattern.

Besides they are still selling Intel macs right now. Pretty sure these models will get macOS 12, 13 and perhaps even 14.

I would like to see several more years of Mac OS updates for Intel Macs and a more gradual dropping of support.
This is likely what would happen.

I would be disappointed if my mid-2014 rMBP didn’t get Mac OS 12.
That model is tagged as vintage now. So it might slip down into obsolete soon. It should get the macOS 12 but not beyond that, I would think.
 
  • Like
Reactions: ASentientBot
Whose icon set and background? (Your own?! :) )
Bonjour, ;)

Themes mixed from chris1111 (ModernFunnyBlue + Default-Dark-Low + don't remember sorry) for OpenCore 0.6.6, I redid the wallpaper (color and logo from OC, Apple and Ubuntu Mate) and redid my own icon for Ubuntu Mate.

And of course added the missing icons for the last OpenCore version. 😅
 
This is because when the AppleInternal bit is set, the process involved in Big Sur OTAs switches to using an internal server (which has no DNS entry on public DNS), and since that server is not publicly available, it fails. (Redirecting it back to the normal server works fine.)
Thanks for that clear explanation @dhinakg (and @Bmju for pointing to it).

Struggling to see how supported machines would manage though.
I presume "csrutil disable" sets that bit on such units. Why would they not experience the same issue if this would mean they would also be trying to reach an inaccessible private DNS target?
 
I have an issue. I am on BigSur . I have a 160GB hdd connected through Firewire 800 through Apple Thunderbolt to firewire adapter connected to the thunderbolt port.

Strangely the disk keeps getting ejected and mounted without any reason. This happens once a while not very often.

The disk is properly partitioned with Mac OS Extended Journaled with GUID partition. However, while connecting with USB 2.0 port there is no Issue.

I have currently daisy chained 2 Firewire 800 External 3.5 inch HDD(Self Powered through AC Outlet) through single Thunderbolt port on the iMac 27' inch and both drives show well on the desktop

I want to use the higher speed Thunderbolt port as it allows me above process and freeing my USB port.

Anybody having similar issue could provide some insights. Any solution would really help. I face similar issue on Catalina using Thunderbolt Port, maybe also on High Sierra.
 
Last edited:
Bonjour, ;)

Themes mixed from chris1111 (ModernFunnyBlue + Default-Dark-Low + don't remember sorry) for OpenCore 0.6.6, I redid the wallpaper (color and logo from OC, Apple and Ubuntu Mate) and redid my own icon for Ubuntu Mate.

And of course added the missing icons for the last OpenCore version. 😅
Nice mixe great job :cool: theme SilentNight not bad at all
SilentNight.png
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.