onemanosx

[ref]dlhenke[/ref], I've a wavlink hub that didnt work as expected except for the card reader. No solution for me either.

You're welcome, hope it helps!

Is your DSDT patched with the correct USB power properties?

[ref]MaLd0n[/ref], thank you!

You can try

System architecture between the two machines are different requiring different smbios settings. Read up on SMBios options and its effects on hackintosh.

[ref]mi.shytka[/ref], are u using a custom kext for for x99? if so, look into it and its also asmedia chip. I only did the usual xhci dsdt fix by RH thats all.

Fresh install will be the better option

Discovering Ports in batch and exclusion of ports used by keyboard and mouse Other esteemed hackintoshers may want the option to discover their used USB ports in batches i.e implementing HSxx then SSxx/SSPx. This method will reveal each HSxx/ SSxx/SSPx batches in one pass. 1. Discover ports used by USB Keyboard and Mouse - open the app ioreg and look for the ports used by Keyboard and Mouse - in my case its HS09 and HS10 - therefore, I include the following boot arguments in clover like so uia_include=HS09;HS10 - doing this you will have control over your keyboard and mouse when you use exclude_hs identifier 2. Identifying HSxx ports only and exclude all SSxx/SSPx identifiers - add these 2 boot flags a. -uia_exclude_ss b. -uia_exclude_ssp << no longer required as per 9 Nov 2018 latest commit - reboot and discover all of HSxx ports using USB 2.0 device like in the video link - write down the discovered ports on a piece of paper 3. Identifying SSxx ports only and exclude all HSxx and SSPx identifiers - delete the above bootflags (a) and (b) - add these boot flags c. -uia_exclude_hs d. -uia_exclude_ssp << no longer required as per 9 Nov 2018 latest commit e. do not forget to include uia_include=HS09; HS10 - reboot and discover all SSxx ports using your USB 3.0 device like in the video link - write down the discovered ports on a piece of paper 4. Identifying SSPx ports only and exclude all HSxx and SSxx identifiers - follow steps similar to above instruction set except you replace -uia_exclude_ssp with -uia_exclude_ss instead 5. Final Step - Finally, with the ports you had discovered in steps 1, 2 and 3, you can now use the uia_include or uia_exclude boot flags for your discovered ports a. in my build example, I prefer to use uia_exclude. So, the final boot argument will look like like this uia_exclude=HS05;HS08;HS11;HS12;HS13;SS05;SS06 (all of these are my unused ports) b. if one prefers to use uia_include boot argument, the final boot flag will look like this uia_include=HS01;HS02;HS03;HS04;HS06;HS07;HS09;HS10;HS14;SS01;SS02;SS03;SS04 (all of these are the used ports discovered)

[ref]mi.shytka[/ref], my guess is you are using a pcie card for USB 3.1 and your motherboard only has USB 3.0. Thus the difference in your USB info tree If you would like your system to be patched for optimisation, please post in DSDT request forum.

[ref]artnr28[/ref], https://Olarila.com/forum/viewtopic.php?f=79&t=7370

For brightness, remove backlightinjector.kext but keep the ssdt and patch in clover. Reboot and Enjoy.

DSDT vs SSDT USB Injection which is better for me? While I love the simplicity of having all patches in DSDT, but for the purpose of USB injection, it is a little tricky with this motherboard build. Just look at the previous effort in determining the correct port adr for my USB type C (read here: https://Olarila.com/forum/viewtopic.php?p=63533#p63533). While the method works, the "jump" in adr between HS04 and SS08 is rather strange! In normal circumstances, HS04 is paired with SS04 (instead of SS08 in my case) or HS03 with SS07 where SS03 is more likely. But, its not! So, the solution of using SSDT injection is much preferred as such that the ports are correctly addressed and DSDT is "saved" from further chaos! Plus, I am also able to conduct easier troubleshooting via table blocking if the need arises. Look at how lovely the numbers lines up And the SSDT sample in use

Pentium graphics is not supported in any Mac OS

Freebie! For experimental and learning purposes, I created a custom USB injector kext for this motherboard build. Following the guide found here https://www.hackintosh-forum.de/forum/thread/33300-kext-as-kext-can-oder-usb-3-0-ohne-usbinjectall/ How to Use: 1. Place MSI-B360-USB.kext in Clover/Kexts/Other 2. Remove UsbInjectAll.kext and any other USB injector kexts 3. Reboot! Enjoy this fully functional kext! Update version for port renaming 09022019-MSI-B360-USB.kext.zip MSI-B360-USB.kext.zip

Nvidia graphics not supported in Mojave at this time.

[ref]honghd1993[/ref], should not have major differences. Except that you are using an NVIDIA GPU? Mojave has no Nvidia webdrivers as of this date. You may want to try High Sierra instead. Also what MaLd0n said.

USB Type C not properly detecting device Overview MSI specifies this motherboard to have support for USB 3.1 Gen 2 and comes with a single USB type C port. I have a USB-C hub that has 3 USB 3.) type A ports, an SD card reader and a miniSD card reader slot. But, the ports would not be detected properly and this problem can be seen either by ioreg or USB devices in System Report. The early methods managed to detect card readers and USB type A ports but only in USB 2.0. But, this is a type C Gen 2! Lets look into the problem. Port Detection We will require a USB 3.1 device and a USB 2.0 thumb drive to proceed with the port detection. Unfortunately, I do not have the new generation device to achieve 10gbps, so a USB 3.0 device will do for now. Let's continue. With all the ports enabled, following the steps outlined in this post here https://Olarila.com/forum/viewtopic.php?p=62887#p62887 and here https://Olarila.com/forum/viewtopic.php?p=61162#p61162, I managed to determine the ports used by plugging in my USB 3.0 and USB 2.0 devices. Next, I cleaned up my hack by deleting the unused ports to result only the below used ports. Plus, the recently USB C port is correctly showing USB 2.0 and USB 3.0 devices in its proper device location. And while I am at it, I changed the ioname in DSDT to load driver for USB 3.1 Host controller. Not sure if this makes any difference, but it sure is an eye candy. https://i.imgur.com/Zdq1IQ2.png' alt='IMGUR>'> Back Port Summary https://imgur.com/v6D91N7

No idea.. I dont use Nvidia GPU

Enable USB without kext injector (a continuation) In my previous attempt to enable USB ports without any injector kext, it works with a simple script on DSDT. You may read the attempt made from this link here https://Olarila.com/forum/viewtopic.php?p=61162#p61162. However, I also noticed some errors in verbose. Though the errors does not seem to affect functionality of the enabled ports, I just had to delve into the matter. The solution is quite simple for the knowledgeable in programming language and I am not even in their ranks. Below are the errors I found and possibly with the correct package, the verbose can be eliminated rather easily. For each usb devices in DSDT, I firstly determine what kind of ports they are by referring back to MSI handbook. With that knowledge in mind, here's what I did to the USB devices and its appropriate code to enable : a. for USB external 2.0 ports b. for USB 3.1 external port c. for internal USB ports d. for USB 3.0 external ports

Always GPT for macOS

Yes, you can.

Enabling Intel Quick Sync What I did: 1. enable integrated graphics in bios 2. PEG set as primary 3. Using Whatevergreen patching+ lilu In About This Mac > Graphics/Dispplay, no trace of iGPU is shown except for the RX 580. However, in ioreg clearly IMEI is loaded and using MacX Video Converter Pro, prove that hardware encoding is enabled. So yeah, I initially thought About This Mac is an indicative but I got fooled However, if you'd like to see the cosmetics display in About This Mac > Graphics/Display, injecting intel in clover with ig-platform-id is the way to go.

Option1: First, need to know how your native brightness keys is handled. You can follow simple instruction here under "Brightness keys" https://www.tonycrapx86.com/threads/guide-patching-dsdt-ssdt-for-laptop-backlight-control.152659/ then patch DSDT according to your finding. Option 2: Simply change the the brightness command keys from macOS Keyboard shortcut