Jump to content

TRX40 Bare Metal - Vanilla Patches (Yes it works...but..is Proxmox better?)


Recommended Posts

Posted (edited)

 

@Arrakis

 

I've had no problems running any of the latest BS betas, after removing my TB AIC. There are some similarities between our Kernels, etc, but some differences. I've created a "mini-EFI" folder for you. It contains a config file (current to early v070), an abbreviated ACPI folder, and a kexts folder.

 

The changes you might want to make (besides the obvious filling in of SNs and memory entries) are to enable SSDT #7 if you're using a PCIe WLAN card. (My setup is a bit complicated as I originally swapped out the internal card for an Broadcom-Apple compatible card, which I'm no longer using but don't wish to remove; now I'm using a PCIe AX200 card.) Leave this SSDT disabled if you're using the internal AX200.

 

In the Kernel section, I've replaced Itlwm with AirportItlwm specifically for Big Sur; this works better. There are other additions here that you may want to disable such as the USBInjectAll set, which I use with an SSDT (but that's mobo specific, so I've not included those in the ACPI folder).

 

The patches in the Kernel section are a bit different, run these as is and see how they work.

 

Finally, you may need to adjust the MMIOWhitelist entries for your mobo. The included ones are for my MSI Creator mobo and yours will likely be different. 

 

If you have any issues or questions, ask.

 

 

 

Edited by iGPU
  • +1 1
Link to post
Share on other sites
6 minutes ago, Ploddles said:

 

I've just had a look at your update and am now a bit confused, easily done though 😀

 

Whenever I have extracted the values via the debug version of OC, every single entry has skip 0, not a single skip 1. I must be doing something wrong as this would suggest that I don't need any values in the mmiowhitelist section. In the config file I had no entries in the whitelist whilst I extracting them to the text file.

 

The debug version I use is a good few months old so I will download the latest and test again. There was also no difference between having Above 4G enabled/disabled.

 

  Hide contents

0xC7100000 (0x81 pages, 0x8000000000000001) skip 0

0xCF180000 (0x81 pages, 0x8000000000000001) skip 0

0xD7180000 (0x81 pages, 0x8000000000000001) skip 0

0xD7300000 (0x100 pages, 0x8000000000000001) skip 0

0xDF100000 (0x181 pages, 0x8000000000000001) skip 0

0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0

0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0

0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0

0xFED00000 (0x1 pages, 0x8000000000000001) skip 0

0xFED40000 (0x5 pages, 0x8000000000000001) skip 0

0xFED80000 (0x10 pages, 0x8000000000000001) skip 0

0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0

0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0

0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0

0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0

 

 

Maybe this is mobo specific (we're mostly in our own mobo worlds...). If that is the case, then I would enable all except the final 4 as originally suggested by Vit9696.

 

On my mobo, I can see no difference in booting or functionality, whether I enable "skip 1" entries while disabling "skip 0" entries, versus enabling all except the final 4.

  • Ok 1
Link to post
Share on other sites
7 hours ago, fabiosun said:

 

May you try with this simple one?

 

@fabiiosun 

I tried my config.plist modified by you, it's identical: extinction and reboot etc ...

Il y a 13 minutes, iGPU a déclaré :

 

@Arrakis

 

Je n'ai eu aucun problème à exécuter l'une des dernières bêtas BS, après avoir supprimé mon AIC TB. Il y a quelques similitudes entre nos noyaux, etc., mais quelques différences. J'ai créé un dossier "mini-EFI" pour vous. Il contient un fichier de configuration (actuel à la v070 initiale), un dossier ACPI abrégé et un dossier kexts.

 

Les modifications que vous voudrez peut-être apporter (en plus du remplissage évident des SN et des entrées de mémoire) sont d'activer SSDT #7 si vous utilisez une carte WLAN PCIe. (Ma configuration est un peu compliquée car j'ai initialement remplacé la carte interne par une carte compatible Broadcom-Apple, que je n'utilise plus mais que je ne souhaite pas supprimer ; maintenant, j'utilise une carte PCIe AX200.) Laissez ce SSDT désactivé si vous utilisez l'AX200 interne.

 

Dans la section Kernel, j'ai remplacé Itlwm par AirportItlwm spécifiquement pour Big Sur ; cela fonctionne mieux. Il y a d'autres ajouts ici que vous voudrez peut-être désactiver, tels que l'ensemble USBInjectAll, que j'utilise avec un SSDT (mais c'est spécifique à mobo, donc je n'ai pas inclus ceux-ci dans le dossier ACPI).

 

Les correctifs de la section noyau sont un peu différents, exécutez-les tels quels et voyez comment ils fonctionnent.

 

Enfin, vous devrez peut-être ajuster les entrées MMIOWhitelist pour votre mobo. Les inclus sont pour mon mobo MSI Creator et le vôtre sera probablement différent.

 

Si vous avez des problèmes ou des questions, posez-en.

 

 

mini-EFI.zip24,11 MB · 0 téléchargements

@iGPU it's super cool, thank you so much. i will try your mini EFI and i will get back to you.

Link to post
Share on other sites

@valmeida

HERE is a debug EFI. It is a few months old but that doesn't matter. Nor does it matter if your system boots or fails along the way. Copy it onto a USB stick and boot with it. If the system doesn't go into macOS after a minute or so reboot with your normal EFI to get into your system. In the root of the USB stick there will be a text file, with todays date in it, and the MMIO values will be somewhere in that text file. You then need to convert the hex values to base10 for your whitelist.

Link to post
Share on other sites
Posted (edited)
26 minutes ago, valmeida said:

This sounds like a silly question but can someone help me with my OC so that I can pull logs to update my MMIO whitelist . EFI.zip

 

First, you need to be running the Debug version of OC, not the Release version. Download either version here.

 

Then, you need to change the Misc/Debug section to look like this:

 

1733713729_ScreenShot2021-05-11at11_24_48AM.thumb.png.958e2dd693b2698894b7b2dbd49e0a1b.png

 

Finally, simply boot into macOS and look at the EFI partition to retrieve your text files. (Even if it won't fully boot into macOS, the files are written out onto the EFI partition, which you can later see if you boot using a Release version.)

 

 

 

Edited by iGPU
  • Like 1
Link to post
Share on other sites
Posted (edited)
51 minutes ago, Arrakis said:

 

@Arrakis

 

Je n'ai eu aucun problème à exécuter l'une des dernières bêtas BS, après avoir supprimé mon AIC TB. Il y a quelques similitudes entre nos noyaux, etc., mais quelques différences. J'ai créé un dossier "mini-EFI" pour vous. Il contient un fichier de configuration (actuel à la v070 initiale), un dossier ACPI abrégé et un dossier kexts.

 

Les modifications que vous voudrez peut-être apporter (en plus du remplissage évident des SN et des entrées de mémoire) sont d'activer SSDT #7 si vous utilisez une carte WLAN PCIe. (Ma configuration est un peu compliquée car j'ai initialement remplacé la carte interne par une carte compatible Broadcom-Apple, que je n'utilise plus mais que je ne souhaite pas supprimer ; maintenant, j'utilise une carte PCIe AX200.) Laissez ce SSDT désactivé si vous utilisez l'AX200 interne.

 

Dans la section Kernel, j'ai remplacé Itlwm par AirportItlwm spécifiquement pour Big Sur ; cela fonctionne mieux. Il y a d'autres ajouts ici que vous voudrez peut-être désactiver, tels que l'ensemble USBInjectAll, que j'utilise avec un SSDT (mais c'est spécifique à mobo, donc je n'ai pas inclus ceux-ci dans le dossier ACPI).

 

Les correctifs de la section noyau sont un peu différents, exécutez-les tels quels et voyez comment ils fonctionnent.

 

Enfin, vous devrez peut-être ajuster les entrées MMIOWhitelist pour votre mobo. Les inclus sont pour mon mobo MSI Creator et le vôtre sera probablement différent.

 

Si vous avez des problèmes ou des questions, posez-en.

 

 

@iGPU it's super cool, thank you so much. i will try your mini EFI and i will get back to you.

 

I did not know that I spoke French so well! :classic_wink:

 

Maybe it's because I finished watching all seasons of The Bureau (Le Bureau des Legendes), Spiral (Engrenages) and Wonderland.

 

 

Edited by iGPU
  • whahahah 1
Link to post
Share on other sites
3 minutes ago, iGPU said:

 

I did not know that I spoke French so well! :classic_wink:

 

Maybe it's because I finished watching all seasons of The Bureau (Le Bureau des Legendes), Spiral (Engrenages) and Wonderland.

 

 

@iGPU it's your super powers🤪

  • whahahah 1
Link to post
Share on other sites
18 hours ago, iGPU said:

 

First, you need to be running the Debug version of OC, not the Release version. Download either version here.

 

Then, you need to change the Misc/Debug section to look like this:

 

1733713729_ScreenShot2021-05-11at11_24_48AM.thumb.png.958e2dd693b2698894b7b2dbd49e0a1b.png

 

Finally, simply boot into macOS and look at the EFI partition to retrieve your text files. (Even if it won't fully boot into macOS, the files are written out onto the EFI partition, which you can later see if you boot using a Release version.)

 

 

 

Thanks done.

Link to post
Share on other sites
  • Supervisor

I have weird reboot in my system

I have a very dirty installation but some problems is there

No thunderbolt inserted in my case

i have updated to 069 and Macpro7.1 

i will try to use imacpro and see later if problems persist

 

 

Link to post
Share on other sites

@iGPU @fabiosun

I did the test to remove the Titan Ridge card and my problem is still there. We can therefore definitively exclude a possible problem related to the thunderbolt.

 

What tickles me from the start is that the motherboard ethernet module is not recognized under 11.4 while under 10.15 to 11.3.1 it has always been recognized.

 

For what reason under 11.4. beta3 the system points to the wrong folder for the ethernet module extension ?

Why ?

 

Is there a way in Open-Core to assign the correct folder ?

 

I have checked in IONetworkingfamily.kext and its plugins. Nothing has changed.

699080106_Capturedecran2021-05-12a15_27_12.thumb.png.2f9355755df431c48dfeaf5e8718ee72.png214242624_Capturedecran2021-05-12a15_22_34.thumb.png.8148ac3fb2321653050f3c78d42f20e9.png

Link to post
Share on other sites
1 minute, fabiosun a dit :

J'ai un redémarrage bizarre dans mon système

J'ai une installation très sale mais quelques soucis sont là

Aucun coup de tonnerre inséré dans mon étui

j'ai mis à jour vers 069 et Macpro7.1

je vais essayer d'utiliser imacpro et voir plus tard si les problèmes persistent

 

 

I have already tried with iMacpro 1.1 it is identical.

I have tried with OpenCore 0.6.8 too. I will try again now because I have done a lot of testing and I have some doubts.

Link to post
Share on other sites
  • Supervisor

with my old EFi with iMac Pro 1.1 Smbios I can boot without WEG but I have only a monitor available (hdmi port)

With WEG and same SMBIOS I have black display output before login

I will test with only HDMI and my old EFI

Not trust so much of new SMBIOS for my rig..never used before and I have no comparative test on stability (in previous OS my system never had a reboot or a freeze)

I will try also to remove REstrictEvents kext and memory cosmetic part..

it is. beta but weird behaviour here

 

Link to post
Share on other sites
  • Supervisor

I have removed only the kext..system is stable...no weird reboot for now

let we see 🙂

 

Link to post
Share on other sites
4 hours ago, Arrakis said:

@iGPU @fabiosun

I did the test to remove the Titan Ridge card and my problem is still there. We can therefore definitively exclude a possible problem related to the thunderbolt.

 

What tickles me from the start is that the motherboard ethernet module is not recognized under 11.4 while under 10.15 to 11.3.1 it has always been recognized.

 

For what reason under 11.4. beta3 the system points to the wrong folder for the ethernet module extension ?

Why ?

 

Is there a way in Open-Core to assign the correct folder ?

 

I have checked in IONetworkingfamily.kext and its plugins. Nothing has changed.

699080106_Capturedecran2021-05-12a15_27_12.thumb.png.2f9355755df431c48dfeaf5e8718ee72.png214242624_Capturedecran2021-05-12a15_22_34.thumb.png.8148ac3fb2321653050f3c78d42f20e9.png

 

Upload your IORE file, I'd like to study it (with TB AIC in place).

 

Link to post
Share on other sites
45 minutes ago, fabiosun said:

I have removed only the kext..system is stable...no weird reboot for now

let we see 🙂

 

 

Lately, I've been shutting down the computer at night as I've not had any stability issues to study. However, I left computer on last night (running latest beta 4 and with RestrictEvents enabled) and this morning the computer was off. On restart, I got a macOS warning of a crash, so I seemed to have had a shutdown over night. 

 

The Memory section does not add to any stability problems; I checked that last week (and it's part of OC, not RestrictEvents). It sounds like RestrictEvents is the cuilprit.

 

I'm at work now but I'll study later tonight to see if I get a shutdown again, but it must have happened a few hours into the boot, so it might take some time to sort out. (Today the 6900XT is scheduled to arrive and it I exchange the GPU, that might add to any stability issues.)

 

 

Link to post
Share on other sites
  • Supervisor

today I haven't  had any weird reboot

@iGPUmemory plist is up and also MacPro7.1

I have removed only kext 

 

As side note I would like to say that also new Davinci Resolve 17.2 works without any library patch

 

 

  • +1 1
Link to post
Share on other sites
1 hour ago, fabiosun said:

today I haven't  had any weird reboot

@iGPUmemory plist is up and also MacPro7.1

I have removed only kext 

 

As side note I would like to say that also new Davinci Resolve 17.2 works without any library patch

 

 

I confirm for the version of Resolve 17.2. It works without the patch.

Link to post
Share on other sites
Posted (edited)

@Arrakis

 

I looked at the LAN section of your IORE file (BTW, the TB  section is PERFECT!):

 

TRX40-GB-Designare-LAN.jpg.20700e8df0eeeadbe76b66e186cebaad.jpg

 

Was the IORE file without a LAN kext? It looks good as is (and maybe needs a DeviceProperties injection).

 

If a kext was used and the LAN was not working, then maybe try the one I've attached.

 

Also, can you upload the txt or plist file from Hackintool for the PCI section for your mobo? If you do, I can work up a DeviceProperties injection for you to maybe enable better LAN functionality.

 

 

 

 

SmallTreeIntel82576-I211.kext.zip

Edited by iGPU
Link to post
Share on other sites

6900XT working, using WEG with boot-arg. RestrictEvents left active; will leave on and see if stable.

 

1616623679_6900XTRestrictEvents.thumb.png.5f6528e99f549eab9f29c50ae9841283.png

  • Like 1
Link to post
Share on other sites
7 hours ago, Arrakis said:

@iGPU 

Here is the .txt file of the PCI implementation. There is no improvement under Big Sur 11.4. beta 3 with your SmallTreeIntel82576-I211.kext for the ethernet module.

I attach the config.plist of my current setup which works fine on Big Sur 11.3.1.

PCI DEVICES ARRAKIS.zip 13.72 kB · 1 download config arrakis.plist.zip 6.83 kB · 0 downloads

 

Try adding the code below into your Device/Properties section to see if that helps. (You should try this ± SmallTreeIntel82576 kext.)

 

From the pcidevices list, I see that you have IOMMU enabled. This is required for VM, but not bare metal. I keep it disabled. I don't know if this would have any influence on LAN behavior; I've never checked. Disabling it might affect MMIOWhitelist. Also in BIOS, do you have Wake on LAN disabled?

 

Spoiler

            <key>PciRoot(0x2)/Pci(0x1,0x1)/Pci(0x0,0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
			<dict>
				<key>AAPL,slot-name</key>
				<string>Built in</string>
				<key>built-in</key>
				<data>
				AA==
				</data>
				<key>device_type</key>
				<string>Ethernet Controller</string>
				<key>model</key>
				<string>Intel I210 Gigabit Network Connection</string>
				<key>name</key>
				<string>Intel I210 Ethernet</string>
			</dict>
			<key>PciRoot(0x2)/Pci(0x1,0x1)/Pci(0x0,0x0)/Pci(0x5,0x0)/Pci(0x0,0x0)</key>
			<dict>
				<key>AAPL,slot-name</key>
				<string>Built in</string>
				<key>built-in</key>
				<data>
				AA==
				</data>
				<key>device_type</key>
				<string>Ethernet Controller</string>
				<key>model</key>
				<string>Intel I210 Gigabit Network Connection</string>
				<key>name</key>
				<string>Intel I210 Ethernet</string>
			</dict>

 

 

Link to post
Share on other sites
  • fabiosun changed the title to TRX40 Bare Metal - Vanilla Patches (Yes it works...but..is Proxmox better?)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   1 member

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.