Leaderboard

The sub-vendor and sub-device IDs are based on the mobo's manufacturer. Therefore, our MSI values will be different from those of ASUS. But no matter, as these ID values will not affect the Kernel patches since they are directly applied to Apple's Aquantia kext file without reference to any ID values. And even with the patches applied, I've added cosmetic changes (that is, not essential) via SSDT or DevProp changes, and the Kernel patches still work in Big Sur and Monterey. (I've already cautioned @valmeida to use no DevProp during the test phase.) If an SSDT is used, the attachment point at device BYS3 could be changed but that should not be important at this point. When I look at @valmeida's IORE, which I believe is from a Big Sur boot, we see the following at BYS3. This looks good. And after a boot into Monterey, it should look exactly the same. Please verify. It is not clear to me why @valmeida's Aquantia patch is working on the ASUS mobo in Big Sur, but not working in Monterey. The fact that the port is seen in HackCheck would suggest that the patch is being injected. However, to verify this change, turn off the Aquantia Kernel patch for Monterey in the OC config file. After re-booting, the Aquantia port should not longer be visible in HackCheck. To summarize, @valmeida do two things I've written above. Both will be answered in 2 boots (one with the Monterey Aquantia port enabled and one boot with this same patch disabled): 1. look at the BYS3 section in IORE after a Monterey boot with and without the Monterey Aquantia patch being enabled. 2. look at HackCheck's Network section, again after a Monterey boot with and without the Monterey Aquantia patch being enabled. ***** SPOILER: What I see on my MSI Creator mobo for Aquantia and I211 ports in IORE and HackCheck. While SmallTree is being properly injected, the port is still not active even under Mß6:

ciao fabiosun grazie per la pazienza ho provato adesso alla lettera le tue istruzioni...... purtroppo con il tuo config il sistema non si avvia schermo totalmente nero al boot. lasciando il file ssdt in acpi e rimettendo il mio config il sistema parte ma il file nvram.plist ne viene creato nella efi ne il testo inserito da terminale nella nvram rimane dopo il riavvio Esiste una soluzione per risolvere il problema?

no ma è gente che "gira" tutti i forum... ma non è un problema xD ...una volta chiarito che ce l'avevano palesemente piccolo, si sono ridimensionati 🙂

un vecchio detto recita: chi vive sperando.... muore cag.......