Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,136 posts in this topic

Recommended Posts

Jief_Machak
Jief_Machak
Posted
Posted (edited)
23 minutes ago, matxpa said:

I confirm with CloverX64-RELEASE_XCODE8-20210325001901-4b0ddf4-dirty.efi : boot OK

 

With CloverX64-RELEASE_XCODE8-20210325173256-65f8cc1-dirty.efi                 : boot KO and with 3252bf6 or 3b542ca Clover crashes too

Capture d’écran 2021-03-27 à 09.26.19.png

IMG_20210327_095241.jpg

IMG_20210327_095425.jpg

Yeah, @eng_redaesm already proves that there is a bug introduced.

I am just waiting for him to send me the 2 debug.log corresponding to the 2 commits (4b0ddf4deed019913c1989e192113148139c320a, 65f8cc122d6cd5db4007218b66b72532382cc28c) so I can make a diff on them. Should be easy then to discover what changed.

In this commit I made some change to the settings DellSMBIOSPatch. Do you have a Dell ?

@matxpa If you can do these 2 debug.log, that'll work too...

Edited by Jief_Machak
  • Like 2
Link to comment
Share on other sites
matxpa
matxpa
Posted
Posted
4 minutes ago, Matgen84 said:


@matxpa What app do you use in this screenshot, please ?

 

a free git client 

smartgit-macosx-20_2_4 on https://www.syntevo.com/smartgit/download/

 

I prefer SmartGit at GitHub Desktop

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

@eng_redaesm The debug.log of the LAST commit might be less helpful than the debug.log of the NEXT commit. There is many change between 4b0ddf4 and the last commit. To compare, it's better if there is a minimum of changes between the compared version. Could you do the first non-working commit (65f8cc122d6cd5db4007218b66b72532382cc28c) ?

Link to comment
Share on other sites
matxpa
matxpa
Posted
Posted
2 hours ago, Jief_Machak said:

Yeah, @eng_redaesm already proves that there is a bug introduced.

I am just waiting for him to send me the 2 debug.log corresponding to the 2 commits (4b0ddf4deed019913c1989e192113148139c320a, 65f8cc122d6cd5db4007218b66b72532382cc28c) so I can make a diff on them. Should be easy then to discover what changed.

In this commit I made some change to the settings DellSMBIOSPatch. Do you have a Dell ?

@matxpa If you can do these 2 debug.log, that'll work too...

 

In this commit I made some change to the settings DellSMBIOSPatch. Do you have a Dell ?

Not a Dell but Laptop : Asus X75VB IvyBridge (MBP11,3) : H76M, I5-3340M, HD4000, GF740M (off), 1600x900, 12GB Hynix DDR3L 12800, SSD 2,5" Crucial MX100 500 Gb with Big Sur 11.2.3 (20D91) and Clover r5131 (4b0ddf4), 

@matxpa If you can do these 2 debug.log, that'll work too...

joined

r5131_4b0ddf4de_20210327_BOOTX64.efi.log r5131_4b0ddf4de_20210327_preboot.log r5131_65f8cc122_20210327_BOOTX64.EFI.log r5131_65f8cc122_20210327_preboot.log

Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted

@Jief_Machak I think this time I found some useful info (I hope so). 

So I always had FileVault enabled. But looked at the log we saw that Clover can't ls the directory, so I thought maybe it's a permission issue because FileVault is enabled, so I disabled it for testing.

Restart, and boom. Clover can access the Installer, the entry is appeared. 

- [07]: 'macOS SSD - adatok'
    ApfsContainerUUID=5EF86F43-A55C-4384-B7DF-E35BB7E5CD9F
    ApfsFileSystemUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4
Volume= macOS SSD - adatok
Open "" = Success
Open "\" = Success
Open "\macOS Install Data" = Success
Open "\macOS Install Data\Locked Files" = Success
Open "\macOS Install Data\Locked Files\BaseSystem.dmg" = Success
ls root dir:
  sw
  home
  usr
  Library
  System
  mnt
  macOS Install Data
  private
  Users
  Applications
  opt
  Volumes
  cores
      AddLoaderEntry for Volume Name=macOS SSD - adatok, idx=4
      OSVersion=10.15.7 
      IconName=cata,mac comma=4 size=8
      first=os_cata
      Second=os_mac
      Loader entry created for 'PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,55-7E-62-44-68-B7-26-00)\HD(2,GPT,E2A442FB-9313-4522-AD87-63BD30A5D527,0x64028,0x1D0BB7D8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,9E3BDD7A1D900E44A91AE3BCB619F3E4)\macOS Install Data\Locked Files\Boot Files\boot.efi'
      Menu entry added at index 4

So maybe something has to do with permissions?

 

here is the new log, with disabled FileVault.

 

I did not install it, waiting for some more testing.

 

2021-3-27_11-52_CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief_fv_disabled.log

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

@kushwavez Ah, well done. Yes, I guess I'll have to do exactly what I though : if the volume can't be opened, do not try to detect "dead installer". 

It's not a permission problem. Clover will never be able to open encrypted volume.

11 minutes ago, matxpa said:

 

In this commit I made some change to the settings DellSMBIOSPatch. Do you have a Dell ?

Not a Dell but Laptop : Asus X75VB IvyBridge (MBP11,3) : H76M, I5-3340M, HD4000, GF740M (off), 1600x900, 12GB Hynix DDR3L 12800, SSD 2,5" Crucial MX100 500 Gb with Big Sur 11.2.3 (20D91) and Clover r5131 (4b0ddf4), 

@matxpa If you can do these 2 debug.log, that'll work too...

joined

r5131_4b0ddf4de_20210327_BOOTX64.efi.log 72.38 kB · 1 download r5131_4b0ddf4de_20210327_preboot.log 58.43 kB · 1 download r5131_65f8cc122_20210327_BOOTX64.EFI.log 75.24 kB · 1 download r5131_65f8cc122_20210327_preboot.log 62.49 kB · 1 download

Arg, no significative difference...

Thinking...

Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted (edited)

just curiosity: If it can't access the dir because it's encrypted, then how can Clover see and add the entry?  (before the dead checking)

I suppose the checking isn't working because it's trying to "ls" the dir? But the entry adding is just Clover checking if the boot file (or route for the file) even exists, if yes, add the entry? hmmm. looks like the two is the same thing. idk, can't explain it well

I'm just curious about the detecting method :) 

Edited by kushwavez
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

@kushwavez Could you try this efi (not committed yet). Should solve the dead installer problem : CloverX64-2021-03-27-16-28-19-4a3bc61-dirty-jief.zip

 

The thing is that the boot file (boot.ef) is on Preboot partition but the dmgfile that contains a minimal system (BaseSystem.dmg) is on the data partition. Preboot is never encrypted.

After an installation, install files (\macOS Install Data\) is cleaned. Sometimes, the one on preboot is not. That's why I introduced this check, completely forgetting about FileVault (although I use FileVault with Clover since years now)...

Link to comment
Share on other sites
eng_redaesm
eng_redaesm
Posted
Posted (edited)
12 minutes ago, Jief_Machak said:

@eng_redaesm and confirm that this efi boots : CloverX64-2021-03-25-00-19-01-4b0ddf4-jief.zip No nned for debug.log.

@Jief_Machak confirmed booting 

and here is my config just removed serial 

# and for your info same behaviour on my 1st and 2nd build my 3rd build not tested  "these debugs and config for my 1st build "

config.plist

Edited by eng_redaesm
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

In fact, it doesn't prove anything because both the last file I've sent are commit 4b0ddf4de.

What verifies it is the build id in the "about clover". You can't know once booted to mac.

 

True, I didn't realize that the highlighted line in my screenshot is NOT the one of interest...

Link to comment
Share on other sites
matxpa
matxpa
Posted
Posted
53 minutes ago, Jief_Machak said:

And this one : CloverX64-2021-03-27-18-52-43-4b0ddf4-dirty-jief.zip

I don't need debug.log, but please be 100% (or even 200%) sure you boot the right efi I've sent you.

It's easy in "About Clover" :283483813_Screenshot2021-03-27at18_54_33.thumb.png.60aa6e2738171eb9f72a1affebc0463e.png
Menu will be in text mode. Don't worry, the bug has been already fixed in later commits.

 

i can't boot with CloverX64-2021-03-27-18-52-43-4b0ddf4-dirty-jief.efir5131_4b0ddf4-dirty-jief_20210327-1627_BOOTX64.EFI.log

 

"r5131_4b0ddf4-dirty-jief_20210327-1627_preboot"

 

MemLog inited, TSC freq: 2693880842
CPU was calibrated with ACPI PM Timer
CloverX64 : Image base = 0xC798C000
Self DevicePath()=PciRoot(0x0)\Pci(0x1D,0x0)\USB(0x1,0x0)\USB(0x1,0x0)\HD(1,GPT,E29C42F6-A5B3-40F9-B74C-89E70AF0807E,0x28,0x64000) @C8363318
SelfDirPath = \EFI\CLOVER

Now is 27.03.2021,  16:27:41 (GMT)
Starting Clover revision: 5131 (master, commit 4b0ddf4de) on American Megatrends EFI
Build id: 2021-03-27-18-52-43-4b0ddf4-dirty-jief
Build with: [jief]
SimpleTextEx Status=Success
=== [ GetDefaultSettings ] ======================
...

r5131_4b0ddf4-dirty-jief_20210327-1627_preboot.log

Link to comment
Share on other sites
matxpa
matxpa
Posted
Posted
1 minute ago, Jief_Machak said:

CloverX64-2021-03-27-20-05-17-4b0ddf4-dirty-jief.zipThis one ?

@matxpa That's very strange. Letme finish with @eng_redaesm if he's still available and we'll see.

 

With CloverX64-2021-03-27-18-52-43-4b0ddf4-dirty-jief.zip

 

"boot.log"

 

Starting Clover revision: 5131 (master, commit 4b0ddf4de) on American Megatrends EFI
Build id: 2021-03-27-18-52-43-4b0ddf4-dirty-jief
Build with: [jief]
 

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...