Gigabyte B550 Vision D (Thunderbolt 3) + AMD Ryzen 7 3700X + AMD RX 5600 XT

[oli.mathieu]

Copy SSDT-B550-PTXH-TO-XHC2.aml to EFI/OC/ACPI folder and add an entry for it in config.plist --> ACPI

• Copy SSDT-B550-XHC0-TO-XHC.aml to EFI/OC/ACPI folder and add an entry for it in config.plist --> ACPI
• Copy USBPorts-XHC-XHC2.kext to EFI/OC/Kexts folder and add an entry for it in config.plist --> Kernel

Reboot. Check if sleep/wake works with and without these files.

Quickly :
I reboot with those files enabled in OpenCore ➧ My initial question remains

PTXH is rename SWUS ... how does this happens ? I'm clueless

 

[CaseySJ]

Quickly :
I reboot with those files enabled in OpenCore ➧ My initial question remains

PTXH is rename SWUS ... how does this happens ? I'm clueless

SWUS might be a child device defined in the DSDT or an accompanying SSDT. Will post a modified SSDT that removes SWUS because it’s preventing us from creating XHC2.

 

[Draft]

Some questions:

• Which version of macOS are you running?

Big Sur 11.6.1 (20G221)

• Which version of AirportItlwm.kext is installed?

Version: 2.0.0

• Each version of macOS has its own download of AirportItlwm. Has the correct file been downloaded?

yes

• In Terminal, we can type kextstat | grep -v apple to view all active kernel extensions that don't have "apple" in their name. Is AirportItlwm listed?

Yes, AirportItlwm is listed.

Thanks for your help Casey !

 

[oli.mathieu]

Comments:

• Item 8 in the diagram is for a front panel USB-C header that supports USB 3.x and USB 2.x on a USB Type C port. Does your case have a front-panel USB-C port?
• Item 10 in the diagram is very important. Those are two USB 2.0 internal headers that support a total of 4 USB 2.0 connections.
  • Do you have any internal USB 2 devices?
  • It would be advisable to connect something to USB_E34 and USB_E12 one at a time to determine their port names.

Item 8 and 10 in the diagram were disable in the BIOS .... so I enable them back in the BIOS
I plug adapters like this & this
I connect an USB installation stick in the USB2 & Clone of my Big-Sur in the USB-C
During the boot OpenCore show those 2 recently connected "devices"
MacOS (Finder & Sytem info ➧ USB) & hackintool don't seen any of those "devices"
Any idea ?
Thanks
[EDIT]
My bad I forgot to disable the USBport.kext
Now I see device connected to the Item 8
But Devices connected to item 10 remain unseen
Diagram updated :

The type of the internal usb-c header is 10 ... if i'm not mistaken.
here's my USBPort.kext with corrections for my EFI. Can you check it ?
[EDIT 2]
Once I enable the 2 SSDTs and the .kext
The USB2 device appears in the Finder
here is an example of ioReg.

Many thanks

 

[CaseySJ]

Item 8 and 10 in the diagram were disable in the BIOS .... so I enable them back in the BIOS
I plug adapters like this & this

Yes, very good thinking. I use similar breakout headers myself.

I connect an USB installation stick in the USB2 & Clone of my Big-Sur in the USB-C
During the boot OpenCore show those 2 recently connected "devices"
MacOS (Finder & Sytem info ➧ USB) & hackintool don't seen any of those "devices"
Any idea ?
Thanks
[EDIT]
My bad I forgot to disable the USBport.kext
Now I see device connected to the Item 8
But Devices connected to item 10 remain unseen
Diagram updated :
The type of the internal usb-c header is 10 ... if i'm not mistaken.
here's my USBPort.kext with corrections for my EFI. Can you check it ?

Regarding Item 8:

• When you connect a USB 2.x device with the USB-C cable inserted in one orientation, does it connect to HS31?
• When you then flip the USB-C cable of the same device, does it connect to HS32 instead?
• If so, then it is Type 10 (0x0A).

Next:

• Do you have a USB 3.x device with a USB-C cable?
• Have you tried connecting that device to Item 8?

[EDIT 2]
Once I enable the 2 SSDTs and the .kext
The USB2 device appears in the Finder
here is an example of ioReg.

Many thanks

Regarding Item 10 (internal USB 2 headers):

• It is necessary to disable both USB SSDTs and the USB kext, reboot, and then connect devices to these headers.
• After connecting one USB 2 device at a time, we can identify the port names.
• Have you mapped these ports yet?

Attached are an updated SSDT (for PTXH) and USB kext. This sets Item 8 to Type 10. But we should still add some missing ports.

 

[oli.mathieu]

Regarding Item 8:

• When you connect a USB 2.x device with the USB-C cable inserted in one orientation, does it connect to HS31?
• When you then flip the USB-C cable of the same device, does it connect to HS32 instead?
• If so, then it is Type 10 (0x0A).

Yes that the behaviour I had .... but I connect an USB 3 device via this adapter

Regarding Item 10 (internal USB 2 headers):

• It is necessary to disable both USB SSDTs and the USB kext, reboot, and then connect devices to these headers
• After connecting one USB 2 device at a time, we can identify the port names.

Hackintool can't do it, i'll try with ioreg and report

Attached are an updated SSDT (for PTXH) and USB kext. This sets Item 8 to Type 10. But we should still add some missing ports.

Thanks

 

[TurbineSeaplane]

I am so sorry, disregard my “nvmefix.kext” problem, user error on my part. Apologies. The system boots fine, with NVMeFix.kext disabled.

I will report back if the issue is fixed or not. Thanks a lot for your help

How's it going with your SN750 drive without NVMEfix.kext?

I'm having all kinds of panic issues with my SN750, but I've always been using it (thought I needed to)

 

[oli.mathieu]

Attached are an updated SSDT (for PTXH) and USB kext. This sets Item 8 to Type 10. But we should still add some missing ports.

Is it OK that USBPort.kext has an iMacPro1,1 model and I Use MacPro7,1 SMBIOS ?
Names are now correct

I still Struggle to discover those USB internal port.
I'll work away next week. I'll keep in touch after
many thanks

 

[CaseySJ]

Is it OK that USBPort.kext has an iMacPro1,1 model and I Use MacPro7,1 SMBIOS ?

Good catch. We need to change it to MacPro7,1. Change made in the attached file.

 

[Vorshim92]

The configuration looks correct. Are you using RestrictEvents.kext version 1.0.5?

Yes. 1.0.5. It's the correct one?