Jump to content
30960 posts in this topic

Recommended Posts

43 minutes ago, kushwavez said:

I also see a lot's of SSDT/DSDT errors in your picture (AE_ALREADY_EXISTS, AE_NOT_FOUND), you may need to recreate the SSDT or DSDT and fix these errors. 

 

Also try to exclude them and see what happens (except SSDT-EC)

I never had these errors on Catalina and before and I am using the same Clover to boot. I don’t know what’s the meaning of these errors

I had to download the full installer to get beta 6 and that was before clover 5139 but clover 5139 is working great on both Intel and AMD with beta 6 on both machines.


Sent from my iPhone using Tapatalk

  • Like 4
4 minutes ago, 5T33Z0 said:

For validating the config.plist, should we still use the CloverConfigPlistValidator included in r5134?

 

@5T33Z0 The CloverConfigPlistValidator is included in each CloverPackage. So in the r5139 package too.

6 minutes ago, Matgen84 said:

 

@5T33Z0 The CloverConfigPlistValidator is included in each CloverPackage. So in the r5139 package too.

 

My primary bootloader is OpenCore, so I don't use the .pkg. I use the .zip and update the Clover EFI manually. It has been for this for a year or so. The config validator is not included in the .zip file nor in the Assets of the current release. As of now, I just extracted the contents of the .pkg using the unpkg app. But imo it should be included in the zip as well as a utility.

On 9/5/2021 at 2:56 PM, 5T33Z0 said:

 

My primary bootloader is OpenCore, so I don't use the .pkg. I use the .zip and update the Clover EFI manually. It has been for this for a year or so. The config validator is not included in the .zip file nor in the Assets of the current release. As of now, I just extracted the contents of the .pkg using the unpkg app. But imo it should be included in the zip as well as a utility.

Sorry, I will upload ccpv in each Release.

  • Like 4
6 minutes ago, SavageAUS said:

Thank you!

 

please fix Clover config.plist ???

Edited by Qwels
Thank you!
 
please fix Clover config.plist ???

Use clover config plist validator.
Does your machine boot?
Is the error about memory the only issue?
What’s wrong with config.plist?


Sent from my iPhone using Tapatalk
12 hours ago, Qwels said:

I don't use the configurator.

Download Clover 5136

Config iMacPro1,1 — Great.

Config MP7,1 — donload 

- yes  error about memory the only.

i wanted someone to look from Guru and fix it.

i used to use hamelon before. I thought I'd try the layout BigSur and Monterey

10.14.6 - no error

10.15.7 - error

please refer - OpenCore.pkg - installer

i'll try and see if he can do it

 

@Qwels When I migrate my IvyBridge config from Mojave to Catalina, I had to add an SDDT-EC to boot macOS

I am trying to use the new RealtekCardReader.kext but, I am told, my hardware (RTL8411B) has problems initializing SD cards that other pci-e SD card readers do not have.  So I have been playing with the idea of using a Fake PCI-ID, which Clover already implements for many devices but not SD Card Readers.  Is there a way for me to do this with my card reader in Clover?  I know that the RTS525A works well with this kext and want to spoof my info (0x8752EC10) with the info for the RTS525A (0x5A52EC10).

Edited by mnfesq
I am trying to use the new RealtekCardReader.kext but, I am told, my hardware (RTL8411B) has problems initializing SD cards that other pci-e SD card readers do not have.  So I have been playing with the idea of using a Fake PCI, which Clover already implements for many devices but not SD Card Readers.  Is there a way for me to do this with my card reader in Clover?  I know that the RTS525A works well with this kext and want to spoof my info (0x8752EC10) with the info for the RTS525A (0x5A52EC10).

I believe the dev is aware of this issue and is working on it for our readers.


Sent from my iPhone using Tapatalk

@SavageAUS If I can find a workaround by spoofing the PCI-ID, that would be in the spirit of our OSx86 community to all pitch in to find solutions rather than leaving it all to a small number of developers. And if it doesn't work, well, at least I tried.

  • Like 1

In the commit f424a77c25027e4a5395fdb57287affae51f4ac5 the settings CPU/Latency became ignored, but the settings remains. It means you get no warning if you use this settings, misleading you that it was taken into account.

Should we remove the settings CPU/Latency ?

 

PS : the settings used instead is ACPI/SSDT/C3Latency

  • Like 2
  • Thanks 1
8 hours ago, Jief_Machak said:

In the commit f424a77c25027e4a5395fdb57287affae51f4ac5 the settings CPU/Latency became ignored, but the settings remains. It means you get no warning if you use this settings, misleading you that it was taken into account.

Should we remove the settings CPU/Latency ?

 

PS : the settings used instead is ACPI/SSDT/C3Latency

Yes,  CPU/Latency should be removed. It was for the same purpose as ACPI/SSDT/C3Latency. The parameter used for generation of C-states SSDT tables for CPUPM. Softening or sharpening C-states transition.

  • Like 2
On 9/8/2021 at 2:21 PM, Slice said:

1. Take latest Clover 5139.

2. Use OpenRuntime.efi instead of AptioMemoryFix

3. Make preboot.log by pressing F2 and upload it here.

it's not loading ,there's a screenshot upstairs Linia 1164

 

 

×
×
  • Create New...