Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

@Jief_Machak Quite while ago I posted something about FileVault not working. So I was wrong, it's working, but. 

Now I've had some time and tested again with an encrypted Big Sur drive, it boots to the password input screen but just after an enormously long wait time (2 min). And it's just to the password input, after that the system needs to boot to the desktop. Looking at the debug.log I see these lines, something is happening but I don't know why it is waiting for so long:

...
13:161  0:010  OC: Opening file System with 1 mode gave - Success
13:162  0:001  OC: Opening file Library with 1 mode gave - Success
13:163  0:000  OC: Opening file Caches with 1 mode gave - Success
13:164  0:001  OC: Opening file com.apple.corestorage with 1 mode gave - Success
13:165  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
13:166  0:001  OC: Opening file loginui.efires with 1 mode gave - Success
142:608  129:442  OC: Opening file System with 1 mode gave - Success
142:610  0:001  OC: Opening file Library with 1 mode gave - Success
142:611  0:001  OC: Opening file Caches with 1 mode gave - Success
142:612  0:000  OC: Opening file com.apple.corestorage with 1 mode gave - Success
142:613  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
142:614  0:000  OC: Opening file Lucida13White.efires with 1 mode gave - Success
142:954  0:340  OC: Opening file System with 1 mode gave - Success
142:955  0:001  OC: Opening file Library with 1 mode gave - Success
142:956  0:001  OC: Opening file Caches with 1 mode gave - Success
142:958  0:001  OC: Opening file com.apple.corestorage with 1 mode gave - Success
142:958  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
142:959  0:001  OC: Opening file flag_picker.efires with 1 mode gave - Success
143:141  0:181  OC: Opening file System with 1 mode gave - Success
143:142  0:000  OC: Opening file Library with 1 mode gave - Success
143:143  0:000  OC: Opening file Caches with 1 mode gave - Success
143:144  0:000  OC: Opening file com.apple.corestorage with 1 mode gave - Success
143:145  0:001  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
143:146  0:001  OC: Opening file battery.efires with 1 mode gave - Success
143:167  0:020  OCSMC: SmcReadValue Key 4242494E Size 1
//Then the login screen appeared
//Input password
//System is booting
...
//Arrived at desktop

As you can see, there is something at line "142:608  129:442  OC: Opening file System with 1 mode gave - Success"

Why is there a huge delay?

drivers are in place from off/UEFI/FileVault

Here, a full debug.log

 

debug_v5126_filevault.log

Edited by kushwavez
Link to comment
Share on other sites

3 hours ago, kushwavez said:

@Jief_Machak Quite while ago I posted something about FileVault not working. So I was wrong, it's working, but. 

Now I've had some time and tested again with an encrypted Big Sur drive, it boots to the password input screen but just after an enormously long wait time (2 min). And it's just to the password input, after that the system needs to boot to the desktop. Looking at the debug.log I see these lines, something is happening but I don't know why it is waiting for so long:


...
13:161  0:010  OC: Opening file System with 1 mode gave - Success
13:162  0:001  OC: Opening file Library with 1 mode gave - Success
13:163  0:000  OC: Opening file Caches with 1 mode gave - Success
13:164  0:001  OC: Opening file com.apple.corestorage with 1 mode gave - Success
13:165  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
13:166  0:001  OC: Opening file loginui.efires with 1 mode gave - Success
142:608  129:442  OC: Opening file System with 1 mode gave - Success
142:610  0:001  OC: Opening file Library with 1 mode gave - Success
142:611  0:001  OC: Opening file Caches with 1 mode gave - Success
142:612  0:000  OC: Opening file com.apple.corestorage with 1 mode gave - Success
142:613  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
142:614  0:000  OC: Opening file Lucida13White.efires with 1 mode gave - Success
142:954  0:340  OC: Opening file System with 1 mode gave - Success
142:955  0:001  OC: Opening file Library with 1 mode gave - Success
142:956  0:001  OC: Opening file Caches with 1 mode gave - Success
142:958  0:001  OC: Opening file com.apple.corestorage with 1 mode gave - Success
142:958  0:000  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
142:959  0:001  OC: Opening file flag_picker.efires with 1 mode gave - Success
143:141  0:181  OC: Opening file System with 1 mode gave - Success
143:142  0:000  OC: Opening file Library with 1 mode gave - Success
143:143  0:000  OC: Opening file Caches with 1 mode gave - Success
143:144  0:000  OC: Opening file com.apple.corestorage with 1 mode gave - Success
143:145  0:001  OC: Opening file EFILoginLocalizations with 1 mode gave - Success
143:146  0:001  OC: Opening file battery.efires with 1 mode gave - Success
143:167  0:020  OCSMC: SmcReadValue Key 4242494E Size 1
//Then the login screen appeared
//Input password
//System is booting
...
//Arrived at desktop

As you can see, there is something at line "142:608  129:442  OC: Opening file System with 1 mode gave - Success"

Why is there a huge delay?

drivers are in place from off/UEFI/FileVault

Here, a full debug.log

 

debug_v5126_filevault.log

Remove AppleImageCodec.efi from your efi drivers.

  • Like 1
Link to comment
Share on other sites

@Jief_Machak thanks I deleted that, but now it won't start at all. debug log says:

...
8:005  0:001  OCOS: Should use black background
8:013  0:007  OC: Opening file System\Library\Kernels\kernel with 1 mode gave - Not Found
8:013  0:000  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42 with 1 mode gave - Success
8:015  0:001  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\com.apple.Boot.plist with 1 mode gave - Not Found
8:117  0:102  OC: Opening file Library\Preferences\SystemConfiguration\com.apple.Boot.plist with 1 mode gave - Success
8:569  0:451  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\PlatformSupport.plist with 1 mode gave - Success
9:108  0:539  OC: Opening file System\Library\Caches\com.apple.corestorage\EncryptedRoot.plist.wipekey with 1 mode gave - Success
10:156  1:048  OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Not Found
10:168  0:011  OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Success
20:754  10:586  OCB: InternalEfiExit 65553218 - Aborted / Unsupported
//Exiting in 10 seconds...

EDIT: photo

Spoiler

1310906855_Nevtelen.thumb.jpg.f520714cac915daacb784cf7e2aabb77.jpg

 

debug_v5126_fvault_woutimagecodec.log

Edited by kushwavez
Link to comment
Share on other sites

12 minutes ago, kushwavez said:

@Jief_Machak thanks I deleted that, but now it won't start at all. debug log says:


...
8:005  0:001  OCOS: Should use black background
8:013  0:007  OC: Opening file System\Library\Kernels\kernel with 1 mode gave - Not Found
8:013  0:000  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42 with 1 mode gave - Success
8:015  0:001  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\com.apple.Boot.plist with 1 mode gave - Not Found
8:117  0:102  OC: Opening file Library\Preferences\SystemConfiguration\com.apple.Boot.plist with 1 mode gave - Success
8:569  0:451  OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\PlatformSupport.plist with 1 mode gave - Success
9:108  0:539  OC: Opening file System\Library\Caches\com.apple.corestorage\EncryptedRoot.plist.wipekey with 1 mode gave - Success
10:156  1:048  OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Not Found
10:168  0:011  OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Success
20:754  10:586  OCB: InternalEfiExit 65553218 - Aborted / Unsupported
//Exiting in 10 seconds...

 

debug_v5126_fvault_woutimagecodec.log

Deleting AppleImageCodec.efi is really the only change you've made ?

Maybe replace ApfsDriverLoader.efi with apfs.efi that you got from BigSur : i've had a lot of problem with that {censored}. It's just an OpenCore bad idea to try to do like Apple. Problem is that it's failing to load to latest version sometimes.

Also, I have "AppleUiSupport.efi". Try to add that maybe.

Not related but DataHubDxe.efi is not needed anymore, I think. Anyone can confirm ?

 

Edited by Jief_Machak
  • Thanks 2
Link to comment
Share on other sites

@Jief_Machak Yes I only deleted that file then tried.

But thanks! Deleting "AppleImageCodec.efi" and adding "AppleUiSupport.efi" fixed my problem, booted in a flash. But I needed to grab this .efi from elsewhere, it's not in the Clover.zip

However now a red Error msg appears before the Clover GUI says: "Error: Device Error returned from AppleKeyAggregator.efi". Doesn't seems to affect anything tho.

And yes, DataHubDxe.efi and FSInject.efi are not needed in my case. They were just there by default and I didn't delete them. 

 

Maybe it's a good idea to replace "AppleImageCodec.efi" with "AppleUiSupport.efi" and move DataHubDxe and FSInject to drivers/off in further releases

[...]
0:106  0:000  === [ LoadDrivers ] =============================
0:107  0:000  Loading AppleUiSupport.efi  status=Success
0:210  0:103  Loading AppleKeyAggregator.efi  status=Success
0:213  0:002  Fatal Error: Device Error returned from AppleKeyAggregator.efi
[...]

EDIT: after more testing seems like there is no need to delete "AppleImageCodec.efi" only need to add "AppleUiSupport.efi" to get it working.

 

debug_fvault_appleuisupport_working.log

Edited by kushwavez
Link to comment
Share on other sites

I'm not sure if this is Clover-related or not but here goes:  When I put my custom DSDT.aml in ACPI/Patched, I get a reboot after selecting the OS to boot from within less than 5 seconds of booting up.  If I take the same custom DSDT.aml and put it in ACPI/origin, the system boots.  Any idea what's going on?  I'm using v5126 - the build that can be downloaded as a release from Slice's GitHub.  It's happening on a Haswell-based system (Zotac ID92) which I have running as a MacMini7,1.

 

Oh, btw, the reason I am using a custom DSDT is that I have instant wake problems and the wake reason is GLAN.

Edited by mnfesq
Link to comment
Share on other sites

put the custom DSDT in origin, it has no logic, it must be patched. If patched it results in a boot restart, it's likely not in place for your setup and needs to be refined.
I fully agree with OC's philosophy of not using DSDT but only SSDTs
From your signature I understand that you have LAN RTL8111, if true, just a few days ago Mieze updated his kext for better operation with big sur

Same thing for Clover, you need to use more recent build builds, if you scroll back the pages in this thread, updated Clover has been attached

  • Thanks 1
Link to comment
Share on other sites

8 hours ago, kushwavez said:

after more testing seems like there is no need to delete "AppleImageCodec.efi" only need to add "AppleUiSupport.efi" to get it working.

The less you have the better. "AppleImageCodec.efi" seems not needed. "Not needed" is enough to say that there is a need for deleting it.

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

AppleUiSupport is a combined driver 

UI drawing.

  • Make sure that you remove all the legacy drivers implemented in the past. The list includes: AppleImageCodec-64.efi, AppleKeyAggregator-64.efi, AppleKeyMapAggregator.efi, AppleEvent.efi, AppleUITheme-64.efi, EnglishDxe-64.efi, FirmwareVolume-64.efi, HashServiceFix-64.efi

Some of them can be loaded separately or we can do as vit9696 and load all as one driver.

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

59 minutes ago, Slice said:

AppleUiSupport is a combined driver 

UI drawing.

  • Make sure that you remove all the legacy drivers implemented in the past. The list includes: AppleImageCodec-64.efi, AppleKeyAggregator-64.efi, AppleKeyMapAggregator.efi, AppleEvent.efi, AppleUITheme-64.efi, EnglishDxe-64.efi, FirmwareVolume-64.efi, HashServiceFix-64.efi

Some of them can be loaded separately or we can do as vit9696 and load all as one driver.

Do we have to sources of AppleUiSupport ?

Link to comment
Share on other sites

Thanks @Slice, @Jief_Machak! You're right, I deleted all of the FileVault drivers, put just AppleUiSupport.efi in and it worked fine.

That's also explains the red error msg, AppleUiSupport simply initialized AppleKeyAggregator first.

 

Also I found a source if it helps: https://github.com/acidanthera/AppleSupportPkg/releases/tag/2.0.9

Edited by kushwavez
  • Like 2
Link to comment
Share on other sites

So after some more testing I figured out my PS2 built-in kb doesn't work with AppleUiSupport.efi (because of the built-in AppleKeyAggregator?), so I can't input my password. If I add the separate AppleKeyAggregator.efi the error msg appears as mentioned above, no PS2 kb. I've had to add your "AppleKeyFeeder.efi" to get it working, now with that it's finally okay.

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

Spoiler

667132710_2563-11-2519_46_47.thumb.png.7a8dc1ee376fc9e3aa9b7ace2ddf780e.png

I can use almost all versions. Stuck at the 2nd version only (Mac_OS_X_Lion_10.7.5-Snowleo) that cannot continue. It could be because looking for kext. Not old version Can anyone advise me? Thank you.

Link to comment
Share on other sites

1 hour ago, SavageAUS said:

Here you go, hopefully someone can see something wrong.

EFI I7-9750H.zip

 

I should see ioreg, but from how the config.plist is set you don't seem to have Power Management
If you have reader in fingerprints, you might try adding NoTouchID.kext
SMCLightSensor are you sure you need it?
Have you tried to use the SSDTs proposed here instead of the DSDT

https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-prebuilt.html#laptop-coffee-and-comet-lake-9th-and-10th-gen

  • Like 1
Link to comment
Share on other sites

Hi @Slice @Jief_Machak

Thanks for Clover r5127 Release, and all the work you do for users :thumbsup_anim:

 

Please, when do you plan to solve the problem of icons and detection of BS Recovery !  Since BS 11.0.1 Release and BS Beta 11.1, the Clover GUI don't show correct icons: os_mac instead of os_bigsur   

  • Like 3
Link to comment
Share on other sites

Working fine on notebook 1, minor thing: Keyboard settings, Display settings are resetted with this update, I had to re-login to iCloud even though I didn't change SMBIOS. At devices it's duplicated, I had two devices with same SMBIOS.

Link to comment
Share on other sites

25 minutes ago, Matgen84 said:

Please, when do you plan to solve the problem of icons

if I understand what you're asking for, you're referring to the double icon in Clover's GUI at boot. Just add name assigned to big sur in
config.plist --> GUI --> Hide Volumes
for example I called it BUG-SUR, added to the hide list and now I only have one entry

GUI-HIDE-BUG-SUR.thumb.png.388d5305092b5

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

×
×
  • Create New...