Intel HD Graphics / GMA 5700

[Time2Retire]

Hi

I´m still on the search for a solution for IntelHD Graphics

I tryd any solutions here in this forum, (and looking in others)

via DSDT, via EFI string, kext editing, with always the same result = only Remote display,

backlight on, no screen on LCD

You need to go back a few steps. Please read the "AAPL,os-info" data given a few pages back. That will enable the LCD panel.

[fmac]

You need to go back a few steps. Please read the "AAPL,os-info" data given a few pages back. That will enable the LCD panel.

 

Not for me

believe me i tryed it

its not working

[Time2Retire]

@Cool-Oase: I haven't checked your link, but I guess that you are talking about AppleGraphicsControl.kext in which case you also need to bin-patch MacOS/AppleGraphicsControl and that is done before already.

 

@fmac: I find that hard to believe especially since the real MacBookPro6,1 exposes the same problem when I remove it.

[XmodD]

@dutch

 

i am! sorry did not find files already has been fixed! ll test my files later by my own. if u say gcotrol already has been pached u ll be right.

[kizwan]

I did further testing last night with os-info. I found it function like Nvidia NVCAP.

30 49 01 11 01 10 08 00 00 01 00 00 00 00 00 00 FF FF FF FF

30 49 00 14 14 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

30 49 01 01 01 00 08 00 00 00 00 00 00 00 00 00 FF FF FF FF

This test has been done with external monitor plugged in to HDMI port.

- The 1st & 3rd os-info detected the internal LCD (in IOReg) but the screen is blank/black. No signal to the external monitor.

- The 1st one actually already exist in IOReg (automatically) without manual injection.

- The 2nd os-info turned off the internal LCD. Grey screen on external monitor. No display detected in IOReg.

Since 1st & 3rd behave the same, I found out that the fifth bytes is identical between 1st & 3rd. So I did little experiment with 2nd os-info.

30 49 00 14 01 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- The result is the same with 1st & 3rd.

30 49 00 14 02 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- The result is grey screen on external monitor. Internal LCD turned off. No display detected in IOReg.

30 49 00 14 03 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- The result is only a little artifact on the external monitor. Internal LCD turned off. There is only two lines under IGP device in IOReg.

30 49 00 14 04 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- The result is grey screen on external monitor. Internal LCD turned off. No display detected in IOReg.

 

I think I can make the conclusion that the 0x01 at the fifth bytes is internal LCD connection (LVDS/TMDS).

So, to activate the external monitor I need to find which bytes hold it. Maybe the green one is for primary display while the red one is for secondary display?

30 49 01 11 01 10 08 00 00 01 00 00 00 00 00 00 FF FF FF FF

 

I wish I know what other bytes means.

[yurick]

Всем известно ,что данная видео карта ставится на ноутбуки по тому пошу здесь дабы может у кого возникнит желание помочь с заводкой данной карты ,Которая состоит из intelHD и nVidia 310GT

итак на ноут с данной видюшкой мак ось ставится разными способами ((проверено)

1. Это с флешки вырезав дрова на intelHD

 

2 с той же флешки ( проверялось уже на работающей оси )потем вставки драйверов и изменения info.plist

в 2х кекстах измяем параметр Gеn 575 на любой другой ( может есть конкретное число ) не проверялось лично мной

 

3. Редактирование info.plist кекста AppleGraphicsControl.kext так же путем изменения Gen575 на любое другое

 

4. и самое интересное если удалить AppleUpstreamUserClient.kext и не изменять значения 575 а оставить все родное то система начинает грузится и давольно шустро но увидим только голубой экрам и курсор

 

google translator ˆ

 

Everyone knows that the video card is placed on the laptops by the fact poshu here so can anyone want to help with the appearance winding of the card, which consists of intelHD and nVidia 310GT

So on the laptop with this vidyushkoy maximum axle is placed in different ways ((verified)

1. This is a stick cut out the wood on intelHD

2 with the same stick (tested already on the operating axis) Potem insert drivers and change info.plist

in the 2 kexts crush option Gen 575 [/ b] for any (may have a specific number) is not checked by me

3. Editing info.plist kexts AppleGraphicsControl.kext [/ b] just by changing the Gen575 [/ b] any other

4. and the most interesting if you remove AppleUpstreamUserClient.kext [/ b] and do not change the values of 575 and leave his native then the system starts to boot and quick start but see only the ekram blue and the cursor [/ i]

[Time2Retire]

- The 1st one actually already exist in IOReg (automatically) without manual injection.

Not here. I guess that it means that AppleIntelHDGraphicsFB.kext is going further, doing more for people with Nvidia cards. You might check this by hex-editing the kext and changing the text NVDA and/or nvkernel in the kext to see what happens.

 

BTW: Am I the only person here (with an ATI instead of a NVIDIA GPU maybe?) where adding the os-info property works with any model identifier like MacOnCrack1,1?

 

I wish I know what other bytes means.

I haven't checked but I think that the first two bytes are linked to display0 hence the 30 49. I might be wrong, but 49 is character "0" and 30 is numeric 0. This might explain why changing these breaks stuff.

 

Also. This works here:

/* External Monitor (minimized) */
/* 0000 */	0x30, 0x49, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00, 
/* 0008 */	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
/* 0010 */	0xff, 0xff, 0xff, 0xff

Note: bit 0 is LCD panel and bit 2 is the external monitor here.

[kizwan]

30 49 01 11 01 10 08 00 00 01 00 00 00 00 00 00 FF FF FF FF

30 49 00 14 14 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

30 49 01 01 01 00 08 00 00 00 00 00 00 00 00 00 FF FF FF FF

- The 1st one actually already exist in IOReg (automatically) without manual injection.

Not here. I guess that it means that AppleIntelHDGraphicsFB.kext is going further, doing more for people with Nvidia cards. You might check this by hex-editing the kext and changing the text NVDA and/or nvkernel in the kext to see what happens.

Sorry, I checked it again & the there is no os-info entry in my old IOReg dump. I must have mixed up with real macbookpro's IOReg dump.

 

Anyway, I tested the three os-info again with external LCD connected to VGA port. I got mangled screen at the external monitor with all three os-info.

30 49 01 11 01 10 08 00 00 01 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Backlight only on internal LCD. Display detected in System Profiler & IOReg is the internal LCD.

30 49 00 14 14 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Internal LCD is turned off. Display detected in System Profiler & IOReg is the external LCD.

30 49 01 01 01 00 08 00 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Backlight only on internal LCD. Display detected in System Profiler & IOReg is the internal LCD.

 

I also did further test with 2nd os-info with different value at the fifth bytes:-

30 49 00 14 01 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Backlight only on internal LCD. Display detected in System Profiler & IOReg is the internal LCD.

30 49 00 14 02 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Internal LCD is turned off. Display detected in System Profiler & IOReg is the external LCD.

30 49 00 14 0F 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Backlight only on internal LCD. Display detected in System Profiler & IOReg is the internal LCD.

30 49 00 14 04 14 08 04 00 00 00 00 00 00 00 00 FF FF FF FF

- Mangled screen on external LCD. Internal LCD is turned off. Display detected in System Profiler & IOReg is the external LCD.

 

I also test your os-info:-

/* External Monitor (minimized) */
 /* 0000 */	0x30, 0x49, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00, 
 /* 0008 */	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
 /* 0010 */	0xff, 0xff, 0xff, 0xff

Note: bit 0 is LCD panel and bit 2 is the external monitor here.

- Mangled screen on external LCD. Internal LCD is turned off. Display detected in System Profiler & IOReg is the external LCD.

 

EDIT: Mangled screen means I can see the desktop, icons, etc but it is badly mangled.

[Time2Retire]

Just to let people know: I am now sharing the new* HP G72 notebook with someone else – she does not have her own MacBook Pro – which will make things a little more complicated, but not impossible.

 

The good news is that my field trainings are over (due to the low/freezing temperatures) so I will have some additional time to work on tools like FBDump (school wants me to finish it and let others work on audio, wlan and video) and smbios2struct.

 

* I had a dead pixel from day one which turned into a dead line later on. We got a replacement (same HDD) but was told that I have to slow down a little and give other students a chance... so I am stuck waiting for the HP.

 

Update:

The new HP arrived today (on my desk) and what do you know... it now boots up in a default resolution of 1600 x 900 x 32 where the previous (now broken) HP (same series/type) refused to do this. So what changed? The first thing I noticed was that the EDID data changed so I checked and one thing is sure... there's a new/different brand/type LCD panel (LGDisplay - LP173WD1-TLC3 versus AUO - B173RW01 V3).

[Fiox89]

Sin..i have your same laptop Asus K52Jc, I think I will start looking for a new laptop.

Thanks for your explanation

 

OT: you know laptop with i3/i5 for snow leopard?

[Time2Retire]

Hello everybody, im new to this board but others may or may not recognize my name from the past in other tech-related boards.

...

LOL Good to see people with a sense of humor here... and a degree in word processing hahahaha

[Tomdev]

ok so you said DSDT will not work, but is modifying the kext code itself (disassembling, patching, assembling) not the option then?

[beaups]

Apparently you sir did not understand the purpose of my brilliant informative post on this board. Mind I suggest you, continue carefully with your research project. I will, however, warn you: it is obviously not going to reach any successful result in any time soon. My degree in word processing is, in fact, real and as funny as it may sound, you obviously haven't achieved any of your goals at all so might you stop mocking others for their flawless success.

 

Cheers.

 

And your "flawless success" is not getting anything working?? I hope you are trying to be funny.

[Time2Retire]

And your "flawless success" is not getting anything working?? I hope you are trying to be funny.

The first time I read through it I went like OMG it's Nigerian spam! Same style. Same bs; Here's one example: Google his nickname. I mean how should people recognize him and his nickname... when nothing shows up in Google?

 

@0sX86H4X0R: I laughed because come on dude. A degree in word processing? From what institute? Please enlighten me; how exactly is this degree going to help you to get stuff going on your hackintosh? Mind you I hold two degrees myself, and I am a student at nyenrode.nl A highly acclaimed private university. Also. Look at my avatar. What do you see there? It sure as hell ain't a guy. Nope. I'm a pretty girl thank you very much.

 

You simply can't ask people here to trust you, and to stop because you failed. And all this without adding any source / credibility whatsoever. No thanks. I'm done with it.

[overflow]

So any hope 10.6.6 will change anything? Rumor has it it's only a couple of days away.

Would be a really nice early Xmas surprise

[cuuler]

Apparently you sir did not understand the purpose of my brilliant informative post on this board. Mind I suggest you, continue carefully with your research project. I will, however, warn you: it is obviously not going to reach any successful result in any time soon. My degree in word processing is, in fact, real and as funny as it may sound, you obviously haven't achieved any of your goals at all so might you stop mocking others for their flawless success.

 

Cheers.

 

annoying, obnoxious, and unconstructive.

[AjGilee]

Anyone tried or patched these Intel HD kext to work yet?

 

 

For GMA 4500 series. It still looks pretty similar with the HDs though.

 

http://software.intel.com/en/articles/quic...rated-graphics/

[beaups]

Anyone tried or patched these Intel HD kext to work yet?

 

 

For GMA 4500 series. It still looks pretty similar with the HDs though.

 

http://software.intel.com/en/articles/quic...rated-graphics/

 

Go away! You posted the same thing in multiple threads. There is no solution for x4500 for qe/ci. No need for you to dirty up the GMA5700 threads.

[beta992]

Any update on this?

 

K52JC also has Optimus Technologie

 

What I understand now, even if the Intel HD is the only active gpu (in BIOS), their is still no kext that can load it?

 

Thanks

[Time2Retire]

I had another look at Device GMUX in the Apple DSDT (here it is):

                Device (GMUX)
               {
                   Name (_HID, EisaId ("APP000B"))
                   Name (_CID, "gmux")
                   Name (_STA, 0x0B)
                   Name (_CRS, ResourceTemplate ()
                   {
                       IO (Decode16,
                           0x0700,             // Range Minimum
                           0x07FF,             // Range Maximum
                           0x01,               // Alignment
                           0xFF,               // Length
                           )
                   })
                   Name (_PRW, Package (0x02)
                   {
                       0x16, 
                       0x03
                   })
                   Scope (\_GPE)
                   {
                       Method (_L16, 0, NotSerialized)
                       {
                           Notify (\_SB.PCI0.LPCB.GMUX, 0x80)
                       }
                   }

                   Name ([b][color="#FF0000"]GMGP[/color][/b], 0x16)
                   Method ([b][color="#FF0000"]GMSP[/color][/b], 1, NotSerialized)
                   {
                       If (LLessEqual (Arg0, 0x01))
                       {
                           Or (GP06, Arg0, GP06)
                       }
                   }

                   Method ([b][color="#FF0000"]GMLV[/color][/b], 0, NotSerialized)
                   {
                       Return (GP06)
                   }
               }

The red methods are read/called from MacOS/AppleGraphicsControl (be my guest and check this yourself) and GP06 is just a single bit so it is either 1 or 0, but more importantly is the address range 0700-07ff because if that was somehow linked to an Apple only hardware mulitplexer... then how come switching graphics works in Windows? Why wouldn't Apple use the Intel built in PEG control?

 

What if I tell you that it now selects the DisplayPort, which many of us don't have, and thus we have to (somehow) patch it... to make it select our LVDS instead (that's just a bit setting BTW).

 

Time to use the command line tool reggie maybe, and to poke this area?

 

And no... we are not making any progress Nope. Not at all

[sjuut]

I had another look at Device GMUX in the Apple DSDT (here it is):

                Device (GMUX)
               {
                   Name (_HID, EisaId ("APP000B"))
                   Name (_CID, "gmux")
                   Name (_STA, 0x0B)
                   Name (_CRS, ResourceTemplate ()
                   {
                       IO (Decode16,
                           0x0700,             // Range Minimum
                           0x07FF,             // Range Maximum
                           0x01,               // Alignment
                           0xFF,               // Length
                           )
                   })
                   Name (_PRW, Package (0x02)
                   {
                       0x16, 
                       0x03
                   })
                   Scope (\_GPE)
                   {
                       Method (_L16, 0, NotSerialized)
                       {
                           Notify (\_SB.PCI0.LPCB.GMUX, 0x80)
                       }
                   }

                   Name ([b][color="#ff0000"]GMGP[/color][/b], 0x16)
                   Method ([b][color="#ff0000"]GMSP[/color][/b], 1, NotSerialized)
                   {
                       If (LLessEqual (Arg0, 0x01))
                       {
                           Or (GP06, Arg0, GP06)
                       }
                   }

                   Method ([b][color="#ff0000"]GMLV[/color][/b], 0, NotSerialized)
                   {
                       Return (GP06)
                   }
               }

The red methods are read/called from MacOS/AppleGraphicsControl (be my guest and check this yourself) and GP06 is just a single bit so it is either 1 or 0, but more importantly is the address range 0700-07ff because if that was somehow linked to an Apple only hardware mulitplexer... then how come switching graphics works in Windows? Why wouldn't Apple use the Intel built in PEG control?

 

What if I tell you that it now selects the DisplayPort, which many of us don't have, and thus we have to (somehow) patch it... to make it select our LVDS instead (that's just a bit setting BTW).

 

Time to use the command line tool reggie maybe, and to poke this area?

 

And no... we are not making any progress Nope. Not at all

 

Dear fellow-dutchy,

 

I do have a DisplayPort on my i5-geforce g330m Optimus!

Let me know if I can help out, I've been monitoring this thread for weeks now..

[yurick]

http://www.intelcorei7.net/apple-intel-hd-graphic-kexts.html

[Fiox89]

Work for anyone? QE/CI??

[yurick]

Work for anyone? QE/CI??

not tested

[beaups]

not tested

OLD post...not gonna work, we already have these kexts.