Jump to content
30960 posts in this topic

Recommended Posts

Ok, but I still don't know why you don't have all those messages.

Maybe your firmware didn't switch back to text mode.

Let me send you an efi compiled with xcode.

CLOVERX64.efi.zip

You should see : 

 

Screenshot 2021-02-08 at 14.08.15.png

If you see that and you press a key and you see Clover, it may be an Xcode bug ???

Did you try iCanaro efi too ?

  • Like 1
12 minutes ago, Matgen84 said:

 

I use XCODE 11.3.1 (Mojave 10.14.6) IvyBridge - Z77 to build Clover. Don't use my Z390 for building Clover 

I can only report you some experience, for example on the AMD X570 I can almost never compile, always some mistake whatever it does; with mojave and the same XCODE release that you use, compilation always happens successfully, but often it happened that the Clover produced then did not work.
From me compiling on the Z370 is much more reliable.

25 minutes ago, Jief_Machak said:

Interesting, you are "InsanelyMacaholic", I am "teh 1337n3ss!" !

you've been mis-compiling status today on insanely mac :hysterical:

  • Like 1
36 minutes ago, Jief_Machak said:

You should see : 

 

 

Screenshot 2021-02-08 at 14.08.15.png

If you see that and you press a key and you see Clover, it may be an Xcode bug ???

Did you try iCanaro efi too ?

 

What you describe is exactly what's happen: text message (BootLoader Chooser), after hit a key, the Clover GUI appears few seconds later. Why there is a XCODE bug ???
Remember I use XCODE 11.3.1 (Mojave, Ivybridge Asus z77)

Sorry, but I'm lost. You said that your xcode compilation doesn't work. iCanaro xcode compiled efi and mine works. Looks like an xcode bug, isn't it ?

So now, replace main.cpp by this one main.cpp, compile with xcode and try. What's on the screen ?

20 minutes ago, Jief_Machak said:

Sorry, but I'm lost. You said that your xcode compilation doesn't work. iCanaro xcode compiled efi and mine works. Looks like an xcode bug, isn't it ?

So now, replace main.cpp by this one main.cpp, compile with xcode and try. What's on the screen ?

 

 

On screen: Press any text * Hit any key to continue * :cry:
 

@iCanaro use XCODE 12.4 (Catalina). I use XCODE 11.3.1 (Mojave). I don't know if there is a bug depending on the version.

2 minutes ago, Matgen84 said:

To solve my problem, what do you think if I reinstall XCODE 11.3.1

I would definitely try
xcode removal, macOS restart, and xcode reinstall and start them to end installation

  • Like 1

Hi Slice.

On a Laptop with an Ivy Bridge  (i5-3340M) or on a Desktop with Kaby Lake (i5-7600K), both with :  Big Sur 11.2 (20D64) Xcode  12.4 (12D4e) and clang 12.0.0

The last r_5129 XCODE8 RELEASE i could build is « master, commit e24ceaa47 ».

From a170710 to d66a144a commit XCODE8 build abort but never with GCC.

GCC53 (default) builds all commits from a170710 to the last d66a144a.

So i’m not sure it’s an Xcode and/or clang releases problem.

 

  • Confused 1
3 hours ago, Jief_Machak said:

Sorry, but I'm lost. You said that your xcode compilation doesn't work. iCanaro xcode compiled efi and mine works. Looks like an xcode bug, isn't it ?

So now, replace main.cpp by this one main.cpp, compile with xcode and try. What's on the screen ?

Underscore in the lef-top corner and then switch to next boot entry in UEFI BIOS.

It will happen if execution encounter return;.

  • Like 1

@Jief_Machak @iCanaro @Slice
 

I remove and reinstall XCODE 11.3.1 + command line tools: I can build Clover latest commit but same issue

 

---> On screen at start with Bootloader Chooser: Press any text * Hit any key to continue * :bye:

Remember : I can boot Clover (GCC Build) :hysterical:

  • Like 1
55 minutes ago, SavageAUS said:

So newest clover includes datahubdxe?
On my Intel i7-9750h do I need useARTfrequency?
What if datahubdexe already exists in EFI will clover remove it?


Sent from my iPhone using Tapatalk

Double installed is not a problem. Last will work and no matter if they are the same.

Yes, for i7-9750h you need ARTfrequency. May be obligatory. I can tell exactly if look into Clover's preboot.log.

12 hours ago, Slice said:

DEBUG_ERALY_CRASH does nothing on screen. No messages.

QEMU crashes

Снимок экрана 2021-02-08 в 21.42.54.png

Size of Clover greater then allowed?

Снимок экрана 2021-02-08 в 21.47.51.png

 

 

Cannot reproduce that...

Could send me your QEMU disk image ?

Screenshot 2021-02-09 at 09.51.43.png

 

Also :

Do you use the qemu I put in qemu folder ? If not, could you try, so we have the same exact Qemu version ? To do so :

 - be in your Clover folder in terminal

 - ./Qemu/launch ./Build/Clover/DEBUG_XCODE8/X64/CLOVERX64.efi

 

Edited by Jief_Machak
×
×
  • Create New...