Jump to content

Asus Z390-I: OC config adjustments for 4K output with UHD630


Recommended Posts

Initially, was not able to get the UHD 630 to drive a 4k display...


Was able to enable 4k on internal CPU by setting framebuffer-patch-enable to zero...


Now the question is :


Do I need to have all these other settings?


And is setting framebuffer-patch-enable to zero the proper fix for this?



Screen Shot 2022-01-11 at 9.19.38 AM.jpg


Link to comment
Share on other sites

  • Administrators

It appears you've not realised that framebuffer-patch-enable is a boolean flag (so set it to 0 or 1 and type NUMBER rather than 8 x bytes with type DATA) and that, by setting it to 0 (i.e. FALSE), you actually disable patching. As such, all subsequent framebuffer patches in your config are rendered useless (but probably not connector patches since these have their own boolean flags)...


4K output usually requires that framebuffer memory be a minimum given size and usually greater than 32MB (I don't know the exact minimum value). Such requirements do normally imply that framebuffer memory settings be left untouched. Instead, your framebuffer patches basically limited framebuffer memory (stolenmem) to 19MB which would explain why you could not obtain 4K output. Such patch is only required (and usually accompanied by cursor memory patch too) if DVMT pre-allocated memory is set to to 32MB in BIOS and the selected OS X/macOS framebuffer default memory settings (stolenmem + fbmem) exceeds 32MB, in which case KP occurs if no patches are applied (cf. Firewolf's 2015 explanations). This usually applies to laptops only, desktops (recent/modern ones) very frequently allowing to adjust DVMT settings in BIOS.


You inject/select the expected CFL framebuffer layout 0x3E9B007 which defines/sets/uses 57MB of framebuffer memory (stolenmem) and no cursor memory (fbmem😞

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

so framebuffer memory is indeed >32MB by default.


Given that you do not encounter a KP when you boot without framebuffer patches (i.e. no memory patches), it's fair to conclude that your desktop's default or current DVMT pre-allocated memory is set to at least 64MB (you may be able to check the exact value in BIOS settings or by checking BIOS info through GrubShell). So, indeed, do not apply any framebuffer patches (or limit it to VRAM (unifiedmem) patch), only connector patches if required (for instance to enable HDMI audio output by setting the relevant connector to HDMI type 00080000). I'm not sure all the connector patches you've configured are desired, necessary, suitable or useful though...


I invite you to read the Whatevergreen User Manual and a recent article I posted at IM on the matter of DVMT pre-allocated memory/framebuffer memory settings & patches.

Link to comment
Share on other sites

  • Administrators

There's nothing strange, just a total lack of understanding and knowledge on the matter. There's no secret and if you don't try (to understand), you don't get (knowledge)... Simply copying stuff in the blind leads nowhere, you got that proven if nothing else.


Don't hesitate to Google for info on framebuffer, graphics memory, picture size or colour depth.

Eg: https://www.quora.com/How-can-the-size-of-the-VRAM-determines-the-resolution-and-color-depth-of-the-monitor

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...