Clover Intel HD 3000

[RehabMan]

I've done both of these with no luck. I'm attaching my config.plist, I've just removed my serial number for this post–– any help would be appreciated!

How is your monitor connected to the motherboard?

You have the nvidia disabled and/or removed from the machine?

Also, check your BIOS settings for the IGPU.

 

[jonisign]

For this I have the monitor connected to the integrated graphics HDMI port, not the nvidia port. I also disabled the Nvidia card while trying to get this to work and set the BIOS to post to the integrated card–– everything works fine until about 5-10 seconds into booting when the graphics on the screen become garbled.

 

[RehabMan]

For this I have the monitor connected to the integrated graphics HDMI port, not the nvidia port. I also disabled the Nvidia card while trying to get this to work and set the BIOS to post to the integrated card–– everything works fine until about 5-10 seconds into booting when the graphics on the screen become garbled.

Remove the nvidia card for testing (deal with that later). Check your BIOS settings for IGPU (64mb,etc).

Try a different port (DVI/DP if you have it)...

 

[jonisign]

Alright, will try that later! Thanks for the advice. As far as the IGPU, I had it set to 512mb and also tried 96mb and 64mb in the BIOS.

 

[RehabMan]

Alright, will try that later! Thanks for the advice. As far as the IGPU, I had it set to 512mb and also tried 96mb and 64mb in the BIOS.

Just FYI: I'm using Clover UEFI on my desktop (Intel DH67GD/Core i7-2600K) with HD3000, so I know it is possible. My monitor config is probably quite different from yours though: Dell U3011 2560x1600 connected via DP.

I also use a properly patched DSDT (GFX0 renamed to IGPU) and MacMini5,3 smbios. The rename to IGPU is important as it enables correct IGPU PM.

 

[jonisign]

Just FYI: I'm using Clover UEFI on my desktop (Intel DH67GD/Core i7-2600K) with HD3000, so I know it is possible. My monitor config is probably quite different from yours though: Dell U3011 2560x1600 connected via DP.

I also use a properly patched DSDT (GFX0 renamed to IGPU) and MacMini5,3 smbios. The rename to IGPU is important as it enables correct IGPU PM.

Excellent, right, I'm sure it's possible! The fact that I can get it working with acceleration through chameleon suggests so as well...

I'm currently using an iMac12,2 smbios and have tried the MacMini5,3 as well with the same result. I may try the DSDT route, but was hoping to go without one! Another complicating factor on my setup might be that I'm using a B75 board... I had to make edits to the graphics kexts as mentioned here: http://www.tonymacx86.com/150-enabl...therboards-hd-4000-6-series-motherboards.html

Could that be causing problems? Another thought is that maybe I need different device ID then the one you mentioned? Are there any other posssible ones for the HD 3000? I'm using a 2500K instead of a 2600K.

Thanks!

 

[RehabMan]

Excellent, right, I'm sure it's possible! The fact that I can get it working with acceleration through chameleon suggests so as well...

I'm currently using an iMac12,2 smbios and have tried the MacMini5,3 as well with the same result. I may try the DSDT route, but was hoping to go without one! Another complicating factor on my setup might be that I'm using a B75 board... I had to make edits to the graphics kexts as mentioned here: http://www.tonymacx86.com/150-enabl...therboards-hd-4000-6-series-motherboards.html

Could that be causing problems?

If you've already done the patches to the kexts (I would use a DSDT patch or FakeID in config.plist instead), then that should be working for you.

Another thought is that maybe I need different device ID then the one you mentioned? Are there any other posssible ones for the HD 3000? I'm using a 2500K instead of a 2600K.

Chimera injects device-id 0x0126. You could try that instead and see if it makes a difference. According to this article, http://www.tonymacx86.com/378-new-intel-hd-graphics-boot-flags-chimera.html, Chimera also injects snb-platform-id=0x00301000. Clover does not have the ability to inject snb-platform-id, you have to use DSDT patches (my desktop is working without any injection of snb-platform-id).

You could use this patch to inject the same value as Chimera:

into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
    Return (Package()\n
    {\n
        "AAPL,snb-platform-id", Buffer() { 0x00, 0x30, 0x10, 0x00 },\n
        "hda-gfx", Buffer() { "onboard-1" },\n
    })\n
}\n
end;

I would tend to verify what exactly is being injected by Chimera (look in ioreg), since the updated article (linked from the one I provided), shows two different values for HD3000 desktop snb-platform-id.

 

[jonisign]

Great, thanks for the advice! I'm going to try a few more things before I resort to DSDT edits. Booting with chameleon I see under system info:

Chipset Model: Intel HD Graphics 3000
Type: GPU
Bus: Built-In
VRAM (Total): 512 MB
VRAM (Dynamic, Max): 10
Vendor: Intel (0x8086)
Device ID: 0x0126
Revision ID: 0x0009

Using IOReg I see:
device-ID as <26 01 00 00>
and AAPL,snb-platform-id as <10 00 03 00>

I guess I'll try to inject 0x0126 as a fakeID with clover?

Thanks!

 

[jonisign]

Alright well, I've tried everything, including using a DSDT and adding the patch you suggested with no luck. The DSDT loads fine and compiled correctly. About to give up at this point :\ I tried using the DSDT with the edit you suggest without adding the Intel FakeID and the system will boot and incorrectly identify an HD 2000. Using the DSDT with your patch and adding the FakeID you suggested produces the same garbled screen during boot that I've seen before.

 

[RehabMan]

...
Using IOReg I see:
device-ID as <26 01 00 00>
and AAPL,snb-platform-id as <10 00 03 00>

OK, so the value in the "Chimera 3.0 Devices Table" (http://www.tonymacx86.com/graphics/...lags-igpenabler-igplatformid-igpdeviceid.html) is the actual value used.... 0x00030010, not the value in the first article and not first "default" value in the second article. Never trust documentation.

Corrected DSDT patch:

into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
    Return (Package()\n
    {\n
        "AAPL,snb-platform-id", Buffer() { 0x10, 0x00, 0x03, 0x00 },\n
        "hda-gfx", Buffer() { "onboard-1" },\n
    })\n
}\n
end;

I guess I'll try to inject 0x0126 as a fakeID with clover?

I think the snb-platform-id value is going to matter more.