Recent content by taoj17v
-
T
Trying out 6950XT and MacOS
another snippet you can try. It's hard to fix indentation in this forum's builtin editor. but you can see what we have changed. I think this one has a better chance, since I explicitly define the two bridge deivces' name DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000) { External...- taoj17v
- Post #27
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
can you show what's under D012 if the below does not work? first several lines DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000) { External (_SB_.PCI0.GPP8.BRGA, DeviceObj) External (_SB_.PCI0.GPP8.D012, DeviceObj) External (DTGP, MethodObj) // 5 Arguments Scope...- taoj17v
- Post #26
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
XXXX YYYY should be something like BRG1 PEGP SL01 etc, but not dev id like 73a6. These four letters are acpi objects, not dev id. Like I said we can infer it from ioreg output or dsdt. Maybe you can post both so I can take a look for you. For the dsdt dump I think there is a way in opencore...- taoj17v
- Post #22
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
By looking at the first post second picture, the devid is not changed. Also the posted gfxutil output also has non-changed devid: 73af. We need to first fix that.- taoj17v
- Post #18
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
Thanks for trying. No, any number after @ is not of interest so 30001 does not matter. You have to find the path deep enough so that it contains GFX0. Another way to do this is to read it from your vanilla dsdt (all patches off, you may post that or analyse yourself). 2c:00.0 1002:73a5...- taoj17v
- Post #17
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
According to the windows path, there are 5 nodes after SB ACPI(SB)#ACPI(PCI0)#ACPI(GPP8)#PCI(0000)#PCI(0000)#PCI(0000) So in dsl we should have 5 nodes after SB DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000) { External (_SB_.PCI0.GPP8.XXXX, DeviceObj) Scope...- taoj17v
- Post #13
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
If the above method does not work, you can also use this good documentation to verify if your injection is working: https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#deviceproperties-injection-failing. And post the acpi-path mentioned there. Along with new gfxutil output and...- taoj17v
- Post #11
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
can you change the config.list of the GPU name to "My AMD Radeon RX 6950XT 16GB" for debug purpose? So that we know we changed its name. for the ssdt can you try this snippet: DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000) { External (_SB_.PCI0.GPP8, DeviceObj) Scope...- taoj17v
- Post #10
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
Also in that video it get the gpu address, Can you post the whole output of gfxutil? I can use that to double check if the config.plist is pointing to the right device. Edit: I meant get the gpu address in macos- taoj17v
- Post #8
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
Thanks for sharing. If the forum rule allows can you upload the aml file and the config.plist?- taoj17v
- Post #7
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
I think right now we do need the SSDT. But it seems that yours is not working properly. Please double check if the produced aml file is present and also the values in the config.plist is correct and of correct data type. May be you can post the code.- taoj17v
- Post #5
- Forum: 12.0 Monterey
-
T
Trying out 6950XT and MacOS
0x73FF is pci devid for 6600XT can you try 0x73BF for 6900XT? In practice, BF730000 has to be put into the config.plist. Also by looking at the screen shot it seem that your SSDT is not doing its job: we are expecting to see 0x73FF. Here is a video tutorial one good person put up . The only...- taoj17v
- Post #3
- Forum: 12.0 Monterey
