bisk

OK So no multiboot possible with multiple OS's on a single drive with OpenCore if using single customized DSDT. At least not with the current state of the project. That CustomSMIOSGuid / CustomSMIOSModeCustom quirk briefly described in the master OpenCode guide is already deprecated ? Definitely no OS specific ACPI patching possible ? Tis a bummer ! Thanks for super swift responses !

Hmmm, not sure that I quite understand. Do your custom patched DSDTs solve this problem ? Does ONLY the original/OEM DSDT image load for an OS other Mac ? Sorry to be a pest.

Thanks again for the prompt reply. Yes, I have looked at this wonderful guide as well as several others. These all seem to focus a great deal on installing the MacOS which is of little interest to me. I stopped doing image installs after about my 20th hack back around Lion. I discovered that there were 2 distinct problem sets involved with creating a hack. 1. installation issues and 2. post installation issues. I elected to simply skip the first group. No need to go into anymore detail about that. Anyway, I am with you in preferring to modify just one main DSDT rather than adding a slew of SSDTs. However, I think that the result ends up about the same. Never really embraced the whole Clover hotpatch thing either. I just did all my renames in the DSDT. Sifting through everything, I think that I was able to answer most of my actual questions, like: OpenCore installation == Clover Installation with just a directory structure change and replacing/renaming a bunch of configuration switches. No separate OpenCore installer package just a new Clover installer. Full DSDT replacement DOES work by simply dropping the customized DSDT in OC/ACPI and providing an ACPI/Add item. Looks like DSDT adds result in the REPLACEMENT of ACPI tables while SSDT adds result in the ADDITION of ACPI tables. Also, looks like the patches are applied BEFORE the table replacements, adds and deletes. So customized DSDTs and added SSDTs are never patched. So the presented order of Add/Delete/Patch/Quirk under ACPI in sample configs is counterintuitive. Order= Patch, Replace, Add. Not sure where Delete and Quirk happen with respect to Replace and Add. I now have 3 EFI folders on my ESP and It's interesting to note the differences in behavior. This is all booting Catalina 10.15.7 on a Dell XPS2720. The oldest, Clover v2.5k-r5033 still works fine but will reboot after wake due to the Haswell/AppleALC HDMI audio bug unless I deactivate HDMI audio in the DSDT. It multiboots my alternate boot partitions quite well too. The middle-aged Cloverv2-r5143 (running a Clover config, no longer finds the Windows partition on its own and so cannot multiboot. Maybe with help in the Entries segment of the config that could be fixed but I'm not gonna bother. This is because it FAILS to load my Atheros WiFi kexts correctly and still crashes on wake without the DSDT HDMI Audio disable fix. My instincts tell me that classic Clover functionality will continue to decline as developer focus turns more and more to OpenCore. The new Cloverv2-r5143 (running an OpenCore config) works perfectly in every way on Mac. Loads my customized DSDT, no crash on wake even with active HDMI audio, all kexts loaded and working including AR9462 WiFi. OpenCore is totally blind to my Windows partition but that is corrected by adding a Windows10 section to the Entries category in the config. However, Windows will crash spectacularly when OpenCore replaces the stock DSDT with my Mac-customized DSDT. No surprise there. I imagine that my Linux and FreeBSD boots wouldn't fare much better ! I write code for 4 architectures on my laptop and so find it very convenient to utilize quad boot with each OS sharing the same ExFat partition. So my very final question is ... How can I stop OpenCore from slamming my MacOS modified DSDT into memory when booting an OS that needs no modifications? Breaking the changes into a bunch of SSDTs would obviously bring about the same result. Unless, are we expected to do a (OS=="DARWIN") check at the entry of each SSDT ? If so, is it possible to do the same in DSDT to prevent loading or is it already too late by then ? Using a BIOS-based boot selector is of no use when each OS does not reside on a separate hard drive. Thanks in advance, bisk

Oh, I'm very sorry for not being more clear. My current system, Dell XPS2720 is already "fine tuned" and fully working. I just updated from Mojave 10.14.6 to Catalina 10.15.7, in fact. My system is booting with Clover v2.5k r5033. This is a Haswell Core i7 all-in-one PC with Atheros 9462 WiFi, dual displays, etc. all working perfectly. I do very little in my config.plist other than some USB renames and HD4600 Framebuffer patches to support running dual displays. I do not make use of any SSDTs. All of my fixes are done in my one and only customized DSDT. But now to upgrade to Big Sur, my understanding is that I must go with OpenCore. I have no installation to do. I think that I just need to make some EFI changes. I was just looking for a heads up on how to modify Clover config to OpenCore config and I am especially interested in how to supply a single customized DSDT as opposed to a whole bunch of SSDTs. Is there a place where I can find an example OpenCore EFI with config for a haswell desktop using a customized DSDT ?

Thank you for swift reply ! So di I just drop modified DSDT in OC/ACPI ? Do I need to specify the DSDT.aml with an Add directive ? Does the order of the Add directives dictate the order of the DSDT & SSDT loading ? Thanks again.

I've been away from the hackintosh scene for a couple of years and just now came back to upgrade a couple of my hacks. Been performing my own full DSDT edits for many years and so probably won't trouble you guys for a DSDT fix. I've been reading in some forums that the new OpenCore methodology prefers SSDT incremental adds rather than full DSDT replacement. Is this the case ? Are full DSDT replacements problematic in any way ? If not, how are they implemented ? Just like an SSDT ? Simply drop the full DSDT in the OC folder and create and Add entry in the config.plist ? If I have SSDTs to add as well is the order important ? Is there a handy Clover->OpenCore config.plist conversion guide ? Anything else I need to know ? Thanks in advance