- Joined
- Feb 21, 2016
- Messages
- 392
- Motherboard
- Gigabyte Z390 Aorus Master
- CPU
- i9-9900K
- Graphics
- RX 5700 XT
- Mac
- Mobile Phone
All my kexts is at L/E installed via kextbeast and everything work. I have not any kext in C/K/O
I have just finished a 10.13.6 install with a Z370 Aorus Gaming 7 build(i7-8700k, RX-560, 16gb Vengeance RAM, Samsung 1Tb NVMe, F7 bios, Clover 4458), and it was not an easy build, despite the clarity and detail that HackaShaq provided. I have fixed all of the problems so far, the ones relating to audio, the Atheros LAN port and others, but one problem still remains unsolved with the USB 3.1 ports, a problem that jiffyslot referred to in post #374.
USB SSDs won’t mount on the desktop. Same holds true for my Vantec external hard drive case that comes with a USB 3.0 connection and contains a conventional 1 Tb 3.5” hard drive. Other older Vantek hard drive enclosures with USB 2 connections mount and work fine. All drives and USB hardware work fine when connected to the USB 2.0 port headers on the motherboard. But none of these external drives mount and work in any of the yellow or the blue USB 3.1 Gen 1 ports, but they do mount when connected to the single red USB 3.1 port, the one that is described by Gigabyte as a Gen 2, Type A port. In addition, curiously enough, when I remove the SSD from the buss powered USB 3 external enclosure and substitute a conventional 2.5” hard drive, that hard drive does mount correctly. And if I leave both enclosures(3.5” and 2.5”) connected while restarting the computer, they do turn up in the Clover boot panel that comes up after the Z370 Aorus posts. So at least at this point these drives are being recognized by Clover. But they still do not appear on the desktop.
I have tried different versions of the USBInjectAll.kext(0.6.3-0.6.6) and the latest versions of FakePCIID and FakePCIID_XHCIMux kexts in Library/Extensions, all to no avail. I also compared jb007’s config.plist(post #399) with mine and added a couple of ACPI patches that seemed relevant that my config did not contain, but this didn’t help either. I have not tried any SSDTs that treat USB configurations, for I don’t have any to try. I figured that if HackaShaq didn’t need one to create his ‘perfect build,’ then I didn’t need to go down that road either. But if anyone has such a SSDT that would fix or possibly treat this problem, it would be great if it could be posted here in this thread.
Any ideas on what is going on here? Any suggestions would be greatly appreciated by me and I bet jiffyslot too - thanks!
sudo touch /System/Library/Extensions && sudo kextcache -u /
/Volumes/EFI/EFI/CLOVER/kexts/Other/
├── AppleALC.kext (v1.2.7)
├── FakeSMC.kext (v6.26-344-g1cf53906.1787)
├── Lilu.kext (v1.2.5)
└── USBInjectAll.kext (v0.6.5)
/Library/Extensions/
├── ACS6x.kext
├── ATTOCelerityFC8.kext
├── ATTOExpressSASHBA2.kext
├── ATTOExpressSASRAID2.kext
├── ArcMSR.kext
├── AtherosE2200Ethernet.kext
├── CalDigitHDProDrv.kext
├── EnergyDriver.kext
├── FakeSMC.kext
├── FakeSMC_ACPISensors.kext
├── FakeSMC_CPUSensors.kext
├── FakeSMC_GPUSensors.kext
├── FakeSMC_LPCSensors.kext
├── HighPointIOP.kext
├── HighPointRR.kext
├── IntelMausiEthernet.kext
├── PromiseSTEX.kext
├── SoftRAID.kext
├── XHCI-200-series-injector.kext
└── org.pqrs.driver.Karabiner.VirtualHIDDevice.v060800.kext
Hi HackaShaq, did you use/build your final bootup disk using UEFI Boot Mode with Native NVRAM or Emulated NVRAM?
In a terminal, set a persistent variable entry in memory:
nvram TEST_VAR=DELETE_ME
Restart system.
In a terminal look for the persistent variable entry previously set in memory:
nvram -p | grep TEST_VAR
Delete the persistent variable entry from memory using the terminal:
nvram -d TEST_VAR
No, I ultimately did not use any patches, when you get back, have a look at my config.plist and also my bullet point 2 "disable all USB port patches". I might have it all wrong, but it is working fine for me.
I'll try and see if I can emulate the problem with a SSD attached via a USB 3.1 Gen 1 (Old USB 3!) @borbo120.
Enjoy your vacation!
Yes from what I read, you don't need the patch once you have your custom SSDT. The question was more directed to @borbo120
For the moment I am using the USBInjectall.kext with the 10.13.6 patch by PMHeart. This works fine for me and the USB3 ports recognise my external drives. The only issue I have, is that once the system gets back up from "Sleep", it ejects the external drives not properly.
I hope to solve this issue with the SSDT.