Jump to content
kylon

Increase vram - hd 3000

62 posts in this topic

Recommended Posts

Advertisement

hello

for me , the only solution for graphic glitch is a modified edid injection via dsdt

Share this post


Link to post
Share on other sites

i finished vram patch cleanup for each os.

 

 

================10.6.x=======================

post-980913-0-88573700-1509695403_thumb.png

==4gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745cc00 000018

R: c745cc00 000040

MacOS: 10.6.x

 

post-980913-0-57898600-1509695413_thumb.png

==8gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: eb19b800 000020

R: eb19b800 000040

MacOS: 10.6.x

 

 

================10.7.x-10.11.x==================

==4gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745bc00 000018

R: c745bc00 000040

MacOS: 10.7.x,10.8.x,10.9.x,10.10.x,10.11.x

 

==8gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745bc00 000020

R: c745bc00 000040

MacOS: 10.7.x,10.8.x,10.9.x,10.10.x,10.11.x

 

 

================10.12.x======================

==4gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745c400 000018

R: c745c400 000040

MacOS: 10.12.x

 

==8gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745c400 000020

R: c745c400 000040

MacOS: 10.12.x

 

 

================10.13.x======================

==4gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745d000 000018

R: c745d000 000040

MacOS: 10.13.x

 
==8gb user==

N: com.apple.driver.AppleIntelSNBGraphicsFB

F: c745d000 000020

R: c745d000 000040

MacOS: 10.13.x

 

 

enjoy :thumbsup_anim:

 

Share this post


Link to post
Share on other sites

I've attempted the change right now-


1. replaced 20 with 40 in SNB file for 512 to 1024 (AppleIntelSNBGraphicsFB.kext)


    http://www.insanelym...-2#entry2527339


2. Added VRAMSize as 1024 in HD3000 info.plist (AppleIntelHD3000Graphics.kext)


3. used kext Utility to install both of these changed kexts after disabling the SIP.


4. Restarted


But my graphic memory reduced to 3MB after this, so I've reverted.


Any idea why? Or how to make it work?


 


I'm on latest 10.13.1 right now.


 


MacBook Pro (13-inch, Late 2011)


2.4 GHz Intel Core i5


16 GB 1333 MHz DDR3


Intel HD Graphics 3000 512 MB


Share this post


Link to post
Share on other sites

This kext utility of yours probably did not install the patched kexts properly and/or rebuild the cache properly. Opt for the manual kexts installation + manual cache rebuild; it's totally reliable.

Share this post


Link to post
Share on other sites

I never felt I needed it but I recently got an opportunity to upgrade my Sandy Bridge/HD3000 Latitude E6220 from 4GB to 8GB of RAM. Whist I was running on patched SNB framebuffer for 512MB VRAM, I still encountered the odd/occasional glitch or line through the screen.

 

Since the RAM upgrade, I've reverted to the vanilla framebuffer (i.e. default VRAM allocation=512MB VRAM) and no longer experience any graphic glitches or lines.

 

I can't say if RAM increase is the definitive answer to the well-known HD3000 gremlins so many people experience with most recent versions of OS X/macOS (I had no issues up to Yosemite) but it appears to do the trick for me.

Share this post


Link to post
Share on other sites

The SNB code is different again in High Sierra. In 10.13, the binary string to change is:

 

C7 45 D0 00 00 00 xx
Where xx is the byte to modify according to the default amount of VRAM (should be 18 or 20) and desired target allocation (say 20, 30, 40, 60, 80).

 

So, for instance, to change default VRAM on my E6220 (with 4GB RAM) from 384MB to 1024MB, the patch is:

Find:       C7 45 D0 00 00 00 18
Replace by: C7 45 D0 00 00 00 40
attachicon.gifHD3000_1GB_vRAM.png attachicon.gifHD3000_1GB_VRAM#2.png
Can I use for HD4000? High Sierra?

Share this post


Link to post
Share on other sites

No. It's an entirely different patch for Capri HD4000 (and subsequent iGPU). You'll find all relevant details with a little search. This thread is only for VRAM increase on SNB HD3000 as entitled.

 

Edited by Hervé

Share this post


Link to post
Share on other sites

Sorry, I was late to join the party. Before I start to ask, I want to say sorry for my bad English.

I'm new for this mac's things, but I want to increase my MBP2011(8GB) VRAM to 1024MB too. I already disabled SIP, have Kext Utility, Hex Fiend, and Clover Configurator.

So where I start to tweak these things right now?

 

Thanks for your reply

Share this post


Link to post
Share on other sites

See OP, grab the patch for your osx version and change the value in replace field

Share this post


Link to post
Share on other sites

I already searched AppleIntelSNBGraphicsFB, back it up and then replaced 

C7 45 D0 00 00 00 

to 

C7 45 D0 00 00 00 

The system still says vram on 512MB. Am I missing something?

C7 45 D0 00 00 00 

to 

C7 45 D0 00 00 00 

Sorry I mean replaced

C7 45 D0 00 00 00 20

to

C7 45 D0 00 00 00 40

Share this post


Link to post
Share on other sites

You are using clover, you don t need to mess with kexts, you only need clover kext patches that will be applied on boot by clover, and you can find the links in OP

Share this post


Link to post
Share on other sites

Yeah

Remember to restore the unpatched kext.

 

Save as config.txt and replace the config in efi/clover

Reboot and enjoy

Share this post


Link to post
Share on other sites

5aad52df83850_ScreenShot2018-03-18at00_36_49.thumb.png.3172c8c80002fc6ed0f6b07d3fea5d31.pngSir, I have replaced config.plist (after create a backup) with config.txt. And then restart but it still on 512MB. 

Share this post


Link to post
Share on other sites
Posted (edited)
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 384MB to 1024MB for 10.6.x</string>
          <key>Find</key>
          <data>x0XMAAAAGA==</data>
          <key>MatchOS</key>
          <string>10.6.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XMAAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 512MB to 1024MB for 10.6.x</string>
          <key>Find</key>
          <data>x0XMAAAAIA==</data>
          <key>MatchOS</key>
          <string>10.6.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XMAAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 384MB to 1024MB for 10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
          <key>Find</key>
          <data>x0W8AAAAGA==</data>
          <key>MatchOS</key>
          <string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0W8AAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 512MB to 1024MB for 10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
          <key>Find</key>
          <data>x0W8AAAAIA==</data>
          <key>MatchOS</key>
          <string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0W8AAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 384MB to 1024MB for 10.12.x</string>
          <key>Find</key>
          <data>x0XEAAAAGA==</data>
          <key>MatchOS</key>
          <string>10.12.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XEAAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 512MB to 1024MB for 10.12.x</string>
          <key>Find</key>
          <data>x0XEAAAAIA==</data>
          <key>MatchOS</key>
          <string>10.12.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XEAAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 384MB to 1024MB for 10.13.x</string>
          <key>Find</key>
          <data>x0XQAAAAGA==</data>
          <key>MatchOS</key>
          <string>10.13.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XQAAAAQA==</data>
        </dict>
        <dict>
          <key>Comment</key>
          <string>Increase vram HD3000 from 512MB to 1024MB for 10.13.x</string>
          <key>Find</key>
          <data>x0XQAAAAIA==</data>
          <key>MatchOS</key>
          <string>10.13.x</string>
          <key>Name</key>
          <string>AppleIntelSNBGraphicsFB</string>
          <key>Replace</key>
          <data>x0XQAAAAQA==</data>
        </dict>

 

Edited by SuperReaper

Share this post


Link to post
Share on other sites

My txt is looks like this

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>KernelAndKextPatches</key>
    <dict>
        <key>KextsToPatch</key>
        <array>
            <dict>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>x0XQAAAAIA==</data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>Name</key>
                <string>com.apple.driver.AppleIntelSNBGraphicsFB</string>
                <key>Replace</key>
                <data>x0XQAAAAQA==</data>
            </dict>
        </array>
    </dict>
</dict>
</plist>

 

 

should I replace it with 

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>KernelAndKextPatches</key>
    <dict>
        <key>KextsToPatch</key>
        <array>
            <dict>
              <key>Comment</key>
          	<string>Increase vram HD3000 from 512MB to 1024MB for 10.13.x</string>
          	<key>Find</key>
          	<data>x0XQAAAAIA==</data>
          	<key>MatchOS</key>
          	<string>10.13.x</string>
          	<key>Name</key>
          	<string>AppleIntelSNBGraphicsFB</string>
          	<key>Replace</key>
          	<data>x0XQAAAAQA==</data>
          	</dict>
        </array>
    </dict>
</dict>
</plist>

 

 

?

Screen Shot 2018-03-18 at 11.38.31.png

Share this post


Link to post
Share on other sites

my values:

name: com.apple.driver.AppleIntelSNBGraphicsFB

find: c745d000000020

replace: c745d000000060

1.5gb, this is working here.

are you using a vanilla AppleIntelSNBGraphicsFB?

 

You may also need to patch the infoPlist of the kext, there are more infos in this thread.

i have not tried that yet

Share this post


Link to post
Share on other sites
Posted (edited)

Depending on the Clover version you're using, you may or may not need the "com.apple.driver." syntax in front of the kext name. Rebuild your cache with the vanilla SNB framebuffer, reboot and, if you still do not obtain 1024MB VRAM, given that your binary patch appears Ok in your Clover config, I'd give the revised kext name a shot.

Edited by Hervé

Share this post


Link to post
Share on other sites

Hi guys, I'm so sorry for my late reply. 

Sorry that I little confused about it. Depend on this post

On 3/19/2018 at 4:49 PM, Hervé said:

Depending on the Clover version you're using, you may or may not need the "com.apple.driver." syntax in front of the kext name. Rebuild your cache with the vanilla SNB framebuffer, reboot and, if you still do not obtain 1024MB VRAM, given that your binary patch appears Ok in your Clover config, I'd give the revised kext name a shot.

How do I do this? Is it my backup folder named "AppleIntelSNBGraphicsFB-orig.kext copy" necessary?

Share this post


Link to post
Share on other sites

You re-instate your backup in /S/L/E with its native name in /S/L/E, thereby replacing the patched kext you currently appear to have,. Then, repair kexts permissions and rebuild your cache.

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.

×