Contribute
Register

<< Solved >> Intel HD4000 no acceleration (Catalina/Big Sur)

I will revert to Catalina if i find a solution to the problem. Not working Intel HD acceleration apparently has nothing to do with a specific system (Catalina/Big Sur). For Big Sur I rebuild again EFI and rewrote config. Ivy Bridge (HD4000) must work in Big Sur with fake SMBIOS iMac14,4 (dortania.github.io).
I switched to the Big Sur because I tried all possible ways to solve my problem in Catalina and somewhere I heard that the Catalina does not work well with Intel HD4000 in a number of cases..

Fair enough.

If you do not believe what we say, then ...

Good luck with your build.
 
Your config.plist shows the DeviceProperties for your HD4000 IGPU as follows:

Screenshot 2023-12-08 at 13.58.39.png
The three entires after the AAPL,ig-platform-id entry are not required. They are just details that macOS already uses.

I would suggest you try editing the IGPU DeviceProperties as shown below.

Screenshot 2023-12-08 at 14.03.07.png
The three FrameBuffer entries after the AAPL,ig-platform-id entry are there to get WhateverGreen.kext working with your IGPU.

You can also try using this alternative AAPL,ig-platform-id with your desktop Ivy Bridge IGPU.

Screenshot 2023-12-08 at 14.03.31.png

Framebuffer:
  • AAPL,ig-platform-id (desktop):
    • 0x0166000A (default)
      • 0A006601 (hex swapped)
    • 0x01620005 (alternative)
      • 05006201 (hex swapped)
 
I would suggest you try editing the IGPU DeviceProperties as shown below.
Thanks for you time. I tryed both variants - no results... Also in WhateverGreen manual Intel HD i found boot arg -igfxdvmt, it also has no affect...
32Mb pre-allocated patch suggested me Feartech
may also need:
framebuffer-fbmem -> Data -> 00009000
framebuffer-stolenmem -> Data -> 00003001
I tryed it in Catalina - no result...
 

Attachments

  • photo_2023-11-06_14-03-56.jpg
    photo_2023-11-06_14-03-56.jpg
    125.7 KB · Views: 17
With that bios option you don't need the framebuffer-stolenmem entry. But you should be using the other two.

With your CPU's IGPU using device-id = 0x0162, the alternative AAPL,ig-platform-id would be a better match for your setup than 0x0166.

Screenshot 2023-12-08 at 20.01.53.png IGPU specs
 
Do you have any third-party kexts installed to the /Library/Extensions (/L/E) or /System/Library/Extensions (/S/L/E) folders?

If yes, which kexts have you added to either of these system folders?

I am specifically interested in whether you have any graphics related kexts in either of these folders, not the normal macOS kexts, but specifically any third-party kexts. As these other kexts might interfere with how WhateverGreen.kext works.
 
Thanks for you time. I tryed both variants - no results... Also in WhateverGreen manual Intel HD i found boot arg -igfxdvmt, it also has no affect...
32Mb pre-allocated patch suggested me Feartech

I tryed it in Catalina - no result...
DVMT needs to be set to 64MB !!
 
But you should be using the other two.
Thanks for you time. I tryed - black dock, freeze animation, decoder failed...
Default device-id without any patches - 0x0162, this is what is written in the log WhateverGreen "IGPU has real 0162 acpl 0162 fake 0000 intel HD Graphics 4000". But I tried anyway, as you wrote.
Do you have any third-party kexts installed to the /Library/Extensions (/L/E) or /System/Library/Extensions (/S/L/E) folders?
No - I haven't made any changes to system folders, they are not necessary - CPU is native (iMac13,1), network and sound start with kexts in EFI without any problems...
Also I tryed SMBIOS macmini7,1 - but it also has no result....
I will be glad of any of your advice, all the ways that i can Google have been tried...
 

Attachments

  • photo_2023-12-09_18-44-44.jpg
    photo_2023-12-09_18-44-44.jpg
    47.9 KB · Views: 9
  • photo_2023-12-09_17-17-45.jpg
    photo_2023-12-09_17-17-45.jpg
    175.7 KB · Views: 9
  • EFI.zip
    37.8 MB · Views: 4
Post a copy of your whole EFI folder, so I can see exactly what you are using.

Can you also post screenshots showing the other Hackintool > Patch tabs, i.e. VRAM, Framebuffer & Connectors

The Verbose text image you posted shows some interesting information, additional to what you posted above, regarding WhateverGreen.

Screenshot 2023-12-09 at 15.06.43.png

Can you also post a copy of your IOReg. Use the version linked in this guide.

 
screenshots showing the other Hackintool > Patch tabs, i.e. VRAM, Framebuffer & Connectors
logs in last post - it's log debug version WhateverGreen kext + boot arg -wegdbg, without this arg and release version WhateverGreen kext - this information will not be in the logs...
copy of your whole EFI folder,
I don't understand - it's whole folder EFI - BOOT+OC...
 

Attachments

  • Снимок экрана 2023-12-09 в 19.27.57.png
    Снимок экрана 2023-12-09 в 19.27.57.png
    59.8 KB · Views: 9
  • Снимок экрана 2023-12-09 в 19.28.18.png
    Снимок экрана 2023-12-09 в 19.28.18.png
    67.3 KB · Views: 9
  • Снимок экрана 2023-12-09 в 19.29.28.png
    Снимок экрана 2023-12-09 в 19.29.28.png
    83.6 KB · Views: 9
  • Снимок экрана 2023-12-09 в 19.29.41.png
    Снимок экрана 2023-12-09 в 19.29.41.png
    83.2 KB · Views: 10
  • Снимок экрана 2023-12-09 в 21.06.03.png
    Снимок экрана 2023-12-09 в 21.06.03.png
    82.1 KB · Views: 7
  • iMac14.4.zip
    626.4 KB · Views: 7
Last edited:
it's whole folder EFI - BOOT+OC...
nevermind I have seen the EFI in the post above, Doh!

Your IOReg is for a system using SMBIOS for a Macmini7,1. Your EFI is for a system using SMBIOS for iMac14,4.

Generate an IOReg for the SMBIOS you are using, or post a copy of the EFI for the Macmini7,1.

Can you also post a copy of your system ACPI tables.
These can be obtained from Hackintool > Utilities tab,
Select 'Dump ACPI' icon and tell it which (new) folder to save the ACPI tables in to.
Compress and post a copy of the folder containing the ACPI tables.
 
Back
Top