Contribute
Register

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

I'm currently using lilu. Kext and WhateverGreen. Kext. If the BIOS cannot modify the dvmt-prealloc, is there a minStolenSize patch that can be modified instead of using the 64mb dvmt-prealloc

Read FAQ regarding methods available to change DVMT-prealloc when not present in BIOS.
 
Hello RehabMan,

I've been trying to get the IGPU on my Lenovo Yoga 9000 13ISK to work after updating to Mojave 10.14.3 by following this guide along with headkaze's guide on framebuffer patching using whatevergreen and lilu, here.

This is a clean install of mojave on a new SSD. I still have a working macOS Sierra 10.12.5 install on the laptop's original SSD, and I'm swapping back and forth between them in order to try to figure out what's going on.

I was able to get graphics to work on Sierra by using KextsToPatch in clover and the minstolensizepatch, but using whatevergreen and lilu on Mojave is (obviously) different. The heck of it is, I think i've figured out the actual patch I need in order to patch the framebuffer for the DVMT-prealloc error, but after I apply it and boot verbose, I see a bunch of IGPU output (that doesn't appear without this patch) indicating different things related to the IGPU are now enabled, but afterwards it always stops at the line saying:

"IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0"

I've confirmed the patch I came up with against the one generated for the DVMT-prealloc problem with Hackintool, which seems to generate the exact same patch I've already applied for this problem.

I've googled the IOConsoleUsers error, but the only results I can find are people whose reason for it appearing differ greatly from my own, and the only solutions offered (which in general seem to work for others) involve using things like IntelGraphicsFixUp.kext which the FB patching guide from headkaze specifically says not to do.

For these reasons, I'm at a loss as to where to go from here. Hopefully you're able to point me in the right direction.

Attached is the Problem Reporting .zip is one folder with my mojave EFI partition on it, and another folder with the old config.plist from my sierra install, which has working graphics, in case it helps at all.

Thanks in advance.

-Edited for spelling
 

Attachments

  • Problem_Reporting.zip
    2.2 MB · Views: 186
  • verbose.jpg
    verbose.jpg
    6 MB · Views: 288
  • fb_patch.jpg
    fb_patch.jpg
    249.4 KB · Views: 309
  • gpu_info.jpg
    gpu_info.jpg
    155.9 KB · Views: 281
Hello RehabMan,

I've been trying to get the IGPU on my Lenovo Yoga 9000 13ISK to work after updating to Mojave 10.14.3 by following this guide along with headkaze's guide on framebuffer patching using whatevergreen and lilu, here.

This is a clean install of mojave on a new SSD. I still have a working macOS Sierra 10.12.5 install on the laptop's original SSD, and I'm swapping back and forth between them in order to try to figure out what's going on.

I was able to get graphics to work on Sierra by using KextsToPatch in clover and the minstolensizepatch, but using whatevergreen and lilu on Mojave is (obviously) different. The heck of it is, I think i've figured out the actual patch I need in order to patch the framebuffer for the DVMT-prealloc error, but after I apply it and boot verbose, I see a bunch of IGPU output (that doesn't appear without this patch) indicating different things related to the IGPU are now enabled, but afterwards it always stops at the line saying:

"IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0"

I've confirmed the patch I came up with against the one generated for the DVMT-prealloc problem with Hackintool, which seems to generate the exact same patch I've already applied for this problem.

I've googled the IOConsoleUsers error, but the only results I can find are people whose reason for it appearing differ greatly from my own, and the only solutions offered (which in general seem to work for others) involve using things like IntelGraphicsFixUp.kext which the FB patching guide from headkaze specifically says not to do.

For these reasons, I'm at a loss as to where to go from here. Hopefully you're able to point me in the right direction.

Attached is the Problem Reporting .zip is one folder with my mojave EFI partition on it, and another folder with the old config.plist from my sierra install, which has working graphics, in case it helps at all.

Thanks in advance.

-Edited for spelling

Nevermind. Thanks to this post on ******, I figured it out. I ended up basically using a modern minstolensize patch instead of patching the FB directly, because I just could not get the latter to work.
 
Hello RehabMan,

I've been trying to get the IGPU on my Lenovo Yoga 9000 13ISK to work after updating to Mojave 10.14.3 by following this guide along with headkaze's guide on framebuffer patching using whatevergreen and lilu, here.

This is a clean install of mojave on a new SSD. I still have a working macOS Sierra 10.12.5 install on the laptop's original SSD, and I'm swapping back and forth between them in order to try to figure out what's going on.

I was able to get graphics to work on Sierra by using KextsToPatch in clover and the minstolensizepatch, but using whatevergreen and lilu on Mojave is (obviously) different. The heck of it is, I think i've figured out the actual patch I need in order to patch the framebuffer for the DVMT-prealloc error, but after I apply it and boot verbose, I see a bunch of IGPU output (that doesn't appear without this patch) indicating different things related to the IGPU are now enabled, but afterwards it always stops at the line saying:

"IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0"

I've confirmed the patch I came up with against the one generated for the DVMT-prealloc problem with Hackintool, which seems to generate the exact same patch I've already applied for this problem.

I've googled the IOConsoleUsers error, but the only results I can find are people whose reason for it appearing differ greatly from my own, and the only solutions offered (which in general seem to work for others) involve using things like IntelGraphicsFixUp.kext which the FB patching guide from headkaze specifically says not to do.

For these reasons, I'm at a loss as to where to go from here. Hopefully you're able to point me in the right direction.

Attached is the Problem Reporting .zip is one folder with my mojave EFI partition on it, and another folder with the old config.plist from my sierra install, which has working graphics, in case it helps at all.

Thanks in advance.

-Edited for spelling
Nevermind. Thanks to this post on ******, I figured it out. I ended up basically using a modern minstolensize patch instead of patching the FB directly, because I just could not get the latter to work.

Your profile is missing screen resolution info. Please fix as per FAQ:
 
Your profile is missing screen resolution info. Please fix as per FAQ:
Updated.
 
Thanks.

Note: You will likely need large DVMT-prealloc (not 32mb) for the 4k display.

Like I said, I got it "working" with basically the minStolenSize patch for mojave - which I don't quite know what to call because it was my impression this wouldn't work in Mojave.

There is no custom/developer/etc BIOS for this laptop that I know of, and I'm wary of trying to reverse my BIOS and patch it manually when this patch I'm using seems to work just fine, with no glitching that I've noticed.
 
Like I said, I got it "working" with basically the minStolenSize patch for mojave - which I don't quite know what to call because it was my impression this wouldn't work in Mojave.

There is no custom/developer/etc BIOS for this laptop that I know of, and I'm wary of trying to reverse my BIOS and patch it manually when this patch I'm using seems to work just fine, with no glitching that I've noticed.

Hi!, do you have the patch for Catalina?
 
Back
Top