R9 390 8gb issue 7mb Bigsur!!

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
help!! I have issue with AMD GPU R9 390 8GB shows 7mb
try many method with gpu-spoof fake id and Device properties also without
on different macOS versions Monterey,Bigsur,Catalina,Mojave all same problem also try many SMBIOS imacpro1,macpro6&7 same issue
its been month I try it shows audio gpu but no display
cpu AMD Ryzen 5 2600
I attached my EFI folder if anyone can fix this

Screen Shot 1443-07-23 at 8.07.02 AM.png
 

Attachments

  • EFI.zip
    8.2 MB · Views: 6
Last edited:

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,341
Try this EFI in place of your current one.
  1. I have cleaned up your config.plist - removing some unnecessary entries, including most of the DeviceProperties you added.
    • The Spoof SSDT should cover these aspects, all the DeviceProperties will do is conflict with or make the SSDT not work correctly.
  2. I have changed UEFI >APFS > MinDate and MinVersion to 0, as you are running Big Sur and I assume will upgrade to Monterey at some point.
  3. I changed Misc > Security > SecureBootModel from Disabled to Default, as this is the expected condition when running Big Sur or newer.
  4. I removed two unused Tools.
  5. I have added two kexts, RestrictEvents.kext and AppleMCEReporterDisabler.kext, as these are normally required in an AMD Hack.
Use this EFI from a spare USB pen drive.

Let us know if it makes any difference to how the AMD GPU works.
 

Attachments

  • EFI.zip
    8.2 MB · Views: 2

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
Try this EFI in place of your current one.
  1. I have cleaned up your config.plist - removing some unnecessary entries, including most of the DeviceProperties you added.
    • The Spoof SSDT should cover these aspects, all the DeviceProperties will do is conflict with or make the SSDT not work correctly.
  2. I have changed UEFI >APFS > MinDate and MinVersion to 0, as you are running Big Sur and I assume will upgrade to Monterey at some point.
  3. I changed Misc > Security > SecureBootModel from Disabled to Default, as this is the expected condition when running Big Sur or newer.
  4. I removed two unused Tools.
  5. I have added two kexts, RestrictEvents.kext and AppleMCEReporterDisabler.kext, as these are normally required in an AMD Hack.
Use this EFI from a spare USB pen drive.

Let us know if it makes any difference to how the AMD GPU works.
Thanks bro for reply but still same nothing change 7mb (
Screen Shot 1443-07-23 at 10.27.26 AM.png
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,341
OK, try this EFI folder.

I have updated RestrictEvents.kext to v1.0.6, you were using an older version (v1.0.0). Hopefully this newer version of the kext will help.
 

Attachments

  • EFI 2.zip
    10.5 MB · Views: 4

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,341
Can you post a copy of your IOReg so I can see what is happening in your system regarding the AMD GPU.

How to Make a Copy of IOReg (Note 1)
1. IORegistryExplorer/File/Save a Copy As…. (no extension required)
2. Open file to verify (Note 2)
3. Attach to post (Note 3)

Installation
1, Open Downloads/IORegistryExplorer-SLRID_v10.6.3
2. Drag IORegistryExplorer to Applications

Notes
1. An IOReg.txt is not useful. It is not a "Copy of IOReg." Do not attach .txt files.
2. IOReg must open the file. If TextEdit opens, See Note 1.
3. Zip/compress the IOReg file (right-click select Compress....)

Use the version of IORegistryExplorer attached below. Don't use a newer version as they tend to corrupt the IOReg when you save a copy.
 

Attachments

  • IORegistryExplorer-SLRID_v10.6.3.zip
    254.5 KB · Views: 1

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
OK, try this EFI folder.

I have updated RestrictEvents.kext to v1.0.6, you were using an older version (v1.0.0). Hopefully this newer version of the kext will help.
still same issue 7mb didn't work
here my IORegistryExplorer I use the one you attachment
and if you want I give you full access to remote with TeamViewr just DM
 

Attachments

  • Ryesur’s Mac Pro.zip
    540.1 KB · Views: 2
Last edited:

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52
@Polyman You either need to use the SSDT or inject the values under device properties, don't use both methods.
Try these EFI folders and see if that helps.
 

Attachments

  • EFI - Device Properties.zip
    10.5 MB · Views: 2
  • EFI - SSDT Spoof.zip
    10.5 MB · Views: 2

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
@Polyman You either need to use the SSDT or inject the values under device properties, don't use both methods.
Try these EFI folders and see if that helps.
hi thanks for reply i did before separately many times didn't work
i use your device properties keep stuck in boot
and SSDT same issue shows 7mb
IMG_20220225_021355.jpg
 

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
also there something in Device properties
if i add this device_type on GPU APCI root
it will stock on boot blackscreen
never get in os
 

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52
also there something in Device properties
if i add this device_type on GPU APCI root
@Plyman
I think i found out the issue with that. Please try this:
 

Attachments

  • EFI 2 - EFI - Device Properties.zip
    10.5 MB · Views: 2

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
@Plyman
I think i found out the issue with that. Please try this:
still same stock on boot screen
i did this before many times i extract my gpu pci device from hackintool put device_type VGA compatibile
keep stock on boot won't get os
 

Attachments

  • IMG_20220225_125749.jpg
    IMG_20220225_125749.jpg
    3 MB · Views: 5
  • IMG_20220225_130404.jpg
    IMG_20220225_130404.jpg
    3.6 MB · Views: 11

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52
Boot into macOS with the config that works; Use OpenCore Configurator to open the config.plist, navigate to Device Properties and remove all the items in the list and then add all your device properties form the list like shown in the picture.
Save the config and post it here so I can check the address for the display adapter,
 

Attachments

  • Screen Shot 2022-02-25 at 2.16.21 PM.png
    Screen Shot 2022-02-25 at 2.16.21 PM.png
    709.8 KB · Views: 9

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
Boot into macOS with the config that works; Use OpenCore Configurator to open the config.plist, navigate to Device Properties and remove all the items in the list and then add all your device properties form the list like shown in the picture.
Save the config and post it here so I can check the address for the display adapter,
still same stock on boot because adding device type I did it before
post it here
 

Attachments

  • EFI.zip
    10.6 MB · Views: 2

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52
Try this:
 

Attachments

  • EFI 3.zip
    10.5 MB · Views: 1

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,341
@Polyman are you using the ClearNvram and ResetSystem tools (available by pressing the Spacebar while on the OpenCore boot screen) between these EFI folder changes? As some of the Nvram settings may get carried over from booting with a different EFI.
 

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52

Attachments

  • config.plist.zip
    6.9 KB · Views: 1

Polyman

New member
AMD OS X Member
Joined
Feb 22, 2022
Messages
15
@Polyman are you using the ClearNvram and ResetSystem tools (available by pressing the Spacebar while on the OpenCore boot screen) between these EFI folder changes? As some of the Nvram settings may get carried over from booting with a different EFI.
yes i did use before same issue nothing change
 

Cyberdevs

Donator
Donator
AMD OS X Member
Joined
May 19, 2021
Messages
52
@Polyman
I use the same method to activate my R9 270 GPU, I don't use any bootflags so try removing these flags from the NVRAM section i the config:
raddvi radpg=15
After removing these flags reboot the system. reset the nvram and boot into macOS and see if anything changes.
 
Back
Top Bottom
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.