Jump to content

[Discussion] - TRX40 Bare Metal - Vanilla Patches

fabiosun

By fabiosun
in General

 Share

Recommended Posts

Recommended

Posted by fabiosun,

Ok..good news playing with MMIO and with opencore 061 i have solved reboot/shutdown problem... now it is working as it must work

MMIO rules shutdown and reboot previous problems

Recommended by fabiosun

  • Like

2 reactions

Go to this post
valmeida Senior Member

valmeida

Posted
Posted
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
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted
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 1
Link to comment
Share on other sites
valmeida Senior Member

valmeida

Posted
Posted
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
  • Moderators
iGPU Senior Member

iGPU

Posted
  • Moderators
Posted
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

 

  • Thanks 1
Link to comment
Share on other sites
  • Moderators
iGPU Senior Member

iGPU

Posted
  • Moderators
Posted
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:

 

SSDT-GPU-Rename.thumb.jpg.857e6f494daa6f9b64df384e0edee593.jpg

 

 

Result after above SSDT re-name as seen in IORE:

 

IORE-after-GPU-rename.thumb.jpg.0c3957ab34b10620dbe2055610baab0e.jpg

 

 

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

IORE-after-GPU-WEG-rename.thumb.jpg.f62208b2fd0f5e57dc2b3d0abe24c00e.jpg

 

  • Like 1
Link to comment
Share on other sites
valmeida Senior Member

valmeida

Posted
Posted
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 1
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted (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 by fabiosun
Misc
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

@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
valmeida Senior Member

valmeida

Posted
Posted
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
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted (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 by fabiosun
valmeida put right MMIO
Link to comment
Share on other sites
valmeida Senior Member

valmeida

Posted
Posted
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 1
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted
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 1
Link to comment
Share on other sites
valmeida Senior Member

valmeida

Posted
Posted
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 😞

Screen Shot 2021-08-17 at 1.54.44 PM.png

Link to comment
Share on other sites
Arrakis Senior Member

Arrakis

Posted
Posted

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

Link to comment
Share on other sites
  • fabiosun changed the title to [Discussion] - TRX40 Bare Metal - Vanilla Patches

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • 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.