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 don't want to do a restore nor I can do a restore. Anyway. The way to remove all disks instead of disable OC was the way I'm looking for.

I had one bootable 10.14 Install disk and one seperate disk where I want to install 10.14 which I connect both at the front USB ports. Before I remove all disks I bless the 10.14 bootable install disk via startupvolume then shutdown the MacPro5,1 and remove all bootable disks and connect the two disks via USB front.

After the machine starts and the chime sounds it took a short time until the machine finds the blessed 10.14 bootable installer disk and begin to boot. The rest was easy going.

Thank's for the hint about to remove the disks... I was not aware of this trick.
 
  • Like
Reactions: paalb
Odd issue....
Just flashed my new BootRom from Alex.
Noticed my audio is not longer working. When I checked my settings, it no longer shows the optical output as a choice.

Booted back to vanilla install (Mojave) and it is present there.
Wondering what setting in OC would cause this?

1617038606782.png
 
reinstalled BS, still no digital/optical audio option. (Also does not show my GPU audio channels, used to see x3 of them - 1per DisplayPort)
I'll reinsert my OC config and try that..... this is very strange!


UPDATE: This must be a fluke.
I wiped my OC config, started back with the default config.plist (Martin's). Rebooted and my audio is now showing again. Then applied my customizations (nightshift, disabled DirectGopRendering, add DeviceProperies for GPU).

Audio is back now
1617046559476.png




===============
UPDATE:
FINALLY..... got my cMP completed!
Bought a RIPTOP Dual NVMe PCIe card, installed x2 Sabrent 512GB NVMe drives (1 for each OS)
  • OC installed (Used Martin Lo's and added a couple items to from the #1 Post)
    • nightshift, disabled DirectGopRendering, add DeviceProperies for GPU
  • BigSur on Disk1
  • Windows 10 (UEFI) on Disk2
  • Vanilla Mojave in Slot1 (Sata SSD) --> Used for BootRom flashing
  • Then did a quick check on my BootRom, no sign of Microsoft certs, garbage cleaner seems to be doing its job too.
  • **Only caveat I am seeing occasionally is my bluetooth will show as unavailable/missing on random reboots. I know this is a known issue. Since I stay booted to macOS most of the time I dont mind a 2nd reboot every now and then.
Icing on the cake! 👑🎂.... I believe the new BootRom is the reason my Continuity/Handoff is working again, this broke some time ago, so this was a nice touch to have back. Not even a x5 PRAM reset would make this work.

Just waiting for the next BigSur update to see if it notices/downloads/installs it.


PS: Anyone know how to make macOS be the #1 choice in OC Boot Picker?...
 
Last edited:
When enabling hybridization to do Big Sur updates, my workstation turns black/won't boot after the mandatory restart during the update process.

Mounting the disk to one of my other workstations and turing off hybridization in the config file lets the computer boot normally and finish the update process.

I've done update with hybridization two times, with the same boot issue each time.

Any ideas?
 
Anyone know how to make macOS be the #1 choice in OC Boot Picker?
Look at OC documentation for MISC/Security/AllowSetDefault. You cannot change the disks order but you can set the default. And you should set the default boot partition inside MacOS.
 
  • Like
Reactions: fireheadman
**Only caveat I am seeing occasionally is my bluetooth will show as unavailable/missing on random reboots.
There is a pattern:
The first reboot from Mojave to Big Sur will loose the bluetooth. Keep rebooting to Big Sur and it will come back. It is only lost the first switch from Mojave-->Big Sur.
 
By the way I have random disconnects in Mojave on external drives even though they appear internal in Mojave.
 
PS: Anyone know how to make macOS be the #1 choice in OC Boot Picker?...
Your setup is almost identical to mine. Set the Big Sur drive as the startup disk in the system preferences and it should stick to that (it does on mine). I then use the arrow keys in the OC startup to change to Windows.
 
When enabling hybridization to do Big Sur updates, my workstation turns black/won't boot after the mandatory restart during the update process.
You may want to verify that the agdpmod device property is properly set.
 
Look at OC documentation for MISC/Security/AllowSetDefault. You cannot change the disks order but you can set the default. And you should set the default boot partition inside MacOS.

Took a quick look at these 3 areas... didn't see anything obvious to select, but will look more into the documentation.

Your setup is almost identical to mine. Set the Big Sur drive as the startup disk in the system preferences and it should stick to that (it does on mine). I then use the arrow keys in the OC startup to change to Windows.

Since this was fairly easy to do, went ahead and unlocked the panel, selected my drive and re-locked the panel
 
Took a quick look at these 3 areas... didn't see anything obvious to select, but will look more into the documentation.
If AllowSetDefault is set to True in your config.plist, you can highlight a disk, then use CMD+Enter to have bootpicker remember what disk you're chosen previously.

1617143065136.png
 
Hello, good people, just a quick question: if I install OpenCore on my system (I have already SIP disabled for XtraFinder), is it possible to keep up with Mojave security updates?
 
Is someone experiencing jumping during scroll in the OpenCanopy boot picker? I am on one of the latest revisions and it skips an entry (or 2) after each keystroke on the right/left arrow keys.
 
Is someone experiencing jumping during scroll in the OpenCanopy boot picker? I am on one of the latest revisions and it skips an entry (or 2) after each keystroke on the right/left arrow keys.
I'm also on one of the latest revisions. No skipping of entries, but Ctrl+Enter is not saving the selection anymore. I'm pretty sure this feature was working properly when it was first implemented in the builtin picker...

@Bmju, would you have any insight into these issues?

Edit: False alarm in my case. I had disabled AllowSetDefault in my testing. Perhaps, however, the set-default indicator should not appear when the property is disabled, as it is misleading.
 
Last edited:
Is someone experiencing jumping during scroll in the OpenCanopy boot picker? I am on one of the latest revisions and it skips an entry (or 2) after each keystroke on the right/left arrow keys.
Is this on Apple hardware? I would think so, given this thread? There are new keyboard tuning options in OC; download the latest Configuration.pdf and search for KeyInitialDelay to get started. However these only apply to systems using OpenCore KeySupport=true, and you should not need to be using KeySupport on Apple hardware.

If the above does not resolve the issue then please, open an Acidanthera bugtracker issue.
 
Last edited:
Is someone experiencing jumping during scroll in the OpenCanopy boot picker? I am on one of the latest revisions and it skips an entry (or 2) after each keystroke on the right/left arrow keys.
Have just gone into this a little more and have remembered that, for reasons which are yet to be documented, you are probably using OpenCore's implementation of Apple Event even if you haven't asked to. (Basically, this implementation will essentially always be used unless you have opened OpenCore via Apple's picker; and I think on your machine, you don't even have Apple's picker.) And there are some new key delay options which affect OpenCore's Apple Event (although not Apple's).

TL/DR: If you are not using KeySupport - and I believe you should not be - then the failsafe versions of all newly added keyboard options should not be showing any changed behaviour at all. If they are, then this is a bug which you should report.

But in case you are not using the failsafe values for any of the new options and want to know what to change:
  • If you have a not-quite-new version of OC, you may have set KeySkipFirstDelay to true - it needs to be false when not using KeySupport
  • If you have the very latest version of OC, then you may have set KeyInitialDelay to something other than zero - you should not need to do that, when not using KeySupport
Again, if none of this adds up then please just open an issue, as it would be good to get any real problem here fixed before 0.6.8 is released.
 
Last edited:
  • Like
Reactions: startergo
Oh BTW, is choppy movement of a BT mouse (Apple Magic Mouse in this case) expected behavior in OpenCanopy? I assume it's a marvel it actually works, so not a big deal, but perhaps...
 
Oh BTW, is choppy movement of a BT mouse (Apple Magic Mouse in this case) expected behavior in OpenCanopy?
No choppy movement for me with Apple Magic2 mouse, but remember Bluetooth is not reliable in cMP because of the weak signal. In Big Sur I have sometimes difficulty moving the mouse.

BTW, what is the exact setting to enable the mouse, or the needed driver? For my knowledge.
 
Oh BTW, is choppy movement of a BT mouse (Apple Magic Mouse in this case) expected behavior in OpenCanopy? I assume it's a marvel it actually works, so not a big deal, but perhaps...
The lag should be reduced in version 0.6.8.

BTW, what is the exact setting to enable the mouse, or the needed driver? For my knowledge.
Add 16 to PickerAttributes.
 
  • Like
Reactions: hwojtek and TECK
Now the CPU frequency is detected both from TSC and from "Apple"

Code:
00:113 00:014 OCCPU: Timer address is 408 from LPC
00:232 00:119 OCCPU: Intel TSC:  3457999558Hz,  3457MHz; FSB:   132999983Hz,   132MHz; MaxBusRatio: 26
00:242 00:009 OCCPU: Detected Apple Processor Type: 05 -> 0501
00:264 00:022 OCCPU: CPUFrequencyFromTSC  3457999449Hz  3457MHz
00:277 00:012 OCCPU: CPUFrequencyFromApple  3457999558Hz  3457MHz
00:297 00:020 OCCPU: CPUFrequency  3457999558Hz  3457MHz
00:319 00:022 OCCPU: FSBFrequency   132999983Hz   132MHz
00:335 00:015 OCCPU: Pkg 2 Cores 6 Threads 12
Again FSBFrequency is rounded incorrectly

If you have a not-quite-new version of OC, you may have set KeySkipFirstDelay to true - it needs to be false when not using KeySupport
I think that is what it was. The latest version does not have that switch. It came True as default option.
 
  • Like
Reactions: Bmju
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.