Search results

I just looked at the code for the SSDT-EGFX.aml you provided... I've actually tried that exact code a few days ago and it didn't work (it was one of the earliest things I tried), so I'm down to trying the SSDT-EGFX-SPOOF.aml you provided. I'll let you know how that goes tomorrow.

Lol. I'm hoping to change that in the near feature. I spoke to Apple's engineers today to get them to add support for 0x73af... it could be as soon as next week (soonest Weds. or Thursday, if not more than likely the following Weds. or Thursday). I have a follow up call with the engineers on...

I did see that right after I replied, but I wanted to set the record straight for others that may not of noticed regardless. I don't understood why MacRumors claims it's support as of 12.0.1. I left a comment over there asking them on whether they have evidence to back their claims.

@CaseySJ, I investigated the 73AF support as according to MacRumors, it came with 12.0.1. However, upon my testing on both 12.0.1 & 12.1 Beta, it doesn't work and causes kernel panics. Furthermore, the eGPU Apple Support article still says it's not supported. Upon further investigation...

@MysticalOS, @dehjomz Newly Supported GPUs in macOS 12.1 Beta 1: Navi23: -73E3: Radeon Pro W6600 -73FF: RX 6600, 6600M, & 6600 XT

@dehjomz, never mind... it'd be listed as Navi 22 & the 6600 XT is Navi 23, so I don't need a device-id to check. Let me know when the Public Beta comes out & I'll check for you.

@Gigamaxx, I saw it in Geekbench a few days ago along with Metal Support in System Information, but it doesn’t give me the option to benchmark it… the IO Reg I sent you was after that discovery, so it's unchanged. However, you bring up a good point, my 5500M & 6900 XT use the same kexts for both...

@Gigamaxx I’ll try it in a little bit. By the way, I found the EFI logs as well & I fixed the problematic errors in that log already. At this point, WEG is the only piece with errors in the debug logs.

@dehjomz I will check on my old MacBook later tonight & let you know. Do you know the device-id for the 6700 XT? If not, I’ll scavenge the internet for it.

@Gigamaxx, @tedyun, I already tried that after we talked about it last night... didn't work. The 5500's device-id is listed for "ATY,DeviceID" on GFX0 while "device-id" is "<"@s">." Bizarre, but that confirms that I'm on the right path. I found the debug logs for Lilu & WEG and I think I may...

In the aml Gigamaxx told me to try, he had the former, but I thought it was the latter too.

@Gigamaxx, @CaseySJ, I think you're on an older version of IORegistryExplorer. I'm on version 3.0.2. Try version 3.0.1 or later.

You're looking at PEG0 which is my dGPU (5500M). My eGPU is PEG2->UPSB->DSB1->UPS0->pci-bridge->pci-bridge->pci-bridge->display... there you can see my device-id: <af 73 00 00>.

Let me know if you're able open it, so we can let Gigamaxx & CaseySJ know.

v3.0.2... that sounds like the issue.

@tedyun, my bad. I added it to my prior post with an edit. Let me know if you can open it in IORegistryExplorer.

@tedyun, I just tried downloading both instances of the upload & it wasn't corrupted for me (it downloaded to a different folder, so I know I'm opening the right file). I think I figured it out though: you can't open mine due to different hardware... I have to press "Save a Copy as" instead of...

@Gigamaxx, @CaseySJ Here it is again... not sure why it was corrupted as the file isn't corrupted on my end. Was the config.plist also corrupted?

@CaseySJ, device-id = <af 73 00 00> which translates to 0x73af.

@tedyun, I know. CaseySJ asked if I could add a fake device property, so I was merely answering his question. You're right I should've made that more clear... I edited it to make it more clear. Thanks.