Gigabyte X870E AORUS PRO 9950x3D

svan71

svan71

Donator
Donator
AMD OS X Member
Oct 24, 2020
128
78
28
33
USA
I retired my intel hack and I'm trying to get sequia running on my new build kernel panics galore :(. Any help would be greatly appreciated.

Gigabyte X870E AORUS PRO
WD Black 2TB
32 GB (for now)
AMD 6950XT

Seqoia is loaded. No internet with onboard networking. I'm using an USB NIC currently. Graphics working audio working but I need to turn the volume all the way up to hear it..

No Wi-Fi at the moment, waiting for card.
 
Last edited:
Sort by date Sort by votes
svan71 said:
I retired my intel hack and I'm trying to get sequia running on my new build kernel panics galore :(. Any help would be greatly appreciated.

Gigabyte X870E AORUS PRO
WD Black 2TB
32 GB (for now)
AMD 6950XT

No Wi-Fi at the moment, waiting for card.
Click to expand...
I notice you aren't loading SSDT-CPUR.aml which you need to be able to boot any AM5 board.
 
  • Like
Reactions: svan71
Upvote 0 Downvote
Which CPU are you using?
Have you set the AMD Kernel Patches to match the number of cores in your CPU?
Are you using an RX 6900 XT or an RX 6950 XT?
The later needs a spoofed Device ID to work in macOS.
 
Upvote 0 Downvote
Edhawk said:
Which CPU are you using?
Have you set the AMD Kernel Patches to match the number of cores in your CPU?
Are you using an RX 6900 XT or an RX 6950 XT?
The later needs a spoofed Device ID to work in macOS.
Click to expand...
Hi, The 6950XT, I believe the kernel patch is correct for 16 9950x3d. The 6950XT was patched previously on an old AMD hack I have the saved .aml files. Iv'e successfully loaded Sequoia.
 
Last edited:
Upvote 0 Downvote
Your old AMD hack probably had a different IORegName/DevicePath, compared to your current motherboard. So it may not work.

You need to check the Device Path in Windows to see if it needs editing.

I’ll have a look at your EFI tomorrow (Monday).
 
  • Like
Reactions: svan71
Upvote 0 Downvote
Looking at the pcidevices.txt and your SSDT-RX6950XT.aml table I don't think your SSDT's IOReg Name is correct.

While only the end two sections of the IOReg Name (0/SWDS@0/GFX0@0) are shown in the pcidevices.txt file, they are not what is shown in the SSDT - External (SB.PCI0.GPP0.SWUS.SWDS.VGA_, DeviceObj).

As they don't match - GFX0 vs VGA_, the SSDT won't work.
 
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.