Contribute
Register

Haswell GT1 no QE/CI on Mavericks

Status
Not open for further replies.
tvhung83

tvhung83

Joined
Aug 18, 2011
Messages
48
Motherboard
ASUS H110M-e DDR4
CPU
i3 6100
Graphics
HD530 + HIS RX 470 IceQ X2 OC 4GB
Hi, I'm trying to install Mavericks on my HP Stream Mini 200-010, below is my specs:

CPU: Celeron 2957U 1.4GHz
RAM: 6GB DDR3L 1600MHz
GPU: Haswell GT1
Socket: 1168 BGA (from CPU-Z)
Mainboard: Hewlett-Packard 2B38 (from CPU-Z)
Chipset: Intel Haswell-ULT (from CPU-Z)
Click to expand...

I'm using Clover UEFI. Currently I can boot with -xcpm -kext-dev-mode=1, using FakeCPUID=0x0306A0. I've attached my config.plist, original DSDT, and patched DSDT (applied only one patch: "Rename PCI0.GFX0 to PCI0.IGPU" from RehabMan's repository).

I've tried to force device-id to "0x0a16", using below patch (or FakeID in Clover config):
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

"device-id", Buffer() { 0x16, 0x0a, 0x00, 0x00 },\n

"AAPL,ig-platform-id", Buffer() { 0x05, 0x00, 0x26, 0x0a },\n "hda-gfx", Buffer() { "onboard-1" },\n

})\n

}\n

end;
Click to expand...
Both leads me to no signal via Display Port.

Please help to give me some hints. Thank you very much.
 

Attachments

  • cpu.png
    cpu.png
    29.4 KB · Views: 941
  • mainboard.png
    mainboard.png
    13.4 KB · Views: 546
  • config.plist
    8.2 KB · Views: 342
  • DSDT-origin.aml
    111 KB · Views: 279
  • DSDT-patched.aml
    111 KB · Views: 293
tvhung83 said:
Hi, I'm trying to install Mavericks on my HP Stream Mini 200-010, below is my specs:



I'm using Clover UEFI. Currently I can boot with -xcpm -kext-dev-mode=1, using FakeCPUID=0x0306A0. I've attached my config.plist, original DSDT, and patched DSDT (applied only one patch: "Rename PCI0.GFX0 to PCI0.IGPU" from RehabMan's repository).

I've tried to force device-id to "0x0a16", using below patch (or FakeID in Clover config):

Both leads me to no signal via Display Port.

Please help to give me some hints. Thank you very much.
Click to expand...

What is the native device-id of your graphics device?

You should use a desktop ig-platform-id, not mobile ig-platform-id.

Note: kext-dev-mode=1 is not necessary with Mavericks. And -xcpm is default for Haswell (FakeCPUID probably takes care of it, assuming the FakeCPUID you're using is Haswell [should be]).

0xa16 is GT2, so you don't want to truly force that (and device-id injection only affects IOKit match, not what the kext sees).
 
Hi RehabMan, thanks for your reply.
My (GPU) device-id is 0x0a06.
Where I can find a list of ig-platform-id that I can try?
 
tvhung83 said:
Hi RehabMan, thanks for your reply.
My (GPU) device-id is 0x0a06.
Click to expand...

That device-id is not natively supported by either Info.plist (Azul/HD5000).

So... you'll need to inject a device-id just to get the kexts to load. Which you've already done... But it is probably best to inject an id that is one of the GT1 IDs supported by the kext (look at the Info.plist and do the research on each one).

I suspect if AppleIntelFramebufferAzul.kext supports GT1, it may already be loading, and you may just need the proper ig-platform-id to match the connectors you have (eg. don't use a laptop ig-platform-id). AppleIntelHD5000Graphics.kext is a bit more picky, and usually requires further coercion for unsupported devices (FakePCIID).

Use a remote desktop connection over the network from another computer in order to capture ioreg and do other diagnostics in the event you're unable to get an image on your monitor.

But if there is a whitelist of PCI IDs implemented in the kext (either in FramebufferAzul or HD5000Graphics, then you'll need to look into using FakePCIID.kext (and a custom injector). First step is to determine if any of the IDs in the Info.plist are GT1 and then use that as a target ID via FakePCIID.kext.

Where I can find a list of ig-platform-id that I can try?
Click to expand...

You can see them all by looking directly at the kext in hex edit (search for one you know, then notice how the table is laid out to find the others).

I made this list a while ago from the 10.10.2 kext:
Code: 
ig-platform-id values Azul 10.10.2...

00 00 06 0C
00 00 16 0C
00 00 26 0C
00 00 06 04
00 00 16 04
00 00 26 04
00 00 26 0D
00 00 16 0A
00 00 26 0A
05 00 26 0A
06 00 26 0A
08 00 2E 0A
0C 00 16 0A
07 00 26 0D
03 00 22 0D
0A 00 2E 0A
0A 00 26 0A
0D 00 2E 0A
0D 00 26 0A
04 00 12 04
0B 00 12 04
09 00 26 0D

terminator: 
FF FF FF FF

I haven't made a similar effort to list the IDs in the 10.9.5 kext. There is a list here: http://www.tonymacx86.com/graphics/...lags-igpenabler-igplatformid-igpdeviceid.html

You can use Pike's AppleIntelFramebufferAzul.sh to look at the data associated with each ID. Platform ids with LVDS connectors are generally used for mobile devices, whereas desktop IDs have DP and HDMI ports only.

If I recall correctly, 0x0d220003 is the default desktop ig-platform-id used by Chimera (and probably Clover and Chameleon).
 
Thanks RehabMan. Your answer just opened a lot of possibilities. I will try it tonight when i got home, and update status here :)
 
[SUP]TVhung, have you tried to get the HP stream mini to work? Any updates?

gman[/SUP]
 
Hi gman76, sorry for this late response, I've been quite busy lately, so not much time playing with it. Last time, I've tried all device-id I got from Azul (without ig-platform-id), but no luck, all got the same result as "Unknown Graphics with 64MB shared memory". Until I combined with an ig-platform-id, I got no signal via DP port. And when I remote to it, I saw "Unknown Graphics with 1024MB", which is a good sign I think. But again, this issue may take too much times to resolve, I'm planning to upgrade to a Intel NUC with a Broadwell CPU, since I saw a good progress there. This machine is only as good as a HTPC anyway, too slow to do some coding on it.
 
Hi, so I spent a couple of hours tonight to retry. Good news is, the "no signal" is gone, it turned out that I accidentally left DSDT.aml in patched folder, and it overrides Clover ID injection. Does that mean connector is alright?
Anyway, no matter which device-id & ig-platform-id I tried (0x0c06, 0x0426, 0x0412. etc.), still no QE/CI, and it's still showing Graphics as "Unknown 1024MB". Right now, I'm using device-id=0x0406, and ig-platform-id=0x04060000, which I extracted from Pike's AppleIntelFramebufferAzul.sh. Below is the full list:
The supported platformIDs are:

[ 1] : 0x0c060000 - Haswell SDV Mobile GT1
[ 2] : 0x0c160000 - Haswell SDV Mobile GT2
[ 3] : 0x0c260000 - Haswell SDV Mobile GT3
[ 4] : 0x04060000 - Haswell Mobile GT1
[ 5] : 0x04160000 - Haswell Mobile GT2
[ 6] : 0x04260000 - Haswell Mobile GT3
[ 7] : 0x0d260000 - Haswell CRW Mobile GT3
[ 8] : 0x0a160000 - Haswell ULT Mobile GT2
[ 9] : 0x0a260000 - Haswell ULT Mobile GT3
[10] : 0x04160002 - Haswell Mobile GT2
[11] : 0x0a260005 - Haswell ULT Mobile GT3
[12] : 0x0a260006 - Haswell ULT Mobile GT3
[13] : 0x0a260008 - Haswell ULT Mobile GT3
[14] : 0x0a2e0008 - Haswell ULT E GT3
[15] : 0x0d260007 - Haswell CRW Mobile GT3
[16] : 0x0d220003 - Haswell CRW GT3
[17] : 0x04120004 - Haswell GT2
Click to expand...

I attached here the DSDT.aml and exported IOReg. Hopefully someone can find a clue about what to do next.
 

Attachments

  • HP_Stream.ioreg
    2.3 MB · Views: 292
  • DSDT.aml
    112 KB · Views: 290
tvhung83 said:
Hi, so I spent a couple of hours tonight to retry. Good news is, the "no signal" is gone, it turned out that I accidentally left DSDT.aml in patched folder, and it overrides Clover ID injection. Does that mean connector is alright?
Anyway, no matter which device-id & ig-platform-id I tried (0x0c06, 0x0426, 0x0412. etc.), still no QE/CI, and it's still showing Graphics as "Unknown 1024MB". Right now, I'm using device-id=0x0406, and ig-platform-id=0x04060000, which I extracted from Pike's AppleIntelFramebufferAzul.sh. Below is the full list:


I attached here the DSDT.aml and exported IOReg. Hopefully someone can find a clue about what to do next.
Click to expand...

You don't use the 0x in front of the ID in your config file. At least for the ig-platform-id.
 
slim.jim said:
You don't use the 0x in front of the ID in your config file. At least for the ig-platform-id.
Click to expand...
I'm injecting using DSDT, so it's irrelevant.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top