![]() ![]() This guide does not recommend using a multi-monitor setup with the iGPU. The primary purpose of this Guide is to activate the on-board HDMI port on your motherboard with the intention of using that port to drive a single monitor. A large number of problems are due to the use of televisions, old monitors, or monitors without DisplayPort 1.2+ or HDMI 1.4+ support. This includes (a) modern CPU, (b) modern motherboard, and most importantly, (c) modern monitor. This guide is best suited to relatively new, modern components. This guide is meant to supplement - not replace - existing framebuffer patching guides.ĭo you have a 360, 370, or 390 series motherboard with desktop Coffee Lake processor, either HDMI or DP monitor, and a Gigabyte, ASUS, ASRock, or MSI motherboard and want to try your luck with a pre-built framebuffer patch? Then check out Compilation of Patches for Various Motherboards at the end of this Guide. If you have a relatively recent motherboard with an Intel iGPU, and on-board HDMI is not working, here's a general guide that may help. WhateverGreen 1.4.1 was released today, and it fixes the on-board HDMI output problem with macOS Catalina. The next versions of Lilu and WhateverGreen are expected to fix the HDMI output problem with macOS Catalina. Generally we want to avoid use of third-party tools - though if it's impossible otherwise, then you can link it.Building a CustoMac Hackintosh: Buyer's Guide ![]() In general, try to avoid using "non-Acidanthera" tools when possible. Your PR must be run through a markdown lint and have all issues fixed. Images must be hosted locally in the repo under the. We would also appreciate sources for any bigger commits to make it easier on us to verify the info you provide is valid We will generally tell you why it is rejected though or ask for revisions. Pull Requests can be denied if we feel it does not fit or has inaccurate information. Some of the published conditions for a Dortania PR: I would have to find out who and where to ask before preparing a PR which might be ignored. So far I have not found the developer feedback very encouraging when I submitted issues via the issue trackers. There are a lot of conditions though for submissions and it would take time and communication, if they are even willing to change the default recommended tool from USBMap to USBToolBox. It would be nice if there is a chance that it could be incorporated. ![]() Thank you for pointing out these issues to me! You can see the relevant changes in my OP. Do you have a link where this explained with technical detail for developers?Įdit/Added: Ok, I found the reference to the USB Port Capabilities in the Advanced Configuration and Power Interface Specification ACPI_6.0.pdf on page 524 where it becomes clear that they are referring to the physical ports. You are probably right about the physical port type, and I will change this as well after I can confirm it. I can certainly change this in the guide by moving it as an optional advice to the part where it may actually be needed. Initially this made use of USBToolBox frustrating. As this was not clearly explained in the original documentation I kept disabling and enabling ports unintentionally until I found out that the app was forcing the disabling on both companions. I needed to do this on each hackintosh where I used the tool. The main reason I disabled Bind Companions was so that I could disable ports individually, instead of as fixed together pairs. If you wish to see the port location names (saved in the comments of the generated file) when you check your ports in macOS, you can use the Hackintool > USB tab and observe where your devices get plugged in. For this purpose type in a name such as: C:18:Middle-Left-USB-C and C:22:Up-Left-USB3 (As seen from the direction you are looking at them when the case is upright). You should name each port with a clear location Name. You may need to switch back and forth between the Select Ports screen and the Port Discovery screen after you have been able to determine the physical location of each displayed port. I also recommend to add comments, for the purpose of long term maintainability. Since the functional USB 2 companion ports (which are hosted on physical USB 3 ports) need to be described by their physical connector type, they should be set as USB 3 in the USB mapping. For defining the physical USB C ports (here with switch) type: T:18:9įor defining the internal port type (without outside user access): T:17:255 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |