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.
Larsvonhier said:
Crazy since >10 years now, and counting. Several CAD engineering / office Macs running with OCLP (dosdude1 patches before that era).
Click to expand...
If assets is revenue generating, it would be nuts to run on patchers.

As a proper profitable business, it is desirable to have depreciating (working) assets for tax reasons. No need to be stingy on required equipments.
 
At the end, I used a previous backup from Sonoma, and then updated to 14.5.

This time the VEGA 64 keeps working like a charm.

H264 and HEVC ara enabled.
 

Attachments

  • Captura de Pantalla 2024-06-07 a las 3.52.13.jpg
    Captura de Pantalla 2024-06-07 a las 3.52.13.jpg
    108.3 KB · Views: 107
  • Captura de Pantalla 2024-06-07 a las 4.07.07.png
    Captura de Pantalla 2024-06-07 a las 4.07.07.png
    371.9 KB · Views: 81
Last edited:
  • Like
Reactions: deeveedee and h9826790
mwidjaya said:
If assets is revenue generating, it would be nuts to run on patchers.

As a proper profitable business, it is desirable to have depreciating (working) assets for tax reasons. No need to be stingy on required equipments.
Click to expand...
Some say so. (In fact, most do).
I´d still put it the other way round: If i.e. a Mac Pro that we bought in 2016 for around 500 bucks still runs and does its job today - 8 years later, you can put tax deductions away in comparison to spending 2500 to 4000 for new gear all few years.
deeveedee said:
They do now.
Click to expand...
oh my!
 
  • Haha
  • Like
Reactions: Mystere65 and olad
Hompie said:
Anyone any idea, after the update to Sonoma 14.5 with oclp 1.5.0 i receive a error message on every boot or reboot with 'you shutdown your computer because of a problem' any idea what to do about it ?
Click to expand...
Delete the "Sleep Wake Failure" diag file in
\Library\Logs\DiagnosticReports

this fixed it
 
  • Like
Reactions: 0134168
Sadly my old 2009 4,1->5,1 cMP bootrom finally failed :(

Seen the nMP 2019 deals but decided to be cheap and keep saving for a Studio Ultra
Was able to snag a trashcan 6,1 cheap locally, swapped over my ssd, and a quick OCLP rerun, back in business

bpeH8z.png
 
  • Like
Reactions: K two and Mystere65
nekton1 said:
Has anybody here successfully clean installed Sonoma 14.5 final from a USB installer built with OCLP 1.5 final on to a 12" MacBook (NOT PRO and NOT AIR) 9,1 (with internal SSD erased using Disk Utility at OCLP 1.5 Recovery Disk screen)? I have tried numerous times and simply get the 29 minutes remaining screen that counts down to about 21 minutes and then the MB reboots to the same 29 minutes remaining screen and this repeats endlessly. I'm not a novice at this (see signature) but this has beaten me. I've used different USB sticks, redownloaded OCLP and Sonoma several times, reset the NVRAM and SMC, several times, but the result is always the same. BTW, Monterey final installs seamlessly from a standard non-OCLP USB installer without problems.
Click to expand...
Success at last. Did exactly the same as before using the same USB SSD created previously BUT this time I used a power dongle with a USB 3.2 port so the 12" MB 9,1 was not on battery power but was powered from the Apple power adapter and it went OK first time. The previous times I was using either a USB stick or USB SSD connected to the only USB-C port on the MB and a fully charged (new) battery. Don't know whether this is a bug.
 
  • Like
Reactions: waz0wski, rehkram, houser and 1 other person
HowowcanIgo said:
Hi guys,

I’m having some problems.
I’ve waited updating Sonoma to 14.3 and later as everything was working quite well and my machine wasn’t yet supported by OCLP 1.4.2. This week I tried to install Sonoma 14.5 with OCLP 1.4.3. But I never was able to enter recovery mode. I tried 2 flash drives (same make and model). Yesterday I tried again, got prompted OCLP 1.5.0 had dropped and installed it. Again the creation of the usb-installer wen’t fine. But again I wasn’t able to enter recovery. I tried both flash drives but every time I get the prohibited sign or the ‘no input device’-screen even when a keyboard and mouse are connected through a usb 2.0 hub.

Both flash drives have worked since I started using OCLP when installing Monterey a few years ago. The usb 2.0 hub has worked since the problems on older devices with usb1.1 during install.

At last I tried to use an external hard drive to use as an installer (had to borrow one). The installer created just fine but the same problem occurred.

Any ideas?

2 other things I have to mention:
I can’t install the OCLP 1.5.0 patches. The patch-window says to make sure no updates are pending. I was and still am running Sonoma 14.2. And don’t think I can update without OCLP?
Anyway, I never had a problem skipping an update before so I didn’t think it mattered?
Then I got the luminous idea maybe removing the old patches would allow me to install the new ones. That was’t the case. So I’m running Sonoma 14.2 without patches (and created the last usb-installers without installed patches).

And the second and last thing: In one of my attempts I installed the EFI that was meant to be installed to the usb-installer (right after the verification of the usb-installer) to the hard drive.
Does this affect anything?

I won’t pretend I’m an expert in any way, but it’s not the first time I went through the process and experienced multiple hick-ups. But I’ve never had this persistent issue reoccurring time after time.

*edit:
I reinstalled OCLP 1.4.3 and was unable to install the root patches. Error 31 I think? Something with the KDK.
But I created a new usb-installer with this oclp and succeeded to get into recovery. Erased the container of the old install and got through the proces without a hitch.
But guess what: now I can’t get a keyboard or mouse to connect. I use the same usb 2.0 hub, I see the laser eye of the mouse light up when I reboot the computer but as soon as I choose Sonoma installer or plain Sonoma (after choosing usb EFI) the mouse dies and won’t connect again.
Anyone have any ideas? And sorry for the long read.

Thanks for any advice!

Howocanigo
Click to expand...
Anyone got an idea?
I tested the usb-hub by plugging the external installer-hd in it as well and it boots fine. But everytime I the Apple logo comes on I see the laserlight on the mouse die. The light on the external hd stays on.
I tried multiple smc-resets, natal-resets and managed to get into recovery again with working input devices so retried the clean install.
It made it to a full install but again, when entering the setup-stage of Sonoma, the same problem occurs. I can’t seem to get the external mouse and keyboard to work. Or only on a few occasions that I can’t seem to reproduce.
Has anyone experienced something like this?

Thanks!
 
HowowcanIgo said:
Anyone got an idea?
I tested the usb-hub by plugging the external installer-hd in it as well and it boots fine. But everytime I the Apple logo comes on I see the laserlight on the mouse die. The light on the external hd stays on.
I tried multiple smc-resets, natal-resets and managed to get into recovery again with working input devices so retried the clean install.
It made it to a full install but again, when entering the setup-stage of Sonoma, the same problem occurs. I can’t seem to get the external mouse and keyboard to work. Or only on a few occasions that I can’t seem to reproduce.
Has anyone experienced something like this?

Thanks!
Click to expand...
You may need the patches applied for the internal mouse and keyboard to work on your Mac?
I have solved it by having an external old USB Mac keyboard with a built in hub to get through this but any old USB hub (1.1?) and a keyboard and mouse connected to it should get you through it. Good luck.
 
  • Like
Reactions: HowowcanIgo
houser said:
You may need the patches applied for the internal mouse and keyboard to work on your Mac?
I have solved it by having an external old USB Mac keyboard with a built in hub to get through this but any old USB hub (1.1?) and a keyboard and mouse connected to it should get you through it. Good luck.
Click to expand...
Thanks for your reply. The keyboard, mouse, hub, flash drives,… they all worked fine on previous installs that needed the usb-hub workaround already. That’s where I am stumped.
 
HowowcanIgo said:
Thanks for your reply. The keyboard, mouse, hub, flash drives,… they all worked fine on previous installs that needed the usb-hub workaround already. That’s where I am stumped.
Click to expand...
I am probably missing something, but as 14.5 has new kexts it might be worth a try connecting an external keyboard, probably using an OCLP-built USB installer that adds the kexts for you to make sure. Good luck.
 
Last edited:
  • Like
Reactions: HowowcanIgo
houser said:
Hello,
A slightly esoteric OT question maybe but perhaps someone can comment briefly if they have seen this
and have a fix? I have had issues with hibernation on my rMBP 2012 that I never quite figured out.
I today realised it might be a OCLP multi-boot efi issue as I multiboot various OS:s.
I tested a setting in building a new OCLP config.plist:
Settings/Advanced/Misc/Hibernation Work-around
It says:
" Only load minimum EFI drivers to prevent hibernation issues.
Note: This may break booting from external drives."

This fixes my hibernation issues but breaks
Code: 
 ext4_x64.efi
that I have added in OCLP to mount ext4 volumes in Mac OS. in my multi-boot setup.
This probably all makes sense as I assume the Ubuntu efi drivers might also be what is conflicting with the hibernation and why it is prevented from loading. It does not hide the other Win and Mac volumes, only Ubuntu by name under OCLP and rebooting without the hibernation fix brings back the ubuntu boot option.

I can live with it for sure as it is mostly aesthetics but also makes the Linux instances clearer as it says “ubuntu.xxx” and not “EFI” when booting with a few different volumes named "efi"
Ah well. if anyone has seen a fix or a hypothesis for having the best of both worlds I would certainly appreciate it? Working hibernation and cleaner multi-boot would be nice;).
Click to expand...
Staying on-topic would be nice, as well. 🤨
 
  • Like
Reactions: houser
nekton1 said:
Can you elucidate? I have a MM 7,1 (Core i7 2014) and don't think I've seen a Window Server boot crash and Logs–WindowServer shows nothing. Do you see a report somewhere?
Click to expand...
Brief WindowServer crash at boot. Goes away on it's own, no log entry. Just some artifacts across the screen briefly. Suspect others have seen it, as well. Definitely fixed in OCLP v.1.6.0n, latest. :cool:
 
Hmm—can't say that I've seen that but good that 1.60n fixes it for you. But I have seen a brief flash of artefacts when booting a 2013 MacBook Air with Monterey and 1.5 final so maybe I'll update to 1.60n in case that fixes it.
 
K two said:
Brief WindowServer crash at boot. Goes away on it's own, no log entry. Just some artifacts across the screen briefly. Suspect others have seen it, as well. Definitely fixed in OCLP v.1.6.0n, latest. :cool:
Click to expand...
Which 1.60 Commit? I recall seeing something brief after login a while ago on my MBP6,2, but I'm not yet using 1.6.0 (or the latest 1.5.0 for that matter) and haven't seen it. I think the fix for me was already in a previous version of OCLP, but I don't remember what it was. I'll look and report back if I find it.

In the mean time, if you can pinpoint the exact commit, that would be helpful. Thank you.
 
deeveedee said:
Which 1.60 Commit? I recall seeing something brief after login a while ago on my MBP6,2, but I'm not yet using 1.6.0 (or the latest 1.5.0 for that matter) and haven't seen it. I think the fix for me was already in a previous version of OCLP, but I don't remember what it was. I'll look and report back if I find it.

In the mean time, if you can pinpoint the exact commit, that would be helpful. Thank you.
Click to expand...
475b9e7 :cool:
 
  • Like
Reactions: PropClear
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