Jump to content

Problem with dual monitors

Thebes Knossos

By Thebes Knossos,
in Intel

 Share
37 posts in this topic

Recommended Posts

Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

Hi all. All is working perfect with my Gigabyte H310M SP2 V2 exept dual screen cold start. Hotplugin a second monitor works perfect.

IGpu i3-9100 UHD 630,  latests Opencore and .kexts , my AAPL,ig-platform-id is detected as <07 00 9b 3e> device-id <91 3e 00 00>, iMac19,1 emulated

Monitor 1 : Samsung S24C350 1920*1080 connected via Hdmi to Framebuffer 2 (main monitor)

Monitor 0 : IISonic 1280*1080 connected via VGA to Framebuffer 0 (extended monitor)

 The phase with progress bar displays correctly, then displays correctly on the VGA and when the HDMI monitor wants to display the desktop I have flickering with horizontal black bars on both monitors.

I have try to force Port types without success like written here : https://github.com/dortania/OpenCore-Post-Install/blob/master/gpu-patching/intel-patching/connector.md

Same problem under Monterey, Ventura, Sonoma, but no problem with Linux or Windows on same machine

How to debug more ?

Image from the net, i'm not alone with the problem I see :

 

 

Issue_startup_screen.png

Edited by Thebes Knossos
add image
Link to comment
https://www.insanelymac.com/forum/topic/361471-problem-with-dual-monitors/
Share on other sites
Thebes Knossos
Thebes Knossos
Posted
  • Author
Posted (edited)

@deeveedee  Yes of course, good idea. Single Monitor is working perfect, only cold start with boths monitors connected gives result as on picture.

AttachedOC.zip

Edit:

Opencore version 1.0.5  and added kexts:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   51    5 0                  0x2f000    0x2f000    as.vit9696.Lilu (1.7.1) AE004BE7-2FA9-36BF-AC0A-D40FCCA10FCE <9 7 6 3 2 1>
   52    0 0                  0xd000     0xd000     as.vit9696.RestrictEvents (1.1.6) 93759885-EE52-31AE-92ED-2F2B01B3AD52 <51 9 7 6 3 2 1>
   53    0 0                  0x10000    0x10000    com.rehabman.driver.USBInjectAll (1.0) D6827B73-57CC-341E-B5E1-237D1FA630DB <16 15 6 3>
   54    0 0                  0x83000    0x83000    as.vit9696.WhateverGreen (1.7.1) CF177CEF-BFC9-3C58-840F-180C416F0D3A <51 16 9 7 6 3 2 1>
   55    2 0                  0x18000    0x18000    as.vit9696.VirtualSMC (1.3.7) DE3A2587-8A7F-389A-BC66-19277E0D0835 <51 15 9 7 6 3 1>
   56    0 0                  0xc000     0xc000     as.vit9696.SMCProcessor (1.3.7) 91BEA9A4-5B0B-3F73-AA90-2F298D2EAF8A <55 51 15 9 7 6 3 2 1>
   66    0 0                  0x23000    0x23000    ru.joedm.SMCSuperIO (1.3.7) 7B96A828-ED93-3984-8C08-1DF88A5389AA <55 51 15 9 7 6 3 2 1>
   71    0 0                  0x84000    0x84000    com.insanelymac.RealtekRTL8111 (2.4.2) 9BB95C1D-4C73-3AB7-8F2A-A3327D2F4E87 <49 16 7 6 3 1>

Edited by Thebes Knossos
deeveedee
deeveedee
Posted
Posted (edited)

@Thebes Knossos You are only patching one connector (con2) in your config.plist.  Is con2 connected to the single monitor that doesn't "cold start"?  If not what is the connector (conX) that doesn't "cold start"?

 

EDIT: Also, AAPL,ig-platform-id is commented out in your config.plist.  Does this default to a value in your IORegistry and if so, what is the default AAPL,ig-platform-id?

 

EDIT2: I see this in your first post: AAPL,ig-platform-id is detected as <07 00 9b 3e> 

 

EDIT3: I did read the following in your first post, but it is unclear to me which connector (con0 or con2 is not "cold starting" properly.

Monitor 1 : Samsung S24C350 1920*1080 connected via Hdmi to Framebuffer 2 (main monitor)

Monitor 0 : IISonic 1280*1080 connected via VGA to Framebuffer 0 (extended monitor)

 The phase with progress bar displays correctly, then displays correctly on the VGA and when the HDMI monitor wants to display the desktop I have flickering with horizontal black bars on both monitors.

 

EDIT4: @Thebes Knossos To be sure we're referencing the same framebuffer definition, the defintion of 3e9b0007 (see here) is  

ID: 3E9B0007, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00801302
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
Model name: Intel UHD Graphics 630
Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
01050900 00040000 C7030000
02040A00 00040000 C7030000
03060800 00040000 C7030000
Edited by deeveedee
Thebes Knossos
Thebes Knossos
Posted
  • Author
Posted

Thanks for answer. Boths screens goes to images like above when cold boot if connected boths. If single monitor connected all is ok for boths. The commented lines was test. AAPL,ig-platform-id is removed because WhateverGreen did the job. The patch for con2 (hdmi monitor) is really not necessary for single monitor, it reduce just the boot sequence for it because WhateverGreen initialise it first as Dp without the patch. Con0 is Vga and Con1 is DVI digital, not connected actually. I have same values as you when looking with Kackintool.

deeveedee
deeveedee
Posted
Posted

After our brief exchanges, I get the feeling that you know more about this stuff than I do, so I don't have more to add.  If you want to experiment with other frame buffers, follow my methodology here.  Good luck.

Thebes Knossos
Thebes Knossos
Posted
  • Author
Posted

Thanks for your link ans tests. My platform have same iGPU, but Device ID is 0x3E91 here on the Gigabyte. I have test some different AAPL,ig-platform-id compatible with mine, but yes not all. The ones tested gives all same problem at cold boot, I think the problem is generic. I repeat warm connector plug is working with dual screen. In your table, I don't know if multiscreen says cold boot dual screen oy warm hot plug.

deeveedee
deeveedee
Posted
Posted (edited)

If you add these boot-args, do you notice any difference?

  

darkwake=2 igfxonln=1 igfxagdc=0

 

EDIT: I suspect that the boot-args won't make a difference, but they're worth testing.  If you want to experiment with framebuffer patching, you'll need DeviceProperties similar to what I have added in the attached plist.  Could you test the attached config.plist to make sure that it still "works" the same as your original config.plist?

config.plist.zip

Edited by deeveedee
Thebes Knossos
Thebes Knossos
Posted
  • Author
Posted

Thanks for your help and modified .plist. Tested 'as is', I have black screen when connected single Hdmi monitor on con2. Back to mine, added just 2 lines :

<key>framebuffer-con2-busid</key>
<data>BgAAAA==</data>                       <!-- 06 00 00 00 -->
<key>framebuffer-con2-index</key>   
<data>AgAAAA==</data>                       <!-- 02 00 00 00 -->

result: blackscreen too, so one or both values is/are false. No pipe to specify in this case ?

When I look with IORegistryExplorer at Framebuffer2 I have port-number 7 (if set with Whatevergreen without patch) and AAPL,DisplayPipe <00 00 00 00>

deeveedee
deeveedee
Posted
Posted (edited)

@Thebes Knossos Please test the attached config.plist (with index = 3 for con2).  We need to make sure that the connectors (con0, con1 and con2) are connected as we think they are.

 

EDIT: If you inspect the attached config.plist, you will see that it does not change the index and busID for con0 and con2 from the defined framebuffer 0x3e9b0007 here.  The DeviceProperties in the attached config.plist change only con1 (essentially disabling it by setting busID = 0 and index = -1).

config.plist.zip

Edited by deeveedee
deeveedee
deeveedee
Posted
Posted (edited)

The attached config.plist enables con1 (so all connectors are enabled) and changes con1 port type to HDMI.  Please test it.  I'm still trying to confirm that the connector mappings are as we think.

 

EDIT: If that attached config.plist does not "work" as your original plist, please confirm that your original config.plist still "works" as it did originally (without black screen).

config.plist.zip

Edited by deeveedee
Thebes Knossos
Thebes Knossos
Posted
  • Author
Posted (edited)

Yes progress here, this order changing saves the single hdmi monitor, it works again (like my original). But no change for cold dual connected monitor, at the end of boot i have picture like post 1 (like my original). I have then to disconnect / reconnect hdmi monitor to have normal picture (like my original). Perhaps because monitor on con0 is connected with VGA.

Your mofifications compared with meld:

deeveedee.thumb.png.e9c6b4da4d8d97ccc919b281d493a41e.png

Edited by Thebes Knossos
deeveedee
deeveedee
Posted
Posted (edited)

The 'order changing' did not affect the framebuffer patching (I re-ordered slightly to make it easier for me to match the patches with the framebuffer definition).  The change that mattered was enabling con1.

 

Please try the attached config.plist which disables con2.

 

config.plist.zip

Edited by deeveedee
deeveedee
deeveedee
Posted
Posted

@Thebes Knossos Sorry - I had to upload a new version of the config.plist to my previous post.  Please make sure that the config.plist that you test has this in the boot-args: 

igfxonlnfbs=0x01

NOT

igfxonlnfbs=0x02

 

deeveedee
deeveedee
Posted
Posted

@Thebes Knossos After experimenting on my hack, I learned that I can't "disable" connector con1 as I thought when con0 and con2 are enabled.  The attached config.plist changes the busID of con1 (the connector you're not using) to 0, sets SMBIOS = MacMini8,1 and enables Booter > Patch> SkipBoardIDCheck (to allow Tahoe to boot with MacMini8,1).  I'd like to know if using MacMini8,1 SMBIOS makes any difference in your graphics, since I have found that MacMini8,1 is the most "forgiving" SMBIOS for framebuffer patching.

 

Since you are using USBInjectAll.kext for USB, the SMBIOS change won't affect USB; however, the SMBIOS change will affect other System Settings (Energy, Keyboard...).  If changing SMBIOS improves graphics, then we can focus on the System Settings.

config.plist.zip

deeveedee
deeveedee
Posted
Posted (edited)

Yes - I was hoping that firmware would help.  Thanks for your patience with my attempts to help.  I don't have any more guesses.  I think you're facing one, maybe two issues:

  • VGA (analog) coupled with HDMI (digital) isn't handled well by macos/WhateverGreen
  • Possibly... i3 iGPU has been problematic in other graphics threads.  The i3 iGPUs don't behave the same as their i5, i7, i9 counterparts

The fact that you have a hot-plug work-around is interesting to me, but I'm not sure how to extrapolate that to a working framebuffer patch.

 

Sorry I couldn't help.

 

EDIT: Here are some things that you may want to try on your own

  • Experiment with different framebuffers (AAPL,ig-platform-id)
  • Experiment with different WhateverGreen boot-args (one at a time):  gfxrst=1, gfxrst=4, igfxrpsc=1
  • Experiment with different framebuffer-con0-flags and framebuffer-con2-flags

 

EDT2: I have a VGA port module that I can plug into my HackMini8,1.  When I get some time, I'll experiment with it and let you know if I learn more.

Edited by deeveedee
deeveedee
deeveedee
Posted
Posted (edited)

@Thebes Knossos I swapped the 3rd DP port in my HackMini8,1 for a VGA port and changed the con2 port type to DP.  With two digital DP->DVI displays and an analog VGA display, all displays work perfectly.  No cold start problems and no display artifacts.  My config.plist is attached (derived from my EFI posted here).

 

Hopefully this gives you some suggestions.  I am using quality, shielded video cables.  My CPU is i9-9900.  I have never used an i3 CPU, but have seen others with framebuffer patching issues when dealing with i3.

 

A summary of my tested configuration is as follows:

  • Two (2) DVI displays connected via DP->DVI adapters (corresponding to con0 and con1 framebuffer connectors in the attached config.plist)
  • One (1) VGA display connected via VGA->VGA cable (corresponding to con2 framebuffer connector in the attached config.plist)
  • i9-9900 CPU / UHD 630
  • macOS Tahoe Beta 6
  • Open Core 1.0.5, WhateverGreen.kext 1.7.0

 

Arrange Displays

Spoiler

Screenshot2025-08-15at4_23_04PM.png.cb203fd41a2ef06c7cb8b79258790ae0.png

 

EDIT: Note that I needed to manually adjust the resolution of my VGA display - the VGA resolution was not properly detected by macOS.

config.plist.zip

Edited by deeveedee
 Share
Go to topic listing
×
×
  • Create New...