Clover General discussion

[yapan4]

4 hours ago, naiclub said:

Your problem is most likely caused by the video card is not compatible or not.

@naiclub  

Some users also point to the video card, I think something is wrong with NVRAM ... the right decisions may be in a completely different place ... well, it's a hackintosh

Thank you  for your effort.

[jlrycm]

5 hours ago, naiclub said:

Your problem is most likely caused by the video card is not compatible or not.

 

You need to correct it on your own or have @ MaLd0n .. do it. Which is beyond my capabilities

edit..Which works like my air port Add it by yourself Because it is an external card

I fake the code myself, for example "pci168c, 2b" I fake it as "pci168c, 2a" works with external kext.

  Hide contents

 

Hello @naiclub. I hear you. @MaLd0n also helped me doing something similar for my wifi card to work in Big Sur, but for OpenCore. I already posted a request for him to take a look at it but he hasn’t worked yet on it.

[PG7]

3 hours ago, kushwavez said:

I just tried itlwm with an Intel AC-7260 to see if it's improved or not, it's good for light browsing, but nothing else really at this state. I barely hit 7 MB/s speed on 5 GHz, that normally would be like ~80 MB/s.

 

I also had some very annoying bug when using it with OpenCore, after booting to Windows the wifi cannot be launched and used (error code: 10). Even a CMOS reset couldn't help! The only way to get it working again was to boot with Clover (or delete OC and boot with Windows loader)...strange! I opened a bug report but they said it's a problem with OC.

Well, nice work anyway, not gonna lie.  

Spoiler

 

no comment !

[kushwavez]

@PG7 Yep, sounds about right. Unfortunately as I can see it's only connecting at 20Mhz mode on 5 GHz too, so that's why it's so slow. I hope they'll improve this soon. 

[PG7]

52 minutes ago, jlrycm said:

Which works like my air port Add it by yourself Because it is an external card

I fake the code myself, for example "pci168c, 2b" I fake it as "pci168c, 2a" works with external kext.

 

 

Boa Noite 

 

 

you simulate the 2B in 2A ??? so the original kext already has the 2A inserted .... can you better show your patch for me to understand or are you using the basic Atheros do Repo patch?

 

Patch repo rehabman :

into method label _DSM parent_label PXSX remove_entry;
into device label PXSX parent_label RP02 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
    Return (Package()\n
    {\n
        "device-id", Buffer() { 0x30, 0x00, 0x00, 0x00 },\n
        "name", "pci168c,30",\n
        "AAPL,slot-name", Buffer() { "AirPort" },\n
        "device_type", Buffer() { "AirPort" },\n
        "model", Buffer() { "Atheros 9285 802.11 b/g/n Wireless Network Adapter" },\n
        "subsystem-id", Buffer() { 0x8F, 0x00, 0x00, 0x00 },\n
        "subsystem-vendor-id", Buffer() { 0x6B, 0x10, 0x00, 0x00 },\n
    })\n
}\n
end;

 

[naiclub]

Do you ask me Or you ask someone else

[Jief_Machak]

@everyone : debug.log name has changed. It's now a timestamp followed by the name of the efi file.

[naiclub]

57 minutes ago, mifjpn said:

Slice, Jeif, Chirs
Thank you for always doing the hard development work.

I apologize to had be using my exaggerating "ethics".

I don't want to lost your morale.

Therefore, my tiny ethics can be disregarded.

You have the skills and morale, you can beat me easiry.

And I'm really sick. It's depression. I actually take dozens of anxiolytics.

I say the truth. I'm afraid that someone is scared here,and can not talk here.

I can understand PG7 said, thus,it's not a good idea for anyone to eliminate developers time.
Therefore if someone can not codeing source,they must be not talk.

So I apologize that I had demoralize you.

I want to eliminate all that can interfere with your time.

I would especially like to thank Chris and Jief and Slice for their moderation.

Thank you.
And I'm sorry.

I hope that many voices will come together and that Clover will be great.

I think you are too nervous or not. Don't think too much The blood vessels in the brain will be broken.

[iCanaro]

34 minutes ago, Jief_Machak said:

@everyone : debug.log name has changed. It's now a timestamp followed by the name of the efi file.

 

always inside misc folder?!

[Jief_Machak]

1 minute ago, iCanaro said:

 

always inside misc folder?!

yes

[iCanaro]

great idea what at each startup corresponds a log with the date and time

[SavageAUS]

Hi all. 
I’m not sure which commit I’m using but I’m using clover 5126 on both my machines and recently I’m getting very slow boot. On my intel laptop the first “stall” happens here

 

Spoiler

then I get a few of these

 

Spoiler

 

but it’s a long process but eventually boots but cpu usage is maxed out. Running Big Sur 11.1 beta. I can upload my EFI if needed. 

 

Spoiler

 

[PG7]

10 minutes ago, SavageAUS said:

but it’s a long process but eventually boots but cpu usage is maxed out. Running Big Sur 11.1 beta. I can upload my EFI if needed. 

 

 

put your EFI to try to understand

[kushwavez]

@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 November 24, 2020 by kushwavez

[Jief_Machak]

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.

[kushwavez]

@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

 

debug_v5126_fvault_woutimagecodec.log

Edited November 24, 2020 by kushwavez

[Jief_Machak]

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 November 24, 2020 by Jief_Machak

[iCanaro]

I confirm; I don't use DataHubDxe.efi in any hacks

[kushwavez]

@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 November 24, 2020 by kushwavez

[mnfesq]

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 November 24, 2020 by mnfesq

[iCanaro]

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

[Jief_Machak]

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.

[Slice]

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.

[Jief_Machak]

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 ?

[kushwavez]

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 November 25, 2020 by kushwavez