Jump to content

[AMD] Clover Bootloader Monterey Beta (1 ,2,3) installation patches!!


Recommended Posts

  • Supervisor

@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

  • Like 1
Link to post
Share on other sites
10 hours ago, jsl2000 said:

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.

 

Screen Shot 2021-07-24 at 6.56.40 PM.png

Screen Shot 2021-07-24 at 7.01.19 PM.png


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

IMG_8576.PNG

Link to post
Share on other sites
4 hours ago, 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

IMG_8576.PNG

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

For OpenCore you should set DataHub as mine:

Screen Shot 2021-07-25 at 8.46.44 AM.png

Screen Shot 2021-07-25 at 8.41.19 AM.png

config-OC-FX6300.plist.zip

config-Clover-FX6300.plist.zip

Edited by jsl2000
  • Like 1
Link to post
Share on other sites
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.

Screen Shot 2021-07-25 at 2.31.48 PM.png

Edited by jsl2000
Link to post
Share on other sites
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 ?

Link to post
Share on other sites
  • Supervisor

OC PR Patches.plist.zip

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

attached here patches I use withOpenCore PR 072

1 minute ago, jsl2000 said:

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 ?

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

 

  • Like 1
Link to post
Share on other sites
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 ?

Link to post
Share on other sites
  • Supervisor

yes..

you can try to use old patch for it

or try to verify better the schema proposed here (I will find for you if you do not find it)

 

two kind of patches were proposed from the start

one

core number -1 (count 0 and other stuff)

two

a more articulated ones with mask  and replace masking (count 1)

 

remember..if they have not published in a clear way..a reason could be there 😉

 

  • Like 1
Link to post
Share on other sites
  • Supervisor

@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

 

  • Like 1
  • +1 1
Link to post
Share on other sites
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.

Link to post
Share on other sites
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.

  • +1 1
Link to post
Share on other sites
  • Supervisor

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

  • Like 1
  • +1 1
Link to post
Share on other sites
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 !

Edited by jsl2000
  • Like 1
  • Thanks 2
  • +1 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.