Jump to content
InsanelyMac Forum

ebmesnow

Members
  • Content count

    12
  • Joined

  • Last visited

About ebmesnow

  • Rank
    InsanelyMac Protégé
  1. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I tried it, unfortunately it does not work, my laptop had 8 devices on the i2c bus, number 2 being listed as the 'Panel', if you try a read or write to this or indeed most of the devices it gives an IO error. Devices 6 & 7 were listed as DDC and they did accept the read/write without the IO Error but timed out, assume these are for external displays. Looks like Toshiba don't put the hardware in the display for the EDID.
  2. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I have a Toshiba M11 with exactly the same problem as Pentothal. The screen is LVDS but is not sending an EDID out, if you look under the frame buffer in ioreg with IntelHDGraphicsFB loaded no displays are present. I have tried injecting the EDID through DSDT, Natit and monitor overrides, nothing works. Some of the other Intel framebuffers have EDID override code in them, unfortunately although IntelHDGraphicsFB does have the code it is not used, did try to call it by manually altering the code but that just caused a kernel panic. I think Pentothal is correct, for us because EDID is not being sent the Framebuffer can't determine the correct timing and ignores the screen
  3. Intel HD Graphics (0x00468086) QE/CI on Lenovo X201

    iwin32 aapl,os-info is defined in appleintelhdgraphicsfb there are two defined, but I think only one used in the kext as follows 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 In addition there is another one OsInformation Default 30 49 01 01 01 00 08 00 00 00 00 00 00 00 00 00 FF FF FF FF I am not really sure what they do but suspect they only tell what hardware is in use
  4. [FIXED] Intel GMA HD 5700MHD

    Can you attach your DSDT and I will have a look, have you done this before? Some of the DSDT compilations are known to be full of errors before, does not look like anything we have introduced.
  5. [FIXED] Intel GMA HD 5700MHD

    You need to find the Graphics section of your DSDT, probably called GFX0 or IGPU then add this code under it Method (_DSM, 4, NotSerialized) { Store (Package (0x0A) { "hda-gfx", Buffer (0x0A) { "onboard-1" }, "device_type", Buffer (0x08) { "display" }, "model", Buffer (0x12) { "Intel HD Graphics" }, "built-in", Buffer (One) { 0x01 }, "AAPL,os-info", Buffer (0x14) { /* 0000 */ 0x30, 0x49, 0x01, 0x11, 0x01, 0x10, 0x08, 0x00, /* 0008 */ 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0xFF, 0xFF, 0xFF, 0xFF } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } You will also need to add the DTGP method in not already included in your DSDT, this is a fairly common method of injecting stuff, used to trick kexts into think the hardware is something other than it is and used a lot in fixes, if you look at some of the standard hacks in DSDTSE you will see it frequently used.
  6. [FIXED] Intel GMA HD 5700MHD

    No unfortunately only have Lion around these days, bit of a pain to install on my laptop and get running.
  7. [FIXED] Intel GMA HD 5700MHD

    I have been trying to get the 10.7.4 lion kexts to work for a while now. From what I can see the frame buffer is needed as it looks like this does the VRAM allocation and many other things. On mine with only the AppleIntelHDGraphics kext loaded I get the screen scrambled, via screen sharing there are ways I can get it to show the correct Graphics type but I think these are only cosmetic. I can get the Lion frame buffer to load on mine but have to add the following to the graphics card section of the DSDT using the above method in giofrida's post. "AAPL,os-info", Buffer (0x14) { /* 0000 */ 0x30, 0x49, 0x01, 0x11, 0x01, 0x10, 0x08, 0x00, /* 0008 */ 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0xFF, 0xFF, 0xFF, 0xFF }, I can see a section in the kext which looks for this value, without the os-info addition and the frame buffer I get the spinning thingy continually at startup, with the os-info addition I get a grey screen eventually, and a lot more promising entries in the registry when viewed via screen sharing and it shows 768Mb of video memory. When I tried injecting the VRAM size as above this caused me problems, one of the kexts would not load, can't remember which, but with the frame buffer loaded it shows this value anyway. I think the problem I have is it is now not detecting the screen at all to get the size and timing information, display information is blank which without the intel frame buffer shows at least some information even if wrong. I tried many ways to try and inject display EDID information without success. What I did wonder is if the default NDRIV framebuffer on a real Mac gets this information, on our systems with a single graphics card because the Intel frame buffer has grabbed the card, the NDriv framebuffer can't get any information out of the display. I know without the Intel FB the Ndriv FB loads and shows in ioregistryexplorer against the Intel graphics. If this is the case perhaps someone could write a fake ndriv frame buffer that just reads the information, I believe the source code is available for this frame buffer? Hope this helps someone get a little further, unfortunately I have made many changes to my DSDT to get it nearer to a real MacBookPro 6.2 so not sure if there are any other changes that have helped my intel framebuffer kext to load.
  8. Lion DSDT Sleep fix for HP DC7900

    The HP DC7900 bios is a bit limited and does not allow the switching on/off of HPET. However I managed to fix my original DSDT by comparing with what you provided and at least I have working after a fashion. It does go to sleep and wake correctly now except the very first time it goes to sleep it goes through the process of sleep but then wakes immediately before going straight back to sleep again, after that it functions perfectly every time until next re boot, I can live with this extra few seconds. In the end I think it was removing the IRQ from the RTC which I thought I had already done. The kernel panic in MaLd0n's DSDT was nothing to do with the IRQ for HPET which was my first thought. If anyone is interested I have attached my DSDT, I also have an edited plist for voodooHDA as by default this does not work properly with the DC 7900. MaLd0n many thanks for your help, and such a rapid reply. HPDC7900_DSDT.zip
  9. Lion DSDT Sleep fix for HP DC7900

    MaLd0n Many thanks for the very quick reply, unfortunately I got a kernel panic in AppleIntelCPUPowerManagement 'No HPETs available CPU(s) configured incorrectly' However got a little further comparing your DSDT with mine, made some changes on mine and have got sleep working although it still behaves a little strange first time. One difference I see between the two is the IRQ's for HPET I have 4 defined whilst yours has 2 and they are different. I will have a play over next couple of days and see what makes a difference. Thanks again
  10. Lion DSDT Sleep fix for HP DC7900

    Hope someone can help I have a HP DC7900 with an ATI HD5670 GPU successfully running retail Lion the only extra kexts being fakeSMC, VoodooHDA and AppleIntelE1000e. I have made several modifications to the DSDT most important being HPET which stopped the USB ports working. The only remaining item being sleep not working, it goes into half sleep, though fans still running then it will not wake. I did previously have it working, sort of under Snow leopard 10.6.8 using sleepenabler, although the first time it went to sleep it woke immediately, after that it worked perfectly. With Lion I get kernel panics when I use sleepenabler regardless of pmVersion settings. If nothing else hope my DSDT helps someone else getting a HP DC7900 running, you do need to add a supported graphics card though. I have also included the original DSDT extracted from Win7. Many thanks send_me.zip
  11. Day 4 of No luck? Qosmio X505-Q8100X

    Have you tried with the boot option busratio=12 -v busratio=12
  12. What iAtkos should I use?

    Not sure it helps as not exactly the same as yours but I had the same problem with my HP DC7900. The fix in my case was to install a supported graphics card, an ATI HD 5670. I used iAtkos S3 then update to 10.6.7. It was not immediately obvious when running in verbose mode that it was the graphics card, but I figured it would not hurt and certainly improved windows performance.
×