Problems getting a R7 240 to work

it appears to be the same except for the no-gfx-spoof entry which i don't know what that is, you can try different ids to see which one will work on your card.
 
do you have by any chance a list of possibly working ids?
 
The zipped file below contains the device ID's for most if not all of the AMD GPU's natively supported in macOS.

See if you can find one that is similar to your cards (0x10026611) device id in this file, hopefully one will work.

The AMD 8000 Controller looks the most promising.
 

Attachments

Alright I'll report back if I ever get something to work. Thank you guys for the support (y)
 
no-gfx-spoof is needed in the device property sometimes for a device ID to work.
 
Faced the same problem. Has no one decided? The video card is exactly the same. HP R 7 240. I am ready to accept any help.
 
no-gfx-spoof is needed in the device property sometimes for a device ID to work.
Could you help me with this? I checked all the fakeid from AMD 8000, all to no avail. Now I have already checked half of the AMD 7000, but so far it has not worked out. I would be very grateful.
 
The device ID 3D680000 should work. In your device property in the config for the GPU also add no-gfx-spoof with the value 01000000.
 
The device ID 3D680000 should work. In your device property in the config for the GPU also add no-gfx-spoof with the value 01000000.
Unfortunately, I also tried, it didn't work out. I attach screenshots of my settings. Hands are already dropping :(
 

Attachments

  • B97E2DF6-6FF1-4948-B7D6-17D001F8AB3A.jpeg
    B97E2DF6-6FF1-4948-B7D6-17D001F8AB3A.jpeg
    5.6 MB · Views: 13
  • 9DF22F30-CDEE-4C92-9081-AE24BCB50F9F.jpeg
    9DF22F30-CDEE-4C92-9081-AE24BCB50F9F.jpeg
    8.6 MB · Views: 13
  • C8C399AC-B1C2-4244-A1E8-9BD0D578AA2E.jpeg
    C8C399AC-B1C2-4244-A1E8-9BD0D578AA2E.jpeg
    5.8 MB · Views: 12
  • 880EE863-3FD0-4904-8182-4595F018BBD4.jpeg
    880EE863-3FD0-4904-8182-4595F018BBD4.jpeg
    7.2 MB · Views: 11
  • 9CEBFE03-2AFC-4E01-9E8F-21F41F831988.jpeg
    9CEBFE03-2AFC-4E01-9E8F-21F41F831988.jpeg
    5.9 MB · Views: 12
You don't need to use -lilubetaall boot arg. Monterey is not a beta release, it isn't required for Ventura either.

You may need to use the following boot arg
  • -radcodec
To force the spoofed PID to be used in AMDRadeonVADriver.
 
You don't need to use -lilubetaall boot arg. Monterey is not a beta release, it isn't required for Ventura either.

You may need to use the following boot arg
  • -radcodec
To force the spoofed PID to be used in AMDRadeonVADriver.
Could you look at my EFI? After all the operations, I get a black screen. The computer is working at the same time, it does not turn off.
 

Attachments

@Alexflyme which make and model of motherboard are you using with the FX-4300 4-core CPU?
 
Never mind.

Try this EFI see if it makes any difference.
 

Attachments

  • Like
Reactions: Shaneee
Never mind.

Try this EFI see if it makes any difference.
Thank you, I will definitely try on Monday. Unfortunately, the computer is at work now, there is no possibility. I will definitely let you know about the result on Monday.
 
Never mind.

Try this EFI see if it makes any difference.
Found a problem why I didn't have an image after loading EFI. A slot was reassigned to SSDT-BRG0, I inserted the video card into another one and the image appeared. But the problem remained, still display 3mb. Your EFI also tried, the black screen does not reach the EFI bootloader (as soon as I choose to boot from a USB flash drive, the screen is black immediately and even EFI does not appear.)
 
Never mind.

Try this EFI see if it makes any difference.
Could there be a problem in SPOOF? I inserted my video card into a Windows computer. The path shows this - ACPI(SB)#ACPI(PCI0)#ACPI(GPP8)#ACPI(X161)
 
Yes, the spoof won’t work if the ACPI path is not correct.
 
  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.