MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[CaBa71]

Thanks for your support, @sfalatko!

I believe I followed all necessary steps, but I will give it one more thorough try during the weekend, and provide an update on the settings and options I used (and eventually post my config file).

I am aware Surplus is needed to boot Big Sur (and I already had it included and working in my OC 0.67 config).
From the table listed under "Overview of basic settings" with respect to changes that may be needed, would there be any mandatory changes needed in order to boot Big Sur?

ThirdPartyDrives	true	1 is recommended to enable trim on standard SSD drives
HideAuxiliary	true	Hide recovery mode (press Space to reveal at the boot menu)
LauncherOption	Full	Full is recommended to ensure boot persistence of OpenCore
DirectGopRendering	false	false is recommended as long as the boot menu still appears
PickerAttributes	80	Enable pointer control and hide shutdown and restart buttons
ShowPicker	false	Hide the boot menu (show by holding Escape at startup)
Timeout	0	Disable timeout when boot menu is shown
ExposeSensitiveData	0	Minimize traces of OpenCore
SecureBootModel	Default	Enable Medium Startup Security (Big Sur and later)
WriteFlash	true	true is only recommended if your firmware chip is healthy (need to check?)
AppleBootPolicy	false	The native protocol works fine in Big Sur and later

I had set DirectGopRendering to "false", but left everything else as in the default config for OC 0.76, expecting no other changes needed to be required.

Thanks!

 

[hwojtek]

I am aware Surplus is needed to boot Big Sur (and I already had it included and working in my OC 0.67 config).
From the table listed under "Overview of basic settings" with respect to changes that may be needed, would there be any mandatory changes needed in order to boot Big Sur?

If it ain't broken, don't fix it.

WriteFlash

true

true is only recommended if your firmware chip is healthy (need to check?)

You may find setting this to "false" beneficial if your computer has collected some garbage in the NVRAM throughout the years.

AppleBootPolicy

false

The native protocol works fine in Big Sur and later

You may want to set it to 'true' as per directions from the manual - it works as intended in BS and later.

 

[cdf]

Hi @cdf, any updates on this?

Not yet. It'll be added to the guide as time permits.

In which config file?

Your config for 0.7.6 in post #9,952 uses Mac-7BA5B2D9E42DDD94 (iMac Pro). But I understand now that you fixed that in later versions. Good. In that case, no need to add agdpmod=pikera.

As I wrote, I started editing OC 0.76 sample config file, following step by step the instructions in first page... but I can't boot Catalina (lately also Mojave) with OC 0.76. I tried even using unmodified sample file, and today I tried to add "agdpmod=pikera" in the configuration that most closely follows the instructions (config 076.plist). I tried even to pick some other parts from my working OC 0.72 config file (config AB.plist), but with none of them, I'm able to boot using OC 0.76

Try setting SecureBootModel to Disabled. Note that you should be able to boot Mojave (at least) with the sample config as is.

Edit: I just remembered, FeatureUnlock has been causing panics:

Lilu: kernel panic on Catalina 10.15.7 when patching `_cs_validate_range` in plugins · Issue #1898 · acidanthera/bugtracker

Hi, I got a kernel panic on 10.15.7 when booting up with Lilu 1.5.8 and plugins that patch the _cs_validate_range function, such as RealtekCardReaderFriend and FeatureUnlock. panic(cpu 2 caller 0xf...

github.com

Disable the plugin for now. The next release of Lilu will bring a fix.

 

[0134168]

If it ain't broken, don't fix it.

Amen

 

[NC12]

I have been unable to properly use USB 2.0 devices ever since updating to Monterey. I know there were hot swapping issues but even devices attached on boot do not connect half the time. I know OCLP has patches to resolve this but I would prefer not to go that route. Are there any other fixes for this?

 

[jameslmoser]

I have been unable to properly use USB 2.0 devices ever since updating to Monterey. I know there were hot swapping issues but even devices attached on boot do not connect half the time. I know OCLP has patches to resolve this but I would prefer not to go that route. Are there any other fixes for this?

What did you update from? The issues started in Big Sur, just curious if they aren't worse in Monterey than Big Sur.

I have a usb hub in a KVM I use, and a USB 3 pcie card in the machine that works fine if I need it. Do either of these solutions work for you yet?

 

[NC12]

What did you update from? The issues started in Big Sur, just curious if they aren't worse in Monterey than Big Sur.

I have a usb hub in a KVM I use, and a USB 3 pcie card in the machine that works fine if I need it. Do either of these solutions work for you yet?

I tried using the USB 2 hub and that didn’t work either. I have a 10gb/s USB C card and that works fine

Oh and I updated from Big Sur which somehow I didn’t have any problems with

 

[jameslmoser]

I tried using the USB 2 hub and that didn’t work either. I have a 10gb/s USB C card and that works fine

Oh and I updated from Big Sur which somehow I didn’t have any problems with

Interesting... my KVM is also usb 3, but its hooked up to the USB 2 port on the mac pro. On Big Sur, no problems. Some of my usb 2 drives, etc, work, some do not unless I use the pcie add on card or they are plugged in from boot.

 

[Scansterz]

Audio files, video files, quicktime, youtube videos... nothing plays! Help!
By not playing I mean, press play and nothing happens, no movement in quicktime/Youtube/Finder.

I did get alert sounds to sound out.

MacPro 5,1 Opencore 0.7.3. V2 - Fresh install from scratch to new hard drive today of Big Sur.

Any thoughts? I could not find topic while searching; sorry if it's been addressed before.

 

[borgo1971]

Disable the plugin for now. The next release of Lilu will bring a fix.

Thanks for the tip. I'll wait for the next (Lilu) release, to spend other time on OC upgrade.
I started to upgrade the nvme drive hoping to give a hardware/software refresh (need 2TB disk for an additional BigSur/Monterey partition, and even I'll need more space later to hold another vintage macOS VM) to my Mac between Christmas and the end of 2021, and I'm stuck here with OC 0.72 and a lot of work to finish.
I hope to turn back next time to report success in OC upgrade... ;-)
P.S.: Although I am really grateful for your work here, could I suggest that you put a notice in the guide for this issue?

 

[photodok]

Here's what I'm getting back from terminal with the --verbose:

-bash-3.2# bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/OC/OpenCore.efi --verbose
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is '/Volumes/EFI'
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk1s1
Returning booter information dictionary:
<CFBasicHash 0x7fb2fb500330 [0x109eb28e0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x1098d3be0 [0x109eb28e0]>{contents = "System Partitions"} = (
disk1s1,
disk0s1
)
1 : <CFString 0x1098d43c0 [0x109eb28e0]>{contents = "Data Partitions"} = (
disk1s1
)
2 : <CFString 0x1098d43e0 [0x109eb28e0]>{contents = "Auxiliary Partitions"} = (
)
}

Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi
IOMedia disk1s1 has UUID DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15
Setting EFI NVRAM:
efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</string></dict></array>'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
NVRAM variable "boot-args" not set.
-bash-3.2#

Does anyone see where things might be going wrong and what I might need to do to make it work?
Thank you in advance for any clues.

it's possible you blessed the wrong efi partition.
From recovery or another OS run terminal and enter "diskutil list"
Find the drive that has the OS you want to run, right above the #: will have the disk id, if it has (synthesized) instead of (internal/external, physical) you won't see the efi in list below it and there will be a physical store disk id just above line 1. Scroll the list to find that disk and you will see the efi there with its complete idenifier, bless that partition.

 

[Fastsavage]

Audio files, video files, quicktime, youtube videos... nothing plays! Help!
By not playing I mean, press play and nothing happens, no movement in quicktime/Youtube/Finder.

I did get alert sounds to sound out.

MacPro 5,1 Opencore 0.7.3. V2 - Fresh install from scratch to new hard drive today of Big Sur.

Any thoughts? I could not find topic while searching; sorry if it's been addressed before.

Is this in your browser - or are you using VLC or......
What file types?
If you right click on a file that won't play and then go GET INFO what is the Open with?

 

[Fastsavage]

Thanks for your support, @sfalatko!

I believe I followed all necessary steps, but I will give it one more thorough try during the weekend, and provide an update on the settings and options I used (and eventually post my config file).

I am aware Surplus is needed to boot Big Sur (and I already had it included and working in my OC 0.67 config).
From the table listed under "Overview of basic settings" with respect to changes that may be needed, would there be any mandatory changes needed in order to boot Big Sur?

ThirdPartyDrives	true	1 is recommended to enable trim on standard SSD drives
HideAuxiliary	true	Hide recovery mode (press Space to reveal at the boot menu)
LauncherOption	Full	Full is recommended to ensure boot persistence of OpenCore
DirectGopRendering	false	false is recommended as long as the boot menu still appears
PickerAttributes	80	Enable pointer control and hide shutdown and restart buttons
ShowPicker	false	Hide the boot menu (show by holding Escape at startup)
Timeout	0	Disable timeout when boot menu is shown
ExposeSensitiveData	0	Minimize traces of OpenCore
SecureBootModel	Default	Enable Medium Startup Security (Big Sur and later)
WriteFlash	true	true is only recommended if your firmware chip is healthy (need to check?)
AppleBootPolicy	false	The native protocol works fine in Big Sur and later

I had set DirectGopRendering to "false", but left everything else as in the default config for OC 0.76, expecting no other changes needed to be required.

Thanks!

Since you have a dual processor remember to use AppleMCEReporterDisabler

If your Mac has two processors

Because of the spoofed board ID, you'll need an extra component:

Component ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀	Description ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀	What to do ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀
AppleMCEReporterDisabler	Dual-processor workaround	Download the compressed file from the linked post

➊ Copy the file "AppleMCEReporterDisabler.kext" to your ESP as indicated below:

ESP
└── EFI
⠀⠀ ⠀├── BOOT
⠀⠀ ⠀└── OC
⠀⠀⠀⠀ ⠀ ⠀├── ACPI
⠀⠀⠀⠀ ⠀ ⠀├── config.plist
⠀⠀⠀⠀ ⠀ ⠀├── Drivers
⠀⠀⠀⠀ ⠀ ⠀├── Kexts
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── Lilu.kext
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── WhateverGreen.kext
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── FeatureUnlock.kext
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀└── AppleMCEReporterDisabler.kext
⠀⠀⠀⠀ ⠀ ⠀├── OpenCore.efi
⠀⠀⠀⠀ ⠀ ⠀├── Resources
⠀⠀⠀⠀ ⠀ ⠀└── Tools

➋ Enable the kext:

Find ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀

Replace ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀

<key>Kernel</key> <dict> <key>Add</key> <array> ⋮ </array> <key>Block</key> ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀

<key>Kernel</key> <dict> <key>Add</key> <array> ⋮ <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AppleMCEReporterDisabler.kext</string> <key>Comment</key> <string>Dual-processor workaround</string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>19.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> </array> <key>Block</key>

 

[flaubert]

Edit: I just remembered, FeatureUnlock has been causing panics:

Hi @cdf , should feature unlock be turned off for the time being on all OS versions, or just Catalina as was mentioned in the link below your warning above?

I have a documentation suggestion for the first post: you have some tables in Basic Setup with plist items/keys. I wonder if the tables could be expanded with columns for each OS (Mojave, Catalina, Big Sur, Monterey), and then simple compatibility information put in cells like Yes/No/See note xx. This would likely cut down on newbie questions about "should this be turned on or off in Catalina?" and such. Similarly, a table summary for the kext items might cut down on questions and uncertainty.

My test system is running Monterey 12.1 fine, boots reliabley with no problems. In the basic setup section, second table, where it begins with "third party drives" and ends with "Apple boot policy" I have implemented all of those settings as shown, except for the one about writing to the flash. I've also turned on hybridization, firmware features, lilu, whatevergreen, featureunlock, and the dual processor workaround. However, I haven't tried to do anything tricky with it yet, like do an OTA upgrade. I'm not 100% sure of what I'm doing for use cases other than simple booting, so I thought I would check with you on a few items:

Booting into recovery should just work? (I have the Apple hotkeys turned on)

Can I turn SIP off and on as usual by booting into Recovery?

Will clearing PRAM using command option P R on boot mess anything up?

Can I turn on keepsyms in boot-args without any interference?

Can I install third party kexts like the one for ZFS (from openzfsonosx.org)?

For over-the-air upgrades, just turn on VMM and reboot prior to attempting the update?

Finally, I sometimes contribute to Allison Sheridan's "Nosillacast" podcast at podfeet.com; I'd like to do a review of OpenCore on the Mac Pro 5,1, and part of that would involve explaining how the technology works. Would it be all right to privately send you a draft of the review to make sure that I'm explaining correctly?

Thanks for all your help, as always!

 

[cdf]

Hi @cdf , should feature unlock be turned off for the time being on all OS versions, or just Catalina as was mentioned in the link below your warning above?

I've only ever experienced the issue with Catalina, but from the technical explanation of the bug, it is not quite clear to me that other versions of macOS would not be affected. It's a moot point, though, because the fix is just a few hours away from being released.

I have a documentation suggestion for the first post: you have some tables in Basic Setup with plist items/keys. I wonder if the tables could be expanded with columns for each OS (Mojave, Catalina, Big Sur, Monterey), and then simple compatibility information put in cells like Yes/No/See note xx. This would likely cut down on newbie questions about "should this be turned on or off in Catalina?" and such. Similarly, a table summary for the kext items might cut down on questions and uncertainty.

Makes sense. In fact, I plan on adding some notes with of the following information:

All settings in the tables are suitable for macOS Mojave and later, provided that the right board ID is chosen for the hybridization. The "cleanest" solution (described in post #1) is "Mac-27AD2F918AE68F61" (Mac Pro 2019), but that is only for Catalina and later. To boot Mojave, then either 1) SecureBootModel must be disabled and -no_compat_check kept in the boot args, or 2) the board ID must be changed to "Mac-7BA5B2D9E42DDD94" (iMac Pro), but because this change can result in a black screen at boot, the agdpmod=pikera property should be added. Moreover, DRM in Mojave and Catalina requires the shikigva=80 property.

There will also be an additional section with all the details.

Booting into recovery should just work? (I have the Apple hotkeys turned on)

Yes. Either Command-R or selecting the recovery image at the OC boot menu should just work.

There was an issue with loading recovery in the past (Mojave and Catalina), which was fixed with AppleBootPolicy=true. However, I haven't been able to replicate the issue recently with AppleBootPolicy=false. Therefore, while the sample config still includes AppleBootPolicy=true, you can set it to false, as recommended in the second table.

Can I turn SIP off and on as usual by booting into Recovery?

Yes. The setup detailed in post #1 allows for this. See post #7,645 for my take on managing SIP.

Will clearing PRAM using command option P R on boot mess anything up?

It depends. If the disk with OC gets the top boot priority after an NVRAM reset and you have LauncherOption=Full, then resetting the NVRAM will be just like on a supported Mac, because OC will automatically start and rebless itself. This is what you want to achieve with your setup. Unfortunately, there is no clear-cut rule for which disk gets the top boot priority, so it will take testing to determine. When testing, make sure to have a Mojave disk, so that you can always boot natively (possibly by removing your other disks) to rebless OC manually. This can be painful at first, but well worth it in the end.

Can I turn on keepsyms in boot-args without any interference?

Yes. This is perfectly fine and often used with OC for getting meaningful panic reports.

For adding boot-args, there are two possibilities:

1. If you've cleaned up your NVRAM as described in post #1, then you can add boot-args as usual: nvram boot-args=... in Recovery.
2. Otherwise, you should add boot-args in your config (next to -no_compat_check).

Can I install third party kexts like the one for ZFS (from openzfsonosx.org)?

Yes. You should probably try injecting them through OC (like Lilu, etc.).

For over-the-air upgrades, just turn on VMM and reboot prior to attempting the update?

With your setup (Monterey, Hybridization, SecureBootModel=Default, "updated" firmware features), you shouldn't have to turn on VMM. OTA updates should just work. In your case, VMM should only be necessary for Catalina.

Would it be all right to privately send you a draft of the review to make sure that I'm explaining correctly?

Sure.

 

[cdf]

The guide has been updated to OpenCore version 0.7.7. See Maintenance for the changes that you should make to your config.

Thanks to the amazing work of @Bmju, this version brings audio support to the boot menu.

Happy updating!

 

[PeterHolbrook]

Thanks to the amazing work of @Bmju, this version brings audio support to the boot menu.

What exactly does that audio support entail? Is this some kind of help for visually impaired users? What sound effects, if any (at boot time?), can you get by using the audio parameters in config.plist?

 

[borgo1971]

The guide has been updated to OpenCore version 0.7.7. See Maintenance for the changes that you should make to your config.

Thanks to the amazing work of @Bmju, this version brings audio support to the boot menu.

Happy updating!

Thanks to all the people that work on this project. But I find the Maintenance guide a bit disorienting because I can't understand in which point I should add the text above. Maybe, it could be added in any point in UEFI key, but why are the portions of text separated by dots?

Add ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀
<key>UEFI</key>
<dict>
⋮
<key>AppleInput</key>
<dict>
⋮
<key>PointerPollMask</key>
<integer>-1</integer>
<key>PointerPollMax</key>
<integer>2</integer>
<key>PointerPollMin</key>
<integer>2</integer>
⋮
</dict>
⋮
<key>Audio</key>
<dict>
⋮
<key>AudioOutMask</key>
<integer>-1</integer>
⋮
<key>DisconnectHda</key>
<false/>
<key>MaximumGain</key>
<integer>-15</integer>
<key>MinimumAssistGain</key>
<integer>-30</integer>
<key>MinimumAudibleGain</key>
<integer>-128</integer>
⋮
</dict>

 

[PeterHolbrook]

^Why don't you insert those keys where they should be alphabetically? The dots simply mark a discontinuity. Copy the relevant section, paste it where it should go, and then move on to the new section.

 

[cdf]

What exactly does that audio support entail? Is this some kind of help for visually impaired users? What sound effects, if any (at boot time?), can you get by using the audio parameters in config.plist?

Yes, useful for the visually impaired, but also useful for restoring the boot chime (some machines lost it with MP51.0087.B00) and for when the boot menu doesn't show (graphics cards with broken GOP or Thunderbolt displays on cold boots). The audio includes messages like "Welcome to OpenCore", "macOS selected", "loading macOS", ...

These are the basic changes to enable audio assist:

PickerAudioAssist=true
AudioDevice=PciRoot(0x0)/Pci(0x1b,0x0)
AudioSupport=true
DisconnectHda=true
AppleAudio=true

Also, you'll need to add the AudioDxe driver with argument "--gpio-setup".

Edit: Of course, you'll want the OcBinaryData files in EFI/OC/Resources/Audio.

 

[Gustav Holdoff]

The guide has been updated to OpenCore version 0.7.7. See Maintenance for the changes that you should make to your config.

Thanks to the amazing work of @Bmju, this version brings audio support to the boot menu.

Happy updating!

Thank You. I, just updated to OC version 0.7.7, and test my video card RadeonPro W5700 in geekbench5. It has significantly increased the score. the new Lilu and Whatewergreen is likely to work better under Monterey. below are new and the previous test results for RadeonPro W5500 and W5700. cMP dual Xeon5680, 96Gb RAM

 

[borgo1971]

The guide has been updated to OpenCore version 0.7.7. See Maintenance for the changes that you should make to your config.

Thanks to the amazing work of @Bmju, this version brings audio support to the boot menu.

Happy updating!

Yesss!!! With OC 0.7.7 and updated kext, all my kernel panic and boot problems seems to be gone. I tried all my pervious config files (the ones I tried to use with OC 0.7.6, modified as described in maintenance guide) and all boot my MacPro. Even the 0.7.2 config file with some adjustment. But way try so many config files? Because with all I get an incorrect OC version response:

studio@macpro::~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    UNK-000-0000-00-00

I rebuild entry EFI folder two times too... because I thought it could be a my mistake, but none changed. So I'll like to know if other people experience this behaviour with OC 0.7.7
And two other questions:
1. With this audio support in boot menu, should we hold audio files or remove them as described in setup guide?
2. In 0.7.2 I used "BrcmBluetoothInjector.kext" and "BrcmBluetoothInjectorLegacy.kext"... have this sense anymore? I didn't remember exactly why I decided ti use this kext, but with OC 0.7.7, my original BT card seems to work well even without this kext. Maybe, the kext are necessary with BigSur or Monterey?

 

[cdf]

Because with all I get an incorrect OC version response:

This is expected if you've set ExposeSensitiveData to 0. If you want to see the version number, you can set it to 2.

1. With this audio support in boot menu, should we hold audio files or remove them as described in setup guide?

Keep them. I've edited my post above to add this information.

2. In 0.7.2 I used "BrcmBluetoothInjector.kext" and "BrcmBluetoothInjectorLegacy.kext"... have this sense anymore? I didn't remember exactly why I decided ti use this kext, but with OC 0.7.7, my original BT card seems to work well even without this kext. Maybe, the kext are necessary with BigSur or Monterey?

With supported Bluetooth hardware, this isn't needed.

 

[JeDiGM]

Thank You. I, just updated to OC version 0.7.7, and test my video card RadeonPro W5700 in geekbench5. It has significantly increased the score. the new Lilu and Whatewergreen is likely to work better under Monterey. below are new and the previous test results for RadeonPro W5500 and W5700. cMP dual Xeon5680, 96Gb RAMView attachment 1942414

What were your previous scores Gustav?

 

[borgo1971]

Also, you'll need to add the AudioDxe driver with argument "--gpio-setup".

Can you explain somthing more about this?

Edit: Of course, you'll want the OcBinaryData files in EFI/OC/Resources/Audio.

As I guessed... but, could we hold only english and/or our language audio files?

This is expected if you've set ExposeSensitiveData to 0. If you want to see the version number, you can set it to 2.

OK, I'll try... but important is to know way form strange behavior, and be sure that it's not a sign of something worse

With supported Bluetooth hardware, this isn't needed.

OK, so while I use original bluetooth card (Broadcom chipset 2046), it may have sense to hold them...