Jump to content

Arrakis

Donator
  • Posts

    308
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Arrakis

  1. 1 hour ago, fabiosun said:

    https://forums.unraid.net/topic/109718-problems-with-big-sur-macinabox-vm-and-intel-i210-network-card-after-upgrading-to-114/?do=findComment&comment=1009015

    here is explained well

    copy kext in kext folder and declare it (plist in text mode attached in his message)

     

    I do not think is useful, but it is simple to try

     

    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.

  2. 2 hours ago, fabiosun said:

    @Arrakis

    you have declared your kext in a bad place I think

    (under kernel/Patch))

    you have to add it in usual section (Kernel/add)

     

    follow this:

    2080713921_Screenshot2021-08-19at14_56_09.png.cf34b3d18d2d95e523884c606c62d556.png

     

    in kext plist is present this ID:

    1081057625_Screenshot2021-08-19at14_57_22.png.4c52d00e0e157bde3a47af5ec8eabe5d.png

    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

  3. I have found a strong lead that is interesting here and is consistent with what I have been thinking from the start of this problem (Big Sur 11.4 in Monterey), namely indicating the correct folder for the I210 modules to be operational.

    I checked the kext and it is still existing in Monterey. 

    219036602_IONetworkingFamily.kextundermonterey.thumb.png.e9b38164def6ebce3a6271a43ea02dda.png

    I tested the proposed solution as it is but obviously it does not work because you have to modify the kext (patch) otherwise there will be an error starting again.

    IMG_0475.thumb.jpg.ff682f73d8381c79c837c7d83f56d260.jpg

     

    I have verified the vendor id is 8086 and the product id is 1533 for i210.

    Could someone help me adapt this solution?

    Both files are taken from the forum mentioned above. I haven't changed anything.

    i210.kext.zipPatch I210 Arrakis.plist.zip

  4. 13 hours ago, carlo_67 said:

    I personally have not found any problems, even changing in Misc / Security / ExposeSensitiveData from 0 to 8, it also detects my motherboard,

     

    Schermata 2021-08-07 alle 12.48.11.png

    Schermata 2021-08-07 alle 23.09.34.png

    @fabiosun la mia carretta 🤬

    I have the same problem as @iGPUwith the new version SMCAMDPProcessor.kext making my system unstable

    and moreover I no longer have the temperature near the CPU in iStat Menus (I use this application because I have GPU temperatures and other constants ...)

    I reverted to the previous version. The ExposeSensitiveData value is indeed 8 to recognize my motherboard.

  5. Successful installion of Monterey from BigSur 11.5.1.

    Update is scrolling without problems.

    I did the installation from the EFi posted above here with two changes in the kexts (AirportItlwm-Mont.kext, BlueToolFixup.kext) and delete of the IntelBluetoothInjector.kext

    WiFI and Bluetooth operational.

     

    But I have the same problem as when I went from 11.3.1 to 11.4

    No more ethernet connection.

    The I210 ethernet modules are more recognized while the kexts are included in the OS so in theory recognized natively.

     

    Edited : My config.plist Arrakis Monterey Open Core 0.7.2.zip 

    Monterey.png.ebf9f165fa5135c42d209db384ea3730.png1736954278_Montereyethernet.thumb.png.cb62e61b5abc654988970dda1fb4a2c4.png

     

    • Like 1
  6. 23 hours ago, fabiosun said:

    Lastr test if you want for tonight @Arrakis

    config-arrakis-4 step.plist.zip 6.38 kB · 3 downloads

    if weird frezee you have are not related to your thunderbolt card...there is a problem with topology patch i think (included in ProvvideCPuCountInfo)

    The Arrakis config - step4 starts Big Sur but restarts but less often The Arrakis config - step3

    Starts Monterey Beta 3 installer and begins installation but hangs ... with the message "An error occurred while preparing for installation….."

  7. 3 hours ago, fabiosun said:

    step 2 @Arrakis

    config-arrakis-2 step.plist.zip 6.88 kB · 2 downloads

    Previous system should work the same, test in Monterey to see if it passes previous hang you posted

     

     

    3 hours ago, fabiosun said:

    config-arrakis-3 step.plist.zip 6.97 kB · 1 download

    and this should be last step...

    added these two patches and disable a lot of them...

     

    PR_Algrey Force set cpuid_cores_per_package-10.15.x -11.x

    PR_Algrey Force set cpuid_cores_per_package-12.x

     

    I use "18" that is your exdecimal cores count (24 cores)

    let we see if it could work now

     

    The config-arrakis-2 step starts Big Sur but I get the same error as the onfig-arrakis-1 step config for the Monterey installation.

     

    The config-arrakis-3 step starts Big Sur but very unstable restarts or freezes.

    On the other hand, starts the installer Monterey Beta 3 and begins the installation but freezes at various stages. (I tried several times without changing anything)

  8. 10 hours ago, fabiosun said:

    @Arrakis

    when you have time this is a "clean" config.plist taken from your EFI

    if system starts the same..I will proceed in a further step. 

    config-arrakis-1 step.plist.zip 6.81 kB · 1 download

    I have only disabled stuff

     

    Starts well Big Sur 11.4 and 11.5 but for the installation of Monterey B3 it stops there. 

     I call back on the off chance with all of the patches, I can install Monterey B1.

    IMG_0417.thumb.jpg.1ff14430719143b5bd9e1dcdaedda5aa.jpg

     

    • Thanks 1
  9. 1 hour ago, fabiosun said:

    @Arrakis

    if you have enough patience ..

    try this:

    config-Arrakis-bis.plist.zip 7.05 kB · 3 downloads

    with BS an Monterey if you have

     

    Still not possible to boot on Big Sur 11.4 or 11.5.

    When I try to install Monterey Beta 3 from a stick. I get an endless sequence (See Capture).

    During my test day I already had this and I had disabled all kexts concerning Airport, bluetooth, wifi without result.

    IMG_0415.thumb.jpg.c9b80de739826496197664c2e81a049b.jpg

  10. 1 hour ago, fabiosun said:

    @Arrakisdownloaded your EFI, there is a minimal correction on it you can do

    I think patches maintainer will update as soon they can also their GitHub:

     

    algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0

     

    21.99.99 should be 20.99.99 (maxKernel)

     

    this has already been reported and will be corrected shortly

    I changed the value of MaxKernel and already change the EFI on my post above.

     

    1 hour ago, fabiosun said:

    @Arrakis

     

    config-Arrakis.plist.zip 6.87 kB · 1 download

    with your previous EFi if you like try this

    obviously before with systems working with your EFI then if It works also for more complicated one 🙂

    Backup your 😉

     

    I noticed what you modified in the patch. How I could not understand ..... your explanation however precise.😒

    I tested. with your modified config.plist and I can't boot Big Sur 4. The change stops after selecting the system.

    Attached is the debug file.

     opencore-2021-07-22-171457.txt.zip

  11. On 7/21/2021 at 2:18 PM, Allubz said:

    Slightly off the mainstream topic (12.x booting), I have some random crashes I'm trying to figure out. The system works well, but sometimes, though seemingly randomly, I get a reboot.

     

    I attached a screen. It seems to be CPU related, if I look at the listed kexts. But what could cause the random reboots? No over/underclock settings, CPU is at stock in BIOS.

    782505678_LWScreenShot2021-07-21at10_56_53.thumb.png.58a9b179676bfdde3dc87c2ec339ddc7.png

    Cheers!

     

    PS: Good luck with 12x Monty, all the power to you 🙂

    @AllubzHere is my EFI OpenCore 0.7.1 and with the CPU topology patch that Fabiosun talks about

    Try it with this version of OpenCore to see if the problem persists.

     

    @fabiosun You can put it in OP if you want.

     

    Edit

    This is the right one.

    OpenCore 0.7.1 for Big Sur 11.4 & 11.5

    EFI ARRAKIS OPENCORE0.7.1.zip

     

  12. I managed to install the Monterey B1 version from an EFI OpenCore 0.7.1.

    664717567_Capturedecran2021-07-19a00_16_59.png.715b5230bbe6ed7f5f6d59f206524271.png

     

     

     

    Then I tried to boot with Shanne's PR EFI OpenCore 0.7.2 without success.

    Even try all eGPU suggestions once again. Here

     

    I spent my day trying multiple studies of combinations to no avail. I am stopping there for the moment.

    I'm not even talking about attempts to upgrade Monterey B3 which each time breaks the installation of beta B1 and back to square one.😒

    • Sad 1
    • Cross Finger 1
  13. 1 hour ago, iGPU said:

     

     

    A few comments regarding your config file. But first, are you trying to boot into BS or new Monterey; if latter, then do a fresh install (as I mentioned in a recent post above).

     

    When systems behave strangely, remove un-necessary items. In your case, remove the TB AIC (and note Spoiler below) and any USB devices if possible.

      Reveal hidden contents

    Arrakis-DP-TB.thumb.png.3d538202c45de73f2f3994e2992c356c.png

     

    Kext adjustment (also, if not necessary, since you had so many problems with I225, maybe disable those kexts and unplug your ethernet cables until system booting reliably):

      Reveal hidden contents

    Arrakis-Kernel-Kexts.thumb.png.565a3fd96f60b4f23cbb7cc3f9b2c5db.png

     

    I'd use change these Kernel/Quirks (Boot/Quirks look ok):

      Reveal hidden contents

    Arrakis-Kernel-Quirks.thumb.png.1ec30020295bb095415b2c4d1fe7167e.png

     

    And you might try a MmioWhitelist variation:

      Reveal hidden contents

    Arrakis-MmioWhitelist.thumb.png.60f3053a3a59330e8f068ef989afaac7.png

     

    Your Patches look ok, but the following are not needed for BS onwards and could be removed:

      Reveal hidden contents

    Arrakis-patches.thumb.png.fed449bc482277c09866e590808c73b4.png

     

    Finally, the UEFI section: a few changes to try:

      Reveal hidden contents

    Arrakis-UEFI.thumb.png.22f7e5768172f372b96ef8b50d9be1f0.png

     

    I started under 11.4 with the efi modified according to your remarks.

    I launched the installation on a volume from the disk image which is in the application folder of BigSur 11.4 so a clean instal.

    Same result, the first part is installed correctly but on the second start always the same error.

    my modified config.plist following your remarks and the debug file.

    config.plist Arrakis modified following Egpu.zipopencore-2021-07-18-171901.txt.zip

  14. 2 hours ago, fabiosun said:

    Not in the conventional way or based only on configuration.pdf or on very famous guides that have often copied things from us (and pass me the joke, even in a wrong way) 🙂

    so I would like to understand with you when you have your system fully functional the relationship between for example:

     

    0) patches

    1) DummyPowerManagement

    2) RebuildAppleMemoryMap

    3) SetupVirtualMap

    4) ProvideCurrentCpuInfo

     

    in particular, because 1) not all trx40 users need it, but all Gigabyte users for example and x570 users

    Because 2) it can be circumvented in some cases

    4) why an important patch like Disable _x86_validate_topology some need it and others don't and if it is not needed, what happens by activating the superquirk 4)?

     

    These are just thoughts of a midsummer morning 😉

    but I wanted to share them with you!

    @fabiosun

    As you can see, I have the exact same quirks as yours.
    This means that it is starting to have uniformity between motherboards. (MSI TRX40 Creator, Gigabyte TRX40 Aorus Xtreme, MSI Trx40 Pro 10G, Gigabyte TRX40 Designare)

    I have to keep the DummyPowerManagement activated otherwise I get this error (Screen capture)
    I'm still on your version of Open Core 0.7.2.

    1683311723_Capturedecran2021-07-18a11_40_56.thumb.png.fbb4bc30ac6fc39c2a9dbbd68b6934fd.png

    I will try to remake a Monterey B3 instal today if I have time.

     

     

    @PloddlesDo you also have to activate Dummy Power Management?

    IMG_0321.thumb.jpg.902219e8a6d3cad2bcd263af0e701372.jpg

    • +1 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.