trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

[iGPU]

3 hours ago, Ploddles said:

Anyone tested the new patches with Big Sur 11.5 Beta 5?

 

Not that I am expecting any changes now in the latest beta released today so they should be fine. This will probably be the last update, bar any further security updates, to Big Sur before we move on to Monterey.

 

This update went fine with new patches (using the minimal ones I uploaded last night).

 

RestrictEvents injects the Processor info shown below in the "About This Mac" window (with code in Spoiler).

 

Spoiler

 

 

Edited July 9, 2021 by iGPU

[fabiosun]

@Ploddlesnew patches are good for 11.4.x, 11.5 b5 .12 b1

 

with unreleased single b2 patches all the patches are working also in b2

 

 

also with clover

 

[fabiosun]

For Opencore and Clover bootloders:

 

algrey - new Force set cpuid_cores_per_package (new version of original available @Inasanelymac)

algrey _cpuid_set_info (unreleased)

Goldfish64 - Bypass GenuineIntel check panic - 12.0

algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0

algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0

algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0

algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0

XLNC - Remove version check and panic - 10.15/11.0/12.0

 

--- Published a first version on IM - algrey is improving it (refine its search)

--- Unpublished (Useful to boot Monterey b1 and b2)

--- Useful in Clover Bootloader and in Opencore Bootloader (if you do not use*: ProvideCurrentCpuInfo Kernel quirk)

 

*Clover bootloader misses that quirk in release 5137/38 used by me!

 

Opencore bootloader quirk I use:

 

 

Opencore bootloader quirk I use:

 

 

Clover bootloader quirks I use:

 

 

I hope it could be useful to understand better!

 

[fabiosun]

23 hours ago, iGPU said:

 

@fabiosun

 

We need to see how this formula will hold up for those using a 3990 CPU which has more cores than macOS software supports. It might not have a searchable result (64-1 --> 3F). This patch might have a limitation on CPUs with too many cores.

 

Use: 

f:4489EAC1 EA1A

r:BA3F0000 0090

 

and see what error code is created even if it does not boot.

 

 

A long time ago some users who had dual CPU systems with the Xeon 2696 V4 22 cores 22 threads for each cpu for a total of 44 cores + 44 threads,

we asked pikeralpha to take an interest in this, and he pulled the location where the kernel declared this limit out of the hat.

and it was clearly a value of 3F.

It was not possible to modify it in any way and it had to be limited as today by bios, limiting the total number to 64 c / t

I don't find where we talked about it, if I find the posts I submit them to your attention If my second dose of Pfizer vaccine doesn't make me crazy,

I also remember that we had to patch a kext..but no one has ever succeeded unfortunately and pikeralpha was not very interested in

for testing I have changed 1F in 07 but I have in this way a kp in early booting steps

 

[fabiosun]

@iGPU

https://pikeralpha.wordpress.com/2016/07/26/xcpm-for-unsupported-processor/comment-page-2/#comment-7296

 

[Ploddles]

17 hours ago, iGPU said:

 

This update went fine with new patches (using the minimal ones I uploaded last night).

 

RestrictEvents injects the Processor info shown below in the "About This Mac" window (with code in Spoiler).

 

  Reveal hidden contents

 

 

 

I get this (BS and Monterey) without the revcpu or revcpuname entries as per your spoiler, so I am assuming it must be reading it from the BIOS.

 

 

[Ploddles]

8 hours ago, fabiosun said:

@Ploddlesnew patches are good for 11.4.x, 11.5 b5 .12 b1

 

with unreleased single b2 patches all the patches are working also in b2

 

 

also with clover

 

 

I eagerly await the patches. I will leave my system as it is now until they are released. I want to get rid of that extra patch I need to stop the random reboot / lockup. I will also change my quirks etc to match yours at the same time to see if everything is stable on my system like that. Has Shannee given you any clue as to when they will be released to the rest of us?

[iGPU]

1 hour ago, Ploddles said:

 

I get this (BS and Monterey) without the revcpu or revcpuname entries as per your spoiler, so I am assuming it must be reading it from the BIOS.

 

 

 

Are  you using the RestrictEvents kext?

 

And what value are you using for PlatformInfo/Generic/ProcessorType?

 

[Ploddles]

49 minutes ago, iGPU said:

 

Are  you using the RestrictEvents kext?

 

And what value are you using for PlatformInfo/Generic/ProcessorType?

 

 

Yes, this is with RestrictEvents.

Processor Type = 3842

Edited July 9, 2021 by Ploddles
Add picture

[fabiosun]

@Ploddlesi am not in touch with shanee

as I said I have had it from the creator..😂

@algrey I mean

to reduce instead number of patches you have all you need

unrealease patch is only for Monterey b2

[Ploddles]

@fabiosun

 

I have just tried your patches and quirks and my system will not boot at all.

 

I will stop trying different things for now and wait until you can post your full efi with all your new settings (patches (inc Monterey B2 ones), quirks etc). I will just change the mmio whitelist and memory settings to those for my mb and proceed from there.

 

Thank you for all you are doing for us Threadripper pioneers.

[fabiosun]

@Ploddles

my full EFI is always the same!

now only a patch is not available and Devs decide when publish it

I am helping to debug some stuff if algrey needs to test but all is working fine with latest GitHub AMD OSX patches and algrey one posted here and on insanelymac.

obviously without unreleased one beta 2 does not boot

with patches available for all is it possible to boot fine from 11.4 to 11.5 beta 5 to 12 beta1

 

I am trying also to create an interest to have more people helping devs to find patches and test well also in different conditions but my thread has had few success! 😉

Maybe @algrey gave me this chance because I was in touch with him  from the first days when patches "was borked" 

 

PS

it is possible to use Clover Bootloader and Opencore bootloader with the same set of patches (declared in proper way for both bootloader) clover needs two more patches , but as I said before all patches are posted here !

 

[Ploddles]

No it won't boot at all at the moment. I'm probably doing something wrong along the way.

 

I don't expect it will be long before the Beta 2 patches are released so I will just wait. There is no hurry as I can still boot with the old patches.

Edited July 10, 2021 by Ploddles

[fabiosun]

@Ploddlespost only config .plist you are using to boot in Monterey beta1

 

[Ploddles]

The one that does work for me at the moment is :-

 

config.plist.zip

 

If I just replace the patches section with yours then the system stops as in above image. If I also change the various quirks sections as well it stops at the same place.

[fabiosun]

On 7/10/2021 at 11:11 PM, Ploddles said:

The one that does work for me at the moment is :-

----

 

If I just replace the patches section with yours then the system stops as in above image. If I also change the various quirks sections as well it stops at the same place.

 

try this with your EFI

 

I have disabled few patches and added 0 ones

 

UPDATE 17-07-2021:

 

[Ploddles]

@fabiosun

 

I booted with verbose mode each time.

 

A clean install of BS 11.5 beta 4, updated to beta 5, worked fine for 5 minutes before I restarted for the next test.

 

Older install of BS 11.4 with all my programs installed:-

1st start panicked and automatically rebooted shortly after entering my password and before loading my desktop, menu bar or dock.

2nd start locked up a few minutes after startup.

3rd start worked ok for 5 minutes before I restarted to test Monterey.

 

Monterey seemed to start but never displayed the log on screen. I left it for a few minutes but it didn't reboot or ever display anything on the screen. I rebooted and the same thing happened. 3rd reboot was the same.

[fabiosun]

@Ploddles

better or no? 🙂

about Monterey but also other system

Whatevergreenkext should be disabled or "boot argumetated" well 🙂

if you are using 6900 xt

otherwise black screen when login should happen

 

[Ploddles]

It is about the same for Big Sur.

 

Worse for Monterey as I just get a black screen. I tried with and without whatevergreen.kext, it makes no difference. With my old patches I do get an output to my screen.

[fabiosun]

Clover Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2) 🙂

 

 

Opencore Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2)

 

list of patches I use in above pictures:

 

new_Algrey Force cpuid_cores_per_package (unreleased in latest form tested today, you can use patch available for now)

_cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN (unreleased)

Goldfish64 - Bypass GenuineIntel check panic - 12.0

algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0

algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0

algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0

algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0

XLNC - Remove version check and panic - 10.15/11.0/12.0

 

this patches:

 

algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0

algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0

 

they are not useful if you use a bootloader with ProvideCurrentCpuInfo quirk capability.

 

Personally, my goal was reached by now!

always thank to @algrey for his time and skill! 🙂

 

UPDATE 17-07-2021:

 

 

[iGPU]

5 hours ago, fabiosun said:

Clover Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2) 🙂

 

 

Opencore Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2)

 

list of patches I use in above pictures:

 

new_Algrey Force cpuid_cores_per_package (unreleased in latest form tested today, you can use patch available for now)

algrey _cpuid_set_info (unreleased)

Goldfish64 - Bypass GenuineIntel check panic - 12.0

algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0

algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0

algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0

algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0

algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0

XLNC - Remove version check and panic - 10.15/11.0/12.0

 

this patches:

 

algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0

algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0

 

they are not useful if you use a bootloader with ProvideCurrentCpuInfo quirk capability.

 

Today I have helped algrey to test his Force cpuid_cores_per_package with also older system like 10.13.6.

It is working quite well!

So maybe, in few time , patches will be updated

 

Personally, my goal was reached by now!

always thank to @algrey for his time and skill! 🙂

 

 

I was planning on not writing anything more about patches, but with Ploddles having problems and your repeating a patch list that I think none of us can presently boot with, I felt compelled to write. While I can speak only for myself, and possibly Ploddles, those of us not having access to "algrey _cpuid_set_info (unreleased)" cannot boot into Big Sur or Monterey ß1 with your patch list unless the following are also added:

 

A. Big Sur

1. algrey - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN - 10.13, 10.14, 10.15, 11-11.3
2. DhinakG - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN - 11.3b1 (11.4-12)

B. Monterey ß1 (plus A2 above)

1. Goldfish64 - Bypass GenuineIntel check panic - 12
2. XLNC - jmp to calculations and set cpuid_cores_per_package - 12
3. XLNC - cores and threads calculations #1 - 12
4. XLNC - cores and threads calculations #2 - 12

 

Perhaps the unreleased patch you reference can replace these extra patches, but presently without this unavailable patch, I cannot boot without the above two sets added to the other patches you've listed (whether or not Above 4G is enabled).

 

Since there is currently so many patch changes and associated confusion, I've removed all of my recent posts about patches (they're now blank, since I could not delete them). Those posts are pointless with the constant changes and secrecy, and will only serve to further misdirect current or future readers.

 

 

Edited July 11, 2021 by iGPU

[Ploddles]

47 minutes ago, iGPU said:

 

I was planning on not writing anything more about patches, but with Ploddles having problems and your repeating a patch list that I think none of us can presently boot with, I felt compelled to write. While I can speak only for myself, and possibly Ploddles, those of us not having access to "algrey _cpuid_set_info (unreleased)" cannot boot into Big Sur or Monterey ß1 with your patch list unless the following are also added:

.........

 

 

 

Until AMD-OSX release the full set of new patches that enable BS and Monterey Beta 2 to boot I am not going to try anything else.

 

Even though one of my patches has been deprecated and no longer appears in the official list, my system will not boot reliably without it, so I will leave my patches as per my last upload as at least that is working.

 

Once the new ones are release I will readdress it.

[fabiosun]

I am very sorry that this problem has arisen for you, and most likely I have expressed myself badly from the beginning

If you have a reduced patch system that starts without difficulty or problems,

just adding the patch:

Force cpuid_cores_per_package available on insanelymac and published by algrey,

it is possible to try to further reduce them by deleting some related to:

cpuid_cores_per_package

and:

cores and logicals count if you use any of them in your small patch set

And try to see if you can get any of that type off

I am sorry for any inconvenience this may cause you, but I cannot publish the work of others without permission

it would be a serious disrespect for the work of others.

I hope I have partly clarified the fact that it was created perhaps because of my too much enthusiasm to share things with you on the fly!

I will not do it again'!

[Ploddles]

There is no disrespect to you @fabiosunand I know what you are doing is in good faith.

 

The patches you published do not fully work for me at the moment and I would not expect you to release the new patches to anyone until algrey is happy for you to do so. Hopefully this will be soon but they could well change again with the next beta, in a week or so or whenever it is released by Apple. Hopefully they will make my system more stable.

[fabiosun]

good morning guys 🙂

Italy won a beautiful football match with England and my second dose of Pfizer vaccine is fortunately also losing intensity tighter small problems it has produced in me.

 

So I'll hopefully clarify it definitively.

 

I understand that it is very frustrating to see "solutions" and to be told I cannot provide them.

But, do you also know how much I spent for example to get out the patches for Monterey beta 1 stimulating, at times, perhaps, even in a heavy way, the managers of the same.

having said that, in this space I will try to make myself better understood by talking exclusively about what is available at the moment. That is the official patches downloadable from the official AMD OSX Github.

The patches are those valid up to Monterey Beta1 I will do a further reduction of the field and will think exclusively on systems ranging from Big Sur 11.4 to big Sur 11.5.beta 5

 

This discourse can be carried on up to Monterey beta 1 and, having an unreleased patch available also in Monterey beta 2.

But let's stay with the facts.

 

The schemes that I will propose are for clover bootloader.

Patches used are the same for both bootloaders, obviously with the respective names useful for the two bootloaders that have different nomenclature for their patches entries.

With the Opencore bootloader, it is possible to use two patches less, because the developers of Opencore have added a quirk not present in Clover.

 

Let's begin

0) algrey - Force cpuid_cores_per_package

 

This patch was first posted by algrey on insanelymac:

 

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2762290

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2762342

 

links have been edited few times I think so data could differ a bit.

 

then it was converted by me for Clover and also explained on our forum in several places:

On 7/7/2021 at 8:16 PM, fabiosun said:

la patch 0 che algrey ha pubblicato su Insanely Mac e' fatta per il mio processore

 

e' molto semplice ricrearla per altri tipi di cpu:

 

PatchProvideCurrentCpuInfo set cpuid_cores_per_package

f:4489EAC1 EA1A

r:BA1F0000 0090

attenzione

il valore 1F significa 31, il 3970 x ha 32 cores quindi come da sue indicazioni 32 -1=31=1F

A titolo di esempio per  una CPU con 8 cores:

8-1=7=07

per una da 16:

16-1=15=0F

e via dicendo

 

this above  is the patch that, most likely, is preventing the release of new patches for everyone.

Unfortunately it still doesn't work on macOS HighSierra in tests done in private

thanks to algrey.

 

1) algrey - commpage_populate -remove rdmsr

 

 

2) algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 4

 

 

3) algrey - cpuid_set_cache_info - don't set cpuid_cores_per_package

 

 

4) algrey - cpuid_set_generic_info - remove wrmsr

 

 

5) algrey - cpuid_set_generic_info - set flag=1

 

 

6) algrey - cpuid_set_info - GenuineIntel to AuthenticAMD

 

 

7) algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15/10.16

 

 

😎 algrey - cpuid_set_info - cores and threads calculations - 10.15/10.16

 

 

9) algrey - i386_init - remove rdmsr (x3)

 

 

10) tsc_init - remove Penryn check to execute default case

 

 

11) algrey - tsc_init - grab DID and VID from MSR

 

 

12) NoOne - lapic_init - remove version check and panic - 10.16

 

 

13) DhinakG - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN - 11.3b1

 

 

now let's go a little deeper.

If I activate patch 0 I can deactivate the yellow patches  (this is also valid for osx like Monterey beta 1beta 1 (not in macOSHighSierra).

 

If I used opencore bootloader I can also do without the red patches (10,11), this activating a quirk that is unfortunately not present in clover at the moment.

quirk is:

ProvideCurrentCpuInfo

 

If you have followed this far, it is now possible for you to better understand what Patch 0 does.

Its work is done in the same way also in Beta 1, so if you update the present patches and the new ones available for beta 1 accordingly, activating or not the patches 0 you can reduce the number of patches of the family of those marked here in yellow .. and there are also in the latest release of the patches

if you proceed to this type of test, refer to find and replace and not to the names of the patches (they often take different names depending on who writes them in their config), it's a bad habit that I have too).

I usually try to download the latest official ones, and grab the ones that have the same find and replace that I use in my current working config.plist in use

 

if you have any questions, I will be happy to answer based on my knowledge on this topic

good day everyone