Same here with rMBP 10,1 2012... very nice.
Got a tip for us?
Let us know
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
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Same here with rMBP 10,1 2012... very nice.
Sorry to be unclear I meant updating the OS. Any point update will fix that. Just running the OS you have from a USB stick without changing anything might also fix it. Not sure. But any update of the OS will make the container name reflect properly.
mac pro 5,1 oclp 1.3.0 can anyone please help I cant connect my apple bluetooth mouse and keyboard they are seen and on connecting the code comes up which I enter, bluetooth then shows connected but the green light still flashes and after a while disconnects my trackpad is fine though?
thanks
thanks
Hi, After changing the volume name in Disk Utility, download and install Intel Power Gadget and reboot. You’ll see the name has now changed in OCLP Picker.
You can uninstall it if you want afterwards and the name change will stay.
Thanks @Ausdauersportler
I did the SSD upgrade earlier this week and the GPU upgrade is definitely on the todo, but what threw me was how sweetly Monterey runs on this machine so I wasn't expecting Sonoma to be laggy to the point of being unusable. I'll give Ventura a whir and see how it fares.
Never heard of this, but it is not maintained anymore.
It looks like Intel themselves recommends not using this anymore:
Last edited:
Hi @Ready-for-Apple! I remember having the same problem a long time ago, but I don't know with which version of the System, before macOS 11 Big Sur.
Searching on the Internet I discovered that there is a specific Terminal command that allows you to change the name of the system disk.
I'm very busy right now and can't search, but you can try if you can find it. However, I can't know if the command works with the new Systems from Big Sur onwards.
Maybe try in Recovery Mode the following, open Terminal and run csrutil disable.
Restart into the macOS version the name you want to change, run Terminal.
In Terminal, run: diskutil info / | grep "APFS Volume Group" and note this is the UUID of your boot drive.
In Terminal type: cd /System/Volumes/Preboot/ (the UUID you got from last command) /System/Library/CoreServices/
If Terminal give no errors, next type sudo bless --folder . --label "NEW NAME" for the boot picker menu.
Restart and hold down Option, the boot volume menu should show the new name.
You may re-enable SIP with the Terminal command sudo csrutil clear within a booted macOS or csrutil enable within Recovery Mode.
Last edited:
ok I have got further with my bluetooth problems apple magic keboard and mouse old version to staying connected, if I run ocpl 1.1.0 my bluetooth devices workand connect fine but it seems to be using my 5.1 built in card.In oclp 1.3.0 the wont stay connected,now If i attach my dongle which I need for distance it doesnt work in 1.1.0 although it it is seen in usb devices.
So my question is how can i get my broadcom bluetooth dongle working in 1.1.0 or 1.3.0 seeing my built in bt or use my kext from mojave whiched worked fine?
thanks
So my question is how can i get my broadcom bluetooth dongle working in 1.1.0 or 1.3.0 seeing my built in bt or use my kext from mojave whiched worked fine?
thanks
I recently received a prompt saying that "OpenCore Legacy Patcher has detected that you are booting an outdated OpenCore Build."
It says I booted from 0.6.8 but have 1.2.1 installed and is asking me if I would like to update the OpenCore bootloader. Will I break anything/experience any issues if I click OK and update the bootloader? I'm hesitant to do so, as I've had to reinstall previously and would like to avoid doing so again, if possible.
For reference, I'm on a Late 2012 Mac mini running Ventura 13.5.1.
It says I booted from 0.6.8 but have 1.2.1 installed and is asking me if I would like to update the OpenCore bootloader. Will I break anything/experience any issues if I click OK and update the bootloader? I'm hesitant to do so, as I've had to reinstall previously and would like to avoid doing so again, if possible.
For reference, I'm on a Late 2012 Mac mini running Ventura 13.5.1.
Attachments
Should be no problem, but maybe install OCLP 1.3.0 first install and repatch because 1.2.1 is also outdated - may also take a look at https://dortania.github.io/OpenCore-Legacy-Patcher/START.html & https://github.com/dortania/OpenCore-Legacy-Patcher/releases ;-) fingers crossed.
Last edited:
Sonoma 14.2 + OCLP 1.3.0 running well on an i7 MacBookPro9,2 (13 inch mid-2012). I'm very pleased with the overall performance! It feels just as fast as it did when running Catalina.
The only major negative so far is that neither Parallels 19.2.0 nor VMware Fusion 13.5.0 are working on this machine. Parallels just shows a black screen, and starting a vm on VMware Fusion yields a "Transport (VMDB) error -14: Pipe connection has been broken" error, after which Fusion crashes and the entire machine becomes unstable.
I've also seen some relatively minor issues with Apple Music. For example, when viewing a playlist, clicking a different playlist in the sidebar selects the different playlist, but the list of songs displayed often remains the list of songs from the first playlist. I'm not sure if that is a general Apple Music bug or something that is showing up because of the unsupported installation. I'm also seeing occasional problems where I am unable to click/select items in the sidebar or in playlists, e.g. I will click on an item, but another item actually becomes selected.
Otherwise, as long as I don't attempt to run Parallels or VMware, the system is running very well. Kudos to the developers.
The only major negative so far is that neither Parallels 19.2.0 nor VMware Fusion 13.5.0 are working on this machine. Parallels just shows a black screen, and starting a vm on VMware Fusion yields a "Transport (VMDB) error -14: Pipe connection has been broken" error, after which Fusion crashes and the entire machine becomes unstable.
I've also seen some relatively minor issues with Apple Music. For example, when viewing a playlist, clicking a different playlist in the sidebar selects the different playlist, but the list of songs displayed often remains the list of songs from the first playlist. I'm not sure if that is a general Apple Music bug or something that is showing up because of the unsupported installation. I'm also seeing occasional problems where I am unable to click/select items in the sidebar or in playlists, e.g. I will click on an item, but another item actually becomes selected.
Otherwise, as long as I don't attempt to run Parallels or VMware, the system is running very well. Kudos to the developers.
Build and Install OpenCore from the patcher. That's it.
Did you ever find a solution to this? The fan ramp up wasn’t too bad on Ventura but the screensavers are now unable on Sonoma.Just a luxury question if allowed and tolerated..
Some of the Aerial screensavers are very nice, but run the GPU out of town...
I don't expect a solution to this other than saying they are a nice pitch for new MacBooks
I would assume the only way to run them quietly on an old-ish Mac without taxing the GPU and running the fans at full tilt would be to down-convert some of the best Screen Savers (should really be called GPU Hoggers) to lower display resolution and perhaps other friendlier codec. Might defeat the purpose by not looking good anymore anyway.
They run quietly on the Apple TV
Ah well, if against all odds, there is a way to run them without upsetting the fans please comment.
Might give that 3rd party Aerials screensaver app a try.
Regardless the pitch is working lol, really want a new macbook!
hi, I just tried it on my mac Pro 5,1 and the bluetooth works just fine.
14.2rc oclp 1.3.0
I'm testing Sonoma 14.2 with OCLP 1.3 on a MacBook Air 6,2. I created a second volume for Sonoma; Big Sur is on the original with my data. I can access the Big Sur volume data from Sonoma. It's not the subject of this post, but I can report that the MBA no longer has a wake-from-sleep issue, which it did with an earlier version of Sonoma.
For now I'm still testing, however if I want to transfer settings and data to the Sonoma volume later, would I use Migration Assistant and the Big Sur volume or a Time Machine backup to copy to the Sonoma volume? I'm curious what people here consider a reliable practice. As noted, I can use the applications and data on the Sonoma volume, and I may get used to this way of working, but it seems clumsy to manage apps and data on another volume.
For now I'm still testing, however if I want to transfer settings and data to the Sonoma volume later, would I use Migration Assistant and the Big Sur volume or a Time Machine backup to copy to the Sonoma volume? I'm curious what people here consider a reliable practice. As noted, I can use the applications and data on the Sonoma volume, and I may get used to this way of working, but it seems clumsy to manage apps and data on another volume.
I updated my macPro 5,1 (specifications in my signature below) from 14.1 to 14.2 (OCLP 1.3.0) two days ago. All appeared to be working well. I did the NVRAM reset. Before the update, I did my routine BootROM reflash without OpenCore from a natively booted Mojave SSD with a clean image from @tsialex.
Yesterday evening it 'froze' - I noticed because the TV app stopped streaming a video file to my Apple TV. Neither the wired trackpad 2 nor the wired Mac keyboard was working. The macPro was unresponsive. I had to restart the macPro by using the power button. The same freeze has taken place while backing up one 24Tb RAID drive to its identical backup this morning. (I was using SuperDuper to do the backup. I do this every 24 hours with a third copy of the drive once per week.)
I had to do the power button restart again to continue the backup. After approximately 30 minutes it happened again. Then 20 minutes later again. On the second occasion, I copied the error report into a text file and have attached it below.
I am at a loss to discover how to fix this - any suggestions?
Yesterday evening it 'froze' - I noticed because the TV app stopped streaming a video file to my Apple TV. Neither the wired trackpad 2 nor the wired Mac keyboard was working. The macPro was unresponsive. I had to restart the macPro by using the power button. The same freeze has taken place while backing up one 24Tb RAID drive to its identical backup this morning. (I was using SuperDuper to do the backup. I do this every 24 hours with a third copy of the drive once per week.)
I had to do the power button restart again to continue the backup. After approximately 30 minutes it happened again. Then 20 minutes later again. On the second occasion, I copied the error report into a text file and have attached it below.
I am at a loss to discover how to fix this - any suggestions?
The only issued I've been having since upgrading to macOS Sonoma 14.2 (from 14.1.2 via OTA & OCLP 1.3.0), I am having this kernel panic every time the iMac 15,1 goes to sleep.
Does anyone have a suggestion on how to fix this issues or a work around?
Any help is greatly appreciated -- many thanks!
Does anyone have a suggestion on how to fix this issues or a work around?
Any help is greatly appreciated -- many thanks!
Attachments
Have you tried this?
Download Ben Baker's Hackintool.app. Use the app to edit NVRam directly. Look for the entries:
bluetoothExternalDongleFailed
bluetoothActiveControllerInfo
bluetoothInternalControllerinfo
Delete all the entries, and wait for the NVRam to refresh itself. At least one of the entries (bluetoothExternalDongleFailed) should come back with value of <00>. If not, repeat deleting the entries.
For me bluetooth worked correctly again, when I performed the above steps, bluetooth settings will show all previously paired devices, and auto connect to them just as before the update.
Guys, I need some help. In updating my MBP11,4 to Sonoma 14.2 (update window download - about 13 gb, install, restart in Safe Mode, apply patch, restart etc...), I - somehow - renamed my main macOS drive - o' and I can't figure out how. So I renamed the SSD back to macOS, did FirstAid test with Disk Utility and confirmed the drive's label - macOS. There were no errors, and I rebooted starting with Option, only to find the drive's name didn't change (from o'). Yet, the drive boots normally and has the macOS name on the desktop. It is not causing me any grief, but I would prefer to remove the o' name from the drive. Can anyone advise me how to go about it? I am using OCLP 1.30. Thanks.