Jump to content

⚠️ Can someone figure out what's wrong with my VRAM? ⚠️


stinkyskunk
 Share

16 posts in this topic

Recommended Posts

Hey there, I've installed Olarila OpenCore macOS 12.1 since my raw OpenCore one was going through a lot of errors on my iGPU, it turned out I managed to install the system but the VRAM sticks to 5MB even after I troubleshoot it the way OpenCore's Post-Install guide asks to, there's a screenshot down below of my "DeviceProperties" section according to the values of my specs also listed down below followed by the OC's Post-Install VRAM Troubleshooting guide, I'm also leaving here my EFI without my serial number so if any kind soul that could be able to identify the error and might consider fixing it I'd be glad.

 

My specs:

  • Motherboard: Gigabyte GA-H110M-S2V
  • CPU: Intel Core i5 7400 3.5 GHz (Kaby Lake)
  • iGPU: Intel HD Graphics 630

 

 

Here's the screenshot with the values according to: 

1306235506_ScreenShot2022-01-26at10_43_35PM.thumb.png.3a9281cdbc9536d1ad1fe2dc08ead9bc.png

 

Here's the platform-id Framebuffer for Intel HD Graphics 630 (Kaby Lake):

1565439477_ScreenShot2022-01-26at10_59_46PM.png.b00138146bb697ee545aca2aef625a8b.png

 

Here's the Intel HD Graphics 630 Device ID:

2069700335_ScreenShot2022-01-26at11_01_15PM.png.397d006dfcd9c4f6a026a8532ce518c1.png

 

Here's the rest of the values according to the Post-Install "Patching VRAM" guide:

315848927_ScreenShot2022-01-26at11_02_08PM.png.e02ba9867a888d0616f5499f9a098c3e.png

 

Here's my EFI:

EFI.zip

 

PS: I'm a newbie at Hackintosh.

Link to comment
Share on other sites

@Hervé Those errors might be because I tried so many possibilities already because it wasn't working, and still... I've made the change you suggested on "AAPL,ig-platform-id, deleted "device-id" and used a iMac18,1 SMBIOS according to OpenCore's KabyLake Installation guide for "...computers utilizing the iGPU for displaying", it didn't work so I tried 18,3 instead... but it didn't work as well, what should I do?

Link to comment
Share on other sites

22 hours ago, stinkyskunk said:

@Hervé Those errors might be because I tried so many possibilities already because it wasn't working, and still... I've made the change you suggested on "AAPL,ig-platform-id, deleted "device-id" and used a iMac18,1 SMBIOS according to OpenCore's KabyLake Installation guide for "...computers utilizing the iGPU for displaying", it didn't work so I tried 18,3 instead... but it didn't work as well, what should I do?

Test them all

 ig-platform-id:
0x591E0000 (mobile, 3 connectors, no fbmem, 35 MB)
0x87C00000 (mobile, 3 connectors, no fbmem, 35 MB)
0x59160000 (mobile, 3 connectors, no fbmem, 35 MB)
0x59230000 (desktop, 3 connectors, no fbmem, 39 MB)
0x59260000 (desktop, 3 connectors, no fbmem, 39 MB)
0x59270000 (desktop, 3 connectors, no fbmem, 39 MB)
0x59270009 (mobile, 3 connectors, no fbmem, 39 MB)
0x59160009 (mobile, 3 connectors, no fbmem, 39 MB)
0x59120000 (desktop, 3 connectors, no fbmem, 39 MB)
0x591B0000 (mobile, 3 connectors, 39 MB)
0x591E0001 (mobile, 3 connectors, no fbmem, 39 MB)
0x59180002 (mobile, 0 connectors, no fbmem, 1 MB)
0x59120003 (mobile, 0 connectors, no fbmem, 1 MB)
0x59260007 (desktop, 3 connectors, 79 MB)
0x59270004 (mobile, 3 connectors, no fbmem, 58 MB)
0x59260002 (mobile, 3 connectors, no fbmem, 58 MB)
0x87C00005 (mobile, 3 connectors, no fbmem, 58 MB)
0x591C0005 (mobile, 3 connectors, no fbmem, 58 MB)
0x591B0006 (mobile, 1 connectors, no fbmem, 39 MB)

 

Link to comment
Share on other sites

21 hours ago, TheDreamOfSurf said:

Good Evening 

So i tested with several AAPL,ig-platform-id    DeskTop

- 00002659 Reboot 

- 00002759 Reboot

- 00001259 ok with memory 7mb

What about 07002659?

 

0x59260007 (desktop, 3 connectors, 79 MB)
Link to comment
Share on other sites

  • 2 months later...

I am posting here because my problem is similar and I wasn't sure if I should start a new thread.

My rig is: GA-H270N-WIFI with a Kaby Lake processor (i5 7600K) using built in HD 630 graphics.

I have been running Catalina (via Clover) on my Hack for a couple of years and decided to update it to Monterey and switch to OpenCore. I did a clean install of Monterey, then migrated a backup. Everything appears to be running well EXCEPT the graphics. Under Catalina, graphics were fine, my monitor was recognized, and About this Mac showed that I was using 1536 MB of VRAM. 

However, under Monterey/OpenCore, my monitor is not recognized and my VRAM is showing as 8 MB!

See images below.

catalina.png.ad1d69639127bbe3ac336bd86e80b2fa.png

monterey.png.8f2ad0ddaaa44c68f399a41f0b13992d.png

 

Below is a screenshot of the relevant section of my config.plist. Adding or deleting the frambuffer entries (highlighted) makes zero difference.

 

2007075616_ScreenShot2022-04-09at10_04_01AM.png.35ae2d5c96f7d25f85e32a09752f98f0.png

 

Thanks in advance for any insights.

Link to comment
Share on other sites

27 minutes ago, Hervé said:

Invalid device-id value, which is even more daft that this particular injection is not even required... Read the above posts.

So you are saying remove the device-id line and everything will work as expected?

Link to comment
Share on other sites

16 hours ago, shl628 said:

 

Add the igfxagdc=0 boot arg and try rebooting.
It will solve the black screen issue of Intel HD Graphics 630.

 

You, my friend, are amazing!

This fixed my issue. VRAM is now 1536 and monitor is recognized. THANK YOU!

 

monterey-fixed.png.02d5155252719fca16d3193b15f2bd42.png

config-changes.png.7e4f74dabc5d2eb2dc4ba3cf4ff3a6b8.png

Link to comment
Share on other sites

One more thing...

Didn't notice this at first, but every time the computer sleeps, the monitor won't wake up. The computer is still running, and I can share the screen from another computer; but the monitor attached to the computer won't wake up. It's just a black screen. 

Anyone know how to fix this?

This was not a problem when the machine was running Catalina/Clover. 

Is there a boot argument or other config.plist edit needed?

Thanks in advance.

Link to comment
Share on other sites

15 hours ago, Hervé said:

Try and add boot arg igfxonln=1. You could also try and experiment with darkwake boot arg though it probably won't change anything.

Thanks. I tried igfxonin=1 but it didn't make any difference. I'll try darkwake when I get time and let you know. Thanks again.

Link to comment
Share on other sites

  • 8 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...