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.
I want to make a partition with 10.14 but I want it to be formatted as HFS+. To me, the better way is to interrupt the install process and change items in the install files rather than the CCC approach. To do it that way though, I need to boot from the usb installer but dont know what setting to put on OC to make that work. No usb shows

I suspect there is no HFS+ in the drivers, that may be the culprit... Not sure version of OC here hmm..bless app would give it away

Anyway thanks for all of course
Why interrupt the installation process is better than CCC? I don't get it.
 
Why interrupt the installation process is better than CCC? I don't get it.
My thinking was I would not have to do the extra steps of CCC. Turns out with some reading, The old way of editing files in the install partition does not work anymore. I dont think its worth the effort hearing about things not working without APFS.

I gave up and did the apfs, now the wifi stuff does not load in mojave so its not so great. Should be working with the native wifi/BT card 94360 but I think the kexts to make it work in newer system is probably the reason. Thats a thing Clover has over OC, you could disable kexts at will at the loader...

Extra nvme (second) slowed the OC load pretty significantly. I have to wonder how it would be with no nvme... maybe even faster load? System has 10 disks counting an extra nvme, that is a lot of disks...
 
Last edited:
My thinking was I would not have to do the extra steps of CCC. Turns out with some reading, The old way of editing files in the install partition does not work anymore. I dont think its worth the effort hearing about things not working without APFS.

I gave up and did the apfs, now the wifi stuff does not load in mojave so its not so great. Should be working with the native wifi/BT card 94360 but I think the kexts to make it work in newer system is probably the reason. Thats a thing Clover has over OC, you could disable kexts at will at the loader...

Extra nvme (second) slowed the OC load pretty significantly. I have to wonder how it would be with no nvme... maybe even faster load? System has 10 disks counting an extra nvme, that is a lot of disks...
NVMe's initialisation time on the cMP can be quite long. That's one of the reason why NVMe not necessary boot faster than SATA SSD on cMP.
 
I dont think its worth the effort hearing about things not working without APFS.
It is a quick fire/forget process with CCC.
The only thing that doesn't work are auto updates.
If you are on the last released version, that is no longer an issue.
HFS+ is now a better place to be than APFS on Mojave/HiSierra as a result IMO.

Thats a thing Clover has over OC, you could disable kexts at will at the loader
You missed the "Kernel >> Block" section when you checked the OpenCore documentation.
Here is a link to the properties of that option: Disable Kexts in OC
 
Last edited:
It is a quick fire/forget process with CCC.
The only thing that doesn't work are auto updates.
If you are on the last released version, that is no longer an issue.
HFS+ is now a better place to be than APFS on Mojave/HiSierra as a result IMO.


You missed the "Kernel >> Block" section when you checked the OpenCore documentation.
Here is a link to the properties of that option: Disable Kexts in OC
Auto updates I could not care less about. I enjoyed booting into it, was a fresh install so felt extra snappy. Maybe will do it one day. The HFS I always thought was great as it was.

Ah, thanks for the link. Yea, nice to read the manual. Can really help figure things out. Thats even better fiddle once then you dont even mess around in the loader

As for the Wifi issue, removing those kexts did the trick but what I did not expect was to log back into Monterey and have them work but they are somehow. I thought they dropped support for them in 11

Did not like seeing those notifications of ejected disks when sleeping or even saw them without machine sleeping. Used to have an app I made to do that on sleep but not preferred.
 
Last edited:
Please bear with me on this rather long post.

I have been on OC for a while and about 3 months ago moved from Catalina to Monterey 10.5 skipping Big Sur. Things have been stable until Wednesday.

Now as to some hardware background. I have two disk drive buses. One the standard 4 drive slots and an ArcRaid card with 4 cables that are running Samsung 360 SSD’s that are RAIDed into two drives. My operating system is divided into a system drive and a user drive. Each one on separate drives. All are running APFS.

I cloned a copy of Catalina System to a separate SSD and the user drive was cloned to a separate SSD both on the internal drive bus. All are running APFS.

I then upgraded the two ArcRAID drives (system and user) from Catalina to Monterey. All went well since Apple understands this set up and makes the process fairly simple.

On the boot picker I can see Monterey and Monterey recovery. I can see Catalina and Catalina recovery. I have booted from Monterey and from Catalina.

On the system drive I have an Admin user where the Admin user directory is on the system disk. This allows for logging into the Admin account and using Admin to dismount the normal user drive for disk repair etc.


Which brings us to Wednesday. The machine and been slowing down for a couple of days and a disk utility was reporting the user drive needed repair. So I went into Admin user and run the apple disk utility on the disk and then on the user APFS container. I did notice the number of snapshots went from 61 >> 53. Seems odd.

Afterwards I logged out of Admin and into my account and all was working fast and as expected. Ii worked for about 1.5 hours went to feed the cats and when I came back the screens where off and I couldn’t get into the computer. I forced a reboot and it came up into the boot screen. I picked Monterey and the progress bar starts and gets about 5% in and there is what looks like a kernel panic and we go into a reboot loop. The same things happens with Catalina and the recovery drives.
Tried using safe mode, no joy.

So video works, mouse works, USB works (I have a RF wireless mouse), Firewire probably works (Time Machine flashes) on attempted boot up, sound works.

I spent some time last night checking the diagnostic LEDs. They all act as expected using plug/unplug and diagnostic button etc. I reseated the DIMMs.

So far no joy. I removed all the disk drives and tried a couple of PRAM resets (no joy) and went to bed.



OC EFI, is on the system part of the ArcRaid branch. So if I pull the ArcRaid PCI card for a test I lose the OC EFI.


So to my questions:

1) Any thoughts as to what is the issue?


2) I saw from Martin Lo

If you have a 11.6.2 and OC 0.7.3 as backup. You can …

1) plug in a USB flash drive into the USB 2.0 front port of the cMP

2) Format the USB drive to GUID

3) Mount the EFI partition of the USB drive

4) Install OC 0.8.8 onto the USB drive

5) Run the bless tool (assume ONLY the USB's EFI partition is mounted)

6) Reboot


Can I create all of this on another Mac and put into the MacPro top, front USB and have it work for open core? Doing the blessing seems to be an issue. Of course I am not sure what blessing actually does. Could someone explain in some detail.


3) For doing PRAM resets is it necessary to remove the drives first? And why?


4) Is there any problem with having multiple EFI’s with OC. For instance one in ArcRaid branch and one in the SSD Catalina branch of the disk systems. One can also imagine having a USB that is setup for upgrades. Where one installs it for upgrades and removes when finished. Thoughts??




I do have a Mojave recovery disk and video card but hoping to avoid.


Thanks
 
Please bear with me on this rather long post.

I have been on OC for a while and about 3 months ago moved from Catalina to Monterey 10.5 skipping Big Sur. Things have been stable until Wednesday.

Now as to some hardware background. I have two disk drive buses. One the standard 4 drive slots and an ArcRaid card with 4 cables that are running Samsung 360 SSD’s that are RAIDed into two drives. My operating system is divided into a system drive and a user drive. Each one on separate drives. All are running APFS.

I cloned a copy of Catalina System to a separate SSD and the user drive was cloned to a separate SSD both on the internal drive bus. All are running APFS.

I then upgraded the two ArcRAID drives (system and user) from Catalina to Monterey. All went well since Apple understands this set up and makes the process fairly simple.

On the boot picker I can see Monterey and Monterey recovery. I can see Catalina and Catalina recovery. I have booted from Monterey and from Catalina.

On the system drive I have an Admin user where the Admin user directory is on the system disk. This allows for logging into the Admin account and using Admin to dismount the normal user drive for disk repair etc.


Which brings us to Wednesday. The machine and been slowing down for a couple of days and a disk utility was reporting the user drive needed repair. So I went into Admin user and run the apple disk utility on the disk and then on the user APFS container. I did notice the number of snapshots went from 61 >> 53. Seems odd.

Afterwards I logged out of Admin and into my account and all was working fast and as expected. Ii worked for about 1.5 hours went to feed the cats and when I came back the screens where off and I couldn’t get into the computer. I forced a reboot and it came up into the boot screen. I picked Monterey and the progress bar starts and gets about 5% in and there is what looks like a kernel panic and we go into a reboot loop. The same things happens with Catalina and the recovery drives.
Tried using safe mode, no joy.

So video works, mouse works, USB works (I have a RF wireless mouse), Firewire probably works (Time Machine flashes) on attempted boot up, sound works.

I spent some time last night checking the diagnostic LEDs. They all act as expected using plug/unplug and diagnostic button etc. I reseated the DIMMs.

So far no joy. I removed all the disk drives and tried a couple of PRAM resets (no joy) and went to bed.



OC EFI, is on the system part of the ArcRaid branch. So if I pull the ArcRaid PCI card for a test I lose the OC EFI.


So to my questions:

1) Any thoughts as to what is the issue?


2) I saw from Martin Lo

If you have a 11.6.2 and OC 0.7.3 as backup. You can …

1) plug in a USB flash drive into the USB 2.0 front port of the cMP

2) Format the USB drive to GUID

3) Mount the EFI partition of the USB drive

4) Install OC 0.8.8 onto the USB drive

5) Run the bless tool (assume ONLY the USB's EFI partition is mounted)

6) Reboot


Can I create all of this on another Mac and put into the MacPro top, front USB and have it work for open core? Doing the blessing seems to be an issue. Of course I am not sure what blessing actually does. Could someone explain in some detail.


3) For doing PRAM resets is it necessary to remove the drives first? And why?


4) Is there any problem with having multiple EFI’s with OC. For instance one in ArcRaid branch and one in the SSD Catalina branch of the disk systems. One can also imagine having a USB that is setup for upgrades. Where one installs it for upgrades and removes when finished. Thoughts??




I do have a Mojave recovery disk and video card but hoping to avoid.


Thanks
You should have only one EFI partition.

Yes you can create an EFI partition with your OC config on a USB drive. Create an EFI partition, put the files on it, and then bless the partition.

Boot with the option key (you said you see the boot menu) and select the USB drive (it will say EFI or something like that) and then you will get the OC boot menu and can pick Catalina or Monterey to boot. Once you are booted into macOS you can inspect your EFI partition(s) and fix what you need to get it working like you had it.

I always boot from either a USB drive or a rescue CD with my EFI files there. I do this because I don't want to mess with my legacy Win 10 install - it works fine but is a bit of work when upgrading macOS - I have to manually select the right drive to keep the upgrade process flowing through the 3-4 reboots.

Regards,
sfalatko
 
You should have only one EFI partition.

Yes you can create an EFI partition with your OC config on a USB drive. Create an EFI partition, put the files on it, and then bless the partition.

Boot with the option key (you said you see the boot menu) and select the USB drive (it will say EFI or something like that) and then you will get the OC boot menu and can pick Catalina or Monterey to boot. Once you are booted into macOS you can inspect your EFI partition(s) and fix what you need to get it working like you had it.

I always boot from either a USB drive or a rescue CD with my EFI files there. I do this because I don't want to mess with my legacy Win 10 install - it works fine but is a bit of work when upgrading macOS - I have to manually select the right drive to keep the upgrade process flowing through the 3-4 reboots.

Regards,
sfalatko
Well some progress. Booting from the USB failed a little further into the process. I ended up using a Mojave recovery disk and video card. The OpenCore (0.9.2) seems to have been hosed. I dropped a copy of 0.8.9 an it and it will boot. I then moved the EFI/OC to an internal SATA drive.

So now I can boot in.

The Catalina boot system seems OK. I can boot in and it works normally.

Monterey system is unhappy, things are really SLOW. I don't see any issues in the Activity monitor, or task manager but something is using up lots of space on the user drive and everything is VERY slow. Logging into Admin works better but really limited. How do I boot into SAFE mode on OpenCore. Everytime I have tired Shift after getting to the boot picker I get a reboot. Any suggestions would be appreciated.

Thanks
 
Last edited:
Martin, please check there are old kexts in your 0.9.4 beta
LILU 1.6.6 (new one is 1.6.7)
Whatevergreen 1.6.5 (new one is 1.6.6)
appleALC 1.7.8 (new one is 1.8.4)
 
Martin, please check there are old kexts in your 0.9.4 beta
LILU 1.6.6 (new one is 1.6.7)
Whatevergreen 1.6.5 (new one is 1.6.6)
appleALC 1.7.8 (new one is 1.8.4)
Thanks, I should have those updated. I will double check if I uploaded the beta package which still with the old kext.

Update: Package checked, you are right, and here is the beta 2 with updated kexts.
 

Attachments

  • OpenCore 0.9.4 beta 2.zip
    14.1 MB · Views: 95
Last edited:
Thanks, I should have those updated. I will double check if I uploaded the beta package which still with the old kext.

Update: Package checked, you are right, and here is the beta 2 with updated kexts.
can i use for cMP5,1 with Radeon RX 580?
 
 
#ask
im using OC 0.9.4 With OS HS and Monterey
With AMD Radeon Vega 64
but, after restart or shutdown cant boot just sound boot

must be reset NVRAM first, then it can boot and show picker
how to FIX it?

thanks
 
#ask
im using OC 0.9.4 With OS HS and Monterey
With AMD Radeon Vega 64
but, after restart or shutdown cant boot just sound boot

must be reset NVRAM first, then it can boot and show picker
how to FIX it?

thanks
So, after NVRAM reset, your cMP will boot to OpenCore and show you the boot picker.

But then all subsequent cold boot / warm reboot. You can only hear the boot chime, but nothing shows on the screen. And no matter how long you wait, the cMP won't boot to the desktop and show you anything on the monitor?
 
So, after NVRAM reset, your cMP will boot to OpenCore and show you the boot picker.

But then all subsequent cold boot / warm reboot. You can only hear the boot chime, but nothing shows on the screen. And no matter how long you wait, the cMP won't boot to the desktop and show you anything on the monitor?
yes righ, I don't know what a problem
sometime normal, but sometime after reboot or shutdown just boot chime nothing show anything then restart and loop, as long as it's not reset vram, loop restart
 
If your cMP can boot to OC boot picker after NVRAM reset, that means OC itself is good.

You better check the logic board battery / BootROM healthiness etc for this particular issue. I don't think the issue itself is OpenCore / HWAccel related.
 
If your cMP can boot to OC boot picker after NVRAM reset, that means OC itself is good.

You better check the logic board battery / BootROM healthiness etc for this particular issue. I don't think the issue itself is OpenCore / HWAccel related.
ok bro
thanks so much for info
 
Well some progress. Booting from the USB failed a little further into the process. I ended up using a Mojave recovery disk and video card. The OpenCore (0.9.2) seems to have been hosed. I dropped a copy of 0.8.9 an it and it will boot. I then moved the EFI/OC to an internal SATA drive.

So now I can boot in.

The Catalina boot system seems OK. I can boot in and it works normally.

Monterey system is unhappy, things are really SLOW. I don't see any issues in the Activity monitor, or task manager but something is using up lots of space on the user drive and everything is VERY slow. Logging into Admin works better but really limited. How do I boot into SAFE mode on OpenCore. Everytime I have tired Shift after getting to the boot picker I get a reboot. Any suggestions would be appreciated.

Thanks
Monterey is now running and very zippy. I have no idea why OC went belly up, but it is happy with the new OC install.

The Monterey slowness was caused by Time machine and CCC using up too much disk space with snapshots.
I changed CCC's default to 60GB and that cleared that up. This issue did not cause the OC corruption issue, since they where on different external disk chains and SSD drives.

I found a couple of pieces of software trying to use bluetooth and got rid of them. My mouse uses RF.

As a side note Monterey seems fast or at least as fast as Catalina.

regards
 
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.9.4]
Could you please let me know, what I am doing wrong, running OC 0.9.4 with Monterey installed. McFiver is recognized in the system and the ethernet port is working. But it is not possible for me to get more than 100 MB/s out of the port, connected to my NAS. I've set the network settings to manual and enabled 10Gbase-T and set the MTU to Jumbo9000 but the system report shows up just with 1000Base-T instead of 10Gbase-T. I checked it with Monterey 12.2.1 and 12.6.8. same at both systems. And same situation with Solo10G card. On my other system, I am running Big Sur (which does not support McFiver) with a Solo10G running on 10Gbe. Just wanted to know, if I missed something during installation process or if there is another workaround - would be great to have a feedback, if someone managed it to get more than 100 MB/s transfer speed with McFiver. Thanks a lot!
 
Is there any need/benefit from adding the NVMeFix kext?
I've just cloned by boot drive to an NVMe drive. I can see there are modifications to show NVMe drives as internal, but i'm wondering if there are further optimisations for booting from an NVMe drive on a PCIe adapter.
 
Should explain the motivation here. Had too much from an old system that went way back that I had been updating so I did a clean install and was still getting the system choking at the finder and other things .. so was going to try to enable the tool for resetting nvram. Loaded the plist into propertree and did a clean snapshot and that made the system fail to boot so I took the disk into another machine and got the new OC on it and that fixed it fine now.

I see that you have reset nvram disabled to align with native apple bootloader- But just wondering what could be making the system choke. Could be brand new Monterey is doing some indexing for spotlight?
I took care not to let anything old into the clean install. Should be enough space on drive...


Screen Shot 2023-08-28 at 7.10.36 PM.png





earlier post:
---->Just updated to latest open core and got the validation error here and not sure what to do with that one....My thought is its for hackintoshes... wont bother with it since it works fine

Kernel->Emulate->Cpuid1Data requires Cpuid1Mask to be active for replaced bits!
CheckKernel returns 1 error!

Completed validating /Volumes/EFI/EFI/OC/config.plist in 2 ms. Found 1 issue requiring attention.

Screen Shot 2023-08-28 at 5.44.48 PM.jpg
 
Last edited:
Kernel->Emulate->Cpuid1Data requires Cpuid1Mask to be active for replaced bits!
CheckKernel returns 1 error!

Completed validating /Volumes/EFI/EFI/OC/config.plist in 2 ms. Found 1 issue requiring attention.

View attachment 2251908
This is intentional.

As per the error return, the Cpuid1Data won't be activated unless the user change the Cpuid1Mask to match it.

With this config, the VMM will be disabled for normal daily use. But the user can also just change Cpuid1Mask (with reference to the Cpuid1Data) to enable VMM when they need it (e.g. for Monterey installation).
 
So traditional way of zapping pram should work with this system? Anyway for me it appears to do away with the GOP feature. So is a bit of a trick to get it back .... just happened to have an nvidia supported os online at the time (i have macvidcards gtx 980) Ultimately should keep something that does support it online.

Any idea to get the GOP to come back by itself without swapping cards? No operating EFI on any PCIe, except for whatever apple does, so not going to be that. (Unless just having a couple nvme on could effect it?)

I do believe that it has fixed the lagging problem with the fresh install. Still could switch to a much better system, hackintosh I made but its working pretty good and like the case 10 fold over the pc

Update: THAT did not fix the problem with the lag. I think that taking out the 2nd NVMe card made it run better. Will have to further use it but seems better at the moment.

Put the 2nd one in the 1st card that has 2 slots but did not bother to try enabling it probably cause I did not have the stuff on hand to send more power to it. An expansion slot utility would be cool but good luck on old machines
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.