trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

[gosi]

Thank you so much!

Two questions remaning:

1) the boot drive was renamed, in OpenCore it still shows the old name. Is there a way to fix that?

2) if I add a Thunderbolt card or another graphics card, do I have to check the MMIO again or just BIOS settings?

[fabiosun]

1) to rename in opencore menu you should add a txt file in a folder with right name (you have to search exactly how to (I do not remember) 🙂)

 

2)I f I do not mind you have in your config a SSDT for a thunderbolt card, for MMIO you do not have to check BIOS setting

If you change your bios or some value in it like 4G option could change your list

The check you will have to do is always in debug log

If skip to 1 is there and you have put it in your MMIO whitelist with a yes value you are fine

if you have set to yes a MMIO and you see in debug log skip to 0..it means value is changed and you have to take hex value of it from your debug log and recalculate properly in decimal

Addingr nvme or fulfill your pci express slot could change your MMIO (also if your BIOS settings are the same)

 

I advice you to read better @igpu explanation for this subject in the link I have posted to you previously

Now, do not worry, think I do not change my MMIO whitelist from a year or so and I have changed also 3 bios release of my motherboard

🙂

 

 

 

Edited September 21, 2021 by fabiosun

[gosi]

Okay thanks again. So what would the senseful process look like, lets say replacing the graphics card? it will most likey still boot, but I need to check if the MMIO has changed and update the whitelist accordingly otherwise every now and then booting will fail?

 

Should we update to the latest Big Sur release or rather stay away from it? I just saw that one popping up 😄

[fabiosun]

if you put GPU in the same slot, maybe nothing will change

if you use whatevergreen kext Mac Pro 7.1 smbios and you put a 6900 xt maybe you have to tweak a bit your actual config.plist

for the update

I read from @Arrakisgigabyte and others manufactured  board has some problem with ethernet (i2xx)on board ..I do not know if it is true also in 11.6 or only in Monterey beta

 

I use an Aquantia card so I have not this problem

 

Edited September 21, 2021 by fabiosun

[Arrakis]

@ Gosi

 

Several things:
1) In the config.plist you can delete in DeviceProperties the values of my graphics cards and possibly that of the titan ridge if you do not install it.

 

2) If you do not use the titan ridge card you can delete the SSDT-DTGP and SSDT-TBOLT3-NVM23 from the config plist and also delete them from the ACPI folder of the EFI

 

3) The ram values should be replaced by yours in all banks.

 

4) as part of the installation of the Titan Ridge card, it must be installed in slot 4.

 

5) Wait until I update Big Sur 11.6 so as not to put a potential problem (I210) on you.

 

I am under the AGESA bios version 1.0.0.4 (FBd).
As long as you don't have an AMD 6000 series card, there is no point in upgrading to AGESA version 1.0.0.5 (FBi) which brings Add Re-size bar support on Windows (not supported by MacOS).

[gosi]

Thanks Arrakis 🙂

 

1) whats the easiest way to remove it? I am used to running Hackintosh with Glover but I have about zero clue about the config.plist. So removing makes me a bit scared as I think I might damage something.

2) the card that came with the mobo is broken, it is not even detected by the BIOS. Replacement was hard to get but it should be there next week. Do I need another version of the SSDT if its Revision 2 or vice versa?

3) ah I can just string replace and should be happy?

4) I double checked the manual and was never able to see which slot is number 4. I guess to one closest to the CPU is 1 and downwards are 2,3,4?

5) yes good point 😄

 

 

[fabiosun]

Beta 7 is out (Monterey)

21A5522h

 

if you do not see it put a securbootmodel value according your used SMBios

 

Edited September 21, 2021 by fabiosun

[fabiosun]

old method to upgrade from beta 5 to beta 6 is not working here

 

[fabiosun]

 

for tonite this is my best 😀

[Driftwood]

Big Sur 11.5.2 straight to Monterey Beta 12.06 and then onto beta 7. Strangely I could only download the installer with that cruddy old EFI with all the patches on (no j160 was used!) - Reduced patch EFI just wouldn't do it. And then switched half way thru install (2nd reboot) to reduced patch EFI. And we're in! Now lets do 7.

 

 

Now to do the beta 7 update you have to change SMBIOS to iMacPro17,1  - reboot - get the update.  download,

 

 

 

Install (during install some users have managed to change SMBIOS back to = MacPro7,1 and get the install working), or, after first reboot switch to your OC usb stick with 7,1 SMBIOS on (which is what I did in the end).

 

Anyways, here's the complete process I did:-

 

 

1/ Change config to iMacPro17,1

 

Now let it download... you shouldn't need to set j160 in SecureBootModel to download.

 

 

2/ Let it continue install...

 

 

 

3/ It will reboot to black install gauge...

 

4/ Next reboot (if you can, switch configs to your 7,1 SMBIOS on a separate USB stick ) or let it go on to 17,1 install.

 

5/. As soon as your in Beta 7, ensure SMBIOS is back to MacPro7,1 settings, reboot to check. Update NVRAM.

 

 

We're in!

 

 

Edited September 22, 2021 by Driftwood

[TheGreatArtist]

Any informations on Monterey supporting more than 64 threads?

[fabiosun]

3 hours ago, TheGreatArtist said:

Any informations on Monterey supporting more than 64 threads?

No support in this beta 7

[fabiosun]

do not know how I did it...

[Driftwood]

Nice to see Apple still supporting Firewire/RME Fireface800 in Monterey!

Edited September 22, 2021 by Driftwood

[Driftwood]

Hey @fabiosun did you manage to suss how you got yours working? Im taking you didn't use the iMacPro17,1 method?

When I tried just the MacPro7,1 method it kept going on a continuous reboot loop on the second reboot. So was forced to use the 17,1 hack method.

 

Also question for everybody, if running Quicktime movies/Apple TV / or FCPX (like here) how much of your CPU% in VTDecoderXPCService is being used? Over 300% playback and sometimes unto 1000% for FCPX encodes? I would be interested in hearing results.

 

Actually Davinci shows less than half the cpu& time over FCPX doing the same video.

Edited September 22, 2021 by Driftwood

[fabiosun]

@Driftwood

i didnt understand well how i did it

the weird thing is i have had to boot two times from mackintosh hd 

then mackinyTosh install disk vanished

used 17.1 smbios to finish installation but also cleared NVRAM and enabled SIP

later i will test with davinci cpu jpb

[fabiosun]

first one a simple timeline play

Second one a complex SFX export I Apple Pro Res 422 (4k)

 

[Driftwood]

On 9/22/2021 at 4:18 PM, fabiosun said:

first one a simple timeline play

Second one a complex SFX export I Apple Pro Res 422 (4k)

 

 

Yeah 422 10-bit encodes will smack up the CPU%.

 

 

Interestingly, Monterey is the first OSX to fully support Adaptive Sync. Display is much better on this 8K monitor

[Driftwood]

Dell 8K at 60Hz on Monterey

 

[iGPU]

 

While I got the update to show up using j160; I cannot get past the "Macintosh HD" first reboot stage. Even using iMac17,1 does not help. (Driftwood, above you referenced "iMacPro17,1" and the other forums are using "iMac17,1".)

 

Since I'm now at work, later tonight I'll try changing other settings in SMBIOS associated with iMac17,1.

 

 

[fabiosun]

@iGPUsimilar behaviour happened to me

the only thing if it fails is better to download again 

 

So, MacPro 7.1 and j160 to download (if you do not seeit you can try to clear Nvram)

 

before restart after download change to iMac17.1 and put to Disabled SecureBootModel

Other big variable for me was TPM enable/disabled in BIOS

It worked with it enabled from MacPro7.1 Smbios download step

 

Tested also other bootloader (clover with no success) but above should be the "gold" method

 

As side note, when I have updated from beta5 to beta 6 I have only had one time mackintosh hd icon

this time I have it for two times before it vanished and I have had only good Monterey icon for two last steps to do

I have finished the update using 17,1 Smbios and with only one monitor detected with it (hdmi connected)

 

 

Edited September 22, 2021 by fabiosun

[Driftwood]

4 hours ago, iGPU said:

 

While I got the update to show up using j160; I cannot get past the "Macintosh HD" first reboot stage. Even using iMac17,1 does not help. (Driftwood, above you referenced "iMacPro17,1" and the other forums are using "iMac17,1".)

 

Since I'm now at work, later tonight I'll try changing other settings in SMBIOS associated with iMac17,1.

 

 

Sorry this is what I used.... quickly generated a SMBIOS for the cause. Feel free to use any of this as I now no longer need.
I actually used all of these numbers in my config just in case it balked. I dont think you'll need to use j160 as the Mac17,1 profile will get you into the install. So leave SecureBootModel on Disabled. I believe quite a few Intel users had to do the same as above, and sometimes they had to re-download a few times. I think if you download with the 17,1 profile booted you'll be good.

 

Type:         iMac17,1

Serial (SystemSerialNumber):       C02Q7EYGGG7L

Board Serial (MLB): C02533200GUGPF7UE

SmUUID:       2D61C34C-61C7-4854-82DC-44DDBBA3DD34

Apple ROM:    98FE945C3654

 

You could actually use the above to download, then retry the install, and on 2nd reboot you enter your 7,1 profile.

Edited September 22, 2021 by Driftwood

[Driftwood]

Ive decided to ditch my USB map as each of my USB controllers are no bigger than 10 ports. Well under the 15 per controller. Tell me if Im wrong?! Everything works fine without!

Edited September 22, 2021 by Driftwood

[Driftwood]

Latest OpenCore 0.7.4 will fix the update to Beta 7 Monterey negating the need to switch SMBIOS or any silly hacks we've been doing!

 Here: https://github.com/dortania/build-repo/releases/download/OpenCorePkg-6107bc9/OpenCore-0.7.4-RELEASE.zip

Edited September 22, 2021 by Driftwood

[iGPU]

I211 is now working with the old SmallTree kext file on Monterey ß7.  (The same file works with Catalina-BigSur-Monterey.)

 

The entire time is was a macOS problem, not a SmallTree kext problem. And most likely, the I210 ports will be working again too.