trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

iGPU · July 27, 2021

11 hours ago, fabiosun said:

Tested in a rush Opencore new Patches!

Work fine

"algrey - _cpuid_set_generic_info - Disable check to allow leaf7 - 10.13/10.14/10.15/11.0/12.0"

as before is not needed to boot..

I have asked if there is some unknown reason to maintain it

As always thanks to the devs and patches maintainers!

Besides the leaf7 patch, and ignoring patches specifically for < Big Sur, these 2 have not been required for the TRX40:

Edited July 27, 2021 by iGPU

fabiosun · July 27, 2021

yes @iGPUI have said this a couple of hour ago @Shaneee (also for others platform as x370 or x570 are not mandatory)

Clover for me was useful to do this kind of testing

I do not use them also from older releases

I think they will be revisited also other typos in their commit...

fabiosun · July 27, 2021

😂😂

fabiosun · July 27, 2021

Ploddles · July 27, 2021

Eureka, BS 11.4, 11.5, Monterey B3 and Monterey B4 all load/install. Patches reduced to 12 as I don't need to load anything less than BS 11.4 - which will be upgraded to 11.5.1 later this week.

Shaneee · July 27, 2021

6 hours ago, fabiosun said:

yes @iGPUI have said this a couple of hour ago @Shaneee (also for others platform as x370 or x570 are not mandatory)

Clover for me was useful to do this kind of testing

I do not use them also from older releases

I think they will be revisited also other typos in their commit...

😉 https://github.com/AMD-OSX/AMD_Vanilla/commit/807c03aca74e67135aabd76ea58e81acb8dcd02d

fabiosun · July 30, 2021

https://github.com/trulyspinach/SMCAMDProcessor/releases/tag/0.7

new version for AMD Power Gadget

Ploddles · July 30, 2021

New Gigabyte BIOSs for the TRX40.

HERE

fabiosun · July 31, 2021

On 6/28/2021 at 1:09 AM, iGPU said:

On booting with Clover, I decided to look at Memory slot issues before looking at the Patches since the Memory Error pop-up was annoying me. After several re-arrangements and re-boots, I came up with code that seems to almost work.

If the code in Spoiler below is copied and pasted into the Text section of Clover, it will produce the Memory window shown below.

Reveal hidden contents















		<key>Memory</key>
		<dict>
			<key>Channels</key>
			<integer>0</integer>
			<key>Modules</key>
			<array>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000000</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>0</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000001</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>1</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000002</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>2</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000003</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>3</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>0</integer>
					<key>Part</key>
					<string></string>
					<key>Serial</key>
					<string></string>
					<key>Size</key>
					<integer>0</integer>
					<key>Slot</key>
					<integer>4</integer>
					<key>Type</key>
					<string></string>
					<key>Vendor</key>
					<string></string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>0</integer>
					<key>Part</key>
					<string></string>
					<key>Serial</key>
					<string></string>
					<key>Size</key>
					<integer>0</integer>
					<key>Slot</key>
					<integer>5</integer>
					<key>Type</key>
					<string></string>
					<key>Vendor</key>
					<string></string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000006</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>6</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000007</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>7</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000008</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>8</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>3600</integer>
					<key>Part</key>
					<string>CMK64GX4M2D3600C18</string>
					<key>Serial</key>
					<string>AAA000000009</string>
					<key>Size</key>
					<integer>32768</integer>
					<key>Slot</key>
					<integer>9</integer>
					<key>Type</key>
					<string>DDR4</string>
					<key>Vendor</key>
					<string>Corsair</string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>0</integer>
					<key>Part</key>
					<string></string>
					<key>Serial</key>
					<string></string>
					<key>Size</key>
					<integer>0</integer>
					<key>Slot</key>
					<integer>10</integer>
					<key>Type</key>
					<string></string>
					<key>Vendor</key>
					<string></string>
				</dict>
				<dict>
					<key>Frequency</key>
					<integer>0</integer>
					<key>Part</key>
					<string></string>
					<key>Serial</key>
					<string></string>
					<key>Size</key>
					<integer>0</integer>
					<key>Slot</key>
					<integer>11</integer>
					<key>Type</key>
					<string></string>
					<key>Vendor</key>
					<string></string>
				</dict>
			</array>
			<key>SlotCount</key>
			<integer>12</integer>
		</dict>

Go to Text pane below to paste all of code into area of Memory as shown below:

This is very similar to what is seen under OpenCore (shown below).

The above code at least shifts the DIMMs into the correct positions, mimicking what we see under OC. However, under Clover, there is a warning about single modules being too large. I think the problem is with Clover. When booting with Clover, Clover won't accept more than 16GB per DIMM (see the Size pop-up on the SMBIOS pane; it maxes out at 16384), unlike OpenCore. Clover then probably sends the wrong DIMM size data to macOS, leading macOS to generate the Memory error msg.

If I try to fool Clover by only entering 16GB instead of 32GB, the computer won't boot (I suppose it knows that 256GB are present, not 128GB).

I don't know who the developers are, but I think this should be fixable. If fixed, we could stop memory error flags.

[Now, if you have smaller DIMMs, then this may work for you. If you have fewer DIMMs and they're also smaller, you'll have to work out the pattern as I'm not pursuing further.]

On a related matter, despite entering a consistent SN and UUID, which can be verified in Clover logs and is properly saved in the Clover config.plist file, Clover in the SysInfo window (Spoiler below), keeps the correct SN, but changes the UUID and enters it own ROM. Weird.

Hide contents

I take back this interesting conversion made by iGPU, making only a small modification.

In the empty slots I added:

Type = DDR4

if clover's config plist is left blank in that memory section we have a non-destructive formal error.

to download :

Clover Config Plist Validator

Clover_memory_mapping.plist.zip

Ploddles · August 2, 2021

OC 0.7.2 has landed. No mention of Shanee's pull request in the release notes as far as I could see.

fabiosun · August 2, 2021

38 minutes ago, Ploddles said:

OC 0.7.2 has landed. No mention of Shanee's pull request in the release notes as far as I could see.

https://github.com/acidanthera/OpenCorePkg/pull/277
you can find here in the comments more information about PR

fabiosun · August 3, 2021

072 OC release-AMD_3970x Patches.plist.zip

These are the patches i use to boot from BigSur to latest Monterey b4

if you use a PR opencore edition you can disable first two (0,1)

Arrakis · August 3, 2021

@fabiosun

Here is my new Efi under OpenCore 0.7.2 with the patches for Monterey simplified to 11.

To put in the OP.

Works perfectly under BigSur 11.5.1

I haven't done the Monterey installation test yet.

TRX 40 GIGABYTE DESIGNARE OPENCORE 0.7.2 zip.zip

tuxy · August 3, 2021

58 minutes ago, Arrakis said:

@fabiosun

Here is my new Efi under OpenCore 0.7.2 with the patches for Monterey simplified to 11.

To put in the OP.

Works perfectly under BigSur 11.5.1

I haven't done the Monterey installation test yet.

TRX 40 GIGABYTE DESIGNARE OPENCORE 0.7.2 zip.zip 31.53 MB · 0 downloads

does it work with AMD platform X570 as well?

tuxy · August 3, 2021

27 minutes ago, tuxy said:

does it work with AMD platform X570 as well?

I have been comparing my config 0.7.1 with the one you have posted. I was expecting the new quirks but I could not find it.

BTW I did the comparison by hand so maybe I could miss it but basically I could not find any difference between the two of them.

fabiosun · August 4, 2021

@tuxyexplain better because I do not understand well!

iGPU · August 4, 2021

9 hours ago, tuxy said:

I have been comparing my config 0.7.1 with the one you have posted. I was expecting the new quirks but I could not find it.

BTW I did the comparison by hand so maybe I could miss it but basically I could not find any difference between the two of them.

@tuxy,

I don't know if you were asking for help with patches for the X570 or not. If you were, then maybe the attached config file for OC v072 will be helpful. It was used to boot a GB Aorus Master X570 into Big Sur 11.5.1 with the latest patches with a 3950X CPU. It was not verified with Monterey or earlier macOSes.

I've removed most custom SSDT references, but please check and adjust the ACPI, DevProp and Kernel/kext sections for your own set up. SNs were removed. Finally, if you are using a different core count from the 3950X, adjust the first 2 patches accordingly.

If you only want the patches, then throw everything else away. 😉

config-X570-v072-basic.plist.zip

iGPU · August 4, 2021

On 7/30/2021 at 7:54 AM, fabiosun said:

https://github.com/trulyspinach/SMCAMDProcessor/releases/tag/0.7

new version for AMD Power Gadget

@fabiosun ,

I've begun having sudden crashes since using the new AMD Power Gadget (only tested in Monterey ß4).

The computer locks up after about 3 or 4 minutes or will even spontaneously re-boot from the login screen. It happens whether or not SMCAMDProcessor is enabled, so it would seem to be a problem with either AMDRyzenCPUPowerManagement or the Power Gadget app. I did not see this with the older version.

I now have the new kexts disabled and the computer has been stably running for hours, just like before.

Have you noticed any problems?

fabiosun · August 4, 2021

No @iGPUi am using newest version (app and kext)

no problem

In these days I am testing my system with clover bootloader to try solving two little problems I have with it :

1)

RestrictEvents.kext does not load with clover in my system

2)

this error as you said beforre

~~I will try new AMDPower Gadget app also in Opencore today and I will report~~ No problem, tested for a couple of hours.It works

I am testing exclusively in beta 4

fabiosun · August 4, 2021

19:891  0:010  OCAK: Local relocs 686 on FFFFFF8004315000
19:895  0:004  OC: Prelinked injection Kexts\Other\AMDRyzenCPUPowerManagement.kext () - Success
19:899  0:003  OCAK: as.vit9696.RestrictEvents got KXLD 0 0
19:903  0:004  OCAK: Requesting __LINKEDIT for as.vit9696.RestrictEvents - AEA09438 at 41D5000
19:907  0:004  OCAK: Requesting SymbolTable for as.vit9696.RestrictEvents - 520
19:916  0:008  OC: Prelinked injection Kexts\Other\RestrictEvents.kext () - Invalid Parameter
19:919  0:003  OC: Prelink size 69029888 kext offset 67031040 reserved 2048000
19:928  0:008  OCAK: KC TEXT is 65536 bytes with 63800 Mach-O headers need 456

not possible to open an issue because Opencore devs does not support others bootloader

Interesting thing (I hope is not a Nvram "feature" , I have no memory popup error with MAcPro7.1 inMonterey beta 4, I have that problem with Big Sur 11.5.1)

tuxy · August 4, 2021

8 hours ago, fabiosun said:

@tuxyexplain better because I do not understand well!

Dear Fabio ,

Maybe I misunderstood your reply here

I was expecting a new quirk on 0.7.2 in order to enable a smaller amount of patches.

But comparing the entrie between 0.7.1 vs 0.7.2 I could not find any difference whatsoever.

Thanks

fabiosun · August 4, 2021

@tuxyquirk is the same..but as I said in quoted thread Shaneee's PR was retired and so we have to use core count patch in our config..or..to use Closed Shaneee's PR 🙂

IF a Pull Request is not accepted by opencore devs we can't have that feature in an official Opencore release 😉

fabiosun · August 4, 2021

to explain better attached a minimal set of patches booting BS and MR (if you use Opencore Pr edition)

patches for closed OC Shaneee's PR edition.plist.zip

Ploddles · August 5, 2021

HERE is my OC 0.7.2 EFI.

It boots 11.5, 11.5.1 and 12.0 Beta 4 with BIOS version F4Q and F4R.

Sleep still doesn't work in Big Sur but does in Monterey.

fabiosun · August 6, 2021

@Ploddlesin your config latest kernel patch is not needed for trx40 chipset:

And usually also in system that needs it (X370,x470,x570 and lower) , it produces worst GPU benchmark..

maybe you can try to skip it

Sign In

trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members

Important Information