Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
On 3/26/2021 at 1:07 AM, kushwavez said:

Unfortuantely I'm facing another issue right now. 

I'm trying to install a Catalina 10.15.7 supplemental patch with Clover v5131 (commit sha in log name), but I can't see the Installer entry, therefore I can't boot from it. It isn't there even with "Show hidden entries".

Same with Clover v5130

 

 

 

It's okay with Clover v5128 (can't test v5129 because I can't find the .efi):

 

I was updating Mojave with 5131. Click on Update and see what is happen without touching mouse or keyboard.

First reboot: I see an Installer in the Clover menu. It started.

Second reboot: no the Installer. Clover started from regular OS preboot.

Some more reboots, don't know exactly how many.

Voila, I see new system not touching mouse or keyboard during the whole update process.

  • Like 2
Jief_Machak
Jief_Machak
Posted
Posted (edited)
1 hour ago, eng_redaesm said:

@Jief_Machak  until this commit 4b0ddf4de (5131)it was booting without any problem 

Ok I'll have a look in few minutes.

@eng_redaesm Just to be sure. 4b0ddf4deed019913c1989e192113148139c320a works, 65f8cc122d6cd5db4007218b66b72532382cc28c doesn't. Am I correct ?

Could you send me both the debug.log from these 2 commits.

 

10 minutes ago, Slice said:

So you told about QEMU boot?

Told who ? eng_redaesm ?

Edited by Jief_Machak
matxpa
matxpa
Posted
Posted
1 hour ago, eng_redaesm said:

@Jief_Machak  until this commit 4b0ddf4de (5131)it was booting without any problem 

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

  • Sad 1
kushwavez
kushwavez
Posted
Posted (edited)
5 hours ago, Jief_Machak said:

@kushwavez try this efi : CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief.zipand send me the log.

alright, here you are. 

 

And I think I know what is the problem (correct me if my hypothesis is wrong).

In the log I see this:  

Volume= Preboot
Open "" = Success
Open "\" = Success
Open "\macOS Install Data" = Not Found
Open "\macOS Install Data\Locked Files" = Not Found
Open "\macOS Install Data\Locked Files\BaseSystem.dmg" = Not Found

So that location is wrong for Catalina. On Cata, the Installer is located in /System/Volumes/Data/macOS\ Install\ Data/Locked\ Files/BaseSystem.dmg

 

It is working for you @Slice because on Mojave, there is no separate Container for System and Data, but there is on Cata, so for you the Installer is located in the "right" place (I suppose) (/macOS\ Install\ Data/) and Clover detects it.

 

EDIT: nvm, I was wrong about that :) 

2021-3-27_8-54_CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief.efi.log

Edited by kushwavez
Jief_Machak
Jief_Machak
Posted
Posted

@kushwavez : the path is correct. /System/Volumes/Data is added by macos. It's the mount point. There is no mount point under Clover.

From this :  

- [07]: 'macOS SSD - adatok'
    ApfsContainerUUID=5EF86F43-A55C-4384-B7DF-E35BB7E5CD9F
    ApfsFileSystemUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4
Volume= macOS SSD - adatok
Open "" = Not Found
Open "\" = Not Found

It seems clear that Clover can't read at all your data partition. I'm installing Catalina and will check if it's a normal behaviour.

I'll let you know if I need a test.

Should be done by today.

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

 


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

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
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
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) ?

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

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

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

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
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)...

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