mrjayviper Posted July 24, 2018 Share Posted July 24, 2018 what would be the recommended clover version for those still in High Sierra. Recent discussions seems specific to Mojave so it's possible those clover versions are not suitable for <10.14? Thanks 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627310 Share on other sites More sharing options...
ameenjuz Posted July 24, 2018 Share Posted July 24, 2018 I installed and tested Clover_v2.4k_r4617 it has bug EDID Custom this above version didn't inject custom edid I tested rehab man's clover version Clover_v2.4k_r4444.RM-4652.c1f8602f Inject custom edid work fine please fix and reconsider version Clover_v2.4k_r4617 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627326 Share on other sites More sharing options...
ameenjuz Posted July 24, 2018 Share Posted July 24, 2018 I tested rehab man's clover version Clover_v2.4k_r4444.RM-4652.c1f8602f didn't work with headkaze 32mb frambuffer patch and i added this on config.plist <key>Devices</key><dict> <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data>CQClPg==</data> <key>framebuffer-patch-enable</key> <integer>1</integer> <key>framebuffer-stolenmem</key> <integer>19922944</integer> <key>framebuffer-fbmem</key> <integer>9437184</integer> <key>framebuffer-unifiedmem</key> <integer>2147483648</integer> </dict> didn't work rehabman please update your prebuilt clover version Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627334 Share on other sites More sharing options...
Slice Posted July 25, 2018 Share Posted July 25, 2018 17 hours ago, mrjayviper said: what would be the recommended clover version for those still in High Sierra. Recent discussions seems specific to Mojave so it's possible those clover versions are not suitable for <10.14? Thanks I have no 10.14 and recent Clover is good. 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627431 Share on other sites More sharing options...
chris1111 Posted July 27, 2018 Share Posted July 27, 2018 (edited) Any body please confirm since a lots of clover revision its failed boot ESP for macOS Mojave I an talk about Boot Install ESP / Boot0af in MBR+ Drivers64 / Clover 64 Bit SATA Like this image Try latest compile my self, also try Source forge package 4617 and Boot falled now try Clover r4512 and its work for SSD Mojave and USB Create install Media I have another working clover is 4586 works for ESP Boot UEFI Only as no issue for latest Clover EDIT FIX With nvram kextcache Cleaner 1.0.4.dmg thanks to @cyberdevs Edited July 27, 2018 by chris1111 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627622 Share on other sites More sharing options...
Badruzeus Posted July 27, 2018 Share Posted July 27, 2018 Not a big deal, but.. Can we use pre-Release version of Clover with different color logo? Uhmb, for *pkg installer, prefPane and Updater.. maybe. Thanks. 3 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627675 Share on other sites More sharing options...
FredWst Posted July 28, 2018 Share Posted July 28, 2018 (edited) Hi, To remove second FACS create by clover you can try. To put lines After //FredWst in AcpiPatcher.c at the good place. Works for me. // if (Facs) newFadt->FirmwareCtrl = (UINT32)(UINTN)Facs; // else DBG("No FACS table ?!\n"); if (newFadt->FirmwareCtrl) { Facs = (EFI_ACPI_4_0_FIRMWARE_ACPI_CONTROL_STRUCTURE*)(UINTN)newFadt->FirmwareCtrl; newFadt->XFirmwareCtrl = (UINT64)(UINTN)(Facs); } else if (newFadt->XFirmwareCtrl) { newFadt->FirmwareCtrl = (UINT32)XFirmwareCtrl; Facs = (EFI_ACPI_4_0_FIRMWARE_ACPI_CONTROL_STRUCTURE*)(UINTN)XFirmwareCtrl; } //patch for FACS included here Facs->Version = EFI_ACPI_4_0_FIRMWARE_ACPI_CONTROL_STRUCTURE_VERSION; if (GlobalConfig.SignatureFixup) { DBG(" SignatureFixup: 0x%x -> 0x%x\n", Facs->HardwareSignature, machineSignature); Facs->HardwareSignature = (UINT32)machineSignature; } else { DBG(" SignatureFixup: 0x%x -> 0x0\n", Facs->HardwareSignature); Facs->HardwareSignature = 0x0; } // //FredWst if (newFadt->FirmwareCtrl) { Facs = (EFI_ACPI_4_0_FIRMWARE_ACPI_CONTROL_STRUCTURE*)(UINTN)0x0; newFadt->XFirmwareCtrl = (UINT64)(UINTN)(Facs); } else if (newFadt->XFirmwareCtrl) { newFadt->FirmwareCtrl = (UINT32)0x0; Facs = (EFI_ACPI_4_0_FIRMWARE_ACPI_CONTROL_STRUCTURE*)(UINTN)XFirmwareCtrl; } Fred Edited July 28, 2018 by FredWst 1 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627877 Share on other sites More sharing options...
Slice Posted July 29, 2018 Share Posted July 29, 2018 What is the problem for you to raise a question about FACS? The question was closed several years ago. Duplicates exist due to Rsdt-Xsdt and correctly treats by Clover. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627925 Share on other sites More sharing options...
FredWst Posted July 29, 2018 Share Posted July 29, 2018 (edited) 1 hour ago, Slice said: What is the problem for you to raise a question about FACS? The question was closed several years ago. Duplicates exist due to Rsdt-Xsdt and correctly treats by Clover. There is 2 versions of FACS in my case revision 1 and revision 2. One Rsdt and one Xsdt. After Clover patch it show 2 FACS with same revision. So, is it a normal situation to get FACS and FACS-1 ? (MacIASL) Fred Edited July 29, 2018 by FredWst Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627929 Share on other sites More sharing options...
Slice Posted July 29, 2018 Share Posted July 29, 2018 Yes it is normal. We know this and correctly use this. And I am not responsible for maciasl. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2627942 Share on other sites More sharing options...
surfinchina Posted July 30, 2018 Share Posted July 30, 2018 Hi, for some reason, after I updated my Clover (to 46xx and then to 4617) it's taking about 15 seconds to get from the initial clover splash screen to the clover menu. Is this normal for the clovers of the last month or is my install wacky? Previously it was 1 second. Thanks. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628163 Share on other sites More sharing options...
Slice Posted July 31, 2018 Share Posted July 31, 2018 10 hours ago, surfinchina said: Hi, for some reason, after I updated my Clover (to 46xx and then to 4617) it's taking about 15 seconds to get from the initial clover splash screen to the clover menu. Is this normal for the clovers of the last month or is my install wacky? Previously it was 1 second. Thanks. If we look into debug.log then we may see time for each operation. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628212 Share on other sites More sharing options...
arsradu Posted August 1, 2018 Share Posted August 1, 2018 (edited) Hehe! Niice! I wish that someone would find a fix for the Error 65 when building with CLT 10 and UDK2018 (with no extra customisations). I'm currently using 10L221o and...still the same error. With Xcode 10 Beta 2 I don't get this error, but I get a build.py error... So, not sure if THAT was a bug, or this one is. But one thing is for sure, it doesn't seem to work (at least for me) with the latest Xcode 10 and Command Line Tools. Aaand it does work with CLT 9.4.1. Also, when building with CLT 9.4.1, the Clover Updater is white, even in Dark Mode... Not sure if that's intended. Probably yes... But I can't build with CLT 10 in Mojave (get error 65), so I can't test this theory. Anyway, nice job! Congrats guys! Looks cool! Edited August 1, 2018 by arsradu 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628412 Share on other sites More sharing options...
Allan Posted August 1, 2018 Share Posted August 1, 2018 In this new version, there's a little (very little) issue with the translation: Sorry if this post is silly. 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628438 Share on other sites More sharing options...
chris1111 Posted August 2, 2018 Share Posted August 2, 2018 (edited) Thanks Slice and Clovy for the new change great change it was time that there is something new on this side, I had to ask a few years ago I prefere only the New Logo Without icon with arrow that looks a bit like recovery HD Icon, so I mode my own Icon panel Thats what its like now Light Mode Dark Mode EDIT ++ The only Graphics card showing DARK Panel now is my GeForce 210 in Mojave Beta 5 This is Broken for my GT 710 in Mojave Beta 5 Edited August 2, 2018 by chris1111 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628452 Share on other sites More sharing options...
Matgen84 Posted August 2, 2018 Share Posted August 2, 2018 10 hours ago, arsradu said: Hehe! Niice! I wish that someone would find a fix for the Error 65 when building with CLT 10 and UDK2018 (with no extra customisations). I'm currently using 10L221o and...still the same error. With Xcode 10 Beta 2 I don't get this error, but I get a build.py error... So, not sure if THAT was a bug, or this one is. But one thing is for sure, it doesn't seem to work (at least for me) with the latest Xcode 10 and Command Line Tools. Aaand it does work with CLT 9.4.1. Also, when building with CLT 9.4.1, the Clover Updater is white, even in Dark Mode... Not sure if that's intended. Probably yes... But I can't build with CLT 10 in Mojave (get error 65), so I can't test this theory. Anyway, nice job! Congrats guys! Looks cool! Like @arsradu I've error 65 on Clover Prefpane/ Clover Updater when make package with CLT10 Xcode Beta 5 and UDK 2018. Only Xcode 10 Beta 2 don't get errors. Any solutions? Please. Anyway great job for this change 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628463 Share on other sites More sharing options...
arsradu Posted August 2, 2018 Share Posted August 2, 2018 (edited) Yeah, with Beta 2, I get this: Active Platform = /Users/jimmy/src/UDK2018/Clover/Clover.dsc Flash Image Definition = /Users/jimmy/src/UDK2018/Clover/Clover.fdf Processing meta-data ... done! Building ... /Users/jimmy/src/UDK2018/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64] Building ... /Users/jimmy/src/UDK2018/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64] make: *** No rule to make target `/Users/jimmy/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/OUTPUT/object_files.lst', needed by `/Users/jimmy/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/OUTPUT/BasePcdLibNull.lib'. Stop. build.py... : error 7000: Failed to execute command make tbuild [/Users/jimmy/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull] build.py... : error 7000: Failed to execute command make tbuild [/Users/jimmy/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull] build.py... : error F002: Failed to build module /Users/jimmy/src/UDK2018/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64, XCODE8, RELEASE] - Failed - It does build successfully in the end. But I doubt that this error is ok. Then again, this is with Beta 2... Anything newer than that can't build (error 65), but also no build.py error. Edited August 2, 2018 by arsradu 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628488 Share on other sites More sharing options...
Slice Posted August 2, 2018 Share Posted August 2, 2018 This error can be corrected with ./ebuild.sh -fr 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628490 Share on other sites More sharing options...
arsradu Posted August 2, 2018 Share Posted August 2, 2018 (edited) 3 hours ago, Slice said: This error can be corrected with ./ebuild.sh -fr You’re right. It is. But with ./ebuild.sh -fr I don’t get the external drivers anymore. That’s why I switched to ./ebuild.sh —ext-pre. Is there any way to combine the two? Or how to add them to the build? Edit: Nevermind. Apparently ./ebuild.sh --ext-pre -fr works. :)) Not sure if that's how you do it...But...well, works. @Slice I noticed something. The official builds have "-64" added to all the drivers (including external ones). But when I build it, the external drivers don't have that suffix. I was wondering how to add it... Because, otherwise, when I install a Beta version after an official one, I'll get two ApfsDriverLoaders in drivers64UEFI. One is just ApfsDriverLoader. The other one is added by the official build and it's ApfsDriverLoader-64. I was wondering how to fix that. Edited August 2, 2018 by arsradu 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628522 Share on other sites More sharing options...
chris1111 Posted August 2, 2018 Share Posted August 2, 2018 (edited) Now for no special reason Clover Panel on Dark Mode works on my GeForce GT 710 Some times work some time not Edited August 2, 2018 by chris1111 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628527 Share on other sites More sharing options...
Matgen84 Posted August 2, 2018 Share Posted August 2, 2018 1 hour ago, arsradu said: You’re right. It is. But with ./ebuild.sh -fr I don’t get the external drivers anymore. That’s why I switched to ./ebuild.sh —ext-pre. Is there any way to combine the two? Or how to add them to the build? Edit: Nevermind. Apparently ./ebuild.sh --ext-pre -fr works. :)) Not sure if that's how you do it...But...well, works. @Slice I noticed something. The official builds have "-64" added to all the drivers (including external ones). But when I build it, the external drivers don't have that suffix. I was wondering how to add it... Because, otherwise, when I install a Beta version after an official one, I'll get two ApfsDriverLoaders in drivers64UEFI. One is just ApfsDriverLoader. The other one is added by the official build and it's ApfsDriverLoader-64. I was wondering how to fix that. you can try --ext-co (checkout & build external drivers at ..src/EXT_PACKAGES) Instead of --ext-pre 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628529 Share on other sites More sharing options...
Slice Posted August 3, 2018 Share Posted August 3, 2018 Any corrections in the package in other languages? 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628584 Share on other sites More sharing options...
arsradu Posted August 3, 2018 Share Posted August 3, 2018 14 hours ago, Matgen84 said: you can try --ext-co (checkout & build external drivers at ..src/EXT_PACKAGES) Instead of --ext-pre Thank you. That fixed it. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628587 Share on other sites More sharing options...
arsradu Posted August 3, 2018 Share Posted August 3, 2018 (edited) 1 hour ago, Slice said: Any corrections in the package in other languages? Slice, I'd love to confirm for other languages, but I was never able to see Clover's prefPane in other language than English. I don't know why... Right now, system language is set to RO, but Clover's prePane language is still EN. Not sure if that's intended. And for EN, yes, the bug reported before where на was not translated to EN, is now fixed (build 4631). But still...not sure how to check other languages when the prefPane language is always EN for me. I checked the installer though. And that one seems to be correctly translated to RO. But...prefPane was always in EN for me, despite the fact that there is a translation for it (in RO), inside the build. Edited August 3, 2018 by arsradu 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628589 Share on other sites More sharing options...
Sherlocks Posted August 3, 2018 Share Posted August 3, 2018 Any corrections in the package in other languages?i'm working for korean나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/708/#findComment-2628590 Share on other sites More sharing options...
Recommended Posts