Vram Issue on R9 280

mankurt

New member
AMD OS X Member
May 2, 2020
13
2
3
Hello good people of AMD OSX community. I have successfully installed Sonoma on my computer, everything 's working except for vram. I searched a lot and tried different things even can't name them now. I am using Asus R9 280 Direct CU Top 3GB.
Gpu acceleration is fine, my mouse doesn't gets stuck or anything. I can't play videos , what I think cause of the vram issue.
Please help me find a solution.
Screenshot 2025-03-16 at 05.12.21.png
 

Attachments

Use the Device ID for a HD 7970 shown below, when spoofing your card. It is similar enough and uses the same dev id as the R9 280X.

1002:6798
 
First of all thank you for the quick response. now I did what is told in the guide and have attached ssdt. do I put it in ACPI folder or what will I do with it. I am just trying to make sure cause I crushed 2 os system already :)
 

Attachments

The SSDT-GPU-SPOOF.aml table goes in the /EFI/OC/ACPI folder, with a corresponding entry in the ACPI > Add section of your config.plist.

Just make sure you are using the correct Device Path for the GPU in the SSDT, before you add it to your OC setup.
 
well didn't work. do you think changing smsbios will help? it is imac19,1
 
Yes, you meed to use the iMacPro1,1 or MacPro7,1 SMBIOS with your AMD system, assuming you want to run something newer than Monterey.

Did you add the SSDT-GPU-SPOOF.aml (ACPI Machine Language Binary) table to your ACPI folder and config.plist, or
Did you use the SSDT-GPU-SPOOF.dsl (disassembled ASL File)?

Try booting with the attached SSDT-GPU-SPOOF.aml table. I have edited the Fake Device ID to 1002:6798 in the attached SSDT.
 

Attachments

changed to iMac pro1 ,1 and yes I put .aml file. still same. any bootlegs or adding device properties. I am this close buy a real Mac spend all may savings xd
 
Have you tried the SSDT I provided in post #7?
Did you have the same results?

Are you sure the ACPI Device Path in the SSDT is correct?

Can you post a screenshot showing the Hackintool > PCIe window, with the Window fully expanded to show all entries. As shown in the example below.

Screenshot 2025-03-18 at 16.58.11.png Hackintool > PCIe tab fully expanded to show all details.
 
This is part of the IOReg Name for your R9 280 - GPP8@3,1/GFX0@0, taken from the latest pcidevices.txt file. So you will need to change the SSDT, in order for it to work.

The pcidevices.txt file is a really poor choice for sharing information of this type. As the file only provides part of the IOReg Name. You or anyone looking to help you need to be able to see the whole name.

A screenshot showing the fully expanded Hackintool PCI tab would be a better option. Even just the right hand side of the PCI tab with the IOReg Name and Device Path fully displayed would be better than the pcidevices.txt file.
 
sorry I couldn't expand it to full. resolution is low so there is no room. best I can do is this. I appreciate all you done so far. thank you.
 

Attachments

  • Screenshot 2025-03-19 at 10.07.32.png
    Screenshot 2025-03-19 at 10.07.32.png
    236.7 KB · Views: 5
  • Screenshot 2025-03-19 at 10.00.41.png
    Screenshot 2025-03-19 at 10.00.41.png
    404.1 KB · Views: 4
  • Screenshot 2025-03-19 at 10.01.42.png
    Screenshot 2025-03-19 at 10.01.42.png
    394.5 KB · Views: 2
  • Screenshot 2025-03-19 at 10.02.57.png
    Screenshot 2025-03-19 at 10.02.57.png
    368.3 KB · Views: 2
That’s much better. I will look at this again when o am at my desk later today.
 
Try this SSDT-GPU-SPOOF.aml table.

This table uses the correct IOReg Name (\_SB.PCI0.GPP8.GFX0) for your R9 280 and contains the correct Device ID - 6798:1002
 

Attachments

-v keepsyms=1 npci=0x2000 debug=0x100 unfairgva=1 alcid=13 agdpmod=pikera -radvesa -lilubetaall these are my bootlegs. spoof didn't work. what else I can change
 
  • Like
Reactions: Edhawk
These boot arguments should be removed, as none of these are required.

agdpmod=pikera -radvesa -lilubetaall

These boot arguments can be removed, if your system is booting macOS without any issues.

-v keepsyms=1 debug=0x100
 
I gave up, couldn't make it work. probably have some other problem somewhere else idk. Thank you for your time.
 
  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.