trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

[fabiosun]

@Arrakistry to export  a DCP  (film of about 1h.24m with a colored and fusion SVX timeline on it)  with also a GPU like 3090 or 6900xt (it adds hot air also in your case)

80 ° is not so much but also depend on your additional pc part

 

About restricevents.kext i do not use it

if you tell me what you want to try i will do

 

[valmeida]

On 5/3/2021 at 4:27 PM, Jaidy said:

for the people running RDNA2 cards, is there a problem with the display properties? I have a Benq EW3280 monitor, with a Power Color Red Devil 6800 XT. I am using agdpmod=pikera boot argument. The display is fed via a DisplayPort. It turns out that the picture is much less brighter than previously. Furthermore, on the On Screen Display (OSD) menu for the monitor, the Brightness and Contrast options are disabled. This seems to be a macOS thing, since when I boot into the BIOS configuration, then the brightness is fine, and also the aforementioned options are enabled in the monitor OSD. 

 

Is anyone else facing this issue? Can some one advise me how to address it? I tried using Mac Pro 7,1 SMBIOS. That would boot to black screen too without the agdpmod=pikera argument. On another forum, it was mentioned that Mac Pro 7,1 definitions along with -wegoff works. I have not tried that. Is -wegoff a boot argument?

 

Never mind, HDR was enabled.

I'm also using agdpmod=pikera boot argument and seems to be working fine. 

[Arrakis]

@fabiosun

that's why I chose blower type cards. they expel the air directly outside the case. So I don't have a problem with overheating in the PC case.

They are both at 80 ° degrees when used by 100% resolve. I calibrated a 4h00 opera in 50i with Resolve noise reduction. The render was over 1h30 and I had no problem with the CPU heating (around 70-75 °). I always check the temperatures with IStatMenus. The advantage of this software is that it has a temperature history. If I had abnormal temperatures on the CPU or case I would have acted accordingly.

 

I look forward to the next ones based on Navi 21 always blower type.

if I had to switch to windows, I would choose 2 RTX 3090s on the same principle.

[valmeida]

@fabiosun here are my test results with beta 2  . Im available today if you need me to run something else.

 

 

 

  

 

Edited May 6, 2021 by valmeida

[Arrakis]

@valmeida

Great to have done the tests. according to the Blackmagic Raw test. Your current config with the 6900XT gives a hell of a slap in a 2019 macpro.

there is a small problem with the Blackmagic Raw test.

When you look at the counters, it's an impressive score but when you look at the values in the how fast columns it's way below.

 

The 1st screenshot attached is a 2019 MacPro

16 cores with 2 AMD Radeon Pro Vega II Duo 32 GB. And the second screenshot is my current configuration

Edited May 6, 2021 by Arrakis

[iGPU]

On 5/5/2021 at 12:27 AM, Arrakis said:

@fabiosun

is there the problem with the RestrictEvents kext ?

 

If you go to this web site (here it is RestrictEvents), you can get the latest commits of most things OC. By choosing the pop-up (highlighted in red below), you can move between the various kexts and OC builds.

 

When I run the latest RestrictEvents, the Memory section is still working. I'm normally not using this kext after modifying the Memory section of OC. I am not seeing any error issues with the PCI section (which is not working, and for which I've not yet found any solution).

 

 

 

Edited May 6, 2021 by iGPU

[Arrakis]

14 minutes ago, iGPU said:

When I run the latest RestrictEvents, the Memory section is still working. I'm normally not using this kext after modifying the Memory section of OC. I am not seeing any error issues with the PCI section (which is not working, and for which I've not yet found any solution).

@iGPU

it's exactly the same for me.

[iGPU]

On 5/4/2021 at 11:22 PM, fabiosun said:

 

beta 2 alive & kicking!

 

Automatic Bandwidth Configuration flagged produces this 

I think it is Intel coding related

 

 

I too updated without any issues (and see the same error with Expansion Slot Utility, when not running RestrictEvents, which I've seen from at least 11.2.3).

 

 

Edited May 6, 2021 by iGPU

[Jaidy]

On 5/1/2021 at 3:07 PM, iGPU said:

I've finally figured out how to correctly use the Memory section in OC. I decided to work on this since I've now changed to using MacPro7,1 instead of iMacPro1,1 due to the former apparently being a better match for going forward with AMD 6x00XT GPUs.

 

If you follow this guide carefully, you will not need the kext "RestrictEvents.kext" file, and you will no longer see a memory error. I've only tested in Big Sur, but it should work under Catalina as well.

 

Here's the guide (I've paralleled posted on another forum):

 

OC's "BANK" numbers were re-arranged to better match the memory upgrade instructions per Apples's docs. The Bank numbers in their order of appearance are slots: 7, 8, 9, 10, 11, 12, 6, 5, 4, 3, 2, and 1. These correspond to the slot numbers on the memory board. In Apple's docs, the slots are arranged into Channels, A-F. Channel A are Banks/slots 7, 8; Channel B are 9,10; C are 11, 12; D are 5,6; E are 3,4; and F are 1,2 (see spoiler below).

  Reveal hidden contents

 

 

 

 

 

 

 

If properly arranged, below is what is seen with 8 DIMMs installed on my mobo. An actual MacPro7,1 has 12 slots, so our 8 DIMM slotted mobos will always have at least 4 banks empty. Now, should you only be using 4 memory sticks, then set to empty the following slots:  1, 2, 3, 5, 8, 10, 11, 12. In other words, if you are using 4 DIMMs, only slots 4, 6, 7 and 9 will be populated (thanks djlild7hina!).

 

Note: this does not mean you physically move your DIMMs about on your mobo; this whole process is to map your DIMMs into software locations where the macOS is expecting them to be positioned. Keep your DIMMs physically where the mobo manual recommends.

 

 

The code within OC is shown in excerpt below (the full code is downloadable as an attachment). Add it enbloc as the "Memory" section within the PlatformInfo section (also make sure to enable "CustomMemory"). The SNs are arbitrary (add your actual ones if you're more OCD than me). The part numbers are mine as used, made by Cosair; change these values as you wish. The AssetTag is also arbitrary but only entered if that memory slot is populated. Finally, change the Size and Speed values to better match your DIMM.

 

  Reveal hidden contents

 

If SystemInformation is run, the following is seen:

  Reveal hidden contents

 

In the attachment, I included the 8 DIMMs as well as one for 4 DIMMs (4 DIMM verified and fixed by djlild7hina on another forum). Inactivate either one with "#" symbol or activate by removing "#" and editing heading label to "Memory":

 

 

OC-Memory-MacPro7,1.plist.zip 1.33 kB · 10 downloads

shifted to MacPro7,1, removed the Whatevergreen kext, and it boots without agdpmod=pikera argument. Thank @iGPU for this guide, works perfectly for me! 🙂

[Arrakis]

@Jaidy

Hello, In what context can we remove the whatevergreen.kext of EFI?

[iGPU]

13 hours ago, Arrakis said:

@Jaidy

Hello, In what context can we remove the whatevergreen.kext of EFI?

 

On the TonyMacx86 site there were posts in 2019 that found in Catalina, that 5700s and Radeon VIIs were having issues with WEG. Specifically, there were computer freezes happening within 1 to 5 minutes of booting. Some of the ports (I forget exactly which ones; eg, the middle DP port wouldn't work) were not active if WEG was disabled. These issues did not affect older GPUs like RX580 (a very solid workhorse of a GPU) or Vega 56/64 GPUs. (The Radeon VIIs were actually the last of the Vegas while the 5700 was the first of the Navi architecture; the 6x00XTs are now Navi-2.) In other words, with older GPUs, use WEG, no boot-arg needed.

 

Such WEG issues are why in my early EFI posts on this thread, I used the boot-arg "-wegbeta" to get my Radeon VIIs to properly work once we switched to bare-metal. I don't seem to need this boot-arg any longer.

 

With the latest 11.4 betas, the 6x00XT line of GPUs seem to be supported (and will probably get more robust with later 11.x releases), but if the current generation WEG is used (and it too over time will become more robust with Navi-2 support), there are black screens or other problems. If WEG is disabled, then some users have good functionality with Navi-2.

 

The other option, when using 6x00XT GPUs, is to enable WEG and add the boot-argument "agpdmod=pikera". There is a current thread on this at TonyMacx86 here (I've read the whole thread and you could skip the first half or so until the discussion hits 11.4 stuff). They have found some inconsistent responses with the 6700XT (from the posts, I'd stick with the 6800XT or the 6900XT for now). As an aside, as Pavo pointed out in this post, not all WEG boot-arguments work in Big Sur.

 

 

Edited May 7, 2021 by iGPU

[Arrakis]

@iGPU

Thank you for taking the time for me to explain the role of kext whatevergreen.

As I am new to hackinstosh I do not have all the basics.

 

As I have 2 WX9100 GPUs based on the vega 64 architecture I simply deleted this kext and no arguments.

[Arrakis]

@fabiosun@iGPU

I installed Big Sur 11.4. Beta 2.

I did a clean install in 11.3.1 and then directly to 10.4. beta 2

Unlike you, I do not have the error message on the locations of the PCI cards.

On the other hand, I have a mess of kernel panic.

After 1 minute it's a black screen and a complete restart of the PC

I am using the same EFI as for version 11.3.1

Memory mapping is manual.

I put the kext whatevergreen back on because while loading Osx there are display artifacts on the boot screen (HDMI) and also the two screens are reversed on every boot.

I have no WEG argument.

 

 

[fabiosun]

Hi @Arrakisi have error only if i click here:

no problem during booting or while using OSX

 

This week i will receive from AMD a shiny and new RX 6900 Xt...

And i Will back more actively in OSX scene

I hope it has resolved also some problems it has with Davinci in windows Environment OS

If so i will sell my 3090 FE 

Otherwise i will sell 6900 xt

 

 

[Arrakis]

@fabiosun

Absolutely no problems installing Beta 11.4.  OS loads without problems.  This is after logging on the session about 1 minute after the screens go black and the pc completely reboots with the Kernel panic report each time at the next log session.

[fabiosun]

@Arrakisweird

I do not have that problem

[tomnic]

1 hour ago, Arrakis said:

@fabiosun

Absolutely no problems installing Beta 11.4.  OS loads without problems.  This is after logging on the session about 1 minute after the screens go black and the pc completely reboots with the Kernel panic report each time at the next log session.

 

It is VirtualSMC which is in backtrace, try another version or FakeSMC instead.

[iGPU]

@Arrakis

 

I think you're having a TB-USB kernel panic (there is a new firmware to flash onto the card that stops kernel panics with BS > 11.3, but beyond scope of this thread;  see here for more details). Remove the TB card, re-boot and if no more freezes, then it was the TB AIC's USB generating the kernel panic.

 

The screen artifacts during boot, when WEG is disabled, is normal and of no concern. WEG simply suppresses them (they began with Catalina).

 

 

Edited May 8, 2021 by iGPU

[iGPU]

@fabiosun

 

My card did not arrive this week. I think I got scammed off eBay; the seller supposedly sold 6 pieces but has no reviews themselves. The seller has not responded to my messaging and never supplied a tracking number. I'll have to open a file with eBay.

 

Meanwhile, I ordered another 6900XT on Thursday and it should arrive middle of next week (TN was supplied).

 

Edited May 8, 2021 by iGPU

[fabiosun]

@iGPU

mine should arrive on Wednesday from AMD..some doubts here ..because i am very happy (for Windows site) of my 3090 FE

 

[iGPU]

In case anyone is interested, I posted a reply on another forum here, on how to use the RestrictEvents kext to rename your CPU in the "About This Mac" box:

 

 

Attached is the latest commit of RestrictEvents, enabled as shown below:

 

RestrictEvents.kext.zip

[Jaidy]

for the people running Gigabyte motherboards using F4q bios, do you have the problem we previously had when shutdown would lead to a restart? I have set the "Wake on LAN" to be disabled in the bios, but it still restarts when I shutdown. 

[fabiosun]

@Jaidy

have you checked if Mmios are correct?

 

[Arrakis]

@Jaidy it's the values in MMIO list that have changed. I had the exact same problem when I built the Hackintosh

[Arrakis]

On 5/8/2021 at 4:53 PM, iGPU said:

@Arrakis

 

I think you're having a TB-USB kernel panic (there is a new firmware to flash onto the card that stops kernel panics with BS > 11.3, but beyond scope of this thread;  see here for more details). Remove the TB card, re-boot and if no more freezes, then it was the TB AIC's USB generating the kernel panic.

 

The screen artifacts during boot, when WEG is disabled, is normal and of no concern. WEG simply suppresses them (they began with Catalina).

 

 

@IGPU it's a problem with the thunderbolt card but I'm not sure it's the flash version because when I disable SSDTs (SSDT-TBOLT3-NVM23 & SSDT-DTGP.aml).

I don't have Kernel panic anymore. The system can see the card and the peripherals plugged into it. (See Screen capture) but inoperative.

The flash I used was TitanRidgeNVM23-E64Fr.

Do you have any idea what's wrong with these SSDTs? (both are from the EFI Meina22 so you have to work together for the proper functioning of the hot plugging)

 

 

In my multis tests, I noticed that the Kext: SmallTreeIntel82576.kext was useless for the ethernet card installed on Gigabyte Designare motherboards (Intel I210) because the Kext is already installed in the OS. (See Screen capture)

But oddly on Big Sur 11.4 beta2 not functional and the kext: SmallTreeIntel82576.kext is inoperative.

However, the wifi works with IntelBluetoothFirmware, IntelBluetoothInjector, AirportItlwm on Big Sur 11.3.1 and Big Sur 11.4. Beta2.

 

And still no PCI implementation error message in SMBIOS MacPro 2019.
One difference from your simplified kernel patches is that I am forced to keep the occurrence (cpu_topology_sort -disable _x86_validate_topology) enabled with this motherboard.

 

Edited May 10, 2021 by Arrakis