Contribute
Register

Official HD 4000 Support

Status
Not open for further replies.
When I enable
Code:
GraphicsEnabler=Yes
got a black screen
using chimera 1.11.1
 
tell me the procedure of your installation pls
 
There is a lot of support for HD4000 with 77 chipset, but although I was searching all over the forum, I couldn't find anything about IB CPU + SB chipset (except this http://www.tonymacx86.com/150-enabl...therboards-hd-4000-6-series-motherboards.html).

So, long story short. My MoBo is GA-H67N-USB3-B3 (BIOS F9). CPU is IB i7 3770. Installing M Lion wasn't a problem, it looks like everything is working so far, even sleep (first time in my hackintosh route), but I couldn't get the HD4000 work. If I boot in safe mode (-x) it works (see screen), but after I try to boot normally it ends up in KP.
I didn't change anything except the 2 kext following this article (http://www.tonymacx86.com/150-enabl...therboards-hd-4000-6-series-motherboards.html) and set my IG memory size to 64 MB in BIOS (32MB or 96MB doesn't change anything)

Any support would be much appreciate.
 

Attachments

  • image.png
    image.png
    89.4 KB · Views: 462
One thing that helped me with HD4000 QE/CI - I was able to get full QE/CI support after Multibeast but was loosing QE/CI support after restart. Solution was to turn off kernel cache in org.chameleon.Boot.plist or in Chimera boot options

<key>UseKernelCache</key>
<string>No</string>
 
Intel HD 4000 Solution for Desktops


- In org.chameleon.boot.plist write the following things:


<key>UseKernelCache</key>
<string>No</string>
<key>Graphics Mode</key>
<string>1920x1080x32</string>
(if your display not support this resolution, write your display best resolution)

<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000005006201140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

- In Multibeast, set the System Definition to iMac 12,2

With this solution, no distorted screen when booting and after booting. Only works with DVI.

Sorry for my bad English :D
 
RE-Edit: It stopped working... Not sure why, but upon another reboot is was all wrong again. Sorry folks.

Edit: I was able to solve my problem by reverting to GraphicsEnabler=Yes and following up with multibeast. I worried that this change might cause me to be unable to boot again, but I have not had that problem yet. Hopefully this is useful to some of my fellows.




I also have this problem. Just FYI, would love to hear an answer.

I, too, am having the same issue. Screen Shot 2012-09-12 at 12.10.00 PM.pngScreen Shot 2012-09-12 at 12.10.00 PM.png
I have taken care to use GraphicsEnabler=No and to make sure the internal graphics memory is set at 64mb in the BIOS. What do we that are experiencing this issue need to do to get the HD 4000 recognised by the computer? Thanks very much in advance for your kind help.

My specs:
i5 3570k
H77-DS3H
Integrated HD 4000 (as yet unrecognised)
Corsair Vengeance 2x4gb
Seagate Barracuda 1TB
 
RE-Edit: It stopped working... Not sure why, but upon another reboot is was all wrong again.
The formula for working HD4000 in Mountain Lion is:
1. MultiBeast 5.0.2
1a. Graphics Enabler = Yes
1b. Chimera 1.11.1 or newer

Those selections are automatic with EasyBeast for a new installation.

Chimera takes care of the device_id and framebuffer.
Remove device property injection from Extra/org.chameleon.Boot.plist
 
The formula for working HD4000 in Mountain Lion is:
1. MultiBeast 5.0.2
1a. Graphics Enabler = Yes
1b. Chimera 1.11.1 or newer

Those selections are automatic with EasyBeast for a new installation.

Chimera takes care of the device_id and framebuffer.
Remove device property injection from Extra/org.chameleon.Boot.plist

with all due respect, i beg to differ. please do correct me where i'm wrong here......

all chimera does is inject platform ID 0166009. and some hda-gfx property. this either matches your setup or not. eep357 and myself looked into the framebuffer kext connector tables and i ran some tests, and it seems that even the driver itself disregards the connector type, its the port number thats important. you need to choose a platform id that contains at least one refernce to a port your motherboard uses for one of its displays. here are the connector tables, the ports are he first 2 bytes of each line. the HD4000 seems to have its ports numbered as 0,5,6,7 respectively. as you see platform ID 0166009 does not output on port 0x7, if thats where your display is connected on your motherboard, it wont work. i know people love the easyness of chimera, but until it lets you choose what platform-id to insert, its simply not up to scratch, and you'll need to inject via other means, DSDT or whatever.

Code:
AAPL,ig-platform-id: 01660000, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3
@0, 01 00 00 00 02 00 00 00 03 00 00 00 // (LVDS) (port 0x0)
@1, 02 05 00 00 00 04 00 00 07 00 00 00 // (DisplayPort) (port 0x5)
@2, 03 04 00 00 00 04 00 00 07 00 00 00 // (DisplayPort) (port 0x6)
@3, 04 06 00 00 00 04 00 00 07 00 00 00 // (DisplayPort (port 0x7)

AAPL,ig-platform-id: 01660001, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3
@0, 01 00 00 00 02 00 00 00 30 00 00 00 // (LVDS)
@1, 02 05 00 00 00 08 00 00 06 00 00 00 // (HDMI)
@2, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@3, 04 06 00 00 00 04 00 00 07 01 00 00 // (DisplayPort


AAPL,ig-platform-id: 01660002, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 1, FBMem: 1
@0, 01 00 00 00 00 02 00 00 30 00 00 00 // (LVDS)

AAPL,ig-platform-id: 01660003, Stolen RAM for FB: 64MB, Pipes: 2, Ports: 4, FBMem: 2
@0, 05 03 00 00 02 00 00 00 30 00 00 00 // (LVDS)
@1, 02 05 00 00 00 04 00 00 07 04 00 00 // (DisplayPort)
@2, 03 04 00 00 00 04 00 00 81 00 00 00 // (DisplayPort)
@3, 04 06 00 00 00 04 00 00 81 00 00 00 // (DisplayPort) 


AAPL,ig-platform-id: 01660004, Stolen RAM for FB: 32MB, Pipes: 3, Ports: 1, FBMem: 1
@0, 05 03 00 00 02 00 00 00 30 02 00 00 // (LVDS)

AAPL,ig-platform-id: 01620005, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2 
@0, 02 05 00 00 00 04 00 00 11 00 00 00 // (DisplayPort)
@1, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@2, 04 06 00 00 00 04 00 00 07 01 00 00 // (DisplayPort) 

AAPL,ig-platform-id: 01620006, Stolen RAM for FB: 0MB, Pipes: 0, Ports: 0, FBMem: 0

AAPL,ig-platform-id: 01620007, Stolen RAM for FB: 0MB, Pipes: 0, Ports: 0, FBMem: 0

AAPL,ig-platform-id: 01660008, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3
@0, 01 00 00 00 02 00 00 00 30 00 00 00 // (LVDS)
@1, 02 05 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@2, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)


AAPL,ig-platform-id: 01660009, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 
@0, 01 00 00 00 02 00 00 00 30 00 00 00 // (LVDS)
@1, 02 05 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@2, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)

AAPL,ig-platform-id: 0166000A, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2
@0, 02 05 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@1, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@2, 04 06 00 00 00 08 00 00 06 00 00 00 // (HDMI) 

AAPL,ig-platform-id: 0166000B, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2
@0, 02 05 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@1, 03 04 00 00 00 04 00 00 07 01 00 00 // (DisplayPort)
@2, 04 06 00 00 00 08 00 00 06 00 00 00 // (HDMI)
 
Status
Not open for further replies.
Back
Top