Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About RemC

  • Rank
    InsanelyMac Protégé
  1. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    OK, thanks guys. Good to know it's not me messing something up. I've played around a bit but to no avail. It seems Mac's have had this issue and I've read an old post from bcc9 where it had to do with the order of connectors.
  2. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    Has anyone "Computer sleep" working? I have "Display sleep" working, I can put it in hibernation but when I turn it back on it freezes. The login window is visible and the mouse pointer moves but clicking cancel or typing doesn't do anything. My log file shows the following: 2013-04-08 8:14:25.000 PM kernel[0]: sleep 2013-04-08 8:14:25.000 PM kernel[0]: Wake reason = PWRB 2013-04-08 8:14:25.000 PM kernel[0]: No interval found for . Using 8000000 2013-04-08 8:14:25.000 PM kernel[0]: Previous Sleep Cause: 5 2013-04-08 8:14:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2) 2013-04-08 8:14:25.028 PM loginwindow[41]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check 2013-04-08 8:14:25.000 PM kernel[0]: [0xffffff8008be1000](0)/(5) Device not responding 2013-04-08 8:14:25.000 PM kernel[0]: IONetworkController::enable 2013-04-08 8:14:26.438 PM WindowServer[84]: handle_will_sleep_auth_and_shield_windows: no lock state data 2013-04-08 8:14:28.062 PM configd[18]: network changed: v4(en1-: DNS- Proxy- SMB 2013-04-08 8:14:28.000 PM kernel[0]: USBMSC Identifier (non-unique): 20090516388200000 0xbda 0x138 0x3882 2013-04-08 8:14:31.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x8c27 on MAIN ring: called from 2013-04-08 8:14:31.000 PM kernel[0]: timestamp = 0x8c26 2013-04-08 8:14:31.000 PM kernel[0]: **** Debug info for apparent hang in MAIN graphics engine **** 2013-04-08 8:14:31.000 PM kernel[0]: ring head = 0x000000a0, wrap count = 0x 0 2013-04-08 8:14:31.000 PM kernel[0]: ring tail = 0x00000a38 ring control = 0x00003001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x004 4KB pages It seems a problem with the graphics engine. Is anyone else experiencing this? Does anyone have wake from sleep working?
  3. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    Hey GhostRaider! I've been a bit busy since the resolution patch. I was very excited when I learned about the progress that has been made on the QE/CI front. I've got it working on my Acer Aspire 5742z with a Intel P6100 processor (10.8.3). The dimming/contrast is working except for my function keys, will have to look at that later. I couldn't figure out why some people need Natit.kext and others don't. I'm pretty sure it has to do with the SMBios. As long as you choose SMBios 6.1 you don't need Natit.kext. For all other SMBios choices you need Natit to do the injection using AAPL,os-info (or do it in your DSDT). Maybe you can add this to the guide if you think so too. Cheers for writing it and keeping it up-to-date!
  4. Yes it is the Flurry screensaver, but without natit.kext I just get a white screen... I've been reading the https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CC4QFjAA&url=http%3A%2F%2Fwww.insanelymac.com%2Fforum%2Ftopic%2F284096-intel-hd-graphics-0x00468086-qeci-on-lenovo-x201%2F&ei=As3wUMTkOIWFiALNrIDwCw&usg=AFQjCNFot9OVtIGrx7FTFfN8CqOMcDyZRQ&bvm=bv.1357700187,d.cGE topic and it looks like it should be possible without to much effort. Some DSDT editing at least it seems.
  5. I don't know much about the AppleIntelHDGraphics kexts (or kexts in general), except for that I have to delete them to make my system work :-) At the moment I'm using natit.kext which at least makes my screensaver work and probably some other stuff. Definitely not hardware accelerated. Natit/Titan are not drivers and only written to enable NVIDIA and ATI cards by manipulating the registry. It seems the project dates from 2006 but no development has been done since? It might be possible to add support for INTEL cards, the fact that my screensaver is working with it indicates that at least something can be achieved! Any thoughts?
  6. Hi Pentothal, Thanks for all the information, couldn't have asked for more! I'm glad you ran the read-edid utility on Linux because this shows that your monitor and video card combination supports the DDC2 protocol, but somehow fails to execute properly (hardware bug in the implementation of DDC2 in either the monitor or the video card??). It looks like it won't be possible in your case to use the EDID in the Resolution module, so I probably use the values from the "Graphics Mode" in that case. I'm still not sure how Windows got that EDID in the registry, it might be that the graphics driver has generated it instead of retrieved it from the monitor. At least I now know this is a possible scenario and will try to work around it when I detect it. Thanks for all the testing, I'm busy the next few days but hopefully can start patching things up next week. RemC
  7. Thanks for that! All the zero's confirm that the EDID is not being read. The question now is why? Your systems might not support VBE/DDC, I will have to put some checks in place to determine that and once done ask you one more time (hopefully...) to test something for me. For now could you please answer the following: - When choosing Mac OS X in the bootloader and pressing the arrow down key, a menu pops up...if you choose Video Info, what does the first line say (VBE...?). - How did you manage to get your EDID? - You said you're using Win 7, do you have linux as well by any chance or a bootable DVD/USB with Ubuntu or something. If so would you mind running the following and posting the output: $> sudo apt-get update && sudo apt-get install read-edid $> sudo get-edid | parse-edid Thanks a lot!
  8. Hi Pentothal, Your EDID checksum is fine. It looks like the code that retrieves your EDID is not working in your case and as a result continues with an empty EDID, which is of course is not working. I've added another Resolution.dylib, I'd appreciate it if you could try it and post me the debug info (should still give you full resolution, but additional verbosity should help me pinpoint the problem). Thanks, RemC Resolution_1.tar.gz
  9. Great! The EDID checksum failed as I suspected causing it to fall back to a default 1024x768x32 resolution. Something else to look into :-) I should be able to debug it with the EDID you've provided, cheers. I'll come up with an improved Resolution.dylib at some point, just familiarizing myself with the code at the moment and then start improving it. In the meanwhile you've got full resolution!
  10. I could see from your DTD that is is indeed 1366x768. I think I know where the problem must be so I've added some debug information to the attached Resolution.dylib. I also hardcoded the 1366x768x32, so it should also give you full resolution (still does for me)! Please try and paste the bdmesg part from Resolution.dylib that can help me fix it. Others: Don't try this... Resolution.tar.gz
  11. Hi Pentothal, I'm trying to come up with a more stable patch. The bit of code that reads your EDID is coming up with the 1024x768x32. A few questions: Can you post your full EDID? What is the resolution you expect? What hardware are you using?
  12. Nice one! What you've got is not really a bug (and it's also not coming from that bit of code I've added). Your BIOS Type doesn't seem to be recognized and as a result the set_mode function is not doing anything in your case, hence the not patched message. I suspect orlian has a similar scenario and commented the set_mode function out in his 915resolution.c. In my case my BIOS Type is detected as BT_1 and without the set_mode function it won't work for me.
  13. Ah yeah I totally missed your Resolution.zip attachment...my bad! Let me know if the above works for you and hopefully we can come up with some more stable patch that works for all Intel HD Graphics GPU's. It would be great to have some documentation on the GMA Video Bios but that seems difficult to get.
  14. Thanks for the detailed guide. I started converting my Acer Aspire 5742Z into a hackintosh last week. It contains an Intel P6100 processor (Arrandale) with integrated Intel HD Graphics GPU (Ironlake). I have been reading a lot on the different forums and found out about the recent development in this thread: http://forum.voodoop...topic,2754.html Using orlian's code and some changes I now have my native 1366x768 resolution in ML instead of the 1024x768, finally! The code you've posted above is for most people probably not enough, because their video bios won't be unlocked. Orlian has hacked in some code to do that and then it works. However instead of getting your EDID through Windows or even Linux is annoying and unnecessary because the Resolution module already has code built-in to do just that! I have changed the code posted above with the following code that extracts the first valid DTD from the EDID and use that to patch the video bios. vbios_map * map; map = open_vbios(CT_UNKNOWN); if(map) { unlock_vbios(map); char* edidInfo = readEDID(); struct EDID* edid = (struct EDID*)edidInfo; unsigned char* block = (unsigned char*)edid + DETAILED_TIMING_DESCRIPTIONS_START; for (int i = 0; i < 4; i++, block += DETAILED_TIMING_DESCRIPTION_SIZE) { if ((block[0] != 0x00) || (block[1] != 0x00) || (block[2] != 0x00) || (block[4] != 0x00)) break; } memcpy((char*)(VBIOS_START + 0x254), block, DETAILED_TIMING_DESCRIPTION_SIZE); free(edidInfo); set_mode(map, x, y, bp, 0, 0); relock_vbios(map); close_vbios(map); } It is all a bit hacky but hopefully this works for most of us. I haven't been able to find any information about the GMA video bios, so I have hardcoded the magic 0x254 offset that orlian uses. Possibly map->mode_table - 0x14 is a better alternative for VBIOS_START + 0x254 but that's just a guess. It works for me but it might not for someone else. Also, this code could be improved for EDID's with multiple valid DTD's. In that case the resolution should be decoded and the DTD with the highest should be used. I read that this doesn't happen often though. I have attached a tar ball with my Resolution.dylib so people don't have to do all the above but can simply copy it into /Extra/Modules and have native resolution. It also contains my 915resolution.h and 915resolution.c they are the same as orlian's with the above fix applied. resolution_patch.tar.gz