Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted (edited)

Hi @Slice @Jief_Machak 

 

I have annoying issue with r5129 commit d66a14ae3 (IvyBridge config - Mojave): at start, black screen instead of Clover GUI :cry: I don't understand why. Don't try on Z390 and Big Sur 11.3 Beta

Any one have this problem or just me.

Edited by Matgen84
Jief_Machak
Jief_Machak
Posted
Posted
Just now, Matgen84 said:

Hi @Slice @Jief_Machak 

 

I have annoying issue with r5129 commit d66a14ae3 (IvyBridge config - Mojave): at start, black screen instead of Clover GUI :cry: I don't understand why. Don't try on Z390 and Big Sur 11.3 Beta

Any one have this problem or just me.

debug.log ? So we can see as far as it went. It's most likely a NULL pointer exception. Most of firmware just ignore it, some just stop.

Matgen84
Matgen84
Posted
Posted
2 minutes ago, Jief_Machak said:

debug.log ? So we can see as far as it went. It's most likely a NULL pointer exception. Most of firmware just ignore it, some just stop.

 

Debug.log not generated on Ivybridge :cry:  So I can't upload it.

I test just now: same issue on Z390 config

Jief_Machak
Jief_Machak
Posted
Posted

Ah ok. That means a very early crash. Let's compile a version that put debug.log on screen.

Here it is. You may need to film in slow motion (my main usage of a smartphone since a year !! :)).

CloverX64-2021-02-08-10-52-24-d66a14a-dirty-jief.zip

  • Like 1
Matgen84
Matgen84
Posted
Posted
21 minutes ago, Jief_Machak said:

Ah ok. That means a very early crash. Let's compile a version that put debug.log on screen.

Here it is. You may need to film in slow motion (my main usage of a smartphone since a year !! :)).

CloverX64-2021-02-08-10-52-24-d66a14a-dirty-jief.zip 762.62 kB · 0 downloads


I've to find a android app for slow motion movie because I don't have it. :hysterical: I upload the movie, ASAP

I try your dirty efi file: I can boot Big Sur on my Z390 config. Don't test IvyBridge. Is it a local building issue. ?

Jief_Machak
Jief_Machak
Posted
Posted
1 minute ago, Matgen84 said:

Is it a local building issue. ?

Don't know. It's dirty because I redirect the log on screen. Not more.

So maybe.

To be sure, do a rm -r Build in clover directory. That way, you'll rebuild everything.

 

It's strange. Last time, you cannot use the efi I sent you. Now my efi works and not yours... Maybe last time I had the problem you now have, generated builds that cause problems for your computer.

Matgen84
Matgen84
Posted
Posted
4 minutes ago, Jief_Machak said:

Don't know. It's dirty because I redirect the log on screen. Not more.

So maybe.

To be sure, do a rm -r Build in clover directory. That way, you'll rebuild everything.

 

It's strange. Last time, you cannot use the efi I sent you. Now my efi works and not yours... Maybe last time I had the problem you now have, generated builds that cause problems for your computer.

 

I don't find a free android app effective for filming in slow motion. :cry:

Yes, it's strange. I will delete the Build directory and recompile to see. I'll keep you posted.
 

Thanks

Matgen84
Matgen84
Posted
Posted
31 minutes ago, Jief_Machak said:

To be sure, do a rm -r Build in clover directory. That way, you'll rebuild everything.

 

It's strange. Last time, you cannot use the efi I sent you. Now my efi works and not yours... Maybe last time I had the problem you now have, generated builds that cause problems for your computer.

 

I remove Build in Clover, rebuild again everything: same issue :cry: 

Matgen84
Matgen84
Posted
Posted
34 minutes ago, Jief_Machak said:

Let's try to solve that once for all !

In BootLog.cpp, change line 281 : 


   MemLogfVA(TRUE, DebugMode, FormatString, Marker);

by 


   MemLogfVA(TRUE, 2, FormatString, Marker);

Compile (no need to rm -R Build).

 

Which one, there is 2 BootLog.cpp.  I suppose: ⁨rEFIt_UEFI⁩ ▸ ⁨Platform⁩, Right.

 

Note: when I compile with GCC53 instead of XCODE8: I can boot Mojave (IvyBridge)

Matgen84
Matgen84
Posted
Posted (edited)
36 minutes ago, Jief_Machak said:

Yes. The others are in my Xcode unit tests projects and are not used for Clover EFI.

 

Modify Bootlog.cpp, rebuild... Test on Z390 from USB

 

XCODE8 Build:

When I use Bootloader Chooser selected from F12: 'press any key to continue' message after select efi file
When I use normal USB selected from F12: instant return to BIOS boot chooser

GCC53 Build:

When I use Bootloader Chooser selected from F12: I can boot BS

When I use normal USB selected from F12: I can boot BS

Edited by Matgen84
Jief_Machak
Jief_Machak
Posted
Posted

in rEFIt_UEFI/refit/main.cpp, remove line 2570 "#define DEBUG_ERALY_CRASH" and 2 line lower "#endif"

Then, if you don't have message "Start" at the beginning, the crash is not in Clover, which seems impossible.

Let's assume you'll have it.

Then, move these down : 

  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start");
  PauseForKey(L"1) press any key\n");

line 2599.

If now you can't see it : move up.

If you still see the message : move down

 

No need to go past line 2627, because it's MsgLog, which should have printed something on the console. So the crash is before.

 

Jief_Machak
Jief_Machak
Posted
Posted

I realize there is a new thing on line 2612 "DataHubInstall (ImageHandle, SystemTable);"

Maybe it's in there.

 

Also, to go quicker. Instead of moving the 2 lines, just duplicate  

SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start");

and change the message.

Like :  


#ifdef DEBUG_ERALY_CRASH
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start");
  PauseForKey(L"1) press any key\n");
#endif

#ifdef DEBUG_ON_SERIAL_PORT
  SerialPortInitialize();
#endif
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start1");

  {
    EFI_LOADED_IMAGE* LoadedImage;
    Status = gBS->HandleProtocol(gImageHandle, &gEfiLoadedImageProtocolGuid, (void **) &LoadedImage);

//    if ( !EFI_ERROR(Status) ) {
//      XString8 msg = S8Printf("Clover : Image base = 0x%llX\n", (uintptr_t)LoadedImage->ImageBase); // do not change, it's used by grep to feed the debugger
//      SerialPortWrite((UINT8*)msg.c_str(), msg.length());
//    }
    if ( !EFI_ERROR(Status) ) DBG("CloverX64 : Image base = 0x%llX\n", (uintptr_t)LoadedImage->ImageBase); // do not change, it's used by grep to feed the debugger

#ifdef JIEF_DEBUG
    gBS->Stall(1500000); // to give time to gdb to connect
//  gBS->Stall(0500000); // to give time to gdb to connect
//  PauseForKey(L"press\n");
#endif
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start2");

#ifdef CLOVER_BUILD
  construct_globals_objects(gImageHandle); // do this after self.getSelfLoadedImage() is initialized
#endif
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start3");

#ifdef JIEF_DEBUG
//  all_tests();
//  PauseForKey(L"press\n");
#endif

  gRT->GetTime(&Now, NULL);
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start4");

  // firmware detection
  gFirmwareClover = StrCmp(gST->FirmwareVendor, L"CLOVER") == 0;
  if (!gFirmwareRevision) {
//    gFirmwareRevision = P__oolPrint(L"%d", gST->FirmwareRevision);
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start5");
  DataHubInstall (ImageHandle, SystemTable);
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start6");
  InitializeConsoleSim();
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start7");
  InitBooterLog();
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start8");
  ZeroMem((void*)&gGraphics[0], sizeof(GFX_PROPERTIES) * 4);
  ZeroMem((void*)&gAudios[0], sizeof(HDA_PROPERTIES) * 4);

  DBG("\n");
  if (Now.TimeZone < -1440 || Now.TimeZone > 1440) {
    MsgLog("Now is %02d.%02d.%d,  %02d:%02d:%02d (GMT)\n",
           Now.Day, Now.Month, Now.Year, Now.Hour, Now.Minute, Now.Second);
  } else {
    MsgLog("Now is %02d.%02d.%d,  %02d:%02d:%02d (GMT+%d)\n",
      Now.Day, Now.Month, Now.Year, Now.Hour, Now.Minute, Now.Second, gSettings.GUI.Timezone);
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start10");
  //MsgLog("Starting Clover rev %ls on %ls EFI\n", gFirmwareRevision, gST->FirmwareVendor);
  MsgLog("Starting %s on %ls EFI\n", gRevisionStr, gST->FirmwareVendor);
  MsgLog("Build id: %s\n", gBuildId.c_str());
  if ( gBuildInfo ) DBG("Build with: [%s]\n", gBuildInfo);

You can copy and paste this in main.cpp.

 

iCanaro
iCanaro
Posted
Posted
3 hours ago, Matgen84 said:

Hi @Slice @Jief_Machak 

 

I have annoying issue with r5129 commit d66a14ae3 (IvyBridge config - Mojave): at start, black screen instead of Clover GUI :cry: I don't understand why. Don't try on Z390 and Big Sur 11.3 Beta

Any one have this problem or just me.

no problem detected in starting Z68, Z97, Z370, X570

try the clover i compiled

 

CLOVERX64-5129-d66a14ae3.efi.zip

Matgen84
Matgen84
Posted
Posted
21 minutes ago, Jief_Machak said:

I realize there is a new thing on line 2612 "DataHubInstall (ImageHandle, SystemTable);"

Maybe it's in there.

 

Also, to go quicker. Instead of moving the 2 lines, just duplicate  


SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start");

and change the message.

Like :  



#ifdef DEBUG_ERALY_CRASH
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start");
  PauseForKey(L"1) press any key\n");
#endif

#ifdef DEBUG_ON_SERIAL_PORT
  SerialPortInitialize();
#endif
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start1");

  {
    EFI_LOADED_IMAGE* LoadedImage;
    Status = gBS->HandleProtocol(gImageHandle, &gEfiLoadedImageProtocolGuid, (void **) &LoadedImage);

//    if ( !EFI_ERROR(Status) ) {
//      XString8 msg = S8Printf("Clover : Image base = 0x%llX\n", (uintptr_t)LoadedImage->ImageBase); // do not change, it's used by grep to feed the debugger
//      SerialPortWrite((UINT8*)msg.c_str(), msg.length());
//    }
    if ( !EFI_ERROR(Status) ) DBG("CloverX64 : Image base = 0x%llX\n", (uintptr_t)LoadedImage->ImageBase); // do not change, it's used by grep to feed the debugger

#ifdef JIEF_DEBUG
    gBS->Stall(1500000); // to give time to gdb to connect
//  gBS->Stall(0500000); // to give time to gdb to connect
//  PauseForKey(L"press\n");
#endif
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start2");

#ifdef CLOVER_BUILD
  construct_globals_objects(gImageHandle); // do this after self.getSelfLoadedImage() is initialized
#endif
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start3");

#ifdef JIEF_DEBUG
//  all_tests();
//  PauseForKey(L"press\n");
#endif

  gRT->GetTime(&Now, NULL);
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start4");

  // firmware detection
  gFirmwareClover = StrCmp(gST->FirmwareVendor, L"CLOVER") == 0;
  if (!gFirmwareRevision) {
//    gFirmwareRevision = P__oolPrint(L"%d", gST->FirmwareRevision);
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start5");
  DataHubInstall (ImageHandle, SystemTable);
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start6");
  InitializeConsoleSim();
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start7");
  InitBooterLog();
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start8");
  ZeroMem((void*)&gGraphics[0], sizeof(GFX_PROPERTIES) * 4);
  ZeroMem((void*)&gAudios[0], sizeof(HDA_PROPERTIES) * 4);

  DBG("\n");
  if (Now.TimeZone < -1440 || Now.TimeZone > 1440) {
    MsgLog("Now is %02d.%02d.%d,  %02d:%02d:%02d (GMT)\n",
           Now.Day, Now.Month, Now.Year, Now.Hour, Now.Minute, Now.Second);
  } else {
    MsgLog("Now is %02d.%02d.%d,  %02d:%02d:%02d (GMT+%d)\n",
      Now.Day, Now.Month, Now.Year, Now.Hour, Now.Minute, Now.Second, gSettings.GUI.Timezone);
  }
  SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Start10");
  //MsgLog("Starting Clover rev %ls on %ls EFI\n", gFirmwareRevision, gST->FirmwareVendor);
  MsgLog("Starting %s on %ls EFI\n", gRevisionStr, gST->FirmwareVendor);
  MsgLog("Build id: %s\n", gBuildId.c_str());
  if ( gBuildInfo ) DBG("Build with: [%s]\n", gBuildInfo);

You can copy and paste this in main.cpp.

 

 

 

Same issue with Bootloader Chooser and USB normal :cry:

Matgen84
Matgen84
Posted
Posted
4 minutes ago, iCanaro said:

no problem detected in starting Z68, Z97, Z370, X570

try the clover i compiled

 

CLOVERX64-5129-d66a14ae3.efi.zip 650.52 kB · 0 downloads

 

Thanks. :) Do use XCODE or GCC to build ? I've only problem with XCODE.

Matgen84
Matgen84
Posted
Posted
3 minutes ago, iCanaro said:

XCODE usage
I normally click build, 
menu 10 then menu 7

Z370 --> Catalina --> XCODE 12.4

 

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

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