Sign In
Create Account
Find content
Not Telling
Hi all,
I got in touch with Slice (the guy who made Clover Bootloader and many other stuff for the hackintosh community). I explained him my problem. Basically I told him my laptop panel is not outputting any edid and so the framebuffer cannot work at all. I told him I've done many tests (edid injection with clover, different FBs, device string injections and so on) and I came to the conclusion that the FB is not working in my case because of no edid datas were provided by the laptop panel.
Slice thinks the edid is not the problem. I'm quoting his answer: "......About your issue I may say that EDID is injected but Framebuffer don't find any connected monitor. It is not because of EDID. It is because of other address of I2C/DDC registers which is OEM specific. If someone disassemble the kext AppleIntelHDGraphicsFB and understand where is the register then we can propose a method to correct it."
It looks like we were wrong! If anyone is able to disassemble the kext AppleIntelHDGraphicsFB all people with EDID problems may finally have a working FB.
Maybe Verteks can do that?
With hope
Pentothal
pentothal
In Topic: [GUIDE] 1st Generation Intel HD Graphics QE/CI
02 April 2013 - 11:11 AM
GhostRaider, on 01 April 2013 - 07:55 PM, said:
I see that many people are finally getting QE/CI on their computers with 1st Generation Intel HD Graphics IGPU. Welcome everyone to the Mac family ... I mean hackintosh family. 
Looking at old forum posts, a lot people said it was not possible, and said that it required reverse engineering or a brand new kext. All of this time we only had to edit small values in the framebuffer. Not sure how Vertek was the only person that figured this out unless he had some knowledge of the workings of the FB (Maybe he works for Apple?
lol jk)
The toshiba guys are very unlucky ones. I don't understand how Toshiba is so lazy to integrate the EDID into their display instead of the software doing it. Any progress for you guys?
As for eDP users, do the Intel HD Graphics 3000 and 4000 users use this type of connection or LVDS?
Looking at old forum posts, a lot people said it was not possible, and said that it required reverse engineering or a brand new kext. All of this time we only had to edit small values in the framebuffer. Not sure how Vertek was the only person that figured this out unless he had some knowledge of the workings of the FB (Maybe he works for Apple?
lol jk)The toshiba guys are very unlucky ones. I don't understand how Toshiba is so lazy to integrate the EDID into their display instead of the software doing it. Any progress for you guys?
As for eDP users, do the Intel HD Graphics 3000 and 4000 users use this type of connection or LVDS?
Hi Ghostrider,
no progress for me
. I tried injecting the EDID with Clover but I had no luck whatsoever. Apparently OSX disregards forced EDID injection. It looks like this Toshiba guy here was able to have his internal LCD recognized as internal. He has a HD Graphics 3000 but, via dsdt, he managed to have his LVDS panel fully working (QE/CI) under Lion 10.7.3.http://www.tonymacx8...35-z835-ok.html
Maybe his guide is applicable to Mounatin Lion and to our Intel HD Graphics as well. I'll try later on this week.
Regards
Pentothal
In Topic: AppleIntelHDGraphicsFB fixed (SL 10.6.8)
27 March 2013 - 10:04 PM
stacyk819, on 27 March 2013 - 10:01 PM, said:
Also were you able to have any sucess with EDID override? it seems you cant do it without your edid information
Ooh nevemind I got it thank you ill try it out and report back. were you able to get anything working on your laptop
sorry for asking so many questions but what do I enter for my EDID if I cannot find it
Ooh nevemind I got it thank you ill try it out and report back. were you able to get anything working on your laptop
sorry for asking so many questions but what do I enter for my EDID if I cannot find it
To get you EDID try with windows:
Eldim edid viewer
Phoenix edid something
There are many free programs to get your edid.
In Topic: AppleIntelHDGraphicsFB fixed (SL 10.6.8)
27 March 2013 - 09:56 PM
stacyk819, on 27 March 2013 - 09:48 PM, said:
Thanks for the help. Why would using the different bootloader help?
<key>InjectEDID</key>
<string>Yes</string>
<key>CustomEDID</key>
<data>CUSTOM EDID HERE</data>
In Topic: AppleIntelHDGraphicsFB fixed (SL 10.6.8)
27 March 2013 - 09:38 PM
stacyk819, on 27 March 2013 - 09:22 PM, said:
Hey I got it working with mint live cd (i think the problem was that I was using a 64 bit version ) It appears to be working (outputing EDID info)
get-edid: get-edid version 2.0.0
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0x11100 "Intel®Ironlake Mobile Graphics Chipset Accelerated VGA BIOS"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
parse-edid: EDID checksum passed.
# EDID version 0 revision 0
Section "Monitor"
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
Identifier "@@@:0000"
VendorName "@@@"
ModelName "@@@:0000"
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# DPMS capabilities: Active off:no Suspend:no Standby:no
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
get-edid: get-edid version 2.0.0
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0x11100 "Intel®Ironlake Mobile Graphics Chipset Accelerated VGA BIOS"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
parse-edid: EDID checksum passed.
# EDID version 0 revision 0
Section "Monitor"
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
Identifier "@@@:0000"
VendorName "@@@"
ModelName "@@@:0000"
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# DPMS capabilities: Active off:no Suspend:no Standby:no
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
# Block type: 2:0 3:0
Ok,
thanks for the info. Unfortunately you have my same problem:
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
parse-edid: EDID checksum passed.
Basically your display is not outputting any EDID. Not being able to read any EDID from the hardware OSX cannot pass the info to the framebuffer during boot process. That means the FB doesn't know you have an internal LCD panel. You'll be able to get the EDID from windows registry but that is not a live EDID. The EDID values in the register may have been generated by the graphics drivers or by windows itself.
You can try EDID override following this post:
http://www.insanelym...splay-problems/
or try using CLOVER Bootloader:
http://www.insanelym...2-instructions/
Good luck
Pentothal