Ploddles Posted August 16, 2021 Share Posted August 16, 2021 @fabiosun What does the 3-SSDT-6900xt.aml do for us? I've seen it mentioned a few times but haven't seen any explanation as to what it does. Thanks. Link to comment Share on other sites More sharing options...
valmeida Posted August 16, 2021 Share Posted August 16, 2021 24 minutes ago, valmeida said: I now able to boot Big Sur from IGPU EFI he sent me last nite by enabling ssdt-EC and 3-SSDT-6900xt.aml. I will try to boot Monteray and will let you know . EFI.zip 6.27 MB · 2 downloads 1 hour ago, fabiosun said: @valmeida, you have two ssdt disabled in this EFI so if you use this config and it start in BS and not in MR is weird 🙂 Also SSDT disabled are ssdt-EC and 3-SSDT-6900xt.aml have you tried with those ones ON? Attached is the panic log when booting into Monteray panic-2021-08-16-171806.txt.zip Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 16, 2021 Author Supervisor Share Posted August 16, 2021 2 hours ago, valmeida said: Attached is the panic log when booting into Monteray panic-2021-08-16-171806.txt.zip 3.24 kB · 1 download could you try this config, plist? In monterey config-Valmeida.plist.zip @Ploddles It add some feature you can also achieve using Whatevergreen about GPU PM A renaming from display0 to gfx0 then it depends the version you are referring for... 1 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 16, 2021 Author Supervisor Share Posted August 16, 2021 @valmeida have you rtx 3090 board mounted? 1config-Valmeida.plist.zip if previous fails in the same way try also this one if you want Link to comment Share on other sites More sharing options...
valmeida Posted August 16, 2021 Share Posted August 16, 2021 16 minutes ago, fabiosun said: could you try this config, plist? In monterey config-Valmeida.plist.zipUnavailable @Ploddles It add some feature you can also achieve using Whatevergreen about GPU PM A renaming from display0 to gfx0 then it depends the version you are referring for... I tried it with this one and no good here are the crash logs . I will now trey the second one. panic-2021-08-16-194851.txt.zip Link to comment Share on other sites More sharing options...
valmeida Posted August 16, 2021 Share Posted August 16, 2021 15 minutes ago, fabiosun said: @valmeida have you rtx 3090 board mounted? 1config-Valmeida.plist.zip 6.49 kB · 2 downloads if previous fails in the same way try also this one if you want No good booting into Monteray hers are the crash logs for this one panic-2021-08-16-195613.txt.zip Link to comment Share on other sites More sharing options...
Moderators iGPU Posted August 16, 2021 Moderators Share Posted August 16, 2021 2 hours ago, Ploddles said: @fabiosun What does the 3-SSDT-6900xt.aml do for us? I've seen it mentioned a few times but haven't seen any explanation as to what it does. Thanks. It simply injects data for GPU and re-names devices. It is only useful if not using WEG. If using WEG, it is un-necessary, which is why I disabled it for @valmeida 1 Link to comment Share on other sites More sharing options...
Ploddles Posted August 16, 2021 Share Posted August 16, 2021 @valmeida, this may be a long shot but I know a few people who have trouble booting if they have Above4G enabled. I noticed in your screenshots that you do have it enabled so maybe try with it disabled. Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 16, 2021 Author Supervisor Share Posted August 16, 2021 @valmeidai have no more idea for now same Big Sur Efi should be good also for monterey I have also some doubt if you have your 3090 installed and if so if it could create your kp in monterey 1 Link to comment Share on other sites More sharing options...
Moderators iGPU Posted August 16, 2021 Moderators Share Posted August 16, 2021 5 hours ago, valmeida said: I now able to boot Big Sur from IGPU EFI he sent me last nite by enabling ssdt-EC and 3-SSDT-6900xt.aml. I will try to boot Monteray and will let you know . EFI.zip 6.27 MB · 6 downloads The SSDT-6900XT is only useful if not using WEG. For months, I have used BS and now Monterey using only WEG and no SSDT file (for RX580, Vega56, Radeon VII and now 6900XT). Such SSDT files are not necessary for a boot if using WEG. And even if not using WEG, while the SSDT is helpful in re-naming the GPU devices as seen in IORE, the computer will still boot without it. I done this many time on both Intel and AMD platforms. If one wants to inject certain properties (like control the fan and GPU speed), these can be injected via an SSDT or injected by using DevProp section. The SSDT method is best, especially if one also wants to re-name devices. Portion of SSDT code to rename GPU devices. That is, how it's done: bridge after DODF becomes EGP0 and next bridge becomes GFX0: Result after above SSDT re-name as seen in IORE: Result after re-name by WEG. The first bridge is not re-named, but this is only cosmetic and seems to have no impact on GPU functionality. (Note: for those paying attention, this IORE taken from a different mobo than the above example, so the D0BF device is here D0C1, which would mean that the SSDT shown above would not work for this mobo unless changed, and it is for a different GPU and that portion should be changed as well.) 1 Link to comment Share on other sites More sharing options...
valmeida Posted August 16, 2021 Share Posted August 16, 2021 Just now, fabiosun said: @valmeidai have no more idea for now same Big Sur Efi should be good also for monterey I have also some doubt if you have your 3090 installed and if so if it could create your kp in monterey My 3090 is not installed only the 6900XT I gave it to my son. 1 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 16, 2021 Author Supervisor Share Posted August 16, 2021 @valmeida different and desperate approach try to use this one: EFI-Clover 5138 Valmeida.zip It is clover and it is built with your MMIO. Enabled also dummy power management quirk Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 3 hours ago, fabiosun said: @valmeida different and desperate approach try to use this one: EFI-Clover 5138 Valmeida.zip 4.87 MB · 1 download It is clover and it is built with your MMIO. Enabled also dummy power management quirk I tried this clover boot loader and it will boot with BS not Monteray. Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 5 hours ago, Ploddles said: @valmeida, this may be a long shot but I know a few people who have trouble booting if they have Above4G enabled. I noticed in your screenshots that you do have it enabled so maybe try with it disabled. I tried that no dice. Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 17, 2021 Author Supervisor Share Posted August 17, 2021 (edited) Post debug you can find in misc folder thre are a lot choose with new date and time delete all file inside and the boot in Big Sur and monterey tou should see two debug log post both Edited August 17, 2021 by fabiosun Misc Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 9 hours ago, fabiosun said: Post debug you can find in misc folder thre are a lot choose with new date and time delete all file inside and the boot in Big Sur and monterey tou should see two debug log post both Here are the logs for BS and Mont BS.zip Monteray.zip Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 17, 2021 Author Supervisor Share Posted August 17, 2021 @valmeida 21:720 0:006 OCABC: MMIO devirt 0xCB100000 (0x81 pages, 0x8000000000000001) skip 0 21:727 0:007 OCABC: MMIO devirt 0xD7180000 (0x81 pages, 0x8000000000000001) skip 0 21:734 0:006 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 21:741 0:006 OCABC: MMIO devirt 0xE3300000 (0x100 pages, 0x8000000000000001) skip 0 21:748 0:006 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 21:756 0:008 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 21:764 0:007 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 21:771 0:006 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 21:778 0:007 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 21:785 0:006 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 21:792 0:007 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 21:801 0:008 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 21:808 0:006 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 21:814 0:006 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 21:821 0:006 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 21:829 0:007 OCABC: MMIO devirt 0x2040000000 (0x10400 pages, 0x8000000000000001) skip 0 21:835 0:006 OCABC: MMIO devirt 0x3830000000 (0x10400 pages, 0x8000000000000001) skip 0 21:846 0:010 OCABC: MMIO devirt 0x5020000000 (0x10400 pages, 0x8000000000000001) skip 0 21:853 0:007 OCABC: MMIO devirt 0x6810000000 (0x10400 pages, 0x8000000000000001) skip 0 Check your MMIO whitelist Not good Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 1 hour ago, fabiosun said: @valmeida 21:720 0:006 OCABC: MMIO devirt 0xCB100000 (0x81 pages, 0x8000000000000001) skip 0 21:727 0:007 OCABC: MMIO devirt 0xD7180000 (0x81 pages, 0x8000000000000001) skip 0 21:734 0:006 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 21:741 0:006 OCABC: MMIO devirt 0xE3300000 (0x100 pages, 0x8000000000000001) skip 0 21:748 0:006 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 21:756 0:008 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 21:764 0:007 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 21:771 0:006 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 21:778 0:007 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 21:785 0:006 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 21:792 0:007 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 21:801 0:008 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 21:808 0:006 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 21:814 0:006 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 21:821 0:006 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 21:829 0:007 OCABC: MMIO devirt 0x2040000000 (0x10400 pages, 0x8000000000000001) skip 0 21:835 0:006 OCABC: MMIO devirt 0x3830000000 (0x10400 pages, 0x8000000000000001) skip 0 21:846 0:010 OCABC: MMIO devirt 0x5020000000 (0x10400 pages, 0x8000000000000001) skip 0 21:853 0:007 OCABC: MMIO devirt 0x6810000000 (0x10400 pages, 0x8000000000000001) skip 0 Check your MMIO whitelist Not good I guess when I updated the bios yesterday it changed some of the MMIO. I have updated it. I have attached the logs for BS and Mont. Big Sur boots Mont it reboots . Archive.zip Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 17, 2021 Author Supervisor Share Posted August 17, 2021 (edited) Here clover config with right MMIO Check also your Opencore configuration , you have a bit of confusion inside Config.plist wrong MMIO and also wrong comment 5 minutes ago, valmeida said: I guess when I updated the bios yesterday it changed some of the MMIO. I have updated it. I have attached the logs for BS and Mont. Big Sur boots Mont it reboots . Archive.zip 36.72 kB · 0 downloads These MMIO loads fine A question : Are you trying to boot in a preinstalled on other PC Monterey? Edited August 17, 2021 by fabiosun valmeida put right MMIO Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 21 minutes ago, fabiosun said: Here clover config with right MMIO Check also your Opencore configuration , you have a bit of confusion inside Config.plist wrong MMIO and also wrong comment These MMIO loads fine A question : Are you trying to boot in a preinstalled on other PC Monterey? Fresh install on a separate drive. Let me format the drive and start fresh again. 1 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 17, 2021 Author Supervisor Share Posted August 17, 2021 4 minutes ago, valmeida said: Fresh install on a separate drive. Let me format the drive and start fresh again. try to re download the installer and if you can you could also clone your Big Sur drive and try to update it (enrolling on apple developer seed) 1 Link to comment Share on other sites More sharing options...
valmeida Posted August 17, 2021 Share Posted August 17, 2021 1 hour ago, fabiosun said: try to re download the installer and if you can you could also clone your Big Sur drive and try to update it (enrolling on apple developer seed) I tried doing both upgrade and fresh install on the same drive no good 😞 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 18, 2021 Author Supervisor Share Posted August 18, 2021 @valmeida I would do like this: Without mixing two systems in different partitions on one disk I would clone the working Big Sur disk and then update this disk as a normal update (using the seed developer) 1 Link to comment Share on other sites More sharing options...
Arrakis Posted August 19, 2021 Share Posted August 19, 2021 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. 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. 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 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted August 19, 2021 Author Supervisor Share Posted August 19, 2021 @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: in kext plist is present this ID: Link to comment Share on other sites More sharing options...
Recommended Posts
Posted by fabiosun,
MMIO rules shutdown and reboot previous problems
Recommended by fabiosun
2 reactions
Go to this post
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now