idle Posted November 10, 2022 Share Posted November 10, 2022 HP Z2 G5 SFF, Core i5-10500, 16Gb DDR4-2666, Intel UHD630, Ventura 13.0, DELL U2718Q OpenCore 0.8.5 I installed macOS Ventura on top of Monterey, the config was taken from some forum, everything works, except for the correct, not deformed image on the monitor. I tried to turn on HIDPI mode via one-key-hidpi, HiDPI mode turn on, but the image became vertically squished. The computer is connected to the monitor via DisplayPort. Spoiler Please help with advice on how to solve the problem of a flattened image. EFI.zip Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 10, 2022 Moderators Share Posted November 10, 2022 Was it the same when running Monterey? Link to comment Share on other sites More sharing options...
idle Posted November 11, 2022 Author Share Posted November 11, 2022 Yes, I tried to solve this problem there as well, but I also did not succeed in this. But I really want to solve it... It seems to me that everything is in the monitor, more precisely, that MacOS does not receive the correct data about the capabilities of the monitor or receives, but not quite the correct data... In particular, MacOS indicates that a 61-inch monitor is connected, although in fact the U2718Q has only 27 inches. Can Hackintool be of any help? In particular, the "Displays" section. What should I specify in this window? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 11, 2022 Moderators Share Posted November 11, 2022 what type of connection are you using? DP ? HDMI? Have you tried lowering the refresh rate? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 12, 2022 Administrators Share Posted November 12, 2022 You can ignore the size of screen reported by macOS; I've experienced that too with several TV screens that I hooked over HDMI to my Hacks over the years. In my case, it was just a cosmetic thing and never had any impact on screen resolution or manner in which the video was displayed on screen. With regards to your OC config: You've created a dedicated kext to inject your screen's EDID; you no longer enable it so (I guessed it was of no help) so I'd just get rid of it; I've never seen EDID injection required for anything else but laptop's built-in screens. You've got a 4K screen so check the value assigned to DVMT; you'll need at least 64MB allocated at BIOS level. In that respect, you must evidently remove your patch that reduces stolenmem to 19MB (framebuffer-stolenmen 00003001 DATA). You patch your framebuffer's connectors in a way I'm not familiar with: You've opted for CFL framebuffer desktop layout 0x3E9B0007 which defines the following graphics properties: 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 i.e. 3 x DP ports on connectors con0 (0105), con1 (0204) and con2 (0306). Your patches change these connectors to: [1] busId: 0x06, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x05, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [3] busId: 0x04, pipe: 8, type: 0x00000800, flags: 0x000003C7 - ConnectorHDMI 01060900 00040000 C7030000 02050A00 00040000 C7030000 03040800 00080000 C7030000 Can you explain what drove you to such busId patches or was it just part of a config you acquired somewhere? Can you post an IOReg extract to examine things? As asked by Jake, do specify the type of connection you use for your screen. Your HDMI patch would lead us to believe you use HDMI need but your SysInfo screenshot indicated TB/DP. Link to comment Share on other sites More sharing options...
idle Posted November 21, 2022 Author Share Posted November 21, 2022 I am using a DP-mDP cable. Changing the frequency does not help. Spoiler Link to comment Share on other sites More sharing options...
idle Posted November 23, 2022 Author Share Posted November 23, 2022 On 11/12/2022 at 11:20 AM, Hervé said: Can you explain what drove you to such busId patches or was it just part of a config you acquired somewhere? Can you post an IOReg extract to examine things? As asked by Jake, do specify the type of connection you use for your screen. Your HDMI patch would lead us to believe you use HDMI need but your SysInfo screenshot indicated TB/DP. Yes, all this was taken completely from the config that I found. I am connecting the monitor via DisplayPort. IOReg attached. ioreg.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 23, 2022 Administrators Share Posted November 23, 2022 I invite you to experiment with a bootable USB key on which you'll install your current bootloader setup with a modified config file where you'd remove all those connector's patches, i.e. all those framebuffer-conX-YYYY lines. Link to comment Share on other sites More sharing options...
idle Posted November 25, 2022 Author Share Posted November 25, 2022 Unfortunately it didn't help, everything remained the same... Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 26, 2022 Administrators Share Posted November 26, 2022 You did reset NVRAM at OC Picker after you changed your config and rebooted, right? I also note you never got rid of the stolenmem patch... Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now