Intel UHD Graphics 630 - Display not running at 4K

[felix23]

Hey guys. I got a new UHD Monitor yesterday (3840x2160) and wanted to connect it. I am using the Intel UHD Graphics 630 IGPU and thought that it would be relatively simple as my Mainboard has HDMI 1.4b which supports 3840x2160 at 30 Hz. Is it possible to get the screen recognized correctly? Also, the image is not that bad, it is not stretched or showing black bars but you can definitely see the pixels and it is not 4k. I will attach some screenshots. I tried fixing this using SwitchResX but had no success so far.

Thanks for your help in advance
Felix

As I took the screenshot, I realized that the screen seems to be running at 2560 × 1440 as that's the size of the screenshot.

 

[felix23]

I also did an EDID Override as the screen had this pinkish tone to it. I don't know if that makes a difference.

 

[jaymonkey]

@felix23,

Make sure you enable WEG's pixel clock patch (required for 4K displays on IGPU) by using the "-cdfon" boot argument.
See the HiDPI Display section of this guide for more info :-

An iDiot's Guide To Lilu and its Plug-ins

An iDiot's Guide To Lilu and its Plug-in's Last Update: 22nd Jan 2021 (Add note about OpenCore config.plist modifications) About this Guide Note: This guide was written when Clover was the boot loader of choice as such the config.plist examples in this guide are mostley Clover specific ... if...

www.tonymacx86.com

Cheers
Jay

 

[felix23]

Ok, I added this boot argument. I also tried following the guide to get the 2048 MB VRAM but I don't know if it worked. This is why I attached my config.plist. The reason why I am unsure is that About this Mac says 1536 but Hackintool says 2048.

Also, when running ioreg | grep IMEI I get nothing:

Thanks for your help

 

[felix23]

ok, I've added HECI → IMEI Fix and now I get the correct output from the terminal. but the screen is still not running at 4k and the HDR option is not available even though the monitor is HDR capable and is working with windows. also, the refresh rate is greyed but to get 4k via HDMI 1.4b I have to set it to 30 Hz.

Please help me.

Would it be easier if I just get an AMD card? (I could potentially get an RX 5700 XT in a few days).

 

[jaymonkey]

@felix23,

The Hackintool screen shot in post #4 shows that the Intel UHD 630 Graphics device has a ACPI name of "GFX0". This is incorrect ... it should be called "IGPU" ... WEG should have taken care of the renaming but clearly it hasn't.

This would suggest to me that WEG is failing to load for some reason (or loading and exiting/aborting before it's finished its work)) .... you could try installing the debug versions of Lilu + WEG and enable loggin to see if this is the case (see WEG's documentation for help with loggin).

You could also try enabling the GFX0 -> IGPU rename in Clover to see if that helps.

Cheers
Jay

 

[felix23]

You could also try enabling the GFX0 -> IGPU rename in Clover to see if that helps.

Thanks, it is now named IGPU

But now it shows 1536 MB so I think I made a mistake somewhere here:

<key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                CQClPg==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>
            </dict>
        </dict>

I have attached the full config.plist
I got the ig-platform-id from the Hackintool patch section
Do I need to have a device id in there?

 

[jaymonkey]

Thanks, it is now named IGPU ... But now it shows 1536 MB so I think I made a mistake somewhere here.

@felix23,

The code for the 2080MB VRAM patch is correct, however your IGPU platformID id of 0x3E928086 is incorrect ...

Because it ends in "8086" (which no platform-id does) you have most likely copied the device-id value from hackintool rather than the platformID.

The reason the 2048MB VRAM patch is not working is because the platform-id is invalid.

Cheers
Jay