Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

PG7
PG7
Posted
Posted
16 hours ago, Jief_Machak said:

J'ai supprimé la première option de chargement.

N'importe qui avec un démarrage non-osx, veuillez tester. 

 

hello to everyone and the whole team

 

tested here and working 100%
boot on windows 10

 

Spoiler

406595231_Capturedecran2021-03-23a11_52_42.thumb.png.acf17bf7fbd14074c0f99fd50ef62cb6.png

 

  • Like 4
  • Thanks 1
matxpa
matxpa
Posted
Posted
21 hours ago, Jief_Machak said:

I've committed now.

This commit is a refactoring, as usual. Which means, report the least behaviour change, please, but DON'T modify your config to workaround.

The specific point I'd like to be tested, is custom entries and sub entries. If you have some of them configured, please test that it goes as usual.

Thanks.

 

@Jief_Machak

 

On a Laptop Asus X75VB IvyBridge (with MBP11,3 SMBIOS) I5-3340M, HD4000

 

Starting Clover revision: 5131 (master, commit 829fd040d) on American Megatrends EFI 
Build id: 20210322154001-829fd04-dirty
Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG --conf=/Users/xxxxx/CloverBootloader/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 11.2.3]

 

BOOT OK  with r5131 (829fd040d) on the next 5 CustomEntries (without SubEntries) in info.plist GUI section 

 

On Internal SSD 2,5" Crucial MX100 500 Gb

          Big Sur 11.2.3 (20D91) : Preboot                                              item 1 in info.plist GUI/Custom/Entries

          Big Sur 11.2.3 (20D91) : Recovery                                            item 2 in info.plist GUI/Custom/Entries

On External SSD mSata EVO 860 250 Gb

          Big Sur  beta4 11.3 (20E5210c) : Preboot                                item 3 in info.plist GUI/Custom/Entries

          Big Sur beta4 11.3 (20E5210c) : Recovery                               item 4 in info.plist GUI/Custom/Entries

 

On Internal HDD 2,5" WD Black 500 Gb Sata III 7200

          Win10 x64 20h2                                                                          item 5 in info.plist GUI/Custom/Entries

 

 

Thanks

 

Best regards

Capture d’écran 2021-03-23 à 11.32.59.png

Capture d’écran 2021-03-23 à 11.33.33.png

screenshot0.png

screenshot1.png

screenshot2.png

screenshot3.png

screenshot4.png

  • Like 2
  • Thanks 1
maclinuxG4
maclinuxG4
Posted
Posted
12 hours ago, Jief_Machak said:

I you tried my efi, it's a debug version = slower.

Yes Boot->Debug will make it slower, especially on some USB stick, but DEBUG version are non-optimized and the code is also inherently slower.

i recompil all each time

Slice
Slice
Posted
Posted
1 hour ago, Jief_Machak said:

Yes, possible too. But do the same way on the previous version and the slow version.

Sure, debug.log in previous version is fast because it is not saved every line. It was useless because same as preboot.log.

Jief_Machak
Jief_Machak
Posted
Posted
6 minutes ago, Slice said:

Sure, debug.log in previous version is fast because it is not saved every line

I think you are a bit stubborn here. Debug WAS saved at every line.

 

I've told many time to look at the end of the new "SaveMessageToDebugLogFile()", there is "closeDebugLog()".

You were convinced that the log was not generated on panic but in fact it was not generated at ALL because of no configuration in Clover.dsc for release version.

Proof is : you wasted time to re-import old functions and they did the same for release version : no log.

 

So the problem you had with release version was NOT because of the new log function. Period.

Jief_Machak
Jief_Machak
Posted
Posted
34 minutes ago, Slice said:

The fact is debug.log now saved and second fact that in this case clover works much slowly. I see timings.

That's true. What wasn't true is the reason why and when it wasn't saved.

 

That is not true :

3 hours ago, Slice said:

Sure, debug.log in previous version is fast because it is not saved every line

 

The diagnosis was wrong.

when) Right = never generated for release even for successful boot. Wrong = because of a panic.

why) Right = because it was configured in Clover.dsc. Wrong = because log file closed at every line.

 

These are just the facts too. Gdb can be used to prove it. In fact, that's how I got the right diagnosis.

 

Slice
Slice
Posted
Posted

Those menus are intended to be drawn by GraphicsMenuStyle.

And where is it? 

  if (AllowGraphicsMode) {
//    Style = &REFIT_MENU_SCREEN::GraphicsMenuStyle;
    if (ThemeX.VerticalLayout) {
      m_MainStyle = &REFIT_MAINMENU_SCREEN::MainMenuVerticalStyle;
    } else {
      m_MainStyle = &REFIT_MAINMENU_SCREEN::MainMenuStyle;
    }
  }else{
    m_MainStyle = &REFIT_MAINMENU_SCREEN::TextMenuStyle;
  }

 

matxpa
matxpa
Posted
Posted
On 3/22/2021 at 1:42 PM, Jief_Machak said:

I've committed now.

This commit is a refactoring, as usual. Which means, report the least behaviour change, please, but DON'T modify your config to workaround.

The specific point I'd like to be tested, is custom entries and sub entries. If you have some of them configured, please test that it goes as usual.

Thanks.

 

Hi Jief

I try to test "sub entries" with Clover r5131 (commit ff4c90b : Finish refactoring of custom entries settings)

just wana start "Big Sur Preboot" in verbose mode with a sub entry in custom entry to test "sub entry" but Big Sur  boots without verbose mode on std output.

 

regards

screenshot0.png

screenshot1.png

screenshot2.png

config.plist

matxpa
matxpa
Posted
Posted
49 minutes ago, matxpa said:

 

Hi Jief

I try to test "sub entries" with Clover r5131 (commit ff4c90b : Finish refactoring of custom entries settings)

just wana start "Big Sur Preboot" in verbose mode with a sub entry in custom entry to test "sub entry" but Big Sur  boots without verbose mode on std output.

 

regards

screenshot0.png

screenshot1.png

screenshot2.png

config.plist 14.97 kB · 2 downloads

 

SubEntry-boot-log.txt

Jief_Machak
Jief_Machak
Posted
Posted
On 3/9/2020 at 3:48 PM, Jief_Machak said:

I've committed a Qemu folder, in which you can easily start under control of gdb to catch where the panic message come from. It'll considerably speed up the bug resolution.

To use :

 - regenerate your basetools to recompile GenFW

- install qemu with brew (super easy)

- install gdb with brew (super easy too, but wait...)

- codesign gdb. That's a bit annoying. Well there is plenty of guide over the internet and it doesn't take long. The thing is : if you got this error with a very good self explanatory message, you may have to create in your login keychain instead os System and move it after. I was able once to create in System, some time ago, but not anymore. This should work : https://gist.github.com/hlissner/898b7dfc0a3b63824a70e15cd0180154

If it doesn't work first time, it's not because of custom parameter of the certificate. No need to waste your time with that. The field you need to change are specify in the guide. It's really a problem of having your keychain unlock to create the certificate.

 

If you got a panic message, compile with GCC53 toolchain, DEBUG version, then start Qemu/gdb_launch (not need in a the folder). When you got your panic agin, gdb should give you a prompt "(gdb) ". Just type bt, return and send us the backtrace. It looks like this and it's super helpful :  


(gdb) bt
#0  panic () at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/rEFIt_UEFI/cpp_util/panic.cpp:18
#1  0x000000007ddb8448 in REFIT_MENU_SCREEN::RunGenericMenu (this=0x7deddfe0 <MainMenu>, StyleFunc=&virtual REFIT_MENU_SCREEN::MainMenuStyle(unsigned long long, wchar_t const*), DefaultEntryIndex=0x7fcef9b0, ChosenEntry=0x7fcef9c0)
    at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/rEFIt_UEFI/refit/menu.cpp:2770
#2  0x000000007ddc3426 in REFIT_MENU_SCREEN::RunMainMenu (this=0x7deddfe0 <MainMenu>, DefaultSelection=-1, ChosenEntry=0x7fcefac8) at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/rEFIt_UEFI/refit/menu.cpp:5682
#3  0x000000007dda8972 in RefitMain (ImageHandle=0x7ec38918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/rEFIt_UEFI/refit/main.cpp:2641
#4  0x000000007dda2360 in ProcessModuleEntryPointList (ImageHandle=0x7ec38918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/Build/Clover/DEBUG_GCC53/X64/rEFIt_UEFI/refit/DEBUG/AutoGen.c:497
#5  0x000000007dda2297 in _ModuleEntryPoint (ImageHandle=0x7ec38918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/workspace_Clover-master/Clover--CloverHackyColor--master/MdePkg/Library/UefiApplicationEntryPoint/ApplicationEntryPoint.c:59
(gdb)

Sometime, in the backtrace, you get a lot of line before (means below) RefitMain. No need for that.

 

Hope you'll try. I'll assist.

 

Screen Shot 2020-03-09 at 15.38.41.png

That a post I made to explain how to get the backtrace on a panic.

Very easy once you've installed gdb.

 

For example, I added a panic line 729:

1003848437_Screenshot2021-03-25at00_19_21.png.cc0265fda1272b043cf4ae57e9718126.png

 

Compile a DEBUG_GCC53 version, launch ./Qemu/gdb_launch and you get : 

Breakpoint 2, panic_ (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
format=0x7ddb1938 "sdfsdf", va=0x7fcef488 "\377\377\377\377\377\377\377\377", <incomplete sequence \372\316\177>) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/rEFIt_UEFI/Platform/Posix/abort.cpp:37
37	  egSetGraphicsModeEnabled(false);
(gdb)

Enter "bt" for backtrace and that's it : 

(gdb) bt
Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: 
#0  panic_ (format=0x7ddb1938 "sdfsdf", va=0x7fcef488 "\377\377\377\377\377\377\377\377", <incomplete sequence \372\316\177>) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/rEFIt_UEFI/Platform/Posix/abort.cpp:37
#1  0x000000007dc9b0d6 in panic (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
format=0x7ddb1938 "sdfsdf") at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/rEFIt_UEFI/Platform/Posix/abort.cpp:71
#2  0x000000007dc7bb95 in REFIT_MAINMENU_SCREEN::RunMainMenu (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
this=0x7de1d700 <MainMenu>, DefaultSelection=-1, ChosenEntry=0x7fcefa28) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/rEFIt_UEFI/gui/REFIT_MAINMENU_SCREEN.cpp:729
#3  0x000000007dc45ac4 in RefitMain (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
ImageHandle=0x7ec39918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/rEFIt_UEFI/refit/main.cpp:3339
#4  0x000000007dc38369 in ProcessModuleEntryPointList (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
ImageHandle=0x7ec39918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/Build/Clover/DEBUG_GCC53/X64/rEFIt_UEFI/refit/DEBUG/AutoGen.c:649
#5  0x000000007dc38297 in _ModuleEntryPoint (Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
ImageHandle=0x7ec39918, SystemTable=0x7f745f18) at /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.2/MdePkg/Library/UefiApplicationEntryPoint/ApplicationEntryPoint.c:59
(gdb)

Notice the "REFIT_MAINMENU_SCREEN.cpp:729" on the frame #2.

 

That way you'll get the exact line where most likely a loop among MainMenu.entries is wrong.

 

 

I can do it if you send me the Qemu img AND the "./Build/Clover/DEBUG_GCC53/X64/CLOVERX64.debug" file, generated at the compilation of the CloverX64.efi that's in the img. Any other, from a previous compilation, won't work.

Jief_Machak
Jief_Machak
Posted
Posted
1 hour ago, matxpa said:

 

SubEntry-boot-log.txt 59.38 kB · 0 downloads

I tried an old 5123 and your problem is already there. And it happens only when the parameter is "-v", I think. So I guess, somewhere Clover removes it for an unknown reason.

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