[SUCCESS] ASUS Prime Z390-A + i7 9700K + RX VEGA 64 (LC Edition)

[nezoat]

I was seeing the flash drive not detected issue on certain ports before I used the SSDT, but now it's detected no matter where I plug it in. If you don't see USB2 devices on the USB3 port, it makes me think there is a missing SSxx entry for the corresponding HSxx USB 3 entry. I noticed your device on the front panel is HS10, but on my MB HS10 is on the rear at the bottom. Looks like there must be some differences between your MB and mine, which means the SSDT may not be a perfect match for you. Mine is a Z390-A Prime too, so IDK. Since you're already using IOReg and are this far along in figuring out how your devices are identified, you may as well just go ahead and go through every physical port with a USB2 and USB3 device and take notes as to their SS/HS identity, then edit the SSDT.dsl file, then export to the SSDT.aml file and you'll have your own perfect SSDT. I'm surprised it doesn't match already though!

 

[soeryobadja]

I was seeing the flash drive not detected issue on certain ports before I used the SSDT, but now it's detected no matter where I plug it in. If you don't see USB2 devices on the USB3 port, it makes me think there is a missing SSxx entry for the corresponding HSxx USB 3 entry. I noticed your device on the front panel is HS10, but on my MB HS10 is on the rear at the bottom. Looks like there must be some differences between your MB and mine, which means the SSDT may not be a perfect match for you. Mine is a Z390-A Prime too, so IDK. Since you're already using IOReg and are this far along in figuring out how your devices are identified, you may as well just go ahead and go through every physical port with a USB2 and USB3 device and take notes as to their SS/HS identity, then edit the SSDT.dsl file, then export to the SSDT.aml file and you'll have your own perfect SSDT. I'm surprised it doesn't match already though!

Thanks a lot for your encouragement.
I was thinking (or, to be exact, making myself brave enough) to start do my own SSDT edit this time, noob considered here.
Some thing to reconfirm before I do this:
1. I did not remove the USBinjectAll.kext from L/E in my current build, while reading your post, I need to remove the kext. Is this affecting the result of your SSDT injection? Is generally, USBInjectAll.kext needs to be removed after I inject custom SSDT, as I read from the teference guide about custom SSDT, nothing said about removing the kext.
2. I still use the SSDT filename as is you provided in your post, while reading some posts that mostly SSDT for USBs have the file named SSDT-UIAC.aml, will this also contributing to my issue of USB2?
3. Do you think the DVD issue has something to do with SSDT? Or is it just that the DVD is not compatible (with whatever reason)?

Thanks again.

 

[nezoat]

The USBInjectAll needs to be removed if you're using an SSDT, that's the whole idea and I would expect there to be issues if you don't, perhaps what you're experiencing. I don't know how they may interact.

The filename of the SSDT does not matter, to my knowledge and from my experience. It will be discovered in the folder.

I don't know if your DVD issue is related to the SSDT. My guess is that it's not related, but you'll have to eliminate the other issues first, such as removing your USBInjectAll.

 

[soeryobadja]

The USBInjectAll needs to be removed if you're using an SSDT, that's the whole idea and I would expect there to be issues if you don't, perhaps what you're experiencing. I don't know how they may interact.

The filename of the SSDT does not matter, to my knowledge and from my experience. It will be discovered in the folder.

I don't know if your DVD issue is related to the SSDT. My guess is that it's not related, but you'll have to eliminate the other issues first, such as removing your USBInjectAll.

Thank you.
Will try them tomorrow and see how its result.

 

[soeryobadja]

Thank you.
Will try them tomorrow and see how its result.

@nezoat
Deleted the USBInjectAll, but the result still the same, i.e. USB2 device not detected in by front panel USB3 port. Now even, the front panel USB2 port does not detect a USB2 device as well. Looking further at the IOReg, the USB2device@USB3port is detected but did not mounted, same case as USB2device@USB2port. However, having USB3device(USB3 hub in this case)@USB3port works and detected by the system.
I will work further on the custom SSDT later within the week, and will post here the result.
Thank you for your support.

 

[soeryobadja]

@nezoat
Deleted the USBInjectAll, but the result still the same, i.e. USB2 device not detected in by front panel USB3 port. Now even, the front panel USB2 port does not detect a USB2 device as well. Looking further at the IOReg, the USB2device@USB3port is detected but did not mounted, same case as USB2device@USB2port. However, having USB3device(USB3 hub in this case)@USB3port works and detected by the system.
I will work further on the custom SSDT later within the week, and will post here the result.
Thank you for your support.

@nezoat
Continue the tweak today, with no result.
0. I made a fresh clean install to my Mojave.
1. Done through the port discovery and track all the connected ports.
1a. Front connected USB3.0 port still cannot detect properly a USB2 device.
2. Put all the discovered port to SSDT file and save as aml file.
3. Put the built aml file to EFI/Clover/ACPI/Patched, delete USBInjectAll.kext, and restart computer.
4. All port still identified, now with HS06 missing (while on the aml file, I put HS06 port).

5. The HS02 port is for USB2.0 front port; previously before SSDT patching the port still can read device (USB2 drive and USB Wireless Keyboard Dongle), but now as it is not detected, it cannot read any device.
6. I replace my SSDT with the one you provide, reboot the computer, but result of IOReg still the same.
7. Herewith I attached my SSDT-UIAC-my.aml file, ones that I built according to the Port Discovery I did with my computer.
8. As well my problem reporting file attached.

I will be very glad if you willing to spend some time looking at my case here.

PS. The DVD-ROM still cannot be read by the computer, either when I use my own SSDT or yours.

Thanks in advance.

 

[soeryobadja]

@nezoat
Continue the tweak today, with no result.
0. I made a fresh clean install to my Mojave.
1. Done through the port discovery and track all the connected ports.
1a. Front connected USB3.0 port still cannot detect properly a USB2 device.
2. Put all the discovered port to SSDT file and save as aml file.
3. Put the built aml file to EFI/Clover/ACPI/Patched, delete USBInjectAll.kext, and restart computer.
4. All port still identified, now with HS06 missing (while on the aml file, I put HS06 port).
View attachment 411354
5. The HS02 port is for USB2.0 front port; previously before SSDT patching the port still can read device (USB2 drive and USB Wireless Keyboard Dongle), but now as it is not detected, it cannot read any device.
6. I replace my SSDT with the one you provide, reboot the computer, but result of IOReg still the same.
7. Herewith I attached my SSDT-UIAC-my.aml file, ones that I built according to the Port Discovery I did with my computer.
8. As well my problem reporting file attached.

I will be very glad if you willing to spend some time looking at my case here.

PS. The DVD-ROM still cannot be read by the computer, either when I use my own SSDT or yours.

Thanks in advance.

Hello @nezoat
Today tried again building custom SSDT using Hackintool, but still result the same.
What I do just now:
1. Run port discovery using Hackintool v2.5.9, limiting the port and reducing some more port.
2. Disabled USB Port Limit Patch 1,2,3 in KextToPatch
3. Put a new entry under ACPI/DSDT/Patches to Rename EC0 to EC__
4. Put SSDT-UIAC generated by Hackintool to Clover/aCPI/Patched
5. After restart, all the deleted HS ports comes back but the SS ports already limited to what is defined inside SSDT.
6. One noticeable thing, port HS06 always missing, this port supposedly used by front USB2 port, previously the port can be used but now (starting after I inject the custom SSDT), this port is always missing and cannot be used.
7. Error reporting files as attached.
Maybe I am missing something here? If you may, please help in checking my files and pointed out where my mistake?
Also maybe @RehabMan willing to help.

Thank you in advance.

 

[soeryobadja]

Hello @nezoat
Today tried again building custom SSDT using Hackintool, but still result the same.
What I do just now:
1. Run port discovery using Hackintool v2.5.9, limiting the port and reducing some more port.
2. Disabled USB Port Limit Patch 1,2,3 in KextToPatch
3. Put a new entry under ACPI/DSDT/Patches to Rename EC0 to EC__
4. Put SSDT-UIAC generated by Hackintool to Clover/aCPI/Patched
5. After restart, all the deleted HS ports comes back but the SS ports already limited to what is defined inside SSDT.
6. One noticeable thing, port HS06 always missing, this port supposedly used by front USB2 port, previously the port can be used but now (starting after I inject the custom SSDT), this port is always missing and cannot be used.
7. Error reporting files as attached.
Maybe I am missing something here? If you may, please help in checking my files and pointed out where my mistake?
Also maybe @RehabMan willing to help.

Thank you in advance.

Found the solution. What I did:
1. Disable the Port Limit Patch.
2. Rebuild my SSDT from scratch, reading through the guide from @RehabMan once again.
3. Reinstall my USBInjectAll.kext (as I did not see any instruction in the guide to remove the kext).
4. Reboot

Voila! The USB structure is exactly as I build inside the SSDT patch.

I deactivate front USB2.0 and USB3.0 ports, as seems like there is some problem (USB2.0 recognized as Hub, while USB3.0 cannot read any USB2.0 device).
And found a solution to DVD ROM problem (does not mount when plugged in a USB3.0 Hub). Turns out, the DVD ROM has to be plugged in a USB2.0 port on the back connector and not to my USB3.0 hub. And it also cannot work when plugged into both my front USB2.0 and USB3.0 ports.

Considering this issue closed with lesson learned.

 

[dolgarrenan]

Hello guys, has any of your tried new BIOS v1005?? Any improvements? The fact that you can add up to 128GB RAM is a plus that would make the prime Z390A a tough workstation to beat.

 

[alexm91]

Hi @Jakeofspades

Can you please post the BIOS settings you did?