Contribute
Register

[Guide] Alternative to the minStolenSize patch with 32mb DVMT-prealloc

Patching the framebuffer to match your BIOS setting for DVMT-prealloc is likely to be more stable than the minStolenSize patch and with limited BIOS options, comes with less risk than changing DVMT-prealloc.

Thank you RehabMan, always doing a great job.

But what if i have the option to change DVMT-prealloc (even if it is a riskier option) instead of Patching the framebuffer to match my BIOS setting, which one yields the best result ?
Does it have any difference at all, regarding performance, compatibility or reliability ?

Thanks in advance.
 
Thank you RehabMan, always doing a great job.

But what if i have the option to change DVMT-prealloc (even if it is a riskier option) instead of Patching the framebuffer to match my BIOS setting, which one yields the best result ?
Does it have any difference at all, regarding performance, compatibility or reliability ?

Thanks in advance.

It is probably always better to change DVMT-prealloc if possible/safe.
 
Thank you. But I have Broadwell (HD 5500) and this happens on all OS versions (I currently have 10.11.6 and 10.12.5 on dual boot). The Lilu and IntelGraphicsFixup kexts don't solve my issue. The problem is similar to nrudnyk's. It just freezes but I don't have a QHD display either. Mine is 1366x768.


Try different ig-platform-id.
Open separate thread.
Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Provide details re: "strange boot freezing issue". No one here is clairvoyant.
 
I tried these:
0x16160000
0x16160002
0x16160006
0x16260000
0x16260002
0x16260006
This is where it freezes.
 

Attachments

  • 1-3.jpg
    1-3.jpg
    24.8 KB · Views: 290
I tried these:
0x16160000
0x16160002
0x16160006
0x16260000
0x16260002
0x16260006
This is where it freezes.

No "Problem Reporting" files attached (make sure you provide as much data as possible, even if you have to boot with an invalid ig-platform-id...).
You didn't try 0x16260004... (probably others).
 
Back
Top