D-an-W Posted July 2, 2017 Share Posted July 2, 2017 I am kind of wondering the same thing myself, should I install Clover onto my APFS partition of my main SSD drive (As I usually do when testing new releases etc)? BIG thanks to fusion71au and SavageAUS for clearing up custom entries too! 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455659 Share on other sites More sharing options...
arsradu Posted July 2, 2017 Share Posted July 2, 2017 I am kind of wondering the same thing myself, should I install Clover onto my APFS partition of my main SSD drive (As I usually do when testing new releases etc)? BIG thanks to fusion71au and SavageAUS for clearing up custom entries too! Well, if you have a spare SSD, I would suggest installing it there, in case things go south. I don't, so I just split my SSD in half, and installed Hi Sierra (APFS) on one side, with Sierra on the other. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455736 Share on other sites More sharing options...
D-an-W Posted July 2, 2017 Share Posted July 2, 2017 I did the same thing, made a 50GB partition on my boot drive. Did you then Install Clover into High Sierra to get the control panel etc working? Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455740 Share on other sites More sharing options...
arsradu Posted July 2, 2017 Share Posted July 2, 2017 I did the same thing, made a 50GB partition on my boot drive. Did you then Install Clover into High Sierra to get the control panel etc working? To be honest, I didn't even notice there was no Clover pref pane in High Sierra until you mentioned it. )LOL Well, no, I didn't reinstall Clover. I totally forgot about that. But...I guess you could...? So I guess it's a good thing I asked where does Clover put its files when you're installing it on APFS. ) That's good to know. Cause now I know I have to move them manually. So, is this something expected with APFS? Will we always need to move Clover from Root to EFI? Or is it just a feature that's not ready yet and will be done in future versions? I'm only curious. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455757 Share on other sites More sharing options...
D-an-W Posted July 2, 2017 Share Posted July 2, 2017 Once my MAME Software List has finished rebuilding I will reboot into High Sierra and give it a go! Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455760 Share on other sites More sharing options...
SavageAUS Posted July 2, 2017 Share Posted July 2, 2017 To be honest, I didn't even notice there was no Clover pref pane in High Sierra until you mentioned it. )LOL Well, no, I didn't reinstall Clover. I totally forgot about that. But...I guess you could...? So I guess it's a good thing I asked where does Clover put its files when you're installing it on APFS. ) That's good to know. Cause now I know I have to move them manually. So, is this something expected with APFS? Will we always need to move Clover from Root to EFI? Or is it just a feature that's not ready yet and will be done in future versions? I'm only curious. We can only hope that the clever devs will find a way to solve the AFPS + Clover + ESP problem. Sent from my SM-G930F using Tapatalk 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455775 Share on other sites More sharing options...
oSxFr33k Posted July 2, 2017 Share Posted July 2, 2017 I cannot get past the ++++++++++++++++ right after the boot 0 and clover Gui. Sierra 10.12.5 is pre-installed, clover in EFI for 3 legacy PCs, all LGA 775's Core2 Quads, gigabyte GA-G41, EP45-UD3P no issues booting but the Asus Maxiumus Forumla X38 chipset is the one that will not get past the ++++++++++. I am assuming once you see the plus's the bootefi should load then the kernel correct? So it has to be something with the bootefi. I tried placing from the OEM folder where I keep the 3 different PCs and placed the Asus back to the root of EFI/kext and ACPI/patched and still nothing. I have the latest clover sourceforge version 4097. Maybe I can try a later version if anyone has already compiled one link? I don't know how to collect any logs if it cannot get past BootEFI and other suggestions? Thanks! Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455784 Share on other sites More sharing options...
apianti Posted July 2, 2017 Share Posted July 2, 2017 I am kind of wondering the same thing myself, should I install Clover onto my APFS partition of my main SSD drive (As I usually do when testing new releases etc)? BIG thanks to fusion71au and SavageAUS for clearing up custom entries too! You have no choice but to install it on the volume you want to boot, but because APFS creates a bunch of logical volumes from one physical, the files need to be moved until the installer is updated to get the original physical volume to determine the disk's ESP. Also, awesome that I'm the one that said what to do with custom entries but didn't even get a shout out...... We can only hope that the clever devs will find a way to solve the AFPS + Clover + ESP problem. The installer needs updated to detect APFS partitions and determine the physical volume to determine the ESP. I cannot get past the ++++++++++++++++ right after the boot 0 and clover Gui. Sierra 10.12.5 is pre-installed, clover in EFI for 3 legacy PCs, all LGA 775's Core2 Quads, gigabyte GA-G41, EP45-UD3P no issues booting but the Asus Maxiumus Forumla X38 chipset is the one that will not get past the ++++++++++. I am assuming once you see the plus's the bootefi should load then the kernel correct? So it has to be something with the bootefi. I tried placing from the OEM folder where I keep the 3 different PCs and placed the Asus back to the root of EFI/kext and ACPI/patched and still nothing. I have the latest clover sourceforge version 4097. Maybe I can try a later version if anyone has already compiled one link? I don't know how to collect any logs if it cannot get past BootEFI and other suggestions? Thanks! You can't boot 10.12+ with a Core2 that does not have SSE4.1. So you need a Q8200 or better, or QX9650 or better. Or you need to use legacy kernel, if it's even around for 10.12... Not sure... Anyone? 5 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2455961 Share on other sites More sharing options...
oSxFr33k Posted July 2, 2017 Share Posted July 2, 2017 You have no choice but to install it on the volume you want to boot, but because APFS creates a bunch of logical volumes from one physical, the files need to be moved until the installer is updated to get the original physical volume to determine the disk's ESP. Also, awesome that I'm the one that said what to do with custom entries but didn't even get a shout out...... The installer needs updated to detect APFS partitions and determine the physical volume to determine the ESP. You can't boot 10.12+ with a Core2 that does not have SSE4.1. So you need a Q8200 or better, or QX9650 or better. Or you need to use legacy kernel, if it's even around for 10.12... Not sure... Anyone? I though it might be because of that to but I changed my PlatformSupport.plist to include support for MacPro3,1, I don't think the kernel ever loads. I can see the Plus's start but before you see the boot64x.efi or boot.efi I don't remember, within that boot.efi is a string about the boot drive, it never gets to that point, and it is right after that the kernel loads, I just never get to the point of seeing either one of that parts just stuck on +++++++++++. The other two LGA 775 boards have slower quad cores and they boot perfectly fine under the modified PlatformSupport.plist so its something else! I will have to troubleshoot to see if its clover on this piece of hardware or not. I will start out by booting via USB then see if an El Capitan installer will start with Clover 4097 if it does then I am guessing it may have something to do with the combination of Sierra/Clover and this Asus motherboard. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456000 Share on other sites More sharing options...
D-an-W Posted July 2, 2017 Share Posted July 2, 2017 Sorry apianti, I guess I didn't read far enough back in the thread! BIG thanks! Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456003 Share on other sites More sharing options...
apianti Posted July 2, 2017 Share Posted July 2, 2017 I though it might be because of that to but I changed my PlatformSupport.plist to include support for MacPro3,1, I don't think the kernel ever loads. I can see the Plus's start but before you see the boot64x.efi or boot.efi I don't remember, within that boot.efi is a string about the boot drive, it never gets to that point, and it is right after that the kernel loads, I just never get to the point of seeing either one of that parts just stuck on +++++++++++. The other two LGA 775 boards have slower quad cores and they boot perfectly fine under the modified PlatformSupport.plist so its something else! I will have to troubleshoot to see if its clover on this piece of hardware or not. I will start out by booting via USB then see if an El Capitan installer will start with Clover 4097 if it does then I am guessing it may have something to do with the combination of Sierra/Clover and this Asus motherboard. Well what's the debug.log have if you enable debug with Boot/Debug=true? Sorry apianti, I guess I didn't read far enough back in the thread! BIG thanks! Haha, I was just being a smartass. 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456012 Share on other sites More sharing options...
TheRacerMaster Posted July 2, 2017 Share Posted July 2, 2017 If anyone is interested, here are some DarwinDumps for 2017 MacBook Pros (MacBookPro14,1/14,2/14,3). ...and some other 2017 Macs (iMac18,3 with Radeon Pro 580 and MacBook10,1). DarwinDumper_3.0.3_02.07_16.27.03_MacBookPro14,1_Apple_X64_Sierra_16F2073_apple.zip DarwinDumper_3.0.3_02.07_16.25.05_MacBookPro14,2_Apple_X64_Sierra_16F2104_apple.zip DarwinDumper_3.0.3_02.07_16.22.36_MacBookPro14,3_Apple_X64_Sierra_16F2073_apple.zip DarwinDumper_3.0.3_02.07_17.07.12_MacBook10,1_Apple_X64_Sierra_16F2073_apple.zip DarwinDumper_3.0.3_02.07_17.16.49_iMac18,3_Apple_X64_Sierra_16F2073_apple.zip 12 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456031 Share on other sites More sharing options...
Sherlocks Posted July 3, 2017 Share Posted July 3, 2017 If anyone is interested, here are some DarwinDumps for 2017 MacBook Pros (MacBookPro14,1/14,2/14,3). ...and some other 2017 Macs (iMac18,3 with Radeon Pro 580 and MacBook10,1). Thank you so much:) 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456036 Share on other sites More sharing options...
oSxFr33k Posted July 3, 2017 Share Posted July 3, 2017 Well what's the debug.log have if you enable debug with Boot/Debug=true? Haha, I was just being a smartass. I enabled all the possible debug sections in the Clover Config, this won't work because it only gets to the Clover GUI and then starts to boot with the ++++++++, but never loads this part which is before the kernel boot below which never happens so not sure if a log will generate if it cannot get past below? efiboot loaded from device Acpi (PNP0A08,0)/Pci (1F12)/SATA(0,0)/HD(Part1,SigFB80A2E1-C0D7-425B-B471-F5260F9370E7) boot file path: \System\library\CoreServices\boot.efi ................................................................................................ root device uuid is 'E216AA4C-001B-A249-30A9CEE752D3' ................................................................................................. Then the kernel boots next but not on this Asus MB. I thought possibly the SSD drive might be the problem but proved to myself that is not the case same thing happens on a flash drive or regular SATA drive. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456058 Share on other sites More sharing options...
apianti Posted July 3, 2017 Share Posted July 3, 2017 There's no log past that point as when you get that line of plus signs, that is when the kernel is booting. Clover is gone as exit boot services was called. I meant is there anything else in the log that might give an idea of why it's not working. Are you not using a boot fix (like AptioFix)? You should just post the debug.log. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456088 Share on other sites More sharing options...
Slice Posted July 3, 2017 Share Posted July 3, 2017 I enabled all the possible debug sections in the Clover Config, this won't work because it only gets to the Clover GUI and then starts to boot with the ++++++++, but never loads this part which is before the kernel boot below which never happens so not sure if a log will generate if it cannot get past below? efiboot loaded from device Acpi (PNP0A08,0)/Pci (1F12)/SATA(0,0)/HD(Part1,SigFB80A2E1-C0D7-425B-B471-F5260F9370E7) boot file path: \System\library\CoreServices\boot.efi ................................................................................................ root device uuid is 'E216AA4C-001B-A249-30A9CEE752D3' ................................................................................................. Then the kernel boots next but not on this Asus MB. I thought possibly the SSD drive might be the problem but proved to myself that is not the case same thing happens on a flash drive or regular SATA drive. If you pressed F2 in Clover GUI then /EFI/CLOVER/misc/preboot.log was created. Upload it, please! 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456145 Share on other sites More sharing options...
Lucy183 Posted July 3, 2017 Share Posted July 3, 2017 I'm trying to build clover and get this. make: *** No rule to make target `tbuild'. Stop. make: *** No rule to make target `tbuild'. Stop. build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseMemoryLib/BaseMemoryLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseLib/BaseLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePrintLib/BasePrintLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull] build.py... : error F002: Failed to build module /Users/LuCy/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64, GCC49, RELEASE] - Failed - Build end time: 17:08:39, Jul.03 2017 Build total time: 00:00:07 Cloverx64 ERROR!! Ejecting RAM disk "disk4" unmounted. "disk4" ejected. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456342 Share on other sites More sharing options...
bryan51 Posted July 3, 2017 Share Posted July 3, 2017 bryan51, on 01 Jul 2017 - 6:17 PM, said: hmmm ... for some reason I can't load config.plist anymore, even with EFI mounted. I can open it in Wrangler but in CConfigurator everything is blank? I can create enteries like SMBIOS os thats working ok. Any ideas? Seems like a corrupt config.plist. Thats it, thanks. I had tried a previous version but it must have been corrupt too. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456420 Share on other sites More sharing options...
oSxFr33k Posted July 3, 2017 Share Posted July 3, 2017 If you pressed F2 in Clover GUI then /EFI/CLOVER/misc/preboot.log was created. Upload it, please! Does not create one. I'm guessing the kernel never starts. Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456480 Share on other sites More sharing options...
Sherlocks Posted July 3, 2017 Share Posted July 3, 2017 I'm trying to build clover and get this. make: *** No rule to make target `tbuild'. Stop. make: *** No rule to make target `tbuild'. Stop. build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseMemoryLib/BaseMemoryLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseLib/BaseLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePrintLib/BasePrintLib] build.py... : error 7000: Failed to execute command make tbuild [/Users/LuCy/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull] build.py... : error F002: Failed to build module /Users/LuCy/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64, GCC49, RELEASE] - Failed - Build end time: 17:08:39, Jul.03 2017 Build total time: 00:00:07 Cloverx64 ERROR!! Ejecting RAM disk "disk4" unmounted. "disk4" ejected. Try remove clover folder or src folder.Then try build again from clover build script. I tested r4102. Build is nop 나의 LG-F800S 의 Tapatalk에서 보냄 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456507 Share on other sites More sharing options...
Badruzeus Posted July 3, 2017 Share Posted July 3, 2017 Try remove clover folder or src folder. Then try build again from clover build script. I tested r4102. Build is nop 나의 LG-F800S 의 Tapatalk에서 보냄 Wait, "CloverGrowerPro" is still supported and it also has "src" folder compared to "Build_Clover.command"..? Sorry, this one seems new to me. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456531 Share on other sites More sharing options...
apianti Posted July 3, 2017 Share Posted July 3, 2017 Does not create one. I'm guessing the kernel never starts. This has nothing to do with it, F2 is in the clover GUI for preboot.log, debug.log is output no matter what. The log is created way before the kernel boots. I'm guessing you installed directly to the HFS+ partition? You can only write to VFAT volumes during boot, so you need to either have it on your ESP or use a USB. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456537 Share on other sites More sharing options...
oSxFr33k Posted July 3, 2017 Share Posted July 3, 2017 This has nothing to do with it, F2 is in the clover GUI for preboot.log, debug.log is output no matter what. The log is created way before the kernel boots. I'm guessing you installed directly to the HFS+ partition? You can only write to VFAT volumes during boot, so you need to either have it on your ESP or use a USB. Its true its on the HFS+ partition, I'll grab the SSD drive which has clover installed onto the ESP and try again. Is the preboot.log, the debug.log you are referring to or do I need to enable the debug in clover config to generate an output log? Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456583 Share on other sites More sharing options...
oSxFr33k Posted July 4, 2017 Share Posted July 4, 2017 This has nothing to do with it, F2 is in the clover GUI for preboot.log, debug.log is output no matter what. The log is created way before the kernel boots. I'm guessing you installed directly to the HFS+ partition? You can only write to VFAT volumes during boot, so you need to either have it on your ESP or use a USB. Find attached both Preboot and Debug logs, Thanks! I updated my signature I had swapped it for a Q8400 and forgot about that and the other Quad is as you said the Q9650 and both of these support SSE4.1. Was the debug log helpful, I could not see any warning or error that stood out. Debug and Preboot logs.zip Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456771 Share on other sites More sharing options...
Slice Posted July 4, 2017 Share Posted July 4, 2017 Find attached both Preboot and Debug logs, Thanks! I updated my signature I had swapped it for a Q8400 and forgot about that and the other Quad is as you said the Q9650 and both of these support SSE4.1. Was the debug log helpful, I could not see any warning or error that stood out. In your log 2:170 0:000 CPU Vendor = 756E6547 Model=6FB 2:170 0:000 The CPU not supported SSE4.1 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/540/#findComment-2456817 Share on other sites More sharing options...
Recommended Posts