jsl2000

15 minutes ago, fabiosun said:

not all my EFI

it is for a 32 cores set 🙂

take only part of it like drivers and boot folder /clover64.efi

 

Yes, I know.

Unfortunately I got the same problem as my original EFI.

Unable to boot any MacOS from 10.13.6 to 12.1 by Clover 5142 or 5141 now !

5 minutes ago, fabiosun said:

 

 

however with 5142 dock animations have a double speed

Wifi/bt card disconnect often

GPU performances are horrible

I am not using Clover because it is unuseful also to open an ISSUE in their GitHub 

for them all is working always and problem is only due users errors 🙂

I use Clover only to test something..but latest version is a pain

Thanks and I'll test your EFI in my Ryzen 1700X hackintoshs.

9 minutes ago, fabiosun said:

 

try always to reset Nvram, overall if you use sometime also openCore

Clover 5142 is problematic also here

but sometimes works (after resetting Nvram)

try to download my EFI from my TRX40 OP and use only driver EFi and bootX64.efi , cloverX64.EFi and main kexts I use

 

Thanks and may I know where is your TRX40 OP located because I can not find it here by search ?

17 minutes ago, fabiosun said:

to revert to 5141 is an option for you?

or now same problem also?

 

Revert to Clover 5141 got the same problem.

Revert to old BIOS no vain too.

Can you share your working Clover EFI for me ?

1 minute ago, fabiosun said:

Ok I think problem is OSX 12.1

have you tried to boot with 12.01?

in my case with clover I need to reset Nvram a couple of time to have success booting in 12.1

12.01 is fine

if you can try to reset nvram

 

from your log patches are loaded as it should be

 

I think Clover dev have to implement better latest OpenCore features

I can not boot any MacOS from 10.13.6 to 12.1 with Clover 5142 now even after repeated reset Nvram ! Any other possibility for this issue ?

26 minutes ago, fabiosun said:

could you post a debug log?

activate it in boot section of your config and post it

you can find it in your clover/Misc folder

thank you

 

Thanks for your prompt reply and advice.

preboot.log.zip

2021-12-11_10-23_BOOTX64.EFI.log.zip

Before BIOS update I can boot Clover 5141 and OpenCore 0.7.5/0.7.6 successfully without any issue.

However after BIOS update I can boot OC only, if booted by Clover 5142 it always got reboot after ++++++++++++++.

I have tried to downgrade of BIOS or Clover all in vain.

Can anyone check my Clover's config.plist or EFI.zip and give me some help ?

config.plist.zip

EFI.zip

10 minutes ago, fabiosun said:

@jsl2000you mean you have used these attached patches and add on it CPU topology patch and Shaneee fix pat (because I have not inserted it)

Thanks again !

After addition of Shaneee fix pat patch it works now for both Big Sur and Monterey !

config.plist.zip

1 hour ago, fabiosun said:

for problem on old (and bad one for patches imho) config.plist...try to enable Dummypowermanagement quirk

I attached also here my working kernel patches for BS 11.6.1 and MR beta 10

 

clover patches.plist.zip 1.88 kB · 1 download

 

maybe you have to add here only topology patch and Fix pat you use

Thanks for your kind and prompt reply and help.

Unfortunately this config.plist can boot both Big Sur and Monterey past +++++++++++++, but unable to login desktop successfully.

I need figure out how to fix it or using my old config.plist temporarily because I can boot Ryzen and FX-6300 with old patches by OpenCore and Clover. The only disvantage is ProvideCurrentCpuInfo must be disabled to avoid red screen panic during booting.

On 7/31/2021 at 12:43 PM, fabiosun said:

also about this

if you read well

only few users need of this patch.

newer one has a problem with clover masking system , and you can also see in AMD OSX Github why they left Clover without an official patches support..

Then is it possible to have it working well..and we have this from months

 

Hi, fabiosun:

I need your help to fix my Ryzen 1700X's Clover 5140.1 config.plist which can boot 10.13.6/10.14.6/10.15.7/12.0beta9, but always got freeze after +++++++++++++ for Big Sur 11.5.2 or 11.6.1.

Using old config-working-Ryzen-5138.plist which can boot Big Sur, but always got hang after running for 1~2 minutes.

No such an issue by OpenCore 0.7.2 or 0.7.4 with similar kernel patches.

config.plist.zip config-working-Ryzen-5138.plist.zip

1 hour ago, fabiosun said:

I see an error in your config-OC-FX6300.plist:

 

 

if you see this:

FIND: c1 e8 1a 00 00 00
MASK : FF FD FF 00 00 00
BASE:  _cpuid_set_info          
COUNT: 1
REPLACE high sierra to mojave:  b8 XX 00 00 00 00               
REPLACE from catalina to big sur :  ba XX 00 00 00 00                  
REPLACE MASK high sierra to big sur : FF FF FF FF FF 00 
REPLACE monterey : ba XX 00 00 00 90                 
REPLACE MASK monterey : FF FF FF FF FF FF

REPLACE high sierra to mojave:  b8 XX 00 00 00 00               
REPLACE from catalina to big sur :  ba XX 00 00 00 00   

 

for macOS HighSierra, Mojave, Catalina, BigSur 0090 should be 0000

 

in this way OCValidate passes with 0 error masking section

 

Thanks for your correction and I had similar error for Replace High Sierra to Mojave in Clover's config.plist too.

43 minutes ago, fabiosun said:

@jsl2000

thank you so much for the tests you are doing and sharing with the forum

I compiled the latest version of opencore taken from the official github and added the two useful patches for my operating systems (Big Sur 11.4, 11.5 and Monterey 12.b3

The patch for big sur works perfectly even if it does not pass the verification with OC Validate

Tried the same thing with the High Sierra and Mojave patch too

They do not pass the OC Validate validation, but then they work perfectly, allowing you to eliminate many of the patches related to the core logical processor and the core count.

By the way, I allow myself to ask you very humbly, how come you still use all those patches if you use the new ones (0,1)?

Thanks and I can confirm OC PR 0.7.2 working at Monterey beta3 without these 3 patches in my Ryzen 1700X hackintoshs.

The reason I still kept many extra patches because I am a conservative person and try to keep compatibilities between FX-6300 and Ryzen 1700X hackintoshs from High Sierra to Monterey.

It seems FX-6300 lost support from OC team since Monterey beta1.

I can boot it at FX-6300 because I use previous working patches from High Sierra to Big Sur plus newer one at Ryzen 1700X.

Without these experience and basic info I can not boot both now.

Special thanks for your help and many excellent explanation and advice from here.

In the past I can get support from insanelymac mainly and Shaneee's website sometimes.

But recent 2~3 weeks your website provide the newest and excellent info and support as well as prompt reply which I could not find in any other websites.

Thanks again and again you are the most wonderful person in this forum !

35 minutes ago, fabiosun said:

@jsl2000old ones work for you (with FX cpu I mean)?

 

No, in order to boot Monterey beta2 & 3 I apply newer 3 patches in both Clover 5138 and OC 0.7.1 config.plist and it worked well up to now.

35 minutes ago, fabiosun said:

@jsl2000

old one:

patch 0 that algrey posted on Insanely Mac is made for my processor in this example
it is very easy to recreate it for other types of cpu (search on this forum new patch, below is the old one😞
 
PatchProvideCurrentCpuInfo set cpuid_cores_per_package
f:4489EAC1 EA1A
r:BA1F0000 0090
PAY ATTENTION
Value 1F means 31, 3970 x has 32 cores so as stated by @algrey on IM
32 -1=31=1F
IE for a 8 cores  CPU :
8-1=7=07
for 3950x or 5950x 16:
16-1=15=0F
and so on

 

newer (not latest because it is not public for now...but a good one)

FIND: c1 e8 1a 00 00 00
MASK : FF FD FF 00 00 00
BASE:  _cpuid_set_info          
COUNT: 1
REPLACE high sierra to mojave:  b8 XX 00 00 00 00               
REPLACE from catalina to big sur :  ba XX 00 00 00 00                  
REPLACE MASK high sierra to big sur : FF FF FF FF FF 00 
REPLACE monterey : ba XX 00 00 00 90                 
REPLACE MASK monterey : FF FF FF FF FF FF

 

Thanks and that means if I apply the newer patches my current issue will bother me again by ocvalidate warning or interference.

Hope in the near future the developer team of OC or Clover release better solution for FX-6xxx/8xxxx users.

2 minutes ago, fabiosun said:

OC PR Patches.plist.zip 1.78 kB · 0 downloads

to explain better (I hope in a better way I mean)

attached here patches I use withOpenCore PR 072

No, only in 072 PR Patches 0,1,2 are included in that quirk

 

Thanks for your explanation which is the great news for all AMD CPU users.

In case of FX-6xxx which can not enable ProvideCurrentCpuInfo Quirk do you have any other solution ?

Just now, fabiosun said:

@jsl2000OC PR does not need of any of them...they are included in OpenCore

Do you mean by OC 0.7.1 or 0.7.2 if ProvideCurrentCpuInfo was enabled I don't need patch 0,1, & 2 ?

Or just no need patch 1 & 2 ?

17 hours ago, fabiosun said:

@jsl2000

Lightening the number of patches in the config.plist, leaving only those that are really useful for the systems you have installed,

certainly does not solve your "cosmetic" problem on the CPU name ..

but it helps, maybe, to better understand any others problems

imho you should do this with both clover and OpenCore

I need your help and advice to fix one problem I faced OpenCore 0.7.1 or OC PR 0.7.2:

These two versions' ocvalidate always warn me about ReplaceMask of patch 1 & 2 which I need to boot kernel 17.0.0 to 20.x.x

unless I changed from FFFFFFFFFF00 to FFFFFFFFFFFF it can not passed.

In fact after change it can pass ocvalidate, but always failed to boot High Sierra to Big Sur now.

Do you have any solution to fix it ?

In Clover I had the same issue too.

On 7/25/2021 at 5:18 AM, cupecups said:

hi Jsl2000, can you help me about amd fx? I try to boot monterey beta 3 this success but, my cpu frequency is wrong over 200mhz, I’m using amd fx 8150

 

thanks

For Clover you need set CPU parameters as the attached one:

For OpenCore you should set DataHub as mine:

[Edit] Some errors of patches for Replace in both config.plists were corrected.

config-Clover-FX6300.plist.zip config-OC-FX6300.plist.zip

1 hour ago, fabiosun said:

@jsl2000

if you use this quirk as I see in your config:

 

ProvideCurrentCpuInfo

 

you can disable these 2 patches:

 

 

then if you have how I see first two patches you can try to disable all patches you see with core logical string in comment section...

 

if you use also clover you can test easily with it this my latter assertion

Yes, your theory and instruction are correct.

Enabled ProvideCurrentCpuInfo Quirk can disable many patches related to core logical string, but my About this Mac issue still bother me up to now.

Only Clover booting can fix it from Catalina to Monterey beta3 and the same issue occured at High Sierra and Mojave too!

[Edit]

No such an issue in FX-6300 hackintoshs from Catalina to Monterey beta3 booted by Clover or OpenCore.

Unfortunately if ProvideCurrentCpuInfo was enabled my Fx-6300 hackintoshs will got red screen KP on booting Legacy OC.

2 hours ago, fabiosun said:

@jsl2000

 

 

this (maybe) is not useful, it is old version and in position 0 you have newone

 

Thanks for your prompt reply and advice.

Set Number from 3841 to 0 did not fix this issue.

Disable this unused patch (3) was also in vain to fix it.

So I left it over and wait for other solution because it's harmless for this cosmetic issue.

1 hour ago, fabiosun said:

@jsl2000yes with restrict events.kext

Can you check my config.plist of OpenCore 0.7.1 in which related to ProcessorType is correct or not ?

Number-->3841 ? This is the last step in which I need to improve now.

Enabled ProvideCurrentCpuInfo can not fix this issue.

Before OC PR 0.7.2 is it correctly shown in your hackintoshs ?

config.plist.zip

17 hours ago, fabiosun said:

thank you @jsl2000I see your post in IM forum.

I would like only to specify that patches are not mine 🙂

I have only understood the joke done by maintainer..:)

if you read on their readme they stated patches are good for beta 1...

then Algrey posted force cpu patch and also they did a PR with a newer one...

I think they would like to see how smart are their patches users 😉

 

Can you get correct CPU name in About This Mac by OpenCore PR ?

Mine OC 0.7.1 always show Ryzen 1700X 8-Core as 8-Core Intel Xeon W instead.

On 7/22/2021 at 7:45 PM, fabiosun said:

@tuxybefore I was in a rush..so I will explain better

 

public patches on AMD allow to boot till beta 3 if you have followed well also a not included patch you can find here or on insanely Mac :

Force set cpuid_cores_per_package

 

with this patch you can disable many other patches (broken for b2 and b3)

 

so a conditional yes is a better answer to your question. 🙂

 

this patch is instead the one changed from previous beta 1 and available on AMD OSX Github:

 

algrey _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN

 

 

 

 

Thanks for your hint which help me to boot Ryzen 1700X smoothly by Clover 5138 now:

[Edit] Besides RestrivtEvents.kext add CPU->Type->String->0x0f01 Clover can show correct name of Ryzen 1700X now !

But no such a lucky by OpenCore 0.7.1 even Number -> 3841 (which=0x0f01 hex) was added in PlatformInfo -> Generic ->ProcessorType

P

On 7/18/2021 at 4:53 PM, fabiosun said:

With the publication of the updated kernel patches, now available for everyone,

it is possible to clean up the thread, also thanks to the patch present in the PR published by Shaneee in the Opencore github, also applicable to Clover.

 

So I'll clean up some of my posts by referencing this post (UPDATED 18-07-2021)

 

AMD OSX Patches

 

Shaneee Pull Request

 

I provide quirks and patches useful for my system (and as regards the kernel patches also for different platforms such as x570, x370 and some FX AMD user)

if you want or need to try your system with clover bootloader in OSX like Big Sur or Monterey Beta (1,2,3)

For the moment I close here my experience with Clover bootloader, resuming it later if there will be any news!

 

Clover-Kernel_Patches_Quirks.plist.zip 2.57 kB · 6 downloads

Thanks for your help and advice which make my dream come true in FX-6300 hackintoshs now.

It can boot and update up to Monterey beta3 with OpenCore and Clover 5137.

The next step will be reduction of my patches to minimal working setup from 10.13.6 to 12.0 beta3.

27 minutes ago, fabiosun said:

No need of it if you use PR EFI edition

it is included in quirk you use👍

I mean you don’t need of those 3 patches

core count is inside provide cpu info quirk

Thanks.

So even RestrictEvents.kext can be disabled  ?