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.
Latest macOS Monterey 12.7.6 update applied with no issues!
 

Attachments

  • Screen Shot 2024-07-30 at 2.56.08 PM.png
    Screen Shot 2024-07-30 at 2.56.08 PM.png
    73.6 KB · Views: 118
I have installed Martin Lo's OC pkg and it works great - except that my mouse and keyboard both freeze at the boot picker, so I can't choose a different OS. Is there a way to fix this? Been looking all over here but no luck. Also, is there a way to remove the boot picker timeout so it doesn't just load whichever OS it's set to after 10 seconds? Maybe a config file that can be edited? Any help appreciated.
 
  • Like
Reactions: Melbourne Park
I have installed Martin Lo's OC pkg and it works great - except that my mouse and keyboard both freeze at the boot picker, so I can't choose a different OS. Is there a way to fix this? Been looking all over here but no luck. Also, is there a way to remove the boot picker timeout so it doesn't just load whichever OS it's set to after 10 seconds? Maybe a config file that can be edited? Any help appreciated.
Are your mouse and keyboard plugged into native USB 2.0 and not a PCIe card? If plugged into PCIe card, they will not work until OS is loaded.
 
  • Like
Reactions: 0134168
Ok, now for some reason the mouse and kyb don't work in the USB 2.0 slots on the back of the 5,1 cMP. Plugged in a USB 2.0 adapter which got them working, but I remember reading about an issue (Monterey installation?) where the system loses the USB 2.0 kexts in Monterey and only works as 1.1. Sorry if I'm mixing things up, but it's been a while. Is this an issue with Martin Lo's pkg?
 
Ok, now for some reason the mouse and kyb don't work in the USB 2.0 slots on the back of the 5,1 cMP. Plugged in a USB 2.0 adapter which got them working, but I remember reading about an issue (Monterey installation?) where the system loses the USB 2.0 kexts in Monterey and only works as 1.1. Sorry if I'm mixing things up, but it's been a while. Is this an issue with Martin Lo's pkg?

Also here:


I Have MLOC Monterey with original Apple aluminum keyboard plugged into native USB 2.0 port and I have no issues. All my other peripherals are USB 3.0
Screen Shot 2024-08-23 at 7.12.49 PM.png
 
Last edited:
What's the latest strategy for enabling Hardware Acceleration on Mojave? There seems to be a lot of haziness on that subject. The solution seems to be fairly straightforward now on more modern OS's, but I want to do it on Mojave on my 5,1.
 
@aaronhead14, about the latest strategy tons know,
however I do have Mojave installed on both computers

and just checked with videoproc app, if both have acceleration:

pc1 is 2009/2010 and HAS OC installed with Mojave latest version and metal GPU > Hardware info detected with Hardware Acceleration for both H264 and HEVC
pc2 is 2010 has no OC just plain simple Mojave and metal GPU > Hardware info detached give no acceleration status;

so my conclusion is most probably you need next to compatible GPU also OpenCore in place; maybe someone can correct here; got mine via MartinLO which is very straightforward via his Videos on how to do it.


Good Luck+Fun with your computer.

Screenshot 2024-09-13 at 15.59.54.png
 
I'm planning to only have Windows 10 installed on my MacPro5,1 (at the moment I have Windows 10 and Monterey).

Should be okay to install newer versions of @h9826790's OpenCore package from within Windows as long as I can mount the EFI partition, right?
 
Can, tested
Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.

Aha, because PCIe drivers aren't "initialized" so early in the startup process perhaps?
 
Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.

Aha, because PCIe drivers aren't "initialized" so early in the startup process perhaps?
The problem is not PCIe. I forget, does MacPro5,1 have NVMe EFI driver built-in? If not, then you have to put it in the firmware or have it get loaded from a SATA drive using a boot loader or Driver#### NVRAM variables.
https://forums.macrumors.com/threads/mac-pro-3-1-nvme-support-upgrade-guide-questions.2194878/
 
  • Like
Reactions: star-affinity
Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.

Aha, because PCIe drivers aren't "initialized" so early in the startup process perhaps?
You can move the EFI folder to the NVMe EFI partition.

Three points to notes:

1) The cMP must have BootROM 140.0.0.0.0 or above (ideally 144.0.0.0.0)

2) You better bless the NVMe EFI partition when you still have macOS installed. Technically, if you remove your existing drive that contain OpenCore, the cMP will automatically search the remanning drive, and locate the EFI folder. However, there is no guarantee it will happen.

If you have boot screen, either by Mac EFI UGA, or UEFI GOP (e.g. EnableGop), even you've already removed the macOS drive, you can always hold Option key to boot, then manually select (and bless) the OpenCore in the Apple start up manger.

3) Booting OpenCore from NVMe usually much slower than in any SATA drive (even a very slow ancient HDD). This has nothing to do with the drive's performance, but how the cMP initial its storage. If you still have any SATA drive installed as data storage, you can actually put an extra OpenCore copy onto that drive, bless it accordingly, to speed up the boot process.
 
You can move the EFI folder to the NVMe EFI partition.

Three points to notes:

1) The cMP must have BootROM 140.0.0.0.0 or above (ideally 144.0.0.0.0)

2) You better bless the NVMe EFI partition when you still have macOS installed. Technically, if you remove your existing drive that contain OpenCore, the cMP will automatically search the remanning drive, and locate the EFI folder. However, there is no guarantee it will happen.

If you have boot screen, either by Mac EFI UGA, or UEFI GOP (e.g. EnableGop), even you've already removed the macOS drive, you can always hold Option key to boot, then manually select (and bless) the OpenCore in the Apple start up manger.

3) Booting OpenCore from NVMe usually much slower than in any SATA drive (even a very slow ancient HDD). This has nothing to do with the drive's performance, but how the cMP initial its storage. If you still have any SATA drive installed as data storage, you can actually put an extra OpenCore copy onto that drive, bless it accordingly, to speed up the boot process.
Thanks for the info!

If there's no time benefit moving over to the NVMe (and even the opposite) I will just let OpenCore be where it is, on the SATA SSD where I currently have Windows. I will just clone that Windows partition over to the NVMe drive and leave the EFI partition for OpenCore as is.

Or do you think it's good to have an EFI partition with OpenCore in two places (two different drives) just in case something goes wrong with one of them?
 
  • Like
Reactions: crjackson2134
so you can simply use the following process (yours!!) but instead of removing the clone the disk let it in?

You provided this method for OCC

CCC can only clone the OS, it won't clone OC onto another drive.
If you need to move your OC + OS onto a new drive. You can
1) Clone the OS onto the new drive by using CCC
2) Mount the EFI partitions on both drives.
3) copy the EFI folder to the new drive's EFI partition
4) unmount the original drive's EFI partition
5) run the bless tool to "activate" the OC on the new drive
And now, you can shutdown, and remove the old drive.

Can you simply use the following process but instead of removing the clone leave the the disk in, and let CC run every week? Will you boot from it?

I wanted to try clonezilla but i was unsuccesfull, i used an usb drive 32 gb erase it to FAT 32, GUID partition and flashed clonezilla iso on it with BalenaEtcher. When i reboot with optionkey it doesn't show up in the bootpicker.
What the hell am i doing wrong?
 
If someone has an fix for why "Windows" comes up as three entries in the OpenCore boot picker when I only have one physical Windows 10 installation, I'd be happy to get help on that

It used to be two entries (one more than there should) but after doing some command suggested by LLM/AI (used a "bcdboot" command in Windows command prompt to rebuild the boot configuration) I now have three entries instead. 😂

I'm thinking part of the confusion is that I cloned Windows 10 over from one drive to another and the other drive is still "stuck" in OpenCore in some way. Now, why the bcdboot made yet another "Windows" entry show up in the OpenCore boot picker, I have no idea.
 
If someone has an fix for why "Windows" comes up as three entries in the OpenCore boot picker when I only have one physical Windows 10 installation, I'd be happy to get help on that

It used to be two entries (one more than there should) but after doing some command suggested by LLM/AI (used a "bcdboot" command in Windows command prompt to rebuild the boot configuration) I now have three entries instead. 😂

I'm thinking part of the confusion is that I cloned Windows 10 over from one drive to another and the other drive is still "stuck" in OpenCore in some way. Now, why the bcdboot made yet another "Windows" entry show up in the OpenCore boot picker, I have no idea.
You may have just leftover Windows ESPs. Those are also critical, when it comes to unprotected UEFI Windows boots.

Such a boot loader can inject certificates, even when there is no Windows installation on same medium. As of a deleted, former Windows installation.

You should check your firmware for certificates, and use the [check ESPs for Microsoft certificates] tool of the Dumper package to scan your Mac for Windows boot loaders (ESPs).

Dumper link is in my signature.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.