Hervé

Just you... A call to Apple support will probably sort it out.

Not a guide -> moved to the support section. Local zipped copy of the OC EFI added without the Resources folder and all the Intel stuff for the AX210 wireless card.

Released September 2nd, 2025. Build 25A5351b. Available via OTA update: All Ok. Same Clover bootpack as for beta 1 to beta 8.

Released August 25th, 2025. Build 25A5349a. Available through OTA updates. Same Clover bootpack as for beta 1 to beta 7.

Released August 18th, 2025. Build 25A5346a. Available through OTA updates. Same Clover bootpack as for beta 1 to beta 6.

Released August 11th, 2025. Build 25A5338b. Available through OTA updates. Same Clover bootpack as for beta 1 to beta 5.

Released July 29th, 2025. Build 24G84. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.7 (Build 23H723) macOS Ventura Security Update 13.7.7 (Build 22H722) View full article

Released August 5th, 2025. Build 25A5327h. Available through OTA updates. New icon for disks/volumes. Same Clover bootpack as for beta 1 to beta 4.

Please stick to macOS/Hackintosh related matters/topics...

Re: UEFI, I did find out that it would not/coud not boot a USB installer with BIOS in UEFI mode but it certainly could boot macOS once installed. See the instructions for Mojave/Catalina of my E6220 guide for reference. In the end I could boot my E6220 in UEFI mode and without patched DSDT, just a very small set of patched SSDTs, 2 of them being to bring support for the screen brightness Fn keys (otherwise IMEI, PM and PNLF sufficed!). In the same respect, not may kexts were required (and forget about lspci one which was optional and only necessary for the lspci tool). There is no need to patch the kernel with Sandy bridge or Ivy bridge platforms like there was for Haswell and later platforms. All that is needed with regards to CFG lock is the AICPUPM patch. If you want to binary patch the kext yourself, do look at the specific thread that was posted on the matter many years ago. Of course, you need to generate the CPU PM SSDT that suits your own specific CPU model and, to that effect, you have to use the old ssdtPRGen script/tool that Pike R Alpha provided all those years ago. All I ever dropped in terms of SSDTswere the expected CpuPM + Cpu0Ist; 'never had to drop MCFG or whatever else... All in all, your writing style remains difficult to understand/decode and I think you're kind of all over the place so I suggest that, if you want further assistance, you post: 1) the hardware details of your E6520 (HD3000 only model or nVidia model?) 2) a zipped copy of your Clover/OpenCore EFI folder(s) (just include the config file, the ACPI folder and the kexts folder) You'll find details of the recommended BIOS settings for E6x20 laptops at the top of this very E6xxx forum section. I strongly recommend that you consult existing E6x20 installation guides. I went up to Catalina on my E6220 before I sold it off and it ran in UEFI mode. I explained how in the High Sierra instructions of my guide. You could also find my E6230 guide interesting for more recent versions of macOS (Big Sur and later). You want Monterey, ok (it's the last version to natively support Sandy bridge CPU PM) but why not stick with Clover if it works?

It was a bit difficult to follow and understand your writing but, in a nutshell, it seems you want an OpenCore-equivalent of your Clover config. You've not posted this Clover config and you've not stated what OS X/macOS version you're using or targeting. One thing, though, is that you wrote about GFX0 and disabling IGPU which leads me to conclude that your Sandy Bridge E6520 is the nVidia model. If so, please note that it is fitted with a Fermi NVS 4200M dGPU chip that's very poorly supported to not supported since 2016 macOS Sierra 10.12. On the iGPU front, HD3000 was officially dropped in macOS Mojave 10.14 though patches do exit to extend support in subsequent macOS versions despite graphics bugs/gremlins. Do clarify your situation so that people may try and give you the appropriate assistance. This being said, with regards to an OpenCore config for a Sandy Bridge laptop, did you consult the Dortania documentation to begin with? https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/sandy-bridge.html to drop Cpu01st and CpuPm SSDT table, do so in the ACPI->Delete section of the config to rename ACPI devices, do so in the ACPI->Patch section to patch AICPUPM, do so the the kernel->Quirks section All those are very easily done with a tool such as OpenCoreConfigurator if you're not familiar with the text editor method for creating/editing your OC config.

Indeed, I only inject RTS525a properties for cosmetic reasons so that the device gets listed in SysInfo->PCI. It's Firewall's kext that makes it work. RealtekCardReaderFriend is of no use to me as it does not make the RTS525a appear listed as an Apple Card reader. I would not worry too much about the "unassigned class" in Hackintool; I have the same yet the card reader is fully functional, it's just the tool that does not recognise the device type within macOS. Re: Fn keys, all the useful ones natively work (audio, keyboard light, sleep) except the screen brightness keys for which I inject an ACPI patch for Dell laptops. It's been documented several times on the forum. Of course, it applies to Dell machines, not Lenovo...

Hi; I've no experience with RTS5227 but I've had a couple of laptop, including my current Dell Latitude E7270, with the Realtek RTS525a model. All I use is Firewall's RealtekCardReader kext v0.9.7 (without its associated friend). The card reader is only ever functional after a 1st sleep. I suppose an ACPI patch would fix this but I never bothered to debug the wake process to identify what's done at ACPI level for the device compared to what's done (and not done) at 1st boot. I don't use it much so it's never really been a problem. I inject properties in my bootloader's config so my RTS525a card reader is listed in SysInfo->PCI section but, indeed, nothing in the SysInfo->Card Reader section. It's something I could not care less about. Still works perfectly in Sequoia (and Tahoe beta for that matter).

Not an installation guide... Thread moved to the support section where it belongs.