I have upated my mac pro 5.1 to Ventura using ocl all good apert from bluetooth My apple keyboard is seen in the settings bluetooth whenI cick connect I get the 6 digit number that I enter on the apple keyboard and press enter, bluetooth settings shows connected but the keyboards greeen light keeps flashing and after a whie the light goes off and blutooth settings says not connected.
any help please ?
thanks
This thread will be dedicated to the discussion of running macOS 13.0 on Unsupported Macs Welcome to the new macOS Ventura on Unsupported Macs thread! We're eagerly awaiting for all our community developers and enthusiasts to test out the new version of macOS. Please play it by ear and only...
I have successfully installed Monterey on my Mac Pro 5.1 mid 2010 (System firmware version: 9144.0.9.6.0).
I have a Titan Ridge which was recognized perfectly and through the correct configuration of the config.plist it works at 40 Gb/s; this allows me to successfully manage the UA Apollo audio interface connected via Thunderbolt.
However I am experiencing two issues:
1. The UA Apollo systematically causes a kernel panic as soon as it is recognized by the system; it happens at any time it is turned on (before turning on the pc, at the initial sound, during loading and even when the operating system is loaded). This only happens the first time you turn it on. After that the system works fine and even if I have to reboot I don't have any other problems.
2. The second monitor is never detected (previously with Mojave it was detected regularly). I have an NVIDIA GeForce GTX 680 4 GB. In fact I don't have the ability to manage multiple monitors from system preferences.
I have successfully installed Monterey on my Mac Pro 5.1 mid 2010 (System firmware version: 9144.0.9.6.0).
I have a Titan Ridge which was recognized perfectly and through the correct configuration of the config.plist it works at 40 Gb/s; this allows me to successfully manage the UA Apollo audio interface connected via Thunderbolt.
However I am experiencing two issues:
1. The UA Apollo systematically causes a kernel panic as soon as it is recognized by the system; it happens at any time it is turned on (before turning on the pc, at the initial sound, during loading and even when the operating system is loaded). This only happens the first time you turn it on. After that the system works fine and even if I have to reboot I don't have any other problems.
2. The second monitor is never detected (previously with Mojave it was detected regularly). I have an NVIDIA GeForce GTX 680 4 GB. In fact I don't have the ability to manage multiple monitors from system preferences.
you use MartinLo Version, the firmware string is spoofed. The real version you can see in supported OS. Or read it with the Dumper what checks the read out data - not what the OS returns.
Monterey has no Kepler drivers. Either upgrade the GPU or go the OpenCore Legacy Patcher path what inserts an older Kepler driver. Has some incompatibilities when it comes to graphics, tho.
you use MartinLo Version, the firmware string is spoofed. The real version you can see in supported OS. Or read it with the Dumper what checks the read out data - not what the OS returns.
Monterey has no Kepler drivers. Either upgrade the GPU or go the OpenCore Legacy Patcher path what inserts an older Kepler driver. Has some incompatibilities when it comes to graphics, tho.
If I replace the EFI files with newer OCLP (1.2.1) the second monitor is regularly detected but I have problems functioning with the Titan Ridge.
This makes me think it's not a GPU problem. I think I need the right config.plist
It's as if in the config.plist of OC 0.9.6 there was a string that doesn't enable multi-monitor support for the GPU I have.
If I replace the EFI files with newer OCLP (1.2.1) the second monitor is regularly detected but I have problems functioning with the Titan Ridge.
This makes me think it's not a GPU problem. I think I need the right config.plist
It's as if in the config.plist of OC 0.9.6 there was a string that doesn't enable multi-monitor support for the GPU I have.
It works!
Mounted the OCLP EFI and added the tbolt.ssdt in Martin's OC EFI to the OCLP ACPI folder. Then amended the config.plist. (Copy/past from ML's ACPI section in config.)
Hello,
Has anyone had success installing Open Core with an NVidia NVS 510 card (this is a Kepler architecture card, it has 4 miniDP outputs, but none other)?
I'm having a problem with signal fading on these miniDP ports when installing BigSur, so maybe someone could share a successful setup with me. The issue is difficult because there is no other video port on this card.
I am trying to do this on a Mac Pro with a single Westmere X5670 processor, disk is SSD
@cdf since very few people are able to understand what “manually configured” means, can you please put into title (NOT OCLP related), in caps? Hopefully it will stop all this nonsense where people keep asking about OCLP.
How do I install Monterey on a new SSD?
The install began but as soon as it booted it booted into the existing Monetery HD. If I reboot Mac keeps booting back to the original Monterey drive whenever it boots and the "in progress" SSD drive does not appear as an option in the boot picker?
EDIT : Could not do that with drive external. Installed drive internal bay 1 but still cannot install Monterey onto it.
Run Installer. Mac reboots.
Auto selects drive in OC chooser "Mac OS Install" (?) and white apple/progress bar gets about 30% scren loses signal then prohibit sign and displays url: support.apple.com/mac/startup.
Takes long press on power to turn off, wait 10 secs and turn on
Chime
Again, selects drive in OC chooser, now goes 100% of the apple logo/ progress bar and stops there
Restarts by itself
NO chime
OC Picker - selects correct drive (now named "startmeup" as per my naming not "Install Mac OS" or whatever it was)
Around 30% again it cuts out screen then displays same url
Long press on power to turn off and power on after 10 secs
Chime
Progress around 30% again with apple logo. Screen loses signal and returns at different resolution
Continues slowly to 40%
Loses screen signal
Back to OC picker with no chime
At about 40% again it loses screen then returns with same prohibit/URL
Turn off / turn on / etc / 40% = URL appears after screen signal loss
OC config has cpuid1 Data and MAsk: set to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
and updateSMBIOS false
Is making a new Monterey system not possible or am I missing something here?
How do I install Monterey on a new SSD?
The install began but as soon as it booted it booted into the existing Monetery HD. If I reboot Mac keeps booting back to the original Monterey drive whenever it boots and the "in progress" SSD drive does not appear as an option in the boot picker?
EDIT : Could not do that with drive external. Installed drive internal bay 1 but still cannot install Monterey onto it.
Run Installer. Mac reboots.
Auto selects drive in OC chooser "Mac OS Install" (?) and white apple/progress bar gets about 30% scren loses signal then prohibit sign and displays url: support.apple.com/mac/startup.
Takes long press on power to turn off, wait 10 secs and turn on
Chime
Again, selects drive in OC chooser, now goes 100% of the apple logo/ progress bar and stops there
Restarts by itself
NO chime
OC Picker - selects correct drive (now named "startmeup" as per my naming not "Install Mac OS" or whatever it was)
Around 30% again it cuts out screen then displays same url
Long press on power to turn off and power on after 10 secs
Chime
Progress around 30% again with apple logo. Screen loses signal and returns at different resolution
Continues slowly to 40%
Loses screen signal
Back to OC picker with no chime
At about 40% again it loses screen then returns with same prohibit/URL
Turn off / turn on / etc / 40% = URL appears after screen signal loss
OC config has cpuid1 Data and MAsk: set to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
and updateSMBIOS false
Is making a new Monterey system not possible or am I missing something here?
OC is the foundation for booting unsupported versions of macOS. To work it needs a tailored configuration that is contained in the config.plist file.
You can create a config.plist for your mac either manually using the first post of this thread as a guide, using MartinLo's customized setup, or you can use OCLP to automatically create a config.plist.
There are pros and cons with each method. Those that use the manual method in this thread tend to like to dive in, understand, and then know exactly what they have configured. Using OCLP you get a config.plist that covers a lot of situations, some that might not necessarily be pertinent for your hardware and it uses root patching to enable legacy hardware. MartinLo's is a customized config.plist that does the heavy lifting of creating the config.plist but doesn't do root patching like OCLP - sort of a middle ground.
@cdf since very few people are able to understand what “manually configured” means, can you please put into title (NOT OCLP related), in caps? Hopefully it will stop all this nonsense where people keep asking about OCLP.
We’ve been through this before and the thread has already been renamed in a way that was agreed to be best. Those who have understood the difference between OCLP and OC can still participate in this thread meaningfully even if they use OCLP.
I believe more can be done on the part of OCLP to eliminate the confusion. Unfortunately, while there seems to have been some openness to my simple recommendations in the past, amendments have yet to be made. The same perplexing inaction is occurring regarding a requested clarification about the security of OCLP.
@cdf
Much thanks for the guide. I installed OpenCore (manually) and managed to install Monterey on my MP51. Afterwards, I took note of this...
⚠️ It is important to enable the VMM flag only when installing and updating. The reason is that the VMM flag impacts performance and disables power management.
So I reversed the VMM flag. The result was the system wouldn't boot back into Monterey.
Then I enabled VMM again, and booting returned to normal.
Does the VMM flag need to remain ENABLED on my system in order to run Monterey, or is something else going on here?
Also, after I login to my iMessages or other iCloud accounts, it completes, shows my content, the kicks me out about 5 seconds later, and asks me to login again. Is this related?
No, only for installing (using option 1 in the guide). Not being able to boot without the VMM flag indicates that something is wrong with the spoofing. Make sure that BoardProduct is properly configured under both SMBIOS and DataHub and that UpdateSMBIOS and UpdateDataHub are set to true.
Also, after I login to my iMessages or other iCloud accounts, it completes, shows my content, the kicks me out about 5 seconds later, and asks me to login again. Is this related?
Yes, this is probably related: when macOS sees the VMM flag, it thinks it’s running in a virtual machine, which can be problematic for iCloud. Also problematic are issues with the spoofing.
OCLP is so good, that most people forget it's developed by a small team of hobbyists who are working on it part time (and probably have jobs and lives outside of OCLP). I agree the OCLP Devs don't want to include potentially negative facts in the main documentation page because that would hurt adoption and hurt donations (the page still says "... you're just as secure as a real Mac" here when dhinakg (one of the two main OCLP Devs) has clearly stated that OCLP-patched Macs can never be as secure as a real Mac in this thread). However, I also think that OCLP documentation and security warnings may take a backseat to OCLP code / bug fixes because of limited developer bandwidth.
For now, until OCLP Devs make time to revise the docs (and hopefully add warnings in the OCLP app), many of the OCLP security issues are documented in this thread. I'm hoping that the OCLP docs (and in-app notices) are changed to include something like this:
By using OCLP, you understand that your unsupported Mac will not receive Apple Rapid Security Responses, your APFS seal is broken to permit installation of uncertified root patches and SIP has been partially disabled. These security downgrades may expose you to computer security vulnerabilities that may not be present when using a Mac that is still fully supported by Apple.
This warning would need to be conditional on the Mac Model (e.g., the Apple RSR security limitation is MacModel-specific).
No, only for installing (using option 1 in the guide). Not being able to boot without the VMM flag indicates that something is wrong with the spoofing. Make sure that BoardProduct is properly configured under both SMBIOS and DataHub and that UpdateSMBIOS and UpdateDataHub are set to true.
Okay, checked those and they seem to be configured as per the guide. Here's the config.plist. The first one (currently using this) has VMM enabled, the second one is after disabling VMM, and resulting in no-boot.
Just can't seem to run without VMM enabled. Clearly I've overlooked something.
forums.macrumors.com
