Jump to content

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


Recommended Posts

I've left the computer on for ~14 hours with no crash or reboot with new 6900XT GPU, using 11.4 Beta (20F5065a). 

 

RestrictEvents was enabled; using MacPro7,1 SMBIOS. So, I'm not certain what led to previous reboots.

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

@iGPUlatest OC and kext version?

 

 

Yes, I use latest OC commits from here (presently booting with v070, 4cdd360. I update daily (sometimes more often :classic_rolleyes:).

 

I also run ocvalidate (inside OC/Utilities/ocvalidate folder) on current config.plist file to ensure there are no errors; sometimes the docs are behind and ocvalidate will pick up structural changes. Each commit has an updated ocvalidate, so you must use the latest version of ocvalidate to avoid mistakes.

 

The RestrictEvents is also latest (use pop-up box at upper left to navigate amongst the various kexts): here.

 

 

Edited by iGPU
  • Like 1
Link to post
Share on other sites
  • Supervisor

I am using release version and without RestricEvents kext no problem

it is difficult to track this..maybe an OSX beta bug or bootloader stuff

i do not know for now 🙂

Happy of your 6900xt? 🙂

 

Link to post
Share on other sites
15 hours ago, iGPU said:

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

Just curious, where did you get that?

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

I am using release version and without RestricEvents kext no problem

it is difficult to track this..maybe an OSX beta bug or bootloader stuff

i do not know for now 🙂

Happy of your 6900xt? 🙂

 

 

I've only done minimal testing (and I've left on "silent", not "OC", mode). The GPU is so far a bit underwhelming: LuxMark not much better than the Radeon VII results (and the PowerColor 6900XT takes up 3 slots!, so dual cards not possible). Since I never game (I've never seen a purpose in  playing computer or board games; my life is too busy), the 6900XT may not a benefit for my build. But I'll test some more. DaVinci will be interesting (as I actually use it), to see if one 6900XT is close to my old dual Radeon VII set up.

11 minutes ago, A23SS4NDRO said:

Just curious, where did you get that?

 

The 6900XT? eBay.

Link to post
Share on other sites
  • Supervisor
2 minutes ago, iGPU said:

 

I've only done minimal testing (and I've left on "silent", not "OC", mode). The GPU is so far a bit underwhelming: LuxMark not much better than the Radeon VII results (and the PowerColor 6900XT takes up 3 slots!, so dual cards not possible). Since I never game (I've never seen a purpose in  playing computer or board games; my life is too busy), the 6900XT may not a benefit for my build. But I'll test some more. DaVinci will be interesting (as I actually use it), to see if one 6900XT is close to my old dual Radeon VII set up.

 

have you tried Candle Davinci benchmark with your dual radeon rig?

Could be interesting to compare with your new GPU

 

Link to post
Share on other sites
5 hours ago, iGPU said:

 

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?

 

  Reveal hidden contents


            <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>

 

 

@iGPU

I have proceeded in order of suggestion.

 1. I have disabled iommu in the bios (deactivation does not modify the MMIO) which I will keep like that anyway: identical problem, kernel panic or freeze, no recognition of the Intel I210 module.

2. Addition of the codes in Device / Properties: identical problem, kernel panic or freeze, recognition of the Intel I210 module but inactive. (Capture 1)

3. Addition of the SmallTreeIntel82576 kext: identical problem, panic or freeze kernel, recognition of the Intel I210 module but inactive. (Capture 1)

4. Deactivation of the codes in Device / Properties: identical problem, kernel panic or freeze, no recognition of the Intel I210 module but inactive. (Capture 1)

5. Wake on Lan has been disabled since the start of my hack.

 

I still don't understand why the system is loading the wrong kext in the wrong folder. While this Intel I210 is present in the kext of the IONetworkingFamily system (Capture 2)

Why does the system choose this AppleEthernet1000 module?

2066419707_Capturedecran2021-05-13a20_25_28.thumb.png.9bc6ec96ed0490ac13262f2cc102fc90.png1475518770_Capturedecran2021-05-13a22_36_33.thumb.png.1ff7c7211fac26d2f9eae6508fb06b61.png

 

Link to post
Share on other sites
Posted (edited)
18 hours ago, Arrakis said:

@iGPU

I have proceeded in order of suggestion.

 1. I have disabled iommu in the bios (deactivation does not modify the MMIO) which I will keep like that anyway: identical problem, kernel panic or freeze, no recognition of the Intel I210 module.

2. Addition of the codes in Device / Properties: identical problem, kernel panic or freeze, recognition of the Intel I210 module but inactive. (Capture 1)

3. Addition of the SmallTreeIntel82576 kext: identical problem, panic or freeze kernel, recognition of the Intel I210 module but inactive. (Capture 1)

4. Deactivation of the codes in Device / Properties: identical problem, kernel panic or freeze, no recognition of the Intel I210 module but inactive. (Capture 1)

5. Wake on Lan has been disabled since the start of my hack.

 

I still don't understand why the system is loading the wrong kext in the wrong folder. While this Intel I210 is present in the kext of the IONetworkingFamily system (Capture 2)

Why does the system choose this AppleEthernet1000 module?

2066419707_Capturedecran2021-05-13a20_25_28.thumb.png.9bc6ec96ed0490ac13262f2cc102fc90.png1475518770_Capturedecran2021-05-13a22_36_33.thumb.png.1ff7c7211fac26d2f9eae6508fb06b61.png

 

 

@Arrakis

 

Ok, some more approaches...

 

1) First try one more kext (attached). This one (SmallTreeIntel82576_mod.kext), I'd modified in 2019 (it works with I211 and with I210), adding a 'root' ending to the Info.plist file that was missing from original and would give an occasional panic without.

 

Also, have you set the following in red box to "Yes" (it might help):

Spoiler

1308116394_ScreenShot2021-05-13at8_23_32PM.thumb.png.3271906bc10258ce27c9b5d5d9770ca7.png

 

 

2) Are you injecting a DSDT or SSDT that might be interfering? Specifically, I'm wondering what is inside your "SSDT-EC-USBX-DESKTOP.aml". It is possible that the 'DESKTOP' portion is a DSDT extract that may be giving you grief. Instead of enabling this aml file, disable it and use the one attached below (SSDT-TRX40-USBX.aml).

 

BTW, if you want to get a summary of all loaded, non-Apple kext files, enter the following into Terminal:

Kextstat | grep -v com.apple

 

My results are in Spoiler below:

Spoiler

Executing: /usr/bin/kmutil showloaded

No variant specified, falling back to release

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

   49    7 0                  0x2e000    0x2e000    as.vit9696.Lilu (1.5.3) A4C0AB78-C141-3DC5-812F-93408D94A4D7 <8 6 5 3 2 1>

   50    0 0                  0x82000    0x82000    as.vit9696.WhateverGreen (1.4.9) A894BFF2-1A53-30BC-9398-4A3CF1F2E438 <49 14 8 6 5 3 2 1>

   51    0 0                  0x17f000   0x17f000   as.vit9696.AppleALC (1.6.0) DDD8C0F0-0F68-3097-B152-5DA55047637F <49 14 8 6 5 3 2 1>

   52    0 0                  0xd000     0xd000     org.acidanthera.NVMeFix (1.0.7) 423AF334-A79C-3DBF-8961-C8B4E3B0FBCA <49 8 6 5 3 2 1>

   53    0 0                  0x8000     0x8000     xyz.racermaster.NoTouchID (1.0.4) 37FB0D35-0838-317F-9A2A-A0090D85B7D5 <49 8 6 5 3 2 1>

   54    0 0                  0x10000    0x10000    com.rehabman.driver.USBInjectAll (0.7.6) 6C5A1DEA-E541-3792-81AF-D18B6E8D4877 <14 13 5 3>

   55    0 0                  0xc000     0xc000     as.vit9696.RestrictEvents (1.0.2) 5D71A5EA-F38C-348E-BDD7-F4E85A8D548B <49 8 6 5 3 2 1>

   56    0 0                  0x20000    0x20000    wtf.spinach.AMDRyzenCPUPowerManagement (0.6.5) B95928B3-A63F-3633-8D3B-72A5C1D79451 <49 14 9 8 6 5 3 2 1>

   67    0 0                  0x8000     0x8000     com.osy86.USBWakeFixup (1) 36390E0E-C19D-3B81-BDAD-AB8C7A147B8C <13 5 3>

   68    0 0                  0x1a000    0x1a000    as.vit9696.VirtualSMC (1.2.3) 72DED745-B559-3CB5-9F88-CD9531E38098 <49 13 8 6 5 3 2 1>

   80    0 0                  0xd5b000   0xd5b000   com.zxystd.AirportItlwm (1.3.0) A2ED57F8-46E0-3D99-A26D-55A1B1FD7873 <79 47 14 6 5 3 1>

   89    0 0                  0x2e000    0x2e000    com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <47 14 6 5 3 1>

   99    0 0                  0xecc000   0xecc000   com.zxystd.IntelBluetoothFirmware (1.1.2) 3BD877FB-7CD5-3E57-A9E8-A0F07BF78140 <22 6 5 3>

  150    0 0xffffff7f9cd3a000 0x3000     0x3000     com.Sonarworks.driver.Sonarworks (1.8.11) EB8C008E-8442-36E1-AEA6-2C9717CD3D71 <121 6 5 3 1>

 

 

3) The next approach is to create a kext patch. Try the attached code shown in the Spoiler below, if the above SSDT swap does not work.

 

Spoiler


			<dict>
				<key>Arch</key>
				<string>Any</string>
				<key>Base</key>
				<string></string>
				<key>Comment</key>
				<string>I210 Big Sur</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Enabled</key>
				<true/>
				<key>Find</key>
				<data>
				YnVpbHQtaW4=
				</data>
				<key>Identifier</key>
				<string>com.apple.driver.AppleIntelI210Ethernet</string>
				<key>Limit</key>
				<integer>0</integer>
				<key>Mask</key>
				<data>
				</data>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>Replace</key>
				<data>
				YmJiYmJiYmI=
				</data>
				<key>ReplaceMask</key>
				<data>
				</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

 

 

 

4) Finally, what about trying to inject AppleIntelI210Ethernet.kext? Attached is one I extracted from the latest Big Sur beta. If you use this, I'd try with and without the SmallTree82576 kext enabled, listing the SmallTree after AppleIntelI210Ethernet kext as in Spoiler.

Spoiler


			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AppleIntelI210Ethernet.kext</string>
				<key>Comment</key>
				<string>Intel I210</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AppleIntelI210Ethernet</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>SmallTreeIntel82576_mod.kext</string>
				<key>Comment</key>
				<string>Intel I211 LAN Patches</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/SmallTreeIntel82576</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>18.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

 

 

 

In any of these situations, you can probably still use the Device/Properties stuff I uploaded earlier. In fact, in Comet Lake mobos, AppleIntelI210Ethernet can have a kernel panic that is only resolved with a DeviceProperties injection (see here).

 

Also, remember to try re-setting NVRAM.

 

***

 

If the I210 works, you should see sometime like I see for I211:

Spoiler

336605208_ScreenShot2021-05-13at3_31_21PM.thumb.png.20fe9eb60a9674d5444fc8f6a289ec66.png

 

 

1097847881_ScreenShot2021-05-13at4_18_04PM.thumb.png.8030fe9d8fc47e2e117795a4b16727ea.png

 

 

 

SDDT-TRX40-USBX.aml.zipSmallTreeIntel82576_mod.kext.zip

AppleIntelI210Ethernet.kext.zip

Edited by iGPU
  • Like 1
Link to post
Share on other sites
6 hours ago, fabiosun said:

have you tried Candle Davinci benchmark with your dual radeon rig?

Could be interesting to compare with your new GPU

 

 

Yes, I posted the dual Radeon VII results back on 9/9/21, here with an early version of BS beta. (The debate at the time was if bare metal was as good as VM.)

 

  • Like 1
Link to post
Share on other sites
  • Supervisor

@iGPU thank you

in 66 nodes condition dual radeon VII rig is about 8% faster than a single 6900 xt at this drivers development stage..

so i can say it is worth to update to big Navi 2

Link to post
Share on other sites
Posted (edited)
On 5/13/2021 at 10:59 PM, fabiosun said:

@iGPU thank you

in 66 nodes condition dual radeon VII rig is about 8% faster than a single 6900 xt at this drivers development stage..

so i can say it is worth to update to big Navi 2

 

The one annoyance I'm seeing (hearing), is noise coming through my USB audio interface (and this is with the interface muted).

 

If nothing on the computer is used, the speakers are quiet. If I scroll a window, I get a noise proportional to the amount of scroll. If I run a GPU test, the noise gets louder, disappearing once the test is complete. I did not have this with the Radeon VIIs or the RX580. I dislike hums and buzzes in my audio systems. It reminds me of the occasional Vega 64 coil whine, but this is worse.

 

If this doesn't improved, I'll sell the 6900XT. I'd rather have a slow, quiet GPU than a fast, noisy one.

 

 

UPDATE:

 

Better. I was lazy on 1st install and only connected 2 power supply (PS) cables with a jumper from one of these for the 3rd PS jack.

 

Today, I installed a 3rd PCIe PS cable for the GPU, and noise is reduced (not zero, but close enough). The reason to add 3 discrete PS cables rather than use a jumper from one cable is to minimize PS sag. While the new AMD GPUs are more efficient, they require a lot of power under load and this can lead to sag. When the PS sags, it can modulate the PS coils on the GPU, leading to buzz and other noises.

 

In the next day or two, I'll be adding some ferrite collars around the USB cables: one simple clamp on (high freq block) and at the other end, a loop clamp on (lower freq block). Hopefully that will eliminate most all noise. Another option I may try out is a USB filter (they come in various plug shaped combinations).

 

 

2nd UPDATE (5/15/21):

 

Neither the ferrite beads nor the USB filter worked to remove the noise.

 

What did work was an isolation transformer (here; these are rather expensive due to the high quality Jensen transformers, fortunately I already had one from another project). All became quiet once the transformer was placed between the output jacks of the USB Audio Interface and the speakers. This fix suggests that there is a ground loop somewhere in the computer/GPU/PS section that the GPU is modulating.

 

Edited by iGPU
  • Thanks 1
Link to post
Share on other sites
  • Supervisor

Internal USB realtek 2.0 audio?

I have no tried my chip USB external audio, but i cant see any noise

I have read some have coil whine problem..in my case with 2 6900xt reference had ..zero problem (3090 had a little coilwhine..not so much audible but it was there

 

Link to post
Share on other sites
1 hour ago, A23SS4NDRO said:

How many kidneys did it cost?

 

Both, but they threw in a free dialysis unit.

  • +1 2
Link to post
Share on other sites
Posted (edited)
40 minutes ago, A23SS4NDRO said:

XD

 

seriously, do you mind to tell the price?

 

1600 USD.

 

(But I'm still waiting for refund from eBay for the 1300 I spent for 1st 6900XT that seems now to have been from a scammer.)

 

Edited by iGPU
Link to post
Share on other sites

I updated my above post regarding 6900XT noise.

 

It is now better and should further improve with some more changes.

 

  • +1 1
Link to post
Share on other sites
Le 14/05/2021 à 01:19, iGPU a déclaré :

 

@Arrakis

 

Ok, d'autres approches...

 

1) Essayez d'abord un kext de plus (ci-joint). Celui-ci (SmallTreeIntel82576_mod.kext), que j'avais modifié en 2019 (il fonctionne avec I211 et I210), en ajoutant une fin "root" au fichier Info.plist qui manquait à l'original et qui donnerait une panique occasionnelle sans.

 

En outre, avez-vous défini ce qui suit dans la boîte rouge sur "Oui" (cela pourrait vous aider) :

  Révéler le contenu caché

1308116394_ScreenShot2021-05-13at8_23_32PM.thumb.png.3271906bc10258ce27c9b5d5d9770ca7.png

 

 

2) Injectez-vous un DSDT ou un SSDT qui pourrait interférer ? Plus précisément, je me demande ce qu'il y a à l'intérieur de votre "SSDT-EC-USBX-DESKTOP.aml". Il est possible que la partie "DESKTOP" soit un extrait de DSDT qui peut vous donner du chagrin. Au lieu d'activer ce fichier aml, désactivez-le et utilisez celui ci-dessous (SSDT-TRX40-USBX.aml).

 

BTW, si vous souhaitez obtenir un résumé de tous les fichiers kext chargés non Apple, entrez ce qui suit dans Terminal :

Kextstat | grep -v com.apple

 

Mes résultats sont dans Spoiler ci-dessous :

  Révéler le contenu caché

Executing: /usr/bin/kmutil showloaded

No variant specified, falling back to release

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

   49    7 0                  0x2e000    0x2e000    as.vit9696.Lilu (1.5.3) A4C0AB78-C141-3DC5-812F-93408D94A4D7 <8 6 5 3 2 1>

   50    0 0                  0x82000    0x82000    as.vit9696.WhateverGreen (1.4.9) A894BFF2-1A53-30BC-9398-4A3CF1F2E438 <49 14 8 6 5 3 2 1>

   51    0 0                  0x17f000   0x17f000   as.vit9696.AppleALC (1.6.0) DDD8C0F0-0F68-3097-B152-5DA55047637F <49 14 8 6 5 3 2 1>

   52    0 0                  0xd000     0xd000     org.acidanthera.NVMeFix (1.0.7) 423AF334-A79C-3DBF-8961-C8B4E3B0FBCA <49 8 6 5 3 2 1>

   53    0 0                  0x8000     0x8000     xyz.racermaster.NoTouchID (1.0.4) 37FB0D35-0838-317F-9A2A-A0090D85B7D5 <49 8 6 5 3 2 1>

   54    0 0                  0x10000    0x10000    com.rehabman.driver.USBInjectAll (0.7.6) 6C5A1DEA-E541-3792-81AF-D18B6E8D4877 <14 13 5 3>

   55    0 0                  0xc000     0xc000     as.vit9696.RestrictEvents (1.0.2) 5D71A5EA-F38C-348E-BDD7-F4E85A8D548B <49 8 6 5 3 2 1>

   56    0 0                  0x20000    0x20000    wtf.spinach.AMDRyzenCPUPowerManagement (0.6.5) B95928B3-A63F-3633-8D3B-72A5C1D79451 <49 14 9 8 6 5 3 2 1>

   67    0 0                  0x8000     0x8000     com.osy86.USBWakeFixup (1) 36390E0E-C19D-3B81-BDAD-AB8C7A147B8C <13 5 3>

   68    0 0                  0x1a000    0x1a000    as.vit9696.VirtualSMC (1.2.3) 72DED745-B559-3CB5-9F88-CD9531E38098 <49 13 8 6 5 3 2 1>

   80    0 0                  0xd5b000   0xd5b000   com.zxystd.AirportItlwm (1.3.0) A2ED57F8-46E0-3D99-A26D-55A1B1FD7873 <79 47 14 6 5 3 1>

   89    0 0                  0x2e000    0x2e000    com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <47 14 6 5 3 1>

   99    0 0                  0xecc000   0xecc000   com.zxystd.IntelBluetoothFirmware (1.1.2) 3BD877FB-7CD5-3E57-A9E8-A0F07BF78140 <22 6 5 3>

  150    0 0xffffff7f9cd3a000 0x3000     0x3000     com.Sonarworks.driver.Sonarworks (1.8.11) EB8C008E-8442-36E1-AEA6-2C9717CD3D71 <121 6 5 3 1>

 

 

3) La prochaine approche consiste à créer un patch kext. Essayez le code ci-joint affiché dans le spoiler ci-dessous, si l'échange SSDT ci-dessus ne fonctionne pas.

 

  Masquer le contenu


			<dict>
				<key>Arch</key>
				<string>Any</string>
				<key>Base</key>
				<string></string>
				<key>Commentaire</key>
				<string>I210 Big Sur</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Activé</key>
				<true/>
				<key>Find</key>
				<données>				 YnVpbHQtaW4=				 </data>
				<key>Identifier</key>
				<string>com.apple.driver.AppleIntelI210Ethernet</string>
				<key>Limit</key>
				<integer>0</integer>
				<key>Masque</key>
				<données>
				</data>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>Remplacement</key>
				<données>				 YmJiYmJiYmI=				 </data>
				<key>RemplacementMasque</key>
				<données>
				</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

 

 

 

4) Enfin, qu'en est-il d'essayer d'injecter AppleIntelI210Ethernet.kext ? Vous trouverez ci-joint celui que j'ai extrait de la dernière bêta de Big Sur. Si vous l'utilisez, j'essaierais avec et sans le kext SmallTree82576 activé, en répertoriant le SmallTree après AppleIntelI210Ethernet kext comme dans Spoiler.

  Révéler le contenu caché


			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AppleIntelI210Ethernet.kext</string>
				<key>Comment</key>
				<string>Intel I210</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AppleIntelI210Ethernet</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>SmallTreeIntel82576_mod.kext</string>
				<key>Comment</key>
				<string>Intel I211 LAN Patches</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/SmallTreeIntel82576</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>18.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

 

 

 

Dans n'importe laquelle de ces situations, vous pouvez probablement toujours utiliser les éléments Device/Propriétés que j'ai téléchargés plus tôt. En fait, dans les mobos de Comet Lake, AppleIntelI210Ethernet peut avoir une panique du noyau qui n'est résolue qu'avec une injection DeviceProperties (voir ici).

 

Pensez aussi à essayer de réinitialiser la NVRAM.

 

***

 

Si l'I210 fonctionne, vous devriez voir parfois comme je le vois pour I211 :

  Révéler le contenu caché

336605208_ScreenShot2021-05-13at3_31_21PM.thumb.png.20fe9eb60a9674d5444fc8f6a289ec66.png

 

 

1097847881_ScreenShot2021-05-13at4_18_04PM.thumb.png.8030fe9d8fc47e2e117795a4b16727ea.png

 

 

 

SDDT-TRX40-USBX.aml.zip1,05 kB · 1 téléchargement SmallTreeIntel82576_mod.kext.zip71,57 kB · 1 téléchargement

AppleIntelI210Ethernet.kext.zip153,82 kB · 1 téléchargement

@iGPU how to create a patch kext.  ?  to inject the code to test 3.

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

@iGPU how to create a patch kext.  ?  to inject the code to test 3.

 

I created the patch. If's in one of the Spoiler sections above (please look at all of the Spoiler sections!)

 

You simply copy from Spoiler and paste into your config.plist file:

 

kextPatch.thumb.jpg.826c7e2549b32afc6628e31fa2149d51.jpg

 

 

Edited by iGPU
Link to post
Share on other sites
13 minutes ago, iGPU said:

 

I created the patch. If's in one of the Spoiler sections above (please look at all of the Spoiler sections!)

 

You simply copy from Spoiler and paste into your config.plist file:

 

kextPatch.thumb.jpg.826c7e2549b32afc6628e31fa2149d51.jpg

 

 

@iGPU I misspoke my question, what tool do you use to insert into the config.plist ?

Link to post
Share on other sites
Posted (edited)

 

I posted some results on the GPU testing thread here, using Octane X.

 

They are as good as the revised Davinci tests I've run and posted on the same thread.

 

 

Edited by iGPU
Link to post
Share on other sites
On 5/14/2021 at 1:19 AM, iGPU said:

 

@Arrakis

 

Ok, some more approaches...

 

1) First try one more kext (attached). This one (SmallTreeIntel82576_mod.kext), I'd modified in 2019 (it works with I211 and with I210), adding a 'root' ending to the Info.plist file that was missing from original and would give an occasional panic without.

 

Also, have you set the following in red box to "Yes" (it might help):

  Reveal hidden contents

1308116394_ScreenShot2021-05-13at8_23_32PM.thumb.png.3271906bc10258ce27c9b5d5d9770ca7.png

 

 

2) Are you injecting a DSDT or SSDT that might be interfering? Specifically, I'm wondering what is inside your "SSDT-EC-USBX-DESKTOP.aml". It is possible that the 'DESKTOP' portion is a DSDT extract that may be giving you grief. Instead of enabling this aml file, disable it and use the one attached below (SSDT-TRX40-USBX.aml).

 

BTW, if you want to get a summary of all loaded, non-Apple kext files, enter the following into Terminal:

Kextstat | grep -v com.apple

 

My results are in Spoiler below:

  Reveal hidden contents

Executing: /usr/bin/kmutil showloaded

No variant specified, falling back to release

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

   49    7 0                  0x2e000    0x2e000    as.vit9696.Lilu (1.5.3) A4C0AB78-C141-3DC5-812F-93408D94A4D7 <8 6 5 3 2 1>

   50    0 0                  0x82000    0x82000    as.vit9696.WhateverGreen (1.4.9) A894BFF2-1A53-30BC-9398-4A3CF1F2E438 <49 14 8 6 5 3 2 1>

   51    0 0                  0x17f000   0x17f000   as.vit9696.AppleALC (1.6.0) DDD8C0F0-0F68-3097-B152-5DA55047637F <49 14 8 6 5 3 2 1>

   52    0 0                  0xd000     0xd000     org.acidanthera.NVMeFix (1.0.7) 423AF334-A79C-3DBF-8961-C8B4E3B0FBCA <49 8 6 5 3 2 1>

   53    0 0                  0x8000     0x8000     xyz.racermaster.NoTouchID (1.0.4) 37FB0D35-0838-317F-9A2A-A0090D85B7D5 <49 8 6 5 3 2 1>

   54    0 0                  0x10000    0x10000    com.rehabman.driver.USBInjectAll (0.7.6) 6C5A1DEA-E541-3792-81AF-D18B6E8D4877 <14 13 5 3>

   55    0 0                  0xc000     0xc000     as.vit9696.RestrictEvents (1.0.2) 5D71A5EA-F38C-348E-BDD7-F4E85A8D548B <49 8 6 5 3 2 1>

   56    0 0                  0x20000    0x20000    wtf.spinach.AMDRyzenCPUPowerManagement (0.6.5) B95928B3-A63F-3633-8D3B-72A5C1D79451 <49 14 9 8 6 5 3 2 1>

   67    0 0                  0x8000     0x8000     com.osy86.USBWakeFixup (1) 36390E0E-C19D-3B81-BDAD-AB8C7A147B8C <13 5 3>

   68    0 0                  0x1a000    0x1a000    as.vit9696.VirtualSMC (1.2.3) 72DED745-B559-3CB5-9F88-CD9531E38098 <49 13 8 6 5 3 2 1>

   80    0 0                  0xd5b000   0xd5b000   com.zxystd.AirportItlwm (1.3.0) A2ED57F8-46E0-3D99-A26D-55A1B1FD7873 <79 47 14 6 5 3 1>

   89    0 0                  0x2e000    0x2e000    com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <47 14 6 5 3 1>

   99    0 0                  0xecc000   0xecc000   com.zxystd.IntelBluetoothFirmware (1.1.2) 3BD877FB-7CD5-3E57-A9E8-A0F07BF78140 <22 6 5 3>

  150    0 0xffffff7f9cd3a000 0x3000     0x3000     com.Sonarworks.driver.Sonarworks (1.8.11) EB8C008E-8442-36E1-AEA6-2C9717CD3D71 <121 6 5 3 1>

 

 

3) The next approach is to create a kext patch. Try the attached code shown in the Spoiler below, if the above SSDT swap does not work.

 

  Reveal hidden contents


			<dict>
				<key>Arch</key>
				<string>Any</string>
				<key>Base</key>
				<string></string>
				<key>Comment</key>
				<string>I210 Big Sur</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Enabled</key>
				<true/>
				<key>Find</key>
				<data>
				YnVpbHQtaW4=
				</data>
				<key>Identifier</key>
				<string>com.apple.driver.AppleIntelI210Ethernet</string>
				<key>Limit</key>
				<integer>0</integer>
				<key>Mask</key>
				<data>
				</data>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>Replace</key>
				<data>
				YmJiYmJiYmI=
				</data>
				<key>ReplaceMask</key>
				<data>
				</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

 

 

 

4) Finally, what about trying to inject AppleIntelI210Ethernet.kext? Attached is one I extracted from the latest Big Sur beta. If you use this, I'd try with and without the SmallTree82576 kext enabled, listing the SmallTree after AppleIntelI210Ethernet kext as in Spoiler.

  Reveal hidden contents


			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AppleIntelI210Ethernet.kext</string>
				<key>Comment</key>
				<string>Intel I210</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AppleIntelI210Ethernet</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>20.0.3</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>SmallTreeIntel82576_mod.kext</string>
				<key>Comment</key>
				<string>Intel I211 LAN Patches</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/SmallTreeIntel82576</string>
				<key>MaxKernel</key>
				<string>20.99.99</string>
				<key>MinKernel</key>
				<string>18.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

 

 

 

In any of these situations, you can probably still use the Device/Properties stuff I uploaded earlier. In fact, in Comet Lake mobos, AppleIntelI210Ethernet can have a kernel panic that is only resolved with a DeviceProperties injection (see here).

 

Also, remember to try re-setting NVRAM.

 

***

 

If the I210 works, you should see sometime like I see for I211:

  Reveal hidden contents

336605208_ScreenShot2021-05-13at3_31_21PM.thumb.png.20fe9eb60a9674d5444fc8f6a289ec66.png

 

 

1097847881_ScreenShot2021-05-13at4_18_04PM.thumb.png.8030fe9d8fc47e2e117795a4b16727ea.png

 

 

 

SDDT-TRX40-USBX.aml.zip 1.05 kB · 1 download SmallTreeIntel82576_mod.kext.zip 71.57 kB · 1 download

AppleIntelI210Ethernet.kext.zip 153.82 kB · 1 download

@iGPU 

Approach n ° 1 : Doesn't work for I210 (no internet connection) and I already had DisableWatchDog enable from the start.

Approach n ° 2: Does not work for the I210 (no internet connection) but I will keep the SSDT-TRX40-USBX)

Approach n ° 3: Does not work for the I210 (no internet connection)

Approach N ° 4: Prevents the system from starting, stays on the beginning of the loading stuck eternally on the apple.

 

I did the 1,2,3,4 tests with the SSDT-EC-USBX-DESKTOP.aml and / or the SSDT-TRX40-USBX.aml) as well as the I210 Device Properties enabled or disabled.

This makes a number of test….

I even did a clean instal 11.3.1 then update to 11.4.beta 3.

The installation is absolutely problem-free with my EFI. I just changed a DSDT. I kept the SSDT-TRX40-USBX.aml.

I don't get a PCI card placement errors message the first time I log in (I don't use Kext restrict events).

And still no ethernet connection. The Wifi module works as before.

From the moment I start to order the ports for example, it is unstable. (Kernel panic….)

 

I keep the patch and the pci properties of the I210 as it works as you can see. (Screenshot)

I will wait for the next beta and the new version of OpenCore to redo the tests

I saturate and I am a little annoyed ...😞

654659344_Capturedecran2021-05-15a13_38_23.thumb.png.685557a58d743c78a3d3413347e1c54f.png

1951284232_Capturedecran2021-05-15a14_13_12.thumb.png.631ec9f961913590d65f7263c0a0b172.png

Link to post
Share on other sites
Posted (edited)
2 hours ago, Arrakis said:

@iGPU 

Approach n ° 1 : Doesn't work for I210 (no internet connection) and I already had DisableWatchDog enable from the start.

Approach n ° 2: Does not work for the I210 (no internet connection) but I will keep the SSDT-TRX40-USBX)

Approach n ° 3: Does not work for the I210 (no internet connection)

Approach N ° 4: Prevents the system from starting, stays on the beginning of the loading stuck eternally on the apple.

 

I did the 1,2,3,4 tests with the SSDT-EC-USBX-DESKTOP.aml and / or the SSDT-TRX40-USBX.aml) as well as the I210 Device Properties enabled or disabled.

This makes a number of test….

I even did a clean instal 11.3.1 then update to 11.4.beta 3.

The installation is absolutely problem-free with my EFI. I just changed a DSDT. I kept the SSDT-TRX40-USBX.aml.

I don't get a PCI card placement errors message the first time I log in (I don't use Kext restrict events).

And still no ethernet connection. The Wifi module works as before.

From the moment I start to order the ports for example, it is unstable. (Kernel panic….)

 

I keep the patch and the pci properties of the I210 as it works as you can see. (Screenshot)

I will wait for the next beta and the new version of OpenCore to redo the tests

I saturate and I am a little annoyed ...😞

654659344_Capturedecran2021-05-15a13_38_23.thumb.png.685557a58d743c78a3d3413347e1c54f.png

1951284232_Capturedecran2021-05-15a14_13_12.thumb.png.631ec9f961913590d65f7263c0a0b172.png


I'm sorry to hear this, but now I'm beginning to wonder about your actual internet connection. The fact that the drivers are reported being loaded on the PCI window makes me think the ports are active.

 

Am I understanding that if you run an older version of OC, your ports are active, but from (what?) v069 onwards there is no activity? If you create a new EFI with the same kexts/dev prop we just worked on and run under v068, it all works?

 

Some more questions.

 

Are there any LEDs on at the RJ45 jacks on the rear panel of your mobo?

 

Do you have other ethernet cables to try? Are you going through a switch? Is the switch working (powered up, etc; I've had them go bad)?

 

Can you directly run an ethernet cable from the rear of the mobo to your modem/router?

 

To help with trouble shooting, there is an Apple utility (Network Utility) that is useful. Unfortunately, Network Utility was dropped for Big Sur. But fortunately, it can be extracted from Catalina. The Catalina version runs just fine under Big Sur. I'll attach a copy to save you digging around for it. (On new installs, Big Sur removes it (I've variably installed in the Application or Utility folders, but hiding it in the Download folder seems best.)

 

If you run it, it will show you packet transmission information. Below is mine for the I210 port. The one for the Aquantia port is similar (I run 2 cables back to my router). You should be able to see something like this.

 

1789149377_ScreenShot2021-05-15at12_26_17PM.thumb.png.ab40089655c6b54b86f522f2ad5abdd5.png

 

Network Utility.app.zip

Edited by iGPU
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   0 members

    No registered users viewing this page.

×
×
  • 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.