Because you have accelerated graphics, when you get back on the system (tomorrow or whenever) can you please confirm the port/bus connectors very quickly as follows:
Once we get the data point from @poles regarding the new Case 2 configuration (with con1 type = HDMI), we should have the empirical data we need to revise/update framebuffer settings for ASUS.
@CaseySJ Also tried Case 1 it didn't work, after that i found another 2 working configs
and
Bus Id 0x04 also work for the DP port.
In the end DP port on ASUS doesn't care about Bus Id(0x01,0x04,0x05 all worked), HDMI port only works with Bus Id 0x02, and both need correct Indexes to work - 1 for DP, 2 for HDMI. Doesn't matter in which row you put them just requires correct settings.
Last problem i have with HDMI port is that it doesn't turn on unless i reconnect it after logging in into OS. It does light up in FBPatcher and appears in IOReg but monitor says it doesn't have HDMI input connected until i reconnect it.
In the end DP port on ASUS doesn't care about Bus Id(0x01,0x04,0x05 all worked), HDMI port only works with Bus Id 0x02, and both need correct Indexes to work - 1 for DP, 2 for HDMI. Doesn't matter in which row you put them just requires correct settings.
This is a fantastic observation! And it does seem to fit the dots provided by other replies to this thread. These are the original values:
Row 1: Index 2, BusID 0x02, Type HDMI <-- may not be operational and user may have intended DVI-D
Row 2: Index 3, BusID 0x04, Type HDMI
Row 3: Index 1, BusID 0x01, Type DP
We can see that Index 1 is DP and BusID = 0x01. But as you stated, DP is flexible -- it can work on BusID 0x01, 0x04, and 0x05. What matters is that it gets Index 1. Row number does not matter. Index seems to specify physical order of the ports.
We can see that Index 2 is HDMI and BusID = 0x02. As you again stated, HDMI is very particular. It only works with BusID 0x02 and its Index is 2. Row number does not matter.
We can see that Index 3 is also HDMI and BusID = 0x04. This port is actually DVI-D on @poles motherboard, who verified that DVI-D works with this setting.
So I think it's reasonable to test the following 2 simpler configurations to see which works best:
Condition 1: Row 1: Index 1, BusID 0x05, Type DP
Row 2: Index 2, BusID 0x02, Type HDMI
Row 3: Index 3, BusID 0x04, Type DVI-D
Last problem i have with HDMI port is that it doesn't turn on unless i reconnect it after logging in into OS. It does light up in FBPatcher and appears in IOReg but monitor says it doesn't have HDMI input connected until i reconnect it.
Last problem i have with HDMI port is that it doesn't turn on unless i reconnect it after logging in into OS. It does light up in FBPatcher and appears in IOReg but monitor says it doesn't have HDMI input connected until i reconnect it.
Because of your multi-monitor (multi-port) configuration, please see this post by @jaymonkey which I'll repeat here because this is a framebuffer patching guide...
I also found out that some UHD 630 users have to use the AGDP Patch (Apple Graphics Display Policy) which can be applied by using WhatEverGreen and the boot argument agdpmod= (see WEG Readme for values), seems to be needed for 4K displays and/or multi-monitor support on UHD 630.
Using your guide I was finally able to get my 10.14.1 system to the point where I get the black screen when plugged into my HDMI. I have a few issues now though that I think may pertain to my motherboard. It is a generic motherboard from a pre-built HP Pavilion 590-p0066.
1. When I log into my system via TeamViewer and look in the about my Mac section, it now shows nothing in terms on Vram as opposed to 7 mb when I boot with the invalid fake-ids. Is this what SHOULD happen while I am not plugged into any display, or do I have an error somewhere? I was expecting to see the accelerated value, but instead it just says Intel UHD graphics 630
2. When I attempted to follow the rest of your guide (opening FB patcher and checking the ports), none of my connectors turn red to indicate the location of my HDMI, so I am unable to proceed further
I am using platform ID: 3E9B0007 and Device id: 0x3E92. My motherboard only has an HDMI and a VGA port, and my monitor has 2 HDMI and one Display Port. I will attach my IOReg and EFI folder, any insight you may have is much appreciated!
@MadDan Let's continue the debug of your Gigabyte H370N WiFi motherboard here. The board has two HDMI ports and a single DP port.
One of the HDMI ports is activated with:
Case A: Put HDMI-1 in Row 2: BusID 0x06, Type HDMI SUCCESS
Then we tried to activate the second HDMI port as follows:
Case 1: Put HDMI-2 in Row 1: BusID 0x04, Type HDMI FAILED Case 2: Put HDMI-2 in Row 1: BusID 0x05, Type HDMI FAILED
Case 3: Put HDMI-2 in Row 3: BusID 0x04, Type HDMI FAILED
There are several plausible permutations remaining. The lines in green are confirmed HDMI rows, but can still tweak their BusIDs. Our test condition is in blue. Please note that even if none of these settings works, we benefit by reducing the set of plausible entries, and can try a final set after this.
Others in this thread have gone through the same (exhausting) trial-and-error procedure. You are not alone!
Case A: Use BusID 0x06 for confirmed HDMI. Row 1: BusID 0x02, Type HDMI Row 2: BusID 0x06, Type HDMI
Row 3: BusID 0x05, Type DP
Hi @CaseySJ 15 Jan 2019:Intel FB-Patcher has been renamed to Hackintool.
Using your guide I was finally able to get my 10.14.1 system to the point where I get the black screen when plugged into my HDMI. I have a few issues now though that I think may pertain to my motherboard. It is a generic motherboard from a pre-built HP Pavilion 590-p0066.
1. When I log into my system via TeamViewer and look in the about my Mac section, it now shows nothing in terms on Vram as opposed to 7 mb when I boot with the invalid fake-ids. Is this what SHOULD happen while I am not plugged into any display, or do I have an error somewhere? I was expecting to see the accelerated value, but instead it just says Intel UHD graphics 630
2. When I attempted to follow the rest of your guide (opening FB patcher and checking the ports), none of my connectors turn red to indicate the location of my HDMI, so I am unable to proceed further
I am using platform ID: 3E9B0007 and Device id: 0x3E92. My motherboard only has an HDMI and a VGA port, and my monitor has 2 HDMI and one Display Port. I will attach my IOReg and EFI folder, any insight you may have is much appreciated!
Your IOReg shows the magical AppleIntelFramebuffer connected and ready at PCI0@0 --> IGPU@2. Was this IOReg taken through a remote TeamViewer connection?
And when you ran Intel FB-Patcher through the TeamViewer connection, it showed no highlighted ports even with HDMI cable connected to your monitor? This can actually make sense if HDMI BusID is not correct.
So I would suggest the following cases first. We will try only to activate HDMI without regard for any other port, as follows:
Case A1: The attached config.plist already contains the settings in the Case A1 spoiler below, so you can use this file as-is (it's based on your EFI folder). You can then replace the <key>Properties</key> section with the other cases one at a time and test the HDMI port.
Row 1: Index 1, BusID 0x04, Type HDMI
Row 2: Index -1
Row 3: Index -1
Row 4: Index -1
Case A2: We don't need to test this because it's the default case for Platform ID 0x3E9B0007.
Row 1: Index -1
Row 2: Index 2, BusID 0x04, Type HDMI
Row 3: Index -1
Row 4: Index -1
Case A3:
Row 1: Index -1
Row 2: Index -1
Row 3: Index 3, BusID 0x04, Type HDMI
Row 4: Index -1
Thanks for re-starting our discussion here. Well I tested all four cases, no change. The one thing I did notice was that after the first test (Case A), the FB Patcher showed our all our connections as HDMI, instead of DP, as in all previous tests (attached screen). Should the Bus Id value match that as depicted in your examples for row 1, 2 and 3? If so, I'm not seeing that consistency in the post Patcher results. Seems like 1 is always 0x05, 2 is always 0x04, and 3 is always 0x06. I believe our one good connection is row 2 0x04.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.