George1203 Posted June 26, 2022 Author Share Posted June 26, 2022 I have tested your EFI and some issues as below HDMI no output Keyboard function key sound and screen blight "+ " "-" no work after sleep get the black screen and only can press the power to shout down I add the new DSDT FYR because the older one is not the BCM94360NG on-board DSDT.aml.zip Link to comment Share on other sites More sharing options...
Baio77 Posted June 26, 2022 Share Posted June 26, 2022 I understand the problems it is normal I have revolutionized the ACPI, in order to improve I need the log ioreg of my EFI. I didn't work to fix the problems, I just adapted the SSDT-Y520 for use with Opencore, adding (if Darwin) where needed and removing various renames in configplist. All problems need to be fixed, in my EFI OC 0.8.2 + kext last commit. Link to comment Share on other sites More sharing options...
George1203 Posted June 26, 2022 Author Share Posted June 26, 2022 Hi, Here is the log ioreg FYR MacBook Pro.ioreg Link to comment Share on other sites More sharing options...
Administrators Hervé Posted June 26, 2022 Administrators Share Posted June 26, 2022 @Baio77 You may mean well, but please keep this thread on-topic and do not divert onto fixing what you believe to be issues when such things were not even mentioned and your proposed new setups end up creating new issues. It's a recurring pattern of yours... The OC EFI you provided does not even address the O2 SD card reader, the thread's own topic! @George1203 The OC config you posted shows incorrect injections: In addition, these injections useless if you already use a patched SSDT to do so (SSDT-SDCard.aml). So only use one solution or the other but not both. In your case, SSDT-SDCard is correct, your OC config is wrong. As advised by Jake, make sure you also remove those add-on kexts that appear in your OC config (remove them from the OC config and the kexts folder): AppleSDSX AppleSDXCInjector VoodooSDHC As stated here (based on posted reports by forum members), the patch is understood to be applicable to your O2 card reader model (ven/dev id 1217:8621) so all that's required is injecting the property declaring compatibility with Apple's hardware (pci14e4,16bc): You would then expect to see your SD card reader in SysInfo in a manner similar to this: Of course, make sure it's not disabled in BIOS. As detailed here back in 2019, the same O2 SD card reader (pci1217,8621) was said to be fully working in a Lenovo ThinkPad E470 with the stated patch (compatible pci14e4,16bc). One notable difference though: the subsystem-vendor-id being set to Apple's 0x106B: Jake already fixed all this in the OC config he provided where he commented out your incorrect config for the SD crd reader and added the correct properties injection. Link to comment Share on other sites More sharing options...
George1203 Posted June 27, 2022 Author Share Posted June 27, 2022 Hi Hervé Thanks for your reply and I tried to do the everything as your mention, but the result is still no work on sdcard reader. I think the ven/dev id 1217:8621 can work under Clover Device Arbitray and that is different with the OC Device Properties. The Clover configuration is difficult to me, so I can not to proof that. Also maybe the Apple kext version issue dute the MacOS Monterey. I attached the info.list of AppleSDXC.kext from S/L/E. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted June 27, 2022 Moderators Share Posted June 27, 2022 Just review you config again and notice you have a kext patch. You should disable it and keep only the compatible patch or the SSDT you had created. Micro Inc. SD Card Reader - pci14e4,16bc -> pci1217,8621 Link to comment Share on other sites More sharing options...
George1203 Posted June 27, 2022 Author Share Posted June 27, 2022 I had disable the patch and keep only the SSDT-SDCard.aml patch all of the kernel including block, force and patch were disable The result is the same Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted June 27, 2022 Moderators Share Posted June 27, 2022 did you reset NVRam after the changes? post current config file Link to comment Share on other sites More sharing options...
George1203 Posted June 27, 2022 Author Share Posted June 27, 2022 Sorry my laptop got some problem I need time to fix it and contact you later Link to comment Share on other sites More sharing options...
George1203 Posted June 28, 2022 Author Share Posted June 28, 2022 Hi Jack, I am back Yes reset NVRam after the changes no work 0628MacBook Pro.ioreg 0628configOC0.81.plist.zip Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now