Guide - MSI B360 Gaming Arctic (Catalina)

[onemanosx]

where mojave NIVIDA

No idea.. I dont use Nvidia GPU

[ford2201]

and when it's mine and you know how to make a connection to intel 630 together connectively NVIDIA GTX 1050 operation signal it has a bios auto GPU set but does not give the signal to do exactly

[erroruser]

[ref]ford2201[/ref], there is nothing for nvidia in mojave

[onemanosx]

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

Edited August 12, 2019 by Guest

[honghd1993]

This guide may apply to msi b360 Gaming pro carbon

[MaLd0n]

[ref]honghd1993[/ref], u can follow it for all mobos, just don't use same DSDT, the other files is same, same procedure

[onemanosx]

[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.

[honghd1993]

I use nvidia 1070 ti

Added in 1 minute 11 seconds:

guide me install

[onemanosx]

nvidia 1070 ti

Nvidia graphics not supported in Mojave at this time.

[honghd1993]

Main Msi B360 gaming pro carbon

Cpu i3 8100

Vga msi 1070ti gaming x

Wifi tp-link t9e

Thanks

Added in 1 minute 19 seconds:

10.13.6

Added in 1 minute 3 seconds:

Guess I installed 10.13.6 on my motherboard thanks

[onemanosx]

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

Edited February 8, 2019 by Guest

[onemanosx]

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

[mi.shytka]

Why are my usb3.1 not fall into xhci

Архив.zip

[onemanosx]

[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.

[mi.shytka]

Thank .

Usb3.1 built-in, try to ask for MaLd0n.

Added in 13 minutes 23 seconds:

Let me see your DSDT. I can do it myself.

[onemanosx]

[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.

[recash168]

thanks a lot

[onemanosx]

[ref]recash168[/ref],

[onemanosx]

Ways to enable supported Wifi

One of the most common method to enable Wifi is to use kexts placed in Clover>Kexts>other.

Current kexts supporting broadcom chipset are mainly named as below:

- AirportBrcmFixup.kext https://github.com/acidanthera/AirportBrcmFixup

- Lilu.kext v1.2.5 or later (https://github.com/acidanthera/Lilu)

However, there are also other alternatives. And such alternatives makes use of

1. Clover or

2. inject wifi properties via SSDT or DSDT

Here I will just describe the Clover injection method.

There are 3 ioname devices in Mojave that will work with this method.

1. pci14e4,43ba

2. pci14e4,43a0

3. pci14e4,43a3

All we need to do is to inject either one of the id's above to the below method

Clover Injection Method 1 - Just follow the picture screenshot

Clover Injection Method 2 - pciaddr is derived from wifi's pcidebug in ioreg

That's all for today's tips and tricks! Happy Hackintoshing!

Test the methods and let me know how it works out for you!

Edited November 30, 2018 by Guest

[Sampath007]

Good job