Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted (edited)
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
scj312
scj312
Posted
Posted

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

Slice
Slice
Posted
Posted
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

  • Like 2
pkdesign
pkdesign
Posted
Posted
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

apianti
apianti
Posted
Posted (edited)
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
fusion71au
fusion71au
Posted
Posted (edited)
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
  • Like 2
Planet X
Planet X
Posted
Posted
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?

Slice
Slice
Posted
Posted
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.

pkdesign
pkdesign
Posted
Posted
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?

apianti
apianti
Posted
Posted (edited)
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
fusion71au
fusion71au
Posted
Posted (edited)
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
  • Like 1
apianti
apianti
Posted
Posted (edited)
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
  • Like 1
Slice
Slice
Posted
Posted
2 hours ago, Matgen84 said:

For Debug kexts, there is nothing inside the folder. I try again. Thanks.

You means Debug in section KextPatches? Log is impossible here. You can see the process only on screen.

Matgen84
Matgen84
Posted
Posted

Hi,

 

Despite of localizable.strings file, Theme description for Clovy doesn't exist in clover Package from SourceForge, or build with Build_Clover.command and Did script. 

 

I don't understand, why? Some ideas. Please.

Capture d’écran 2018-12-03 à 17.48.32.png

pkdesign
pkdesign
Posted
Posted

Sorry it took me so long to install. I couldn't mess with my production machine and still trying to figure out why my AMD RX 570 doesn’t work right.

 

Installed this version of Clover and it worked without a hitch. So it must be the Xcode version that causes the issue.

 Share
Go to topic listing
×
×
  • Create New...