Arrakis
-
Posts
278 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Downloads
Posts posted by Arrakis
-
-
@fabiosunYou are doing an enormous amount of work, of which I do not understand much. I am completely dumped but I see the result and I test.
I have retrieved your EFI Shannee from the OP and modified according to my configuration.
I can boot on BigSur 11.4, 11.5.
I can run the installation of Monterey Beta 3 but get an error after the first start (screenshot).
Attached is the log file and my config.plist
Edit : I just noticed that I left the patches for Aquantia but that's not the problem I guess.
-
Wonderful job for simplifying the patches.
I am using your patch except the last two.
The job done is so good that I don't even need the argument : cpu_topology_sort -disable _x86_validate_topology in the garbage 😄
I envy your talent in this area.
So since I had some time today, I tested the Big Sur 11.5 Beta 4 installation.
Without installation problem, everything works.
So my current EFI is valid from 11.4 to 11.5. I just changed the patches, the rest I haven't touched and nothing in the bios either.
As a reminder Above 4g decoding: enabled
Thanks again to all of you for contributing in your spare time to perfecting the hack on AMD.
Since I started, not even 1 year ago, I can see the difference in the stability of the system. And since switching to BigSur I find that there is a marked improvement.
Maybe I will have some time this weekend, I would like to test Monterey but I would like to know if I can choose the version that works with the patches.
-
1
-
1
-
-
I also confirm Resolve 17.2.1 works without patch.
-
On 6/2/2021 at 3:04 PM, Allubz said:
Thanks to @Arrakis latest EFI, updated to 0.7.0, I can boot 11.4 just fine on the TRX40 Designare rev. 1.1.
I have the same problem with the Intel I210 NICs, unsurprisingly. I've had similar lockups (when the NIC should receive an address) on modern Realtek chips. In the end setting manual speed usually fixed it.
I set manual speeds for the NICs, but it won't help just like that. I'm looking at using FakePCIID + I225 kext, and then updating the device-id and PrimaryMatch.
UPDATE: Disregard crossed text. Take the I225.kext, update the IOPCIPrimaryMatch to 0x15338086 and you got working LAN and no KP.
Thing is, macOS interface became a bit "choppy" first time, but this seems fixed by defaulting the "Manual" configuration on the "Hardware" tab to "Automatically", which I had set before and it seems to be the only difference.
Maybe there's merit to updating the device-id as well, but I don't understand how to obtain it and edit it conform the info.plist format.
UPDATE 2 / question: How to troubleshoot onboard audio on TRX40, or specifically the Designare? I get Mattise USB2.0 audio devices, regardless of which analogue port I try, but no sound.
The IOPCIPrimaryMatch should be 0x15338086, I got that far.I can't figure out how to obtain the right device-id, and translate it to the typical code the kext info.plist understands. The current entry is: 8hUAAA== which should resemble I225, what I'm looking for is obtaining our device-id, translating it to info.plist text, and testing this kext, as I think the controllers are close to identical and could fix our problem (besides reverting to 11.3.1).Maybe someone can chime in on how to achieve this 🙂@AllubzThanks 😀
I confirm the Allubz solution for my problem of recognizing the I210 ethernet ports under Big Sur 11.4.
The current solution is to use the Kexts FakePCIID + I225 kext with the value: IOPCrimaryMatch at 0x15338086
The ports are functional and no panic kernels.
@fabiosun My efi to put in the OP, thank you.
-
1
-
-
33 minutes ago, Jaidy said:
@Allubz @Arrakis Which BIOS version are you two using? I have a TRX40 Aorux Extreme, F4q BIOS. I can not shutdown my system. It always restarts when I shut down. Previously this problem was solved by disabling "Wakeup on LAN access" option in the BIOS, but not for this one. If shutdown is working for you, would you have any suggestions?
@Jaidy I am using version Agesa 1.0.0.4
and Wakeup on LAN disabled.
Maybe the restart is due to a bad value in Mmio White list.-
1
-
-
😀 For those who need my EFI.
Edit : With OpenCore version 0.7.1 and higher. the problem is solved.
The last EFI dated is in the first post.
-
1
-
-
I tested it with the Big Sur 11.5 beta. I have the same problem. my two I210 ethernet ports are not recognized. I did the test to reinstall from the rescue partition. Under Big Sur 11.3.1 this is possible because the ethernet ports are recognized but under 11.4 impossible because the ethernet connection is not active and recognized.
-
2
-
-
Thank you😀 for the work you did to resolve my issue of recognizing my I210 Ethernet ports under 11.4.0
I have tried all the possible combinations but it still doesn’t work. (DevProp only or DevProp + Patch or Patch only or Force 0 with the correct values or DevProp + Fake PCID.kext or DevProp + Fake PCID.kex + FakePCIID_Intel_I225-V)
I went under 11.4 (20F71), the system is stable unless I want to activate the ethernet kernel panic ports …… etc. (see capture)
Sometimes there is the activation of the ethernet port with no value for the router and DNS server but with completely wrong IP addresses and it is at this precise moment: Kernel panic.
My wifi connection is still working perfectly.
I will test in 11.5.0 to see if I have the same problem.
-
1
-
-
-
@iGPU Merci beaucoup pour l'excellente recherche.😃
This is a great lead, for sure my problem is there. I remember in the multitude of backtrace kernel reports related to IONetworkingFamily.
From the start I suspected this issue related to the IONetworkingFamily car kext in BigSur 11.4. beta 3 the wrong kext is loaded (see capture, AppleEthernetE1000.dext....)
I will do the test at the end of the week as I am in production until Friday.
I have looked in the OpenCore documentation (Page 25) this handles issues related to ONetworkingFamily and IOAudioFamily.
Here are the values in my current config.plist.
-
16 hours ago, Ploddles said:
@Arrakis This is a long shot but have you tried deleting your NetworkInterfaces.plist file and then rebooting.
cd /Library/Preferences/SystemConfigurationsudo rm NetworkInterfaces.plistI didn’t use the terminal command but went directly to the folder.
The "NetworkInterfaces.plist" file does not exist ....! It is worth saying that it was never created. For which reason …..?
-
@fabiosun I checked in Big Sur 11.3.1 and Big Sur 11.4.beta 3 all patches are loading.
-
15 hours ago, iGPU said:
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.
I don't think it's a hardware problem outside the PC, The pc is directly connected to the modem / router. I changed nothing. No cable, no modem / router, etc….
I have just made a 200 GB download with FileZilla from an external server to my hack and conversely a 70 GB upload with Firefox (We transfer) with my current EFI under OpenCore 0.6.9 and Big Sur 11.3.1 and I have encountered no cuts or stability ...
From OpenCore 0.6.2 / Catalina up to OpenCore 0.6.9 / Big Sur 11.3.1 inclusive I had no problem with this I210Intel.
I will do a test with OpenCore 0.6.8 to see if the Intel I210 recognition problem is the same under 11.4 beta 3
-
1 hour ago, fabiosun said:
kernel patches 11.4 beta3.plist.zip 2.19 kB · 1 download
to boot in OSX 11.4 beta 3 I am using these set of patches
I have three differences the occurrence :
- The first is algrey - cpu_topology_sort -disable _x86_validate_topology which I am forced to keep since the start of my hack otherwise blocked when starting Opencore as mentioned here
- The second is lapic_init - remove version check and panic it's not the same values. I checked in the beta patch here there are three occurrences and none match your value. Why ? When did you change these values ?
- The third Aquantia, it's normal I don't have an Aquantia card.
-
-
As I said on a previous post, I removed the Titan Ridge map and I have the same instability under 11.4.beta3 especially since I have absolutely no issues under 11.3.1
My hack has been on for 16:30 with the Titan Ridge card installed with Promise Pegasus2-R storage and an UltraStudio 4K Mini plugged into it. I have no freeze, instability etc…. under 11.3.1.
It works very well with hot and cold connections as well in thunderbolt or USB C.
So I think we can rule out this possibility of instability related to this card.
-
On 5/14/2021 at 1:19 AM, iGPU said:
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):
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:
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.
<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.
<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:
SDDT-TRX40-USBX.aml.zip 1.05 kB · 1 download SmallTreeIntel82576_mod.kext.zip 71.57 kB · 1 download
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 ...😞
-
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:
@iGPU I misspoke my question, what tool do you use to insert into the config.plist ?
-
Le 14/05/2021 à 01:19, iGPU a déclaré :
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) :
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 :
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.
<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.
<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 :
SDDT-TRX40-USBX.aml.zip1,05 kB · 1 téléchargement SmallTreeIntel82576_mod.kext.zip71,57 kB · 1 téléchargement
@iGPU how to create a patch kext. ? to inject the code to test 3.
-
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?
<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>
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?
-
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.
-
1 hour ago, iGPU said:
Upload your IORE file, I'd like to study it (with TB AIC in place).
@iGPU And there you have it, there is work to do this weekend. Merci beaucoup Gigabyte Designare TRX40 REV 1.1 Arrakis .zip
-
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.
-
@fabiosun I confirm ImacPro 1.1 under opencore 0.6.8, it's the same for me.
-
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.
[Discussion] - TRX40 Bare Metal - Vanilla Patches
in General
Posted
@fabiosun
For the SMCAMDProcessor.kext. I am using the iStatMenus app and noticed that if it is not enabled there is no temperature indication near the processor. (This temperature corresponds to the temperature in the AMD Power Gadget app).
I will activate the kexts at the minimum and try again the finalization of the installation.