Jump to content
ErmaC

Clover General discussion

18,976 posts in this topic

Recommended Posts

15 minutes ago, Ritz Carltn said:

There is something wrong with PS/2 Keyboatd and Mouse in revison 4769.
After loading Clover, it did not working PS/2 Device. Is there someone any same experience as me?

Sented by Tapatalk in my Android SM-G930S
 

It looks like wrong compilation of file boot. Take it from previous revision.

Share this post


Link to post
Share on other sites
Advertisement

Hi,

 

Why there is a file "Shell.inf" in EFI/CLOVER/Tools? Please, I don't understand

 

Thanks

 

Share this post


Link to post
Share on other sites
5 minutes ago, Matgen84 said:

Hi,

 

Why there is a file "Shell.inf" in EFI/CLOVER/Tools? Please, I don't understand

 

Thanks

 

Because of a build script bug.

Share this post


Link to post
Share on other sites
20 minutes ago, Slice said:

Because of a build script bug.

 

 

Build_clover.command (EDK2) and Dids script (UDK2018) have the same issue in r4777: a file "Shell.inf" in EFI/CLOVER/Tools. I also found this file in a old version r4761.

 

Some solution.

Share this post


Link to post
Share on other sites
On 11/22/2018 at 1:54 AM, Badruzeus said:

Working fine here either, I've 3 ancient machines using Legacy.

 

On my case is not Clover, but recent "ApfsDriverLoader*.efi".

I just built v 4779 using BuildClover command and I still can not boot my legacy machine. All I see it a blinking cursor.

 

I do not have APFS driver in kext since I don’t use it. 

Share this post


Link to post
Share on other sites
18 hours ago, Matgen84 said:

 

 

Build_clover.command (EDK2) and Dids script (UDK2018) have the same issue in r4777: a file "Shell.inf" in EFI/CLOVER/Tools. I also found this file in a old version r4761.

 

Some solution.

Drag the file to trash.

Share this post


Link to post
Share on other sites
1 minute ago, Slice said:

Drag the file to trash.

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Share this post


Link to post
Share on other sites
10 hours ago, pkdesign said:

I just built v 4779 using BuildClover command and I still can not boot my legacy machine. All I see it a blinking cursor.

 

I do not have APFS driver in kext since I don’t use it. 

There should be more information about the issue.

Did you try other boot6 or boot7 files? From previous revisions.

Did you set Boot->Debug=YES to get a debug.log?

What efi drivers do you have?

3 minutes ago, Matgen84 said:

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Because of build script.

Share this post


Link to post
Share on other sites
56 minutes ago, Slice said:

Because of build script.

 

I've the same Shell.inf file when I use Makepkg from Source :cry:  I keep searching

 

EDIT: Same issue with Clover Release download from SourceForge

Edited by Matgen84

Share this post


Link to post
Share on other sites
21 hours ago, ellaosx said:

it wont hurt to be in there. or add a command just before the mkpkg to delete it in your script.

 

Thanks :) I can do that in my scripts (Build_clover.command and Dids script). 

 

As I said before  Clover Release download from SourceForge has the same Shell.inf file in EFI/CLOVER/Tools. 

 

EDIT: Thanks @Slice for remove Shell.inf from Clover Package source in commits r4780

Edited by Matgen84

Share this post


Link to post
Share on other sites

For some reason when I have an APFS volume present, Clover takes a very long time to display the GUI (30+ seconds). I am using ApfsDriverLoader and there is no delay when booting without an APFS volume present. In the preboot log it looks like [InitScreen] line is 47 seconds. Any ideas?

preboot.log

Share this post


Link to post
Share on other sites

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

Share this post


Link to post
Share on other sites
9 hours ago, mrjayviper said:

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

debug=0x100 keepsyms=1

Share this post


Link to post
Share on other sites
On 11/28/2018 at 2:51 AM, Slice said:

There should be more information about the issue.

Did you try other boot6 or boot7 files? From previous revisions.

Did you set Boot->Debug=YES to get a debug.log?

What efi drivers do you have?

I reinstalled 4779 and was not able to boot again. I never get past a solid cursor on screen after POST so there is no debug file to provide for that.

 

I copied boot file from my 4741 installation in to the 4779 EFI and I was able to boot.

 

These are the drives/kexts I have installed:

 

drivers64
FSInject-64.efi
HFSPlus-64.efi
SMCHelper-64.efi

 

kexts
FakeSMC.kext
realtekALC.kext

 

Attached is the debug file from the successful boot.

debug.log

Share this post


Link to post
Share on other sites
18 hours ago, mrjayviper said:

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

 

9 hours ago, Slice said:

debug=0x100 keepsyms=1

 

Yeah, you can also easily use these options from the spacebar menu when a boot entry is selected as well.

1 hour ago, pkdesign said:

I reinstalled 4779 and was not able to boot again. I never get past a solid cursor on screen after POST so there is no debug file to provide for that.

 

I copied boot file from my 4741 installation in to the 4779 EFI and I was able to boot.

 

These are the drives/kexts I have installed:

 

drivers64
FSInject-64.efi
HFSPlus-64.efi
SMCHelper-64.efi

 

kexts
FakeSMC.kext
realtekALC.kext

 

Attached is the debug file from the successful boot.

 

Your problem is caused by the firmware emulation if you are not even getting a debug.log and replacing boot with a previous version works. It's much harder to debug that but since you gave a range of revisions where the change occurred that is causing the issue, I imagine it will be easy to find any changes that may have been made to the legacy firmware emulation that are responsible for the issue.

Edited by apianti

Share this post


Link to post
Share on other sites
7 hours ago, pkdesign said:

Attached is the debug file from the successful boot.

debug.log

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 

Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

4 hours ago, apianti said:

Does XCODE 10.1 build previous revisions to r4761 without issue? Or does it not build a valid boot firmware at all? Are the different build rules for XCODE 10.1 causing the problem?

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

Edited by fusion71au
Extra info for @apianti

Share this post


Link to post
Share on other sites

Does XCODE 10.1 build previous revisions to r4761 without issue? Or does it not build a valid boot firmware at all? Are the different build rules for XCODE 10.1 causing the problem?

Share this post


Link to post
Share on other sites
On 11/29/2018 at 1:48 AM, scj312 said:

For some reason when I have an APFS volume present, Clover takes a very long time to display the GUI (30+ seconds). I am using ApfsDriverLoader and there is no delay when booting without an APFS volume present. In the preboot log it looks like [InitScreen] line is 47 seconds. Any ideas?

preboot.log

Do you use a NVMe drive? The same happened to me. I use apfs.efi from 10.13.0 again as it boots way faster. But please somebody have a look into this? NVMe drives should also boot faster isn't it?

Share this post


Link to post
Share on other sites
14 hours ago, fusion71au said:

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 


Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

At this moment I can include boot6 and boot7 files from good 4741 revision into next releases until the issue will be resolved.

Share this post


Link to post
Share on other sites
19 hours ago, fusion71au said:

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 


Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

Ah, i see. What an odd problem.

Can anyone build current Clover with Xcode 8 and I can try on my machine?

Share this post


Link to post
Share on other sites
20 hours ago, fusion71au said:

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

 

Are you sure there is not a problem with the build rules for XCODE 10.1? I don't know if you mean that the problem is an intrinsic function or that it's inherent to XCODE 10.1. If you mean the former, can you narrow down exactly what intrinsic is causing the problem since really all that an intrinsic should be doing is generating an instruction or set of instructions in the same way, this behavior shouldn't really change. For either, the most likely scenario is that optimization is deciding that some needed instructions are not helpful for some reason, have you tried completely disabling optimization?

 

EDIT: Didn't realize you said the toolchain is set to XCODE8, are there no toolchain build rules for XCODE10.1? There may need to be different decisions made, so there should probably be XCODE10 toolchain.

Edited by apianti

Share this post


Link to post
Share on other sites
On 12/1/2018 at 2:47 AM, pkdesign said:

Ah, i see. What an odd problem.

Can anyone build current Clover with Xcode 8 and I can try on my machine?

 

Attached Clover r4784 compiled with XCODE 8.2.1 in 10.11.6: Clover_v2.4k_r4784.zip

 

Alternatively, you can use GCC instead of XCODE to build Clover eg if you use the Build_Clover.command script, edit the BuildCloverConfig.txt file like below...

 

GNU=GCC53
Build_Tool=GNU

 

On 12/1/2018 at 4:35 AM, apianti said:

EDIT: Didn't realize you said the toolchain is set to XCODE8, are there no toolchain build rules for XCODE10.1? There may need to be different decisions made, so there should probably be XCODE10 toolchain.

 Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? :)

 

 

13 hours ago, apianti said:

 

You can try a test by changing the tools_def.txt file in your UDK2018\EDK2/Conf directory and modifying the XCODE8 definitions near the bottom, either line 6227 or line 7000 depending which branch you are using, change the flag -Os to -O0 to disable optimizations for debug. Then build the debug version and see if that results in a working boot firmware. If so, then some specific optimization needs disabled, if not, then new rules need made for XCODE10. In that case, I'll let Zenith432 figure out what that would be since he's much better at that and I don't have the time to screw around to figure out what the problem is...

 

EDIT: You might also want to try adding -O0 to the the ASM rule a few lines before as well to see if that makes a difference.

 

Disabled optimization during compilation with -O0 flag in tools_def.txt still results in bad boot6,7 using XCODE 10.1.  Looks like new rules for XCODE10 will be required...

 

Edited by fusion71au
Tried @apianti's suggestion

Share this post


Link to post
Share on other sites
3 hours ago, fusion71au said:

 Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? :)

 

You can try a test by changing the tools_def.txt file in your UDK2018\EDK2/Conf directory and modifying the XCODE8 definitions near the bottom, either line 6227 or line 7000 depending which branch you are using, change the flag -Os to -O0 to disable optimizations for debug. Then build the debug version and see if that results in a working boot firmware. If so, then some specific optimization needs disabled, if not, then new rules need made for XCODE10. In that case, I'll let Zenith432 figure out what that would be since he's much better at that and I don't have the time to screw around to figure out what the problem is...

 

EDIT: You might also want to try adding -O0 to the the ASM rule a few lines before as well to see if that makes a difference.

Edited by apianti

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
×