Jump to content

Arrakis

Donator
  • Posts

    308
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Arrakis

  1. 22 hours ago, gosi said:

    Okay so Upgrade to Monteray did work well for me. Only Wifi and BT is dead now. Arrakis did you do anything to update the Kexts or are those working for you?

    @gosi 

    For BT, you must use the following two kexts: BlueToolFixup.kext Ver 2.6.1 & IntelBluetoothFirmware.kext Ver 2.0.1

    For wifi the following kext: AirportItlwm-Mont.kext Ver 2.0.0

    Kext.zip

  2. 731344236_Capturedecran2021-10-29a21_44.39-copie.png.9b5217f2533245cd082388844fd22a1c.png

    I did a clean install of Monterey 12.0.1 and then update to Monterey 12.1 following the advice of Fabiosun with the kexts disabled: AMDRyzenCPUPowerManagement.kext and SMCAMDProcessor.kext

    It went like clockwork in OpenCore 0.7.4🙂

     

    Still no ethernet connection.🤨

     

    I have tested all the kexts I could find for Intel I210.

    AppleIGB i210 / 1211.kext modified by Shaneee: kernel panic.

    AppleI2xx.kext: kernel panic.

    Small tree.kext: frozen system (yes, I know but we had to try).

    Fake PCIID_Intel_i225-V.kext associated Fake PCIID.kext: Stable system

    I210.kext: Stable system.

    Without kext: System freezes….!

  3. On 9/29/2021 at 11:22 PM, Driftwood said:

    HOW TO INSTALL MONTEREY BETA 8 ON THREADRIPPER TRX40s

     

     

    As you may have seen on OSX Discord server... last nights install of Monterey beta 8 didn't go to plan. It downloaded fine with j160 reboot, then when SBM=Disabled and Nvram reset, it wouldn't install beta 8 despite three re-download attempts too.

    I didn't want to go the iMac17,1 way so I thought I would wait until a solution cropped up. Today, it did.

     

    The new version of RestrictEvents Kext together with the latest Release candidate of OC 0.74 now works - and it won't upset your memory configuration (as set out by iGPU)

     

    Here's the RestrictEvents kext, & download OC0.74: RestrictEvents.zip

    Source: https://github.com/acidanthera/RestrictEvents/commit/2430ed06c15a9f3dd94634ab68e208c8b762e11d

     

    This will negate the need to do anything like change your SMBIOS to iMac17,1 OR SBM=j160 🙂

     

    Just install OC0.74, include the restrictEvents kext in your kext folder, then Propertree snapshot it into your config/EFI.

     

    Reboot, it sees the update, installs, reboots just fine!

     

     

    54135382_OC0.74LatestRelease.thumb.png.5783bffe96d0adc6f307be1ff378ab73.pngrestrictevents.png.a0e13f9cef5c553871112c1324efbe1a.png

    1172817510_Downloadingbeta8.thumb.png.021ee14a74c1a0b07b49cecef5b36ea8.png1095291912_Screenshot2021-09-29at22_21_54.thumb.png.832a07e10b52377c9f36f6ca322ae19a.png

     

    Job done.

     

     

    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🤪

    1458868065_Capturedecran2021-10-02a19_28_39.thumb.png.750129bfe1f20bb25bcd135837b668fb.png

    • Like 2
  4. On 9/21/2021 at 7:16 PM, gosi said:

    Thanks Arrakis 🙂

     

    1) whats the easiest way to remove it? I am used to running Hackintosh with Glover but I have about zero clue about the config.plist. So removing makes me a bit scared as I think I might damage something.

    2) the card that came with the mobo is broken, it is not even detected by the BIOS. Replacement was hard to get but it should be there next week. Do I need another version of the SSDT if its Revision 2 or vice versa?

    3) ah I can just string replace and should be happy?

    4) I double checked the manual and was never able to see which slot is number 4. I guess to one closest to the CPU is 1 and downwards are 2,3,4?

    5) yes good point 😄

     

     

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

    378778392_Capturedecran2021-09-26a17_53_08.thumb.png.8b91f220b57b01646f46c1622bae4110.png

  5. @ 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.

    134061873_Capturedecran2021-09-21a16_56_09.thumb.png.c11798f9e1e156b7b4ad4db602063fda.png

     

    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

    605829293_Capturedecran2021-09-21a17_03_21.thumb.png.f298dc9b61cba8f5de70bae463f9dca6.png

     

    3) The ram values should be replaced by yours in all banks.

    1432440918_Capturedecran2021-09-21a17_22_50.thumb.png.7c705c7d632ec5f96023ee3911afdcbb.png

     

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

    • Like 1
  6. @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

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