amd clover vanilla patches [AMD] Clover Vanilla patches

[jsl2000]

On 7/5/2021 at 10:51 PM, fabiosun said:

post your config because some time in monterey it hangs for many seconds with apple and loading bar then it logs

You can try to clear Nvram and also to use weg with some bootarg

you coold also try to boot with boot debug enabled and the post misc/boot txt file 

 

Eventually my Ryzen 1700X can boot Clover 5137 at Monterey without previous issues now. My config.plist attached here:

[Edit]

Your previous config.plists had some typing error such as 10.5 instead of 10.15 which may cause some trouble to boot smoothly.

 

config.plist.zip

Edited July 7, 2021 by jsl2000

[fabiosun]

@jsl2000

thanks for your confirmation
for this reason I requested a debug that can be activated from the Boot section of your config
I don't know if it is clear that we are trying to minimize the number of patches useful for starting in all OSX supported by patches
For example to start with Big Sur and Monterey beta 1 we can only use 11 with Opencore, at the moment 13 with Clover ..
thanks for posting your results. if you read in the Italian forum, you will find a user with a similar platform to yours who posted his quirks to start with a minimal set of patches 🙂
by the way
did you by chance have another user registered on this forum called jsl2020?
in case do you know that by forum's rule it should be eliminated
Thank you

[jsl2000]

1 hour ago, fabiosun said:

@jsl2000

thanks for your confirmation
for this reason I requested a debug that can be activated from the Boot section of your config
I don't know if it is clear that we are trying to minimize the number of patches useful for starting in all OSX supported by patches
For example to start with Big Sur and Monterey beta 1 we can only use 11 with Opencore, at the moment 13 with Clover ..
thanks for posting your results. if you read in the Italian forum, you will find a user with a similar platform to yours who posted his quirks to start with a minimal set of patches 🙂
by the way
did you by chance have another user registered on this forum called jsl2020?
in case do you know that by forum's rule it should be eliminated
Thank you

Yes, it's me too in another website of Shaneee, but not here.

Because my original name jsl2000 can not login there which forced me to use another name for me.

That means I did not use 2 different names in the same forum.

Edited July 7, 2021 by jsl2000

[fabiosun]

Good news for AMD users thanks to @algrey, and as already anticipated by @Shaneee

 it will be possible for everyone to start with a very small set of patches:

on my system now only 10 are needed to start BigSur 11.4, 11.5 beta 4, Monterey 12 b1 ..... and listen listen beta 2 😂

 

 

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

 

Patch # 1 will be released when the editors of the patches will decide to make them public!

 

Thanks again @algrey for his usual availability and skill

[fabiosun]

 

Always thanks @algrey, thanks especially to the mother of all patches, already posted by algrey on IM and here in our thread

Very useful to further reduce the number of kernel patches to be used with AMD CPUs

two old patches needed if compared with OpenCore bootloader, and some little problem caused by a very Clover Bootloader old bug, but..here we go!

 

 

 

Edited July 8, 2021 by fabiosun
un piccolo aiutino :)

[1515]

my system ryzen 1700

gigabyte B350 gamming 3

ati rx 470 4gb

share the clover efi....

[fabiosun]

there are big changes happening now in the AMD community, hoping for new developments that include in the most used bootloader (OpenCore), some features that will make life easier for many ..

I am attaching the config I use today for maximum functionality

It Uses the latest patches, some only available in the opencore PULL Request made by Shaneee

I hope you find it useful.

It works from Big Sur 11.4 to the latest Monterey beta (b3)

I recommend ... make good use of it 🙂 

config.plist.zip

if you use a X570 or lower platform, you may have to use  also:

 

Shaneee  or Algrey  - _mtrr_update_action fix PAT - 10.13/10.14/10.15/11.0/12.0

 

enjoy it 😉

 

[1515]

Thankyou...pach not working

but our OC pach working good performance 

[fabiosun]

21 minutes ago, 1515 said:

Thankyou...pach not working

but our OC pach working good performance 

sometimes the difference in language makes talking between us complex :P 
patches work, you just have to adapt your quirks to the latest news 
If you want better help Post your EFI which worked with older OSX. 
And if possible, put your pc specifications in signature! 
thank you

[fabiosun]

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

[jsl2000]

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.

Edited July 22, 2021 by jsl2000

[tuxy]

On 7/18/2021 at 10:53 AM, 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 · 8 downloads

Thank you very much . I did not get one point. The link says "macOS Monterey Beta patches only support 12.0 Beta 1. Beta 2 does not work " . But I understood that they work great for beta 1 , 2 and 3 as well . Am I right?

[fabiosun]

@tuxyyes 😉

 

[fabiosun]

@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

 

 

 

[jsl2000]

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

Edited July 23, 2021 by jsl2000

[fabiosun]

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 😉

 

[jsl2000]

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.

Edited July 23, 2021 by jsl2000

[fabiosun]

@jsl2000yes with restrict events.kext

[jsl2000]

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

Edited July 24, 2021 by jsl2000

[fabiosun]

@jsl2000yes is fine always if I use RestrictEvents.kext (071 or 072 PR edition used I mean)

we have pretty same parameter in platform/generic

you could try to put 0 instead of 3841

I think you also can delete many data on Generic tab as I do:

 

[fabiosun]

@jsl2000

 

 

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

 

[fabiosun]

forgive me again, I'm looking at your config better If it works for you ok .. save it.

 But, if you use the first patches in position 0,1,2, you shouldn't be using many of the later ones I see ..

 

to understand which ones, if you want you can try to use a corresponding debug version of Opencore, activate the debug in it (target 67) and then check in your log which patches are skipped according to the operating system you start

From there you can clean up your config a bit

[jsl2000]

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.

[fabiosun]

@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

[jsl2000]

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.

 

Edited July 24, 2021 by jsl2000