Jump to content

Editing Custom Connector info for Intel HD Graphics? (Gma5700, Arrandale, OSX Lion)


iAngelo
 Share

42 posts in this topic

Recommended Posts

Hi all!

How many of you I also own a notebook with Arrandale CPU with a GPU HD IntelGraphics not currently exploited at 100%, and like many of you are sick of seeinghis brother, "CHILD" Intel HD 3000 Graphics work ...

 

As in this link: http://www.insanelym...howtopic=259705

We can not even try to customize the information we monitor connector built?

Who can do tests on:

 

AppleIntelSNBGraphicsFB.kext

AppleIntelHDGraphicsFB.kext

 

?????

 

I confess I can not .... Who can do it? I will be his Tester!

Do not lose the hopes the board does something we just have to adapt to ourneeds ... er make it work

Link to comment
Share on other sites

It's not going to work, there is no driver for the 5700 as Apple never used this hardware. It's not a connector issue. Quit beating a dead horse and just forget about it.

 

Hello beaups!

Excuse me why Apple has not drivers for this device?

If I'm not mistaken it is coupled with an nVidia used in the MacBook Pro 6.1

with the same Device ID that you see below present in my video card ...

The only problem now and the Frame Buffer! and not that of the QE / CI. In this case, if you think I'm wrong to write this, look in this post:

http://www.insanelym...howtopic=223754

 

 

Notebook: HP G62-b15SL

Video adapter: Intel Auburndale / Arrandale Processor - Integrated GraphicsController

GPU Codename: Ironlake-M

Device ID: 8086-0046 / 103C-1439 (Rev 02)

 

 

Guys what I think you should do is:

Or "create" in the Frame Buffer kext from different sources that Apple provides (Butit seems difficult to achieve for those who do not know).

Or try to "correct" Frame Buffer and adapt as we have done with the editing intelHD3000.

 

Again someone can help, please??

Link to comment
Share on other sites

^Sorry, you are correct about combined with NVIDIA usage but there is no stand alone driver as the apple driver requires a muxer. Lot's of work has been done and gotten nowhere. You should move to a different laptop. Acrh between 5700 and 3000 is very different.

Link to comment
Share on other sites

Basically, no one wants to finish working on it. I've already tried to continue testing on this 2 topics under this. 5700 and it hasn't got anywhere because the coder doesnt have a PC to test with :(

 

Yes I have seen your project and we support!But you want to make a new FB. I wish I just"correct it" according to our needs!

 

You know you made me come to mind that there is "manor" who ran the framebuffer kextwith nVidia(http://www.insanelymac.com/forum/index.php?showtopic=261912&st=0) or c 'also succeeded with the Intel(http://www.insanelymac.com/forum/index.php?showtopic=260866).

 

Now I think ... We can do so using only thenVidia Framebuffer and the acceleration ofIntel graphics? Maybe Patching or replacingthe names in the nVidia kext?

Link to comment
Share on other sites

You know you made me come to mind that there is "manor" who ran the framebuffer kextwith nVidia(http://www.insanelym...pic=261912&st=0) or c 'also succeeded with the Intel(http://www.insanelym...howtopic=260866).

For some reason the correct(=native screen) resolution is in his VBios VESA mode table, so OSX will probably boot into this resolution no matter what he does with the IntelHD*.kexts. But this doesn't help any of those, who don't have the native resolution in their mode table. I don't know about the VBios of the Intel HD graphics, but previous generations of intel graphics could be patched on boot-time to include non-standard vesa resolutions.

 

Sorry, you are correct about combined with NVIDIA usage but there is no stand alone driver as the apple driver requires a muxer.

I have looked at the old thread and I think that this is not the case. There is a driver for the 5700, which some got working with the appropriate SMBIOS file, although it "just" resulted in a garbled screen, which could be timing or memory related problems.

Link to comment
Share on other sites

You should edit

AppleIntelHDGraphicsFB.kext – 0×00468086 0×00428086 (It is the framebuffer)

 

 

The other file AppleIntelHDGraphics.kext – 0×00448086 0×00468086 (it is the accelerator)

 

 

You can use any HEXEditor for mac like "Hex Fiend" http://ridiculousfish.com/hexfiend/

 

It's very difficult that i can help you because i haven't the same Video Card and so i am unable to experiment ...

the way to get your video card works may be very long .... i spent a lot of my spare time to reach my intel Hd3000 working ....

  • Like 3
Link to comment
Share on other sites

You should edit

AppleIntelHDGraphicsFB.kext – 0×00468086 0×00428086 (It is the framebuffer)

 

 

The other file AppleIntelHDGraphics.kext – 0×00448086 0×00468086 (it is the accelerator)

 

 

You can use any HEXEditor for mac like "Hex Fiend" http://ridiculousfish.com/hexfiend/

 

It's very difficult that i can help you because i haven't the same Video Card and so i am unable to experiment ...

the way to get your video card works may be very long .... i spent a lot of my spare time to reach my intel Hd3000 working ....

 

 

Caro amico intanto ti ringrazio molto di avermi risposto!

Capisco benissimo il fatto che non puoi fare le prove ma a me basterebbe che mi spiegassi in modo molto semplice quello che hai fatto tu (hai fatto quello che dicono qui: http://www.insanelym...howtopic=259705)

Magari scivi una miniguida qui utilizzando come kext da modificare i nostri intel HD. Noi testeremo i kext... Vuoi essere il nostro Tonymacx? ;)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Meanwhile,thank youdear friendtoldmea lot!

I understandthatyou can not dothe testsbut tome it's enoughthat Iexplainvery simplywhatyou did(you did what yousayhere:http://www.insanelym...forum/index.php?showtopic=259705)

Perhapsslippingamini-guidehere usingasourintelkextto editHD.Wewill testthe kext...Want tobe ourTonymacx? ;)

Link to comment
Share on other sites

What do youpropose to dothen?

Having read through the older thread, you basically need to find one that has the knowledge, time, spirit and hardware to take a look at the IntelHD*.kexts. I think this is not gonna be easy, as its probably a task that requieres a lot of knowledge in terms of working with graphic hardware.

 

Meanwhile,the native resolutionto placebootloader?

I can't test this myself, because I don't have a notebook with the intel 5700 around, but I have read reports that it's not working on intel hd graphics.

Someone with an intel 5700 and some basic linux knowledge could confirm this by adding the ID of the 5700 into the 915resolution source code, compile the program, and try to change the vesa table.

Link to comment
Share on other sites

I can't test this myself, because I don't have a notebook with the intel 5700 around, but I have read reports that it's not working on intel hd graphics.

Someone with an intel 5700 and some basic linux knowledge could confirm this by adding the ID of the 5700 into the 915resolution source code, compile the program, and try to change the vesa table.

 

now that I think I remember reading this thing ... Would you like to do this patch?I will try your work!

Link to comment
Share on other sites

Apple has released an update to the MacBook Pro with the problem of black screen icon_wave.gif

 

With the release of OS X Lion, many users began to experience a problem with black screen, with a mid 2010 MacBook Pro 15 ". Apple has finally released an update of about 70 MB, which should fix the annoying problem. The update there are new drivers for video cards and even a new version of OpenCL. And this seems to be the real problem, namely that the OpenCL were in conflict with the passage of a video card to another. The upgrade is available via Software Update or directly from Apple

 

 

http://support.apple.com/kb/DL1469?viewlocale=en_US

 

http://support.apple.com/kb/TS4088

 

http://support.apple.com/downloads/DL1469/en_US/MacBookProVideoUpdate1.0.dmg

 

We already put at the disposal only Intel kext update:

 

http://www.mediafire.com/?cfh99wapq814it6

Link to comment
Share on other sites

Hi iAngelo, thanks for the idea and I will try to dig the new MBP update a little more, though seemed to be another dead horse on my 1st glance at it. ^_^"

 

For the time being, the old fb kext always crashed with a scrambled screen for 4-5 seconds to reboot. We all knew that the controller kext was working, but the fb kext just could not get the contexts out on the "surfaces" due to non correct settings of the output. The settings of the fb kext was settled by another muxer kext, which would not work if there was no real muxer chip on the mobo.

 

Now, we have 2 problems:

 

1. To get the fb surfaces back. This is the so-called connector info editing.

 

2. To disable the switching mechanism of the muxer, which is always called by the power management routines to switch to a video card that we don't have to crash, and eventually caused the sudden black-outs on real MBPs.

 

 

I DO personally think that we can combine the 2 problems in one:

 

 

How about making/patching a FAKE muxer kext that never switch between cards, ignoring the power management requests, constantly select the 5700 as an ouput device, and always providing the correct surface info of the 5700?

 

 

I am sad because I have to learn the AppleNetwork from the very begining till I can really code something. Is there any talent will help to solve the muxer issue?

Link to comment
Share on other sites

So in summary, the things we want to do are:

1) Resolution Patch Bootloader Chameleon

2) Try editing kext: Change info connector

3) Try editing kext: Change muxer kext. Yes, but what this kext?

 

 

------------------------------------------------------------------------------------------------

Meanwhile, add other information such

 

http://www.mediafire.com/?qqbuv6auipxx4ww macboocpro6.2-2011.zip

Link to comment
Share on other sites

You guys know how to code it? If you write it, I will test it.

 

If something world needs is definitely more clueless testers. How helpful can you be by testing something you have no idea how it works? Zero. You are posting to these threads for so long that you could have learn a lot since start but seems it's much more comfortable to wait for someone else to do real work. And no, this is not personal - it goes for all "I will test it guys". If someone can code/change the kext -> he/she most definitely can test it.

 

Soin summary,the things wewant to doare:

1)ResolutionPatchBootloaderChameleon

 

Done that - you can take a look at my github account. It won't work. Remapping BIOS space is not so trivial as on pre-i3/i5/i7 processors. Asked at Intel forum - got zero answers/help.

 

2)Tryeditingkext:Changeinfoconnector

 

There is no connector info in Framebuffer kext for this videocard.

 

3)Tryeditingkext:Changemuxerkext.Yes, butwhatthiskext?

 

I have no idea what this means. There is a big key on the bottom of your keyboard. It is called "space key" - it separates words with invisible delimiter making them easier to read.

Link to comment
Share on other sites

Anyone here knows how to write C or C++ or Intel assembler? Any of those? + knowing at least a bit about how computers work? And want to learn more? Anyone used hexeditor before? Let's see what we have here and if we can work with this. I personally don't have i5 laptop anymore but my gf has one so I will be able to participate if we assemble a team.

Link to comment
Share on other sites

I have no idea what this means. There is a big key on the bottom of your keyboard. It is called "space key" - it separates words with invisible delimiter making them easier to read.

 

I use google translator! Excuse me if it is not clear!

I meant to say: What is the kext that has the task of making the switch of video card intel/nvidia'.This question came to me after I read the post #19 of "Leon Hong"

 

I do not know programming I'm sorry. My intention was to give the initiative,since the situationon the Intel HD was stopped.

Link to comment
Share on other sites

If something world needs is definitely more clueless testers. How helpful can you be by testing something you have no idea how it works? Zero. You are posting to these threads for so long that you could have learn a lot since start but seems it's much more comfortable to wait for someone else to do real work. And no, this is not personal - it goes for all "I will test it guys". If someone can code/change the kext -> he/she most definitely can test it.

 

 

 

Done that - you can take a look at my github account. It won't work. Remapping BIOS space is not so trivial as on pre-i3/i5/i7 processors. Asked at Intel forum - got zero answers/help.

 

 

 

There is no connector info in Framebuffer kext for this videocard.

 

 

 

I have no idea what this means. There is a big key on the bottom of your keyboard. It is called "space key" - it separates words with invisible delimiter making them easier to read.

 

Yes dear oki270. All your words are so correct that none of the 5700 users will accept the truth once they find out the realities. I will give everybody the reverse-engineered C files of the 3 kexts we mentioned above. One will see that the codes are totally HOPELESS after checking them...

 

Inspite of the facts, yes, I am personally sticking to it, and keep my EP121 from being sold... (But I am almost reaching the red-lines!!)

 

archive.zip

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...