Help Needed: Radeon RX 6900 XT Issue with nootrx.kext - 'Unsupported signal, check your device output' Error

Danish297

Danish297

Member
AMD OS X Member
Oct 26, 2021
83
1
11
8
CPU:
AMD 3950X
@CaseySJ @Edhawk @Shaneee @leesurone /All

I need assistance with fixing my MSI Radeon RX 6900 XT. I attempted to use nootrx.kext, but it gives me the error "Unsupported signal, check your device output."

Here’s what I’ve tried so far:
1. Removed WhateverGreen.kext and installed nootrx.kext (from this GitHub release) with boot arguments: -v debug=0x100 keepsyms=1.
2. Manually compiled nootrx.kext in both Release and Debug versions, following this tutorial.
3. Used nootrx.kext from this thread on tonymacx86. It worked briefly but then the system hung after a few minutes.
4. Created my own nootrx.kext following the steps from the thread mentioned in point 3, but I am still encountering the same "Unsupported signal, check your device output"
5. Followed the guide from this EliteMacx86 thread.
 
Sort by date Sort by votes
  1. Which output are you using?
    1. DisplayPort or HDMI?
  2. Are you using a video adapter or cable adapter?
  3. Have you tried using WhateverGreen.kext (WEG)?
    1. What did WEG show, does it work?
 
Upvote 0 Downvote
What do you need to "fix"? A RX 6900 XT should be supported by macOS.
If it really is a XTXH, spoofing a regular 6900 XT should be easier and safer than NootRX.
 
Upvote 0 Downvote
Should work OOB unless it's the XTXH then it just needs spoofed to a regular version,


Device Properties
device-id = BF730000
 
  • Like
Reactions: Max.1974
Upvote 0 Downvote
@Edhawk

1. Which output are you using? DP
1.DisplayPort or HDMI? DP
2. Are you using a video adapter or cable adapter? cable adapter.
3. Have you tried using WhateverGreen.kext (WEG)? YES
1. What did WEG show, does it work? YES

@etorix
Mine is MSI Radeon RX 6900 Xt

@Shaneee
my device-id: 0x73AF


I'v attached working/notworking config.plist and gpu-details for more details.
 

Attachments

Upvote 0 Downvote
Just use WhateverGreen.kext, with the agdpmod=pikera boot argument, if NootRX.kext gives you issues.
 
  • Like
Reactions: keef247
Upvote 0 Downvote
@Edhawk

Yes, I’m currently using a workaround, but it doesn’t provide "Metal support," which prevents many graphics applications from functioning properly.

I’d appreciate any assistance in enabling Metal support for my GPU.
Please see the attached screenshot for more details.
 

Attachments

  • Metal_Support_Missing.png
    Metal_Support_Missing.png
    161.7 KB · Views: 24
Upvote 0 Downvote
If you have any DeviceProperties in your OC config.plist then NootRX.kext will give you a black screen instead of the Login screen.

You need to delete any/all DeviceProperties from your config, and use boot arguments or custom SSDTs to inform macOS of the properties required for the devices to work correctly.
 
Upvote 0 Downvote
Edhawk said:
If you have any DeviceProperties in your OC config.plist then NootRX.kext will give you a black screen instead of the Login screen.

You need to delete any/all DeviceProperties from your config, and use boot arguments or custom SSDTs to inform macOS of the properties required for the devices to work correctly.
Click to expand...
tried but still same:oops:
 
Upvote 0 Downvote
Shaneee said:
Should work OOB unless it's the XTXH then it just needs spoofed to a regular version,


Device Properties
device-id = BF730000
Click to expand...
After following the instructions from https://github.com/TylerLyczak/Unsupported-6900XT-Hackintosh-Fix, I'm experiencing some unusual behavior:

1. The first boot worked but froze after a few minutes.
2. The second boot got stuck on the Apple logo.
3. The third boot and subsequent ones resulted in a black screen.

Could you please review the attached settings and help me identify what might be going wrong?
 

Attachments

  • bootArgument.png
    bootArgument.png
    23.4 KB · Views: 17
  • device_properties.png
    device_properties.png
    31 KB · Views: 17
  • GFX_ioregistryexp.png
    GFX_ioregistryexp.png
    134.8 KB · Views: 16
  • gfxutil_gfx.png
    gfxutil_gfx.png
    14.7 KB · Views: 21
  • config.plist
    config.plist
    29.1 KB · Views: 2
  • SSDT_BRG0.png
    SSDT_BRG0.png
    128.1 KB · Views: 22
Upvote 0 Downvote
First Screenshot - If you are using NootRX.kext you shouldn't be using agdpmod=pikera or -radcodec boot arguments. These are WEG boot arguments.

Second Screenshot - Delete the DeviceProperties for your RX6900 XT, these will clash with NootRX.kext and cause a black screen instead of the login screen to show.

Fourth Screenshot - This shows you need an SSDT-BRG0.aml table for your dGPU.

Fifth Screenshot - this shows the contents of an SSDT-BRG0.aml table, but it isn't set out as I would expect.
The screenshots below show the 2 x SSDT-BRGx.aml tables I created for my RX 6700XT and AMD SATA controller on my X570 system.

Screenshot 2024-09-04 at 17.52.49.png SSDT-BRG0.aml - SATA Controller pci-bridge fix

Screenshot 2024-09-04 at 17.52.57.png SSDT-BRG1.aml - RX 6700 XT pci-bridge fix

The two screenshots below shot the fixes applied by these SSDT's.

Screenshot 2024-09-04 at 17.53.54.png Screenshot 2024-09-04 at 17.54.25.png

If your SSDT-BRG0.aml table is set correctly you should see a similar 'Fix' for the missing IOReg Name for your RX 6900 XT.

Given the data in the SSDT-BRG0.aml you are using, I am going to assume you didn't create the SSDT from the Device Path for your RX 6900 XT, your system DSDT.aml and Corpnewt's SSDTTime script.

If you post a copy of your System DSDT.aml I will create an SSDT-BRG0.aml table for your RX 6900 XT, using the Device Path shown in your fourth screenshot in the post above - PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 
Upvote 0 Downvote
Edhawk said:
First Screenshot - If you are using NootRX.kext you shouldn't be using agdpmod=pikera or -radcodec boot arguments. These are WEG boot arguments.

Second Screenshot - Delete the DeviceProperties for your RX6900 XT, these will clash with NootRX.kext and cause a black screen instead of the login screen to show.

Fourth Screenshot - This shows you need an SSDT-BRG0.aml table for your dGPU.

Fifth Screenshot - this shows the contents of an SSDT-BRG0.aml table, but it isn't set out as I would expect.
The screenshots below show the 2 x SSDT-BRGx.aml tables I created for my RX 6700XT and AMD SATA controller on my X570 system.

View attachment 14911 SSDT-BRG0.aml - SATA Controller pci-bridge fix

View attachment 14912 SSDT-BRG1.aml - RX 6700 XT pci-bridge fix

The two screenshots below shot the fixes applied by these SSDT's.

View attachment 14913 View attachment 14914

If your SSDT-BRG0.aml table is set correctly you should see a similar 'Fix' for the missing IOReg Name for your RX 6900 XT.

Given the data in the SSDT-BRG0.aml you are using, I am going to assume you didn't create the SSDT from the Device Path for your RX 6900 XT, your system DSDT.aml and Corpnewt's SSDTTime script.

If you post a copy of your System DSDT.aml I will create an SSDT-BRG0.aml table for your RX 6900 XT, using the Device Path shown in your fourth screenshot in the post above - PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
Click to expand...
As you recommended, I tried using nootrx.kext and removed all the device properties entries, but it didn’t work. I’m now attempting to spoof my GPU.
Attaching my full EFI folder , let me know anything else needed here.
 

Attachments

Last edited:
Upvote 0 Downvote
etorix said:
This is 6900 XTXH. And, as explained, you need to name a PCI bridge to apply device properties.

Please put WEG back and try this SSDT in place of your SSDT-BRG0; it names the bridge and spoofs a 6900 XT.
Click to expand...
thanks for sharing but no luck, same issue :(
 
Upvote 0 Downvote
I’ll get back to you tomorrow.
 
Upvote 0 Downvote
Can you test this please.
 

Attachments

Upvote 0 Downvote

Attachments

  • Screenshot 2024-09-05 at 3.37.45 PM.png
    Screenshot 2024-09-05 at 3.37.45 PM.png
    172.1 KB · Views: 18
Upvote 0 Downvote
Here is the SSDT-Bridge.aml table for your RX 6900 XT.


This when compared to your previous SSDT-BRG0 table has only a few differences, but they are important for the dGPU to work correctly.

SSDT_BRG0.png Original SSDT-BRG0.aml

Screenshot 2024-09-05 at 14.51.18.png Revised SSDT-Bridge.aml

Add this new SSDT to your /EFI/OC/ACPI folder and with a new entry for the SSDT in your config.plist.

See if this helps.
 

Attachments

Upvote 0 Downvote
Assuming you are now using WhateverGreen.kext in place of NootRX.kext, you need to replace the DeviceProperties PCIRoot entry in your config.plist.

Use this Device Path in place of the one you are currently using for your RX 6900 XT.

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 
Upvote 0 Downvote
Edhawk said:
Assuming you are now using WhateverGreen.kext in place of NootRX.kext, you need to replace the DeviceProperties PCIRoot entry in your config.plist.

Use this Device Path in place of the one you are currently using for your RX 6900 XT.

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
Click to expand...
I just cross-checked, this path only I'm using it.
 

Attachments

  • device-path.png
    device-path.png
    34.5 KB · Views: 21
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.
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.