Jump to content

Arrakis

Donator
  • Posts

    278
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Arrakis

  1. Updating smoothly until the last boot I get this. I don't know how to read this panic. Which side should I look for?
  2. I did a clean install for Monterey 12.0.1 under OpenCore 0.7.4. 😀The installation went smoothly.😀 Intel I210 ethernet ports are still invalid.😞 For now, I am staying on Big Sur 11.6.1 (20G224) I will wait until Monterey 12.2 to resign myself to buying a 10G ethernet card.
  3. @valmeida I don't know what happened, I tried again with a newer version of OCConfigCompare and I find the same result as you. I am using the sample.plist delivered with the OpenCore 0.7.4 version. There is no example specific to the TRx40.
  4. @valmeida it is missing in your config.plist compared to the example of opencore 0.7.4 what is in blue in the capture
  5. @gosiMaybe you won't need to do that, you will install directly in Monterey 12.0.1. You must try.
  6. @gosi With OpenCore 0.7.4 will suffice. OpenCore 0.7.5 is still in development There are three kexts which requires the version for Monterey AirportItlwm-Mont.kext, BlueToolFixup.kext, IntelBluetoothFirmware.kext and remove the IntelBluetoothInjector.kext otherwise it will conflict with the BlueToolFixup.kext
  7. @gosi Yes, it works great. If you don't have wifi at the first connection. Disable the Wifi port in network preferences and apply. Then reactivate the port and choose your network again.
  8. Hello One question, do you know if this graphics card is supported by Big Sur and Monterey ? https://www.amd.com/en/products/professional-graphics/amd-radeon-pro-w6800
  9. I confirm the driftwood method with OpenCore 0.7.4 and RestrictEvents.Kext allows upgrading to Monterey Beta 8 without modifying the SMBIOS. As I do not support the RestrictEvents memory layout information window, I used the boot argument: revnopatch = mempci to find the one for a 2019 Mac Pro. After all I have a Mac Pro 2021🤪
  10. @gosi You can update to Big Sur 11.6. Intel I210 ethernet ports still work. They will work under Monterey only from beta 7. Slot 4 is the last one at the bottom (See Screen capture) I can not answer for the SSDT in case of TitanRidge Rev2 card.
  11. Good news for me The Ethernet ports (Intel I210) of the Gigabyte Designare motherboard are working again under Monterey Beta7.😃😃😃 I am using the attached Kext I210. I have updated Monterey beta 7 from installation Monterey Beta 6 with OpenCore 0.7.4 under SMBIOS iMac17.1 from download until the full update is complete. i210.kext.zip
  12. @ Gosi Several things: 1) In the config.plist you can delete in DeviceProperties the values of my graphics cards and possibly that of the titan ridge if you do not install it. 2) If you do not use the titan ridge card you can delete the SSDT-DTGP and SSDT-TBOLT3-NVM23 from the config plist and also delete them from the ACPI folder of the EFI 3) The ram values should be replaced by yours in all banks. 4) as part of the installation of the Titan Ridge card, it must be installed in slot 4. 5) Wait until I update Big Sur 11.6 so as not to put a potential problem (I210) on you. I am under the AGESA bios version 1.0.0.4 (FBd). As long as you don't have an AMD 6000 series card, there is no point in upgrading to AGESA version 1.0.0.5 (FBi) which brings Add Re-size bar support on Windows (not supported by MacOS).
  13. @gosi You can try this EFI under OpenCore 0.7.2 For me, this is the best since I started. I am using the WIFi AX200 from the motherboard without problems. Under Monterey it also works. Add the kext BlueToolFixup.kext Change the IntelBluetoothFirmware.kext version for Monterey Remove the IntelBluetoothInjector.kext @fabiosun You can put this EFI in OP
  14. Possible update of Monterey Beta6 following the method described above by iGPU and Fabiosun. Still the problem of I210 ethernet modules not working.😕
  15. I had not tested on Big Sur 11.5.2, it works with just the I210.kext, but it is broken for Monterey yet the IONetWorkingFamily.kext is still in the same location System / Extensions / ... location with the ten kexts taken in identical load and versions.
  16. No, I was not wrong, I put the I210.kext file in the correct folder in this case EFI / OC / Kexts The problem stems from the second file I named Patch I210 Arrakis.plist that needs to be added to the kernel. 1) add the values in key base, key count, key find, key identifier, key limit, key mask, key replace, key replace mask, key skip in this file 2) the second linked to the No schema for BundlePath, ExecutablePatch, PlistPath always in the same file. Because if I understood the principle correctly, this patch will indicate the loading of the kext I210.kext
×
×
  • 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.