Its always possible, but I doubt your Keplar is the thing causing ASR to fail.
OCLP is an automated installer which attempts to analyze your system and then make a bunch of choices about various hacks to install..including for your Kepler...but OCLP tends to over-diagnose and install a lot of extra hacks that really aren't necessary, in an effort to be easy to install. For many people this is still a preferred solution because you don't have to understand much about anything to get OC working. The downsize is that most of you have absolutely no idea what your OC configuration is like, you are just trusting OCLP to make those decisions for you.
I prefer to install OC manually, where I decide exactly which hacks to use, and I am keeping those hacks to the minimum required. Since I don't have a keplar like you, I at least don't have any hacks related to that one, but if I did, I would personally still use the manual method, I would find out what is required to operate the Keplar and I would set it up manually.
You can find out more info about manual OC setup here at this guide which is kept up to date every month for the most clean and smple OC possible. Its a good starting place, but if have difficult hardware such as Keplar then you'd have to figure out how to manually configure that:
This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
forums.macrumors.com
There are any number of other things in a typical OCLP configuration which might be causing ASR to fail...and its also possible that OC has nothing to do with the ASR failure at all, might some other corruption in your MacOS or APFS install.
Dear
@Dewdman42, first of all thank you for your effort. Your ideas are sure to be useful and inspiring for many of us.
I doubt that perhaps you do not know or it is not clear to you that it was the same "great" person, Mykola Grymalyuk aka
@khronokernel, who created and managed the development of both: OpenCore that you love and OpenCore Legacy Patcher.
"OpenCore Legacy Patcher", therefore, was conceived and developed by
@khronokernel and a team of true Geniuses with the aim of running on Apple computers; the excellent and simple named "OpenCore", instead, has its rightful place in the field of PCs and not Macs.
That said, if you want to have complete control of what OCLP does on your Mac, you can do as I did before realizing that instead, I had to blindly trust what Khronokernel and its staff of fellow Developers are proposing.
That is, I used to install OCLP and then customize it using the free -->
"OpenCore Configurator" utility because I thought, as you reason, to leave only what my Mac needs.
"OpenCore Configurator", in fact, is a graphical interface that allows to examine in detail what the “config.plist” file does and decide to disable or remove the OCLP KEXT modules deemed useless.
In my opinion, then, when I was wrong, like you..., ;-) the OCLP's Kext module for WiFi / Bluetooth is not needed in my iMac 14.2 and so I removed this Kext using "OpenCore Configurator" [Note: I can do it directly too, by modifying the "Config.plist", but it's easy to make text errors ...]
Eventually, however, I realized that I was presumptuous and foolish ...
I did not foresee, for example, that other users or even myself would one day using a legacy USB Dongle (specific for WiFi or Bluetooth of keyboards, mice, MIDI or other) and this Dongle, therefore, would not work in Monterey since Apple (from Catalina onwards and getting worse with Big Sur and Monterey) has removed a lot of Kext. Idem for others useful functions, removed or altered by Apple to not works with the new Macs or with unsupported Macs...
So dear friend I realized that if I really wanted an iMac 14,2 that would behave 100% like an original fully supported Mac and in this case even better, thanks to universal kexts modules, installed by OCLP, I have to trust those who know more than all of us and that develop OCLP 360-degree thinking.
So I stopped giving myself "mental bl.wjobs" (alias paranoia) from a know-it-all and as a conceited Nerd and I chose to blindly trust Khronokernel and his friends' staff.
This decision has made me happy and in peace and from several OCLP builds I don't waste time fiddling with the "config.plist" or OCLP options.
Finally: if you really know how to manage the EFI OCLP by yourself and what the "Post Install Patch" does, you realize how complicated it is to intervene in System Folder of Big Sur or Monterey... And therefore it is absurd to give this suggestion in a full forum of Newbies...
For these discussions there is GitHub and Discord and I hope you are really as good as you look and that you will join the Khronokernel staff and their contributors and help the Staff bring your ideas into such development scenario instead of here...
Here, in fact, your post risks having the flavor of a not very constructive criticism, while your point of view could be constructive if you put yourself in the right environment.
Anyway thanks again for your interesting stimuli and good job.
