CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,200
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
No, we should not change those hex values!Hi in this thread it describes setting the DVMT pre allocation to 96MB by poking values into the UEFI firmware variables and then patching AppleIntelFrameBufferAzul, this is to get 4K working on a Dell 7020 with just Intel HD 4600 graphics.
It says;
"Name: AppleIntelFramebufferAzul
Find:
0300220D 00030303 00000002 00003001
Replace:
0300220D 00030303 00000004 00000003 "
I have tried to understand what is being set and think the "00000004" that is being set refers to DVMT pre allocation and it is being set to 64MB, if that is correct, should it be set to 96MB because that's what we have set it in the UEFI firmware?
Ie should i change the replacement with;
0300220D 00030303 00000006 00000003 ?
(which I think sets it to 96mb)
I have tested the change and it does not break anything immediately and wonder if there are any tests that will show that the right setting is in place?
Thanks
DVMT is being set to 96MB inside the firmware itself (inside BIOS). Those hex bytes are modifying the AppleIntelFrameBufferAzul to enable 4K, but this patch does not affect DVMT Pre-Alloc.
Are you getting 4K output with the original unmodified patch?