Matgen84 Posted January 15, 2020 Share Posted January 15, 2020 3 hours ago, Jief_Machak said: I wasn't talking about different machine, but different "EFI" folder on different drive/partition for the same machine. @Matgen84 and I agree about using theme.plist. Everyone is welcome to submit a pull request. Thanks @Jief_Machak I vote for. Link to comment Share on other sites More sharing options...
pkdesign Posted January 15, 2020 Share Posted January 15, 2020 Okay. I am still confused. Do I put it in root of EFI partition or in EFI folder? Do I use # in the front of the name or not? And it if fixed where? In the next distribution of Clover? Link to comment Share on other sites More sharing options...
Slice Posted January 15, 2020 Share Posted January 15, 2020 3 hours ago, pkdesign said: Okay. I am still confused. Do I put it in root of EFI partition or in EFI folder? Do I use # in the front of the name or not? And it if fixed where? In the next distribution of Clover? It fixed here CLOVERX64.efi.zip If you are using bootx64.efi then replace it with this file renamed to BOOTX64.EFI 1 Link to comment Share on other sites More sharing options...
pkdesign Posted January 15, 2020 Share Posted January 15, 2020 (edited) Yes! It works. Edited January 16, 2020 by pkdesign 3 Link to comment Share on other sites More sharing options...
telepati Posted January 20, 2020 Share Posted January 20, 2020 Finally, found time and tested it. Native NVRAM also working on Clover. I attached my files if anyone needs it you can look at it. Archive.zip 1 Link to comment Share on other sites More sharing options...
beton3009 Posted January 22, 2020 Share Posted January 22, 2020 hi all i have succes instal catalina on asus g750jx work 100% thank's to pcfr33k guid. soory if i out of date but i'm stuk with a probleme with clover 1- the new version 5103 do not boot the machin i have black screen so i dowgrad to 4945 to boot 2-i can't hide unwonted partition "this bcs i have yosemite+catalina+win10 instaled and 3 other partition " so i want some help if some one can help for this thank's Link to comment Share on other sites More sharing options...
telepati Posted January 22, 2020 Share Posted January 22, 2020 clover always boot in verbose mode? I checked config.plist no -v boot-arg. While booting click to space and I am seeing verbose mode selected I disable it from there and click boot but still booting in -verbose? WHY and How can I fix that? Link to comment Share on other sites More sharing options...
MICKHAEL Posted January 22, 2020 Share Posted January 22, 2020 3 minutes ago, telepati said: clover always boot in verbose mode? I checked config.plist no -v boot-arg. While booting click to space and I am seeing verbose mode selected I disable it from there and click boot but still booting in -verbose? WHY and How can I fix that? clear NVRAM 1 Link to comment Share on other sites More sharing options...
Pene Posted January 22, 2020 Share Posted January 22, 2020 On 1/20/2020 at 11:40 PM, telepati said: Finally, found time and tested it. Native NVRAM also working on Clover. I attached my files if anyone needs it you can look at it. As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix? Link to comment Share on other sites More sharing options...
telepati Posted January 22, 2020 Share Posted January 22, 2020 8 minutes ago, Pene said: As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix? Yes, it wasnt work natively. It's work with adding PMC ACPI. https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4 1 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted January 23, 2020 Share Posted January 23, 2020 10 hours ago, telepati said: Yes, it wasnt work natively. It's work with adding PMC ACPI. https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4 Thanks @telepati I don't try SSDT-PMC. With OcQuircks+FwRuntime, Memoryallocation.efi do the job: no more "runtime error" with the bios used in Z390 Aorus Master 2 Link to comment Share on other sites More sharing options...
Slice Posted January 23, 2020 Share Posted January 23, 2020 SSDT-PMC is the key. Other optional. 3 Link to comment Share on other sites More sharing options...
apianti Posted January 23, 2020 Share Posted January 23, 2020 21 hours ago, Pene said: As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix? I have a Z390, I could test it but I don't have time currently. It could possibly work, I believe the issue was the shims and they removed the shims and directly modified the ability to write to a memory region by a hook in runtime instead. 1 Link to comment Share on other sites More sharing options...
Pene Posted January 23, 2020 Share Posted January 23, 2020 23 hours ago, telepati said: Yes, it wasnt work natively. It's work with adding PMC ACPI. https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4 Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC? 1 hour ago, apianti said: I have a Z390, I could test it but I don't have time currently. It could possibly work, I believe the issue was the shims and they removed the shims and directly modified the ability to write to a memory region by a hook in runtime instead. I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days. Link to comment Share on other sites More sharing options...
telepati Posted January 23, 2020 Share Posted January 23, 2020 13 minutes ago, Pene said: Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC? I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days. I didnt test with AptioMemoryFix cause this efi always giving an allocation error for me. I am using it with OcQuircks+FwRuntime. 1 Link to comment Share on other sites More sharing options...
LockDown Posted January 24, 2020 Share Posted January 24, 2020 12 hours ago, Slice said: SSDT-PMC is the key. Other optional. with SSDT-PMC installed, do we still need AptioMemoryFix? Link to comment Share on other sites More sharing options...
Slice Posted January 24, 2020 Share Posted January 24, 2020 42 minutes ago, ellaosx said: with SSDT-PMC installed, do we still need AptioMemoryFix? Yes, as usual. You also may use alternatives OsxAptioFix3Drv or OcQuirks if they works. 1 Link to comment Share on other sites More sharing options...
apianti Posted January 24, 2020 Share Posted January 24, 2020 (edited) 14 hours ago, Pene said: Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC? I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days. Yeah, you need OcQuirks or some fix, because that is what adjusts everything for proper system configuration. Also why you need FwRuntimeServices, because that is what actually does all that stuff. Weirdly, I read that link and then inspected my ACPI tables real quick, the device with "PNP0C02" HID and "PCHRESV" UID is a temperature sensor.... The only devices I have under "PNP0C02" HID are temperature sensors. Strange. EDIT: I have only one reservation for the memory range 0xFC800000 to 0xFE7FFFFF. Edited January 24, 2020 by apianti 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted January 25, 2020 Share Posted January 25, 2020 8 hours ago, telepati said: I am not using OpenCore just testing from USB Installer but when I look Hackintool it says current bootloader is OpenCore. I cleaned caches and NVRAM with Mac Optimizer.app but still the same. How can I fix that? Do you try to post your issue in Hackintool Topic? 1 Link to comment Share on other sites More sharing options...
Pene Posted January 26, 2020 Share Posted January 26, 2020 On 6/15/2018 at 8:21 PM, savvas said: I'm working on version detect Any update about this? Link to comment Share on other sites More sharing options...
Slice Posted January 26, 2020 Share Posted January 26, 2020 Pene, did you test Z390 NVRAM with SSDT-PMC + OsxAptioFisx3Drv? Expected success. Link to comment Share on other sites More sharing options...
Pene Posted January 27, 2020 Share Posted January 27, 2020 15 hours ago, Slice said: Pene, did you test Z390 NVRAM with SSDT-PMC + OsxAptioFisx3Drv? Expected success. Hi Slice, no, not yet. I was away for a few days. Will probably test today evening and report. Link to comment Share on other sites More sharing options...
apianti Posted January 27, 2020 Share Posted January 27, 2020 (edited) 3 hours ago, Pene said: Hi Slice, no, not yet. I was away for a few days. Will probably test today evening and report. I think that you will require making some other changes to your ACPI tables. I have an Asrock Z390 Extreme4, and I already have that memory address reserved in a big chunk, so you will probably have to remove that to add the PMC device. EDIT: Just in case anyone is wondering why this device matters, https://en.wikipedia.org/wiki/Programmable_metallization_cell, it's the NVRAM... Edited January 27, 2020 by apianti 1 Link to comment Share on other sites More sharing options...
Pene Posted January 27, 2020 Share Posted January 27, 2020 (edited) On 1/26/2020 at 9:11 PM, Slice said: Pene, did you test Z390 NVRAM with SSDT-PMC + OsxAptioFisx3Drv? Expected success. Yes, I confirm it is working. OsxAptioFix3 without SSDT-PMC - native nvram not working (tested now again, just to be sure). OsxAptioFix3 with SSDT-PMC - native nvram working. (Probably the same also with AptioMemoryFix and OcQuirks - didn't test though). 8 hours ago, apianti said: I think that you will require making some other changes to your ACPI tables. I have an Asrock Z390 Extreme4, and I already have that memory address reserved in a big chunk, so you will probably have to remove that to add the PMC device. Didn't have to do any modifications. I have an Asrock Z390 Phantom ITX/AC, and at my memory map (posted some time ago), you see I have this: Type Start End # Pages Attributes MMIO 00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001 Edit: which is actually 1 page more (?) than what's specified at the PMCR device in the newly added SSDT-PMC: Memory32Fixed (ReadWrite, 0xFE000000, // Address Base 0x00010000, // Address Length ) Edited January 27, 2020 by Pene 2 Link to comment Share on other sites More sharing options...
iCanaro Posted January 27, 2020 Share Posted January 27, 2020 @meaganmargaret https://www.insanelymac.com/forum/topic/341047-cloverapp-testing/ 1 Link to comment Share on other sites More sharing options...
Recommended Posts