Search results

Can I ask you how you mapped your usb ports? Thanks!

So, I have 2 clevo laptops, both have amd r9 m390x card driving internal 4k panel. I installed the last MacOS that support those amd cards, Monterey os. I have acceletion and external DP monitor but no image on internal eDP screen, please see the attachment. Would like to specify that both...

I don't think he's referring to this thread! He has many issues with the EFI from post 5...

Would you please share the EFI folder or the source? I have the same MB. Thank you!

End of the game?

I was sure I wrote it but can't find my reply. Anyway, some symptoms, Davinci resolve cant see the card, LuxMark cant, iStat no, HWmonitor2 also... There's something missing, non of apps can see the card, that should be important to understand the problem.

Ok, solved Shut Down problem. When drivers load the card have high temps (in windows) so I checked the thermal paste and discovered that the provided x-bracket have taller fillet for screws so the heat-sink wasn't pressing enough on chip. Changed x-bracket and now it doesn't shut anymore...

Done, same...shut down... Rebuild was done using: sudo kextcache -i / sudo kcditto Reset NVRAM was done by CleanNvram.efi I was able to save the ioreg before it shuts

With device ID 6810 it kernel panics... Same if changing the smbios from MacPro6,1 to iMac 17,1. But for now I would like to understand why it doing that: The pc shuts down even if I click Cancel

This is with the ssdt. I'm not sure the ssdt make any difference, please confirm.

Sure, it was True. Both, 6920 and 6921, but without your ssdt.

A little progres with dev_id 6920, Mac is seeing 8gb ram now. Atached ioreg. Resolve is not seeing the card but that's another problem for another day. The new problem for now is that after few second on desktop There is the small dialog window that is asking me if I'm sure I want to sut down...

And tried also without ssdt, same result. I think the ssdt does nothing.

Ok, just tried that ssdt and the result is the same. At this point maybe the device id should be chosen for a different card...

You mean that? Please take a look!

Still nothing with new ssdt. But how can yo uexplain the fact that under System nformation the device-id is the injected one?

I'm sorry, can you explain why you think so? As you suggested I injected 0x6929 dev-id and you can see it in IOReg.

It seams to inject the device-id now but no kext attached. We are closer now but mising something.... Any idea?

I tried that way: And now I an see it again under System Information but it's not usable still, and device ID is not the one I'm trying to inject:

Can you point me to a guide, please? I mean, the right way to do that with opencore. Thank you!