Contribute
Register

Gigabyte Brix i7 - GB-BXi7-5500 works on 10.10.3

Status
Not open for further replies.
shhhhh said:
See attached
Click to expand...

OK, I see this is Broadwell... don't think I realized that with my original response... Problem of profile not being filled out...

You don't need FakePCIID kexts (they will not load anyway, so having them installed does nothing)...

The ig-platform-id you're using is for mobile (it has an LVDS connector, note framebuffer@0 connector-type <02 00 00 00>). Try using an ig-platform-id that has only desktop connectors (DP/HDMI).

Note: Some in the laptop forum have reported that booting Windows first, then restarting into Yosemite can solve the hanging problems (graphics chip initialization issue?). But you should try an appropriate desktop ig-platform-id as well.
 
[SUP]Ok, I deleted the FakePCIID kexts and I'm using ig-platform-id 0x16160000 now (the only other HD 5500 platform id as far as I can tell?). I'll let you know how it goes[/SUP]
 
shhhhh said:
[SUP]Ok, I deleted the FakePCIID kexts and I'm using ig-platform-id 0x16160000 now (the only other HD 5500 platform id as far as I can tell?). I'll let you know how it goes[/SUP]
Click to expand...
No luck, I've got another crash. Music is still playing and I can move the cursor, but there's no response to keyboard commands and nothing on the screen is updating (volume etc)
 
shhhhh said:
[SUP]Ok, I deleted the FakePCIID kexts and I'm using ig-platform-id 0x16160000 now (the only other HD 5500 platform id as far as I can tell?). I'll let you know how it goes[/SUP]
Click to expand...

There is more than just 0x16160000 and 0x16160002.

Look at AppleIntelBDWGraphicsFramebuffer in a hex editor (such as HexFiend). The first ig-platform-id is 0x16060000 (search for 00 00 06 16).

Each ig-platform-id is 136 bytes. The end-marker is 0xFFFFF.
 
RehabMan said:
There is more than just 0x16160000 and 0x16160002.

Look at AppleIntelBDWGraphicsFramebuffer in a hex editor (such as HexFiend). The first ig-platform-id is 0x16060000 (search for 00 00 06 16).

Each ig-platform-id is 136 bytes. The end-marker is 0xFFFFF.
Click to expand...
I don't think there are any others corresponding to HD Graphics 5500 is all I'm saying (based on this information):
[ 1] : 0x16060000 – Broadwell GT1 (Intel HD Graphics)
[ 2] : 0x160e0000 – Broadwell GT1 (Intel HD Graphics)
[ 3] : 0x16160000 – Broadwell GT2 (Intel HD Graphics 5500)
[ 4] : 0x161e0000 – Broadwell GT2 (MacBook) (Intel HD Graphics 5300)
[ 5] : 0x16260000 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[ 6] : 0x162b0000 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[ 7] : 0x16220000 – Broadwell GT3 (Intel Iris Pro Graphics 6200)
[ 8] : 0x160e0001 – Broadwell GT1 (Intel HD Graphics)
[ 9] : 0x161e0001 – Broadwell GT2 (MacBook) (Intel HD Graphics 5300)
[10] : 0x16060002 – Broadwell GT1 (Intel HD Graphics)
[11] : 0x16160002 – Broadwell GT2 (Intel HD Graphics 5500)
[12] : 0x16260002 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[13] : 0x16220002 – Broadwell GT3 (Intel Iris Pro Graphics 6200)
[14] : 0x162b0002 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[15] : 0x16120003 – Broadwell GT2 (Intel HD Graphics 5600)
[16] : 0x162b0004 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[17] : 0x16260004 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[18] : 0x16260005 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[19] : 0x16260006 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)

But I'll start trying different ones for lack of any better solutions

EDIT: Do you think this might help? (from hd5500 thread)

(2) Screen Freeze Issue (GPU hang and restart)

Using FakeSMC 5.3.820 or other 5.x.xxx version will decrease the opportunity to freeze.
(Note that please delete CPUSensors.kext from FakeSMC.kext if you get kernel panic related to CPUSensors.kext)
 
shhhhh said:
I don't think there are any others corresponding to HD Graphics 5500 is all I'm saying (based on this information):
[ 1] : 0x16060000 – Broadwell GT1 (Intel HD Graphics)
[ 2] : 0x160e0000 – Broadwell GT1 (Intel HD Graphics)
[ 3] : 0x16160000 – Broadwell GT2 (Intel HD Graphics 5500)
[ 4] : 0x161e0000 – Broadwell GT2 (MacBook) (Intel HD Graphics 5300)
[ 5] : 0x16260000 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[ 6] : 0x162b0000 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[ 7] : 0x16220000 – Broadwell GT3 (Intel Iris Pro Graphics 6200)
[ 8] : 0x160e0001 – Broadwell GT1 (Intel HD Graphics)
[ 9] : 0x161e0001 – Broadwell GT2 (MacBook) (Intel HD Graphics 5300)
[10] : 0x16060002 – Broadwell GT1 (Intel HD Graphics)
[11] : 0x16160002 – Broadwell GT2 (Intel HD Graphics 5500)
[12] : 0x16260002 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[13] : 0x16220002 – Broadwell GT3 (Intel Iris Pro Graphics 6200)
[14] : 0x162b0002 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[15] : 0x16120003 – Broadwell GT2 (Intel HD Graphics 5600)
[16] : 0x162b0004 – Broadwell GT3 (MacBook Pro) (Intel Iris Graphics 6100)
[17] : 0x16260004 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[18] : 0x16260005 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)
[19] : 0x16260006 – Broadwell GT3 (MacBook Air) (Intel HD Graphics 6000)

But I'll start trying different ones for lack of any better solutions
Click to expand...

Contrary to myth, ig-platform-id has nothing to do with the graphics device you have. It specifies a framebuffer configuration (eg. BIOS/framebuffer memory sizes, connectors, etc.)

You need to look at the connector data for each and focus on the ones that don't have LVDS connectors. Alternately you can patch an existing one to remove the LVDS connector.

You can use AppleIntelFramebufferAzul.sh to become more familiar with the connector data. Then apply what you learn to the Broadwell framebuffer kext (it is slightly different but shares much with Azul).
 
RehabMan said:
Contrary to myth, ig-platform-id has nothing to do with the graphics device you have. It specifies a framebuffer configuration (eg. BIOS/framebuffer memory sizes, connectors, etc.)
Click to expand...
0x16060000 seems to work all right! trying really hard, can't crash it
 
Hello there,

I am just trying to install OS Yosemite onto the gigabyte brix. Will there be any update to make the drivers work?
 
adcosta said:
Hello there,

I am just trying to install OS Yosemite onto the gigabyte brix. Will there be any update to make the drivers work?
Click to expand...

Which drivers are you referring to?
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top