Jump to content

Search the Community: Showing results for tags 'intel hd graphics'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 10 results

  1. georges valch

    DSDT Request, help please!

    Hello I hope someone will help me with this: I'm totally noob about programming and this kind of stuff. On the other side I'm passionate about hackintosh. I have a Dell Vostro 1540, mobo is hm57, proc core i5 arrandale, ddr3, with intel hd graphics. In dual boot win 8.1 and mac os 10.9, I really need a patched dsdt to get graphic resolution (cause, strange, i have not qe but ci - translucent menu bar, but no 1366x768 res). Without nullpowermanagement at chameleon boot i get kp. I attach here my dsdt extracted in windows with aida64, i really hope that some1 will help me fix it and patch it properly. Thanks in advance. dsdt.zip
  2. Hey everyone! First post here. I've been following this website for quite some time now, only joined recently. I am a fairly experienced Hackintosh user, but this time I've seem to have run into an unusual problem. I am trying to get Mavericks 10.9.1 to install. (that is the version I downloaded on my real Mac, and that is what I use to create the installer). Intel HD4000 Graphics does not seem to work at all. I've tried tons of stuff, but I can't get it to work. When I remove AppleIntelFrameBufferCapri, it does boot with additional flags, but I have no acceleration. When I put it back, it refuses to boot, getting stuck at [iOBluetoothHCIController] -- Connected to transport successfully -- I think, it finishes booting, but cannot load graphics, so cannot display anything. But that's just my guess. I'll walk you through all the steps that I took, along with everything that I have tried so far, without results 1. Created installer disk manually, and also tried using MacPwn By Niresh. 2. Applied MBR Patch, for dual booting with Windows. 3. Could get to the installer without using any boot flags. 4. Installed OS X on an MBR partition. 5. After installation, I cannot get to the OS directly, I enter Safe Mode using flags: -v -x GraphicsEnabler=No IGPEnabler=No , and finish the setup successfully. 6. I install FakeSMC, NullCPUPowerManagement (to avoid a KP that occurs if I don't), Ethernet, Audio drivers etc. 7. I apply a MacBookPro 9,1 SMBIOS. So far, I haven't touched graphics at all. 7. I try to boot into OS X, fail. When I try to reboot into safe mode, everything is working except graphics. Now, I have been told that Intel HD Graphics works out of the box with Mavericks, but in my case, it just doesn't. I've tried using a DSDT (which I don't know much about), but that didn't make a difference, so I removed it. My ig-platform-id is 0x01660009, as told by 'About This Mac'. I've tried manually injecting this ID, along with others, using the Chameleon boot flags, and also by adding it to com.chameleon.boot.plist I've tried patching my AppleIntelFrameBufferCapri.kext in 2 ways: 1. I opened the AppleIntelFrameBufferCapri executable in /S/L/E/AppleIntelFrameBufferCapri.kext/Contents/MacOS using HexFiend, and changed the hex values. I used this guide: OSXLatitude. This was a total disaster, all I got was a black screen, and I didn't really understand what I was doing, so it made me uncomfortable. The next one was much more promising. 2. I opened the Info.plist inside AppleIntelFrameBufferCapri and added my platform-id in IOPCIPrimaryMatch, and injected 0x01660009 using Chameleon. With some luck, I was able to boot into the installation without safe mode. But graphics were laggy, of course, because of no acceleration. I also tried removing all AppleIntel* , ATI* , And GeForce* Kexts from the /S/L/E/ folder, and that allowed me to boot, but again, no acceleration, which is kind of obvious, because I removed all kexts. Also, in 'About this Mac', it shows me that I have Intel HD 4000 Graphics with 64Mb sometimes, and when I remove all the above kexts, it shows me Display 5Mb (No surprise there). I also rebuild my cache etc. using KextUtility every time I make changes to the /S/L/E folder. For now, I have UseKernelCache=No to avoid any problems. If Graphics works, I'll add it to com.chameleon.boot.plist I read somewhere that I needed to disable VT-d to make it work, but I checked and my processor does not support it, so that's not an issue. So, ultimately, I am stuck now because everything works except Graphics, and I can't really use it without QE/CI because of the flashing lines. Can anyone please help me out here? I've been at it for days now, and I can't seem to find any solution anywhere that works for me. I was also thinking of downgrading to something like ML, Lion or even SL (sigh), if graphics works, and then upgrade from there? I haven't tried it though. I'm so desperate right now, I can try anything My laptop configuration: Intel Core i7-3630QM @ 2.4GHz (Ivy Bridge) Intel HD 4000 Graphics Nvidia GT 650M w/ 2GB VRAM 16GB DDR3 RAM Can't really provide motherboard information, as it is a custom one by Samsung. My laptop is the Samsung NP550P5C-S05IN. Please ask for more info if required Thanks a lot for any help that you can offer! P.S. I'm re-installing vanilla OS X right now, so whatever fixes you guys tell me do not conflict with stuff I've already tried. You can assume I have a clean installation.
  3. How to Enable Resolution on Intel HD Graphics (0046:8086 and 0042:8086) Background Info: It has been said since the dawn of time: “Ye who build a Hackintosh must select a Graphics Card that ye can find in a real Mac to ensure 100% compatibility.” However, it appears a very rare exception is ye…I mean the infamous Intel HD Graphics. These first-gen integrated Graphics Cards found on Core iXXX processors are the first to use the new I/O design, integrating the Northbridge into the CPU itself. The Intel HD Graphics chips have been used in real Macs before, like the Mid-2010 MacBook Pro. The problem: Every Mac that has the integrated Graphics chip also has a dedicated Graphics Card, like the NVIDIA GeForce GT 330M on the same MacBook Pro model. Therefore, it’s not that Apple didn’t write drivers for the Intel HD Graphics, but their drivers are, well, buggy on PCs, resulting in either a frozen or blank screen once the framebuffer Kext loads. People have worked out a way to enable partial Quartz Extreme in Snow Leopard 10.6.7, but even that is very buggy. Try to launch anything Full Screen, get greeted with a surprise Kernel Panic. There was no hope as to how to get full resolution…until now! Manor had thought he had found a way to enable full resolution on Intel HD Graphics, but what he didn’t realize was that his VESA mode tables in his Video BIOS supported his resolution. Everyone that his “fix” worked for them also had it supported in their Video BIOS. Everyone else likely had the maximum of 1024x768 in their mode tables, and therefore couldn’t work. Since then, people had suggested patching the Video BIOS on the fly with the Resolution module… a module based off of the 915resolution Linux hack that also patches NVIDIA and some ATI cards. However, by itself, it doesn’t do a thing. Yet, a recent patch to the module enables support for the Intel HD Graphics! This isn’t a simple one-for-all compile, however. Why? The patch is full of hacks, and it requires you to insert your DTD, an 18-byte sequence extracted from your EDID, into the source code directly. You need a little bit of programming knowledge, but it’s so trivial that just about anyone with little to no programming knowledge (like me) could patch. So, what do you need to get this patch to work? Requirements: Access to Mountain Lion with XCode installed and network access (to compile Chameleon) Access to Windows Extracted EDID of the computer in question UPDATE: If you want, you can try RemC's module in this post; it should be universal and not require any source code patching on your part. Look at the second post: http://www.insanelym...6/#entry1877529 A flash drive (optional, even an old 256MB flash drive would do) You’ll also need to download these tools: DTD Calculator – http://www.clevertec...roductsfree.htm Attached Resolution source code IMPORTANT UPDATE (4/4/2013): If you plan on enabling QE/CI (see below), don't bother with any form of the resolution module. The patched framebuffer will allow custom resolution without the resolution module. The Resolution module is only needed if you want custom resolution on your boot screen. Otherwise, don't mess with it as it may cause distortions. The guide is below is kept for legacy purposes/for those who want to create their own Resolution Module. How to Extract your EDID: This is pretty self-explanatory in another thread: http://www.insanelym...s/#entry1392033 Go to Solution B. I prefer using the Windows way, but the link to the utility there is dead. Go here: http://www.eldim.fr/...lite-free-tools and click the link that reads “EDID Viewer utility”. Please note, though, and I cannot stress this enough: THIS NEEDS TO BE RUN ON THE COMPUTER WITH INTEL HD GRAPHICS INSIDE. THIS WILL EXTRACT THE EDID VALUE FROM YOUR MONITOR, SO YOU NEED TO RUN IT ON THAT COMPUTER ONLY! (Sorry for shouting, but EDID varies from monitor to monitor, even LCD monitors from the same laptop model with the same max resolution. Using someone else’s EDID is like using someone else’s DSDT.aml file. Thus, run only on your computer with Intel HD Graphics on it.) Save your EDID raw data somewhere, or copy your EDID to your clipboard if you’re using the same computer. Now that you’ve got that saved, you’re ready to go to step 1. Step 1 – “Convert” EDID to DTD: I put the word convert in quotation marks because we really aren’t converting it. All we’re doing is extracting specific 18 bytes from the EDID raw data. Launch DTD Calculator and a text editor. For our purposes, Notepad will do. When you copy the raw data from ELDIM, it’ll look something like this: 0x00 00 FF FF FF FF FF FF 00 30 E4 AC 02 00 00 00 00 0x10 00 14 01 03 80 22 13 78 0A C1 25 9D 5F 5B 9B 27 0x20 19 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 0x30 01 01 01 01 01 01 12 1B 56 78 50 00 0E 30 20 20 0x40 24 00 58 C2 10 00 00 19 00 00 00 00 00 00 00 00 0x50 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 00 4C 0x60 47 20 44 69 73 70 6C 61 79 0A 20 20 00 00 00 FE 0x70 00 4C 50 31 35 36 57 48 32 2D 54 4C 51 42 00 C1 You need to have the raw hex data in a single line with only a space to separate them. Using mine, it then should read like this: 00 FF FF FF FF FF FF 00 30 E4 AC 02 00 00 00 00 00 14 01 03 80 22 13 78 0A C1 25 9D 5F 5B 9B 27 19 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 12 1B 56 78 50 00 0E 30 20 20 24 00 58 C2 10 00 00 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 00 4C 47 20 44 69 73 70 6C 61 79 0A 20 20 00 00 00 FE 00 4C 50 31 35 36 57 48 32 2D 54 4C 51 42 00 C1 In DTD calculator, click the Interpret EDID tab, and paste the resulting string in there. And then click Interpret EDID. It should say the DTD on the bottom right. Double click it. You may get a warning that reads “Entered DTD and Generated DTD don’t match”. Ignore it. To make sure you’ve got it right, or if there is more than one, the right should have a value under H Active Pixels and V Active Lines. These values should be your resolution. Now click the Calculation tab. On the bottom you’ll see the calculated DTD. Click in the text box. Press Ctrl+A to select the text and Ctrl+C to copy it to the clipboard. This is the DTD. Here is my DTD as an example: 12 1B 56 78 50 00 0E 30 20 20 24 00 58 C2 10 00 00 18 Paste it into a notepad window and save it as a text document. Make sure you’ll be able to access this on the machine where you’ll be compiling Chameleon. Speaking of which, we now need to move onto the next step, which happens to be compiling Chameleon. Step 2: Compile Chameleon with Modified Resolution Code Just like its mother, 915resolution, the Resolution module will modify our VBIOS on the fly to allow us to select a different resolution from the VESA tables. Therefore, before we compile, we need to modify the code. Thankfully (with many thanks to InsanelyMac User and Chameleon developer orlian, as well as Chameleon developer dmazar), we can patch use already modified code. However, we still need to replace the present DTD with ours. Remember, as this is from EDID, it will vary from monitor to monitor. But first, we need to download and clean up Chameleon’s source code. To do so, download XCode on Mountain Lion, and install command line tools. You can use an already existing hackintosh with internet, a real Mac, or, like me, use a VMware virtual machine. Once you have XCode installed, open a terminal window (don’t freak out if you’ve never used command line before; these commands are safe) and type the following commands: mkdir chameleon-imod cd chameleon-imod svn co http://forge.voodooprojects.org/svn/chameleon/trunk/ cd trunk make clean If all goes well, there should be a folder called “chameleon-imod” in your home folder. In there, should be only one folder called trunk. Inside that folder should be all sorts of file, including an XCode project called Chameleon. Navigate further into i386 > modules. This contains the source code for the individual Chameleon modules. Delete the folder called Resolution and empty the trash. Then, replace it with the attached Resolution source code. Resolution.zip Now, in the Resolution folder, open the file called 915resolution.c. This will open an XCode Window and navigate to line 32. The code should be: map = open_vbios(CT_UNKNOWN); // if(map) { unlock_vbios(map); char* bytes = (char *)VBIOS_START; int patchlocation = 0x0254; verbose("Addr: %X Before patch: %x - ", patchlocation, bytes[patchlocation] ); bytes[patchlocation] = 0x8A; verbose("after patch: %x \n", bytes[patchlocation++] ); bytes[patchlocation++] = 0x25; bytes[patchlocation++] = 0xA0; bytes[patchlocation++] = 0x20; bytes[patchlocation++] = 0x51; bytes[patchlocation++] = 0x84; bytes[patchlocation++] = 0x1A; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0x40; bytes[patchlocation++] = 0x36; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0xBE; bytes[patchlocation++] = 0x10; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x1E; This is the portion we need to modify to match our DTD. Every byte XX in our DTD is read by the source code as bytes[patchlocation++] = 0xXX; Therefore, in my DTD code, 0x8A becomes 0x12, 0x25 becomes 0x1B, 0xA0 becomes 0x56, etc. Once that’s modified, save it and exit XCode. We’re now ready to compile Chameleon. Navigate back to the terminal window and type: make I know it’s a pain we have to compile all of Chameleon when we only need to compile the resolution module, but we can’t just type make in the directory of the resolution module source code; I’ve tried it and it doesn’t do anything. Once that’s taken care of, navigate back up to the trunk directory, and in the sym folder, should be the i386 folder of Chameleon binaries. If you’re going to do step three, copy this back to a Windows computer. I recommend compressing it into a zip file first if you do that. If not, go straight to step 4. Why am I suggesting you don’t have to do step 3? Step 3: Install Chameleon to a test flash drive (optional) This is not required, but I do recommend you do this. Why? There isn’t any reason to believe you can’t simply copy the resulting Resolution.dylib to /Extra/modules/ folder. However, if something went wrong and the computer can’t boot due to wrong resolution/poor timings, the resolution module is only present on the Flash Drive and you can simply reboot off of the hard drive without issues and try compiling again. If you skip step 3, though, you’re stuck until you boot without the module. Therefore, I recommend you install Chameleon to the flash drive for testing purposes. Once you go into Windows, I’ll be showing you a somewhat new way to install Chameleon using Clover’s Win32 tools. Download the package called Win_USBTools-Fat32_Clover_v2_rL954.zip from here: http://www.osx86.net..._efi_tools.html Extract the archive inside there called USBTools-Boot1f32.zip. Be sure to back up everything on your flash drive that you need. We’re going to format it with the tool HPUSBFW.EXE. Run it as administrator, select your flash drive, and tick quick format. Make sure it’s set to format it to FAT32. Click start. Confirm you want to continue and let it do its thing. Once that’s done, and this is important, unplug it (don’t use safely remove hardware), and plug it back in. Next, open a command prompt in the extracted directory as administrator, and type: BootUSB.bat X: Where X is the drive letter of your flash drive. If it completes without errors, do the same replug method as before. Finally, extract our compiled binaries. Copy the file “boot” to the root directory of the flash drive and create an Extra folder. If you need to copy any contents from your own Extra folder (especially true if FakeSMC.kext is inside /Extra/Extensions and not /System/Library/Extensions), do so now. However, be sure to run create a modules folder inside the Extra folder and copy “Resolution.dylib” in that modules folder. Step 3a: Testing Once that’s done, reboot off of the flash drive. If there was a theme inside your Extra folder, the VBIOS patch should be noticeable from the GUI. If there isn’t a theme installed, or the resolution still appears form the GUI as 1024x768, type at the boot prompt “?video” (without quotes) to make sure that the resolution is listed in the VBIOS. If it isn’t listed there, something went wrong. It should patch an already present resolution. In my case, it was 800x600. If your resolution is listed, try typing “Graphics Mode”=”XxYx32” (WITH Quotes, where X and Y are your resolution values, i.e. 1366x768x32) with any other boot flags you need to successfully boot OS X. If all goes well, you should see full resolution. If something looks funny, but the resolution is correct, then the timings are wrong. Make sure that the DTD was copied correctly in step 2 and try compiling again. If, however, it isn’t listed, boot using the flags “-v Wait=Yes” (without quotes), and before it loads OS X, you’ll see a screen with all startup logs by Chameleon. Scroll down (With theme/GUI, use arrow keys, without theme, space bar to go to next page, p to go to previous page) to where it says “Resolution.dylib by Unknown loaded”. This is the log of Chameleon loading the resolution module. If it shows any errors, take a screenshot of the log and feel free to upload an image here. If you’ve got your full resolution within Mac OS X, you’re ready to install the Resolution module to your Chameleon installation. Step 4: Install the Resolution Module to your existing Chameleon/OS X installation Copy the file Resolution.dylib from your flash drive (or your compiled binary extracted from the zip folder) to /Extra/modules. If there isn’t a “modules” folder in the /Extra folder, create it. Also, be sure to modify org.chameleon.Boot.plist to have these lines in: <key>Graphics Mode</key> <string>1366x768x32</string> Of course, be sure to change the resolution to match your own if it’s different. Once that’s done, reboot and you’ll have your resolution in OS X. If something goes wrong, use the same steps in step 3a to debug the error. Step 5: Enabling Acceleration in Mac OS X Mountain Lion TBD. UPDATE (2/5/2013): Mountain Lion now is capable of enabling Core Image on our Graphics Card. Still no Quartz Extreme, but if you try it out, check out Part 2 in this post: http://www.insanelym...s/#entry1885544 Thanks goes to GhostRaider for the guide, and Mehdymehdy for his discovery! MAJOR UPDATE (3/10/2013): We have made history: a patch for the Mountain Lion Framebuffer was made, and it works now on our machine. Look at this thread: http://www.insanelym...-fixed-sl-1068/ and this post: http://www.insanelym...20#entry1895588 Special thanks to verteks and warraisraw for their discoveries!! However, if you don’t have a problem using an older version of OS X, follow these guides to enable partial QE/CI in Snow Leopard: http://www.insanelym...0/#entry1504066 http://www.insanelym...d/#entry1827443 And that’s it! I hope this guide has been of use to you, and that you’ll be able to use your Intel HD Graphics once and for all! Special Thanks To: orlian dmazar slice and last, but certianly not least, everyone who helped contribute to this VoodooLabs thread: http://forum.voodoop...4.msg13045.html
  4. Salve a tutti! Ho Lion su USB (via [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]) e sono pronto a installarlo ma, quando arrivo faccio partire l'installer, riesco a vedere solamente il logo della Apple e l'immagine di caricamento e se aspetto 10 minuti ca. arriva un bel kernel panic. Ho provato quasi ogni tipo di boot flag. So benissimo che è un incompatibilità della Intel HD Graphics ma ho visto molte persone che l'hanno installato lo stesso. Che faccio? Le specifiche sono nella firma. Grazie in anticipo
  5. Hey everyone, I have recently got hold of a T410 laptop for christmas, of which is the Intel HD Graphics version. It has 8GB of RAM and is currently running Windows 7 and requires an old (disallowed to say what bootloader disc to be inside) in order to boot to an install of Snow Leopard I have made. The first thing I did when I got my laptop was install Mavericks using the boot flag: GraphicsEnabler=yes However, I never really knew what to do after the install as it was my first time installing Mac successfully. What I mean by I didn't know what to do, is that it would simply not boot after install. I now know that there are a few Kexts scattered here and there throughout the forums, some contradicting others saying first generation HD Graphics are not supported, whilst others say they are and it has been very confusing. A common error I get whenever booting any kind of installation or even my install of Snow Leopard (which runs fine) is that is says There is an error starting this computer, pausing 5 seconds. Not sure if this means anything, As of now, I can not install Mavericks anymore, not even through the Niresh distro I used to begin with. Some of the time in the verbose mode, there is often an error saying that certain playlists are not found either which can also lead me to believe I need to add some kind of modified version or extra files. One last thing I want to note is that I would like it if somebody could maybe compile me a zip or gather some useful resources such as Playlist files, kexts, and other things that may help me get Mavericks (or even Yosemite now) onto my T410. I have tried all installers, such as Yosemite (through transmac as a distro), I have tried Mavericks (Niresh Distro again), and I have even tried downloading a non-distro and installing it to USB through myHack on Snow Leapoard, and there has been no luck. Thanks for reading this and I hope that maybe somebody can help me get a stable OSX on my Laptop. Forgot to mention another confusion: I don't know how to inject kexts into the USB installer itself, and whether you should do it before or after installation of OSX.
  6. Hey there im having an issue with my Hackintosh here is the info this is my macs system report info: Intel HD Graphics 4400: Chipset Model: Intel HD Graphics 4400 Type: GPU Bus: Built-In VRAM (Total): 3 MB VRAM (Dynamic, Max): 10 Vendor: Intel (0x8086) Device ID: 0x041e Revision ID: 0x0006 Displays: Display: Resolution: 1024 x 768 Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes As you can tell is my VRAM is 3MB i used Niresh to install yosemite and have a intel i3 3.39GHZ Haswell processor in a HP Pavilion 500-223W
  7. Hey every body ... i know the title is weird but really thats true !! this model is forgotten among all this laptops here specially the hp i know it is not the most power-full laptop but at least u can buy it for a great price and its compatible with OS X ... actually EliteBooks & ProBooks are very compatible with OS X.. any how i am seeking help for creating a DSDT for this model ( and later to patch audio for it) i hear you you will tell me there is already a DSDT for this model...!!! but no the real thing is there isn't... the one available DSDT is for (NVS100) graphics where i have (Intel HD Graphics). am here talking about this : Intel Core i5 520M Intel HD graphics.. IDT Audio or HDA Device id= 111d7603 I wanted to make a DSDT for this model and i started but i was forced to quit because DSDT creating needs PATCH as i found in the guides ... and there is no Patch available for this model at all ... and i am looking forward setting mavericks on it but when i solve all problems on 10.8.3 so please every body help me to create that DSDT as i experienced CMOS reset and read that some functions might brick the laptop i am all listening and i have the tools Appreciated thank you
  8. Hello! I have the forever-spinning wheel on my laptop. I have an Asus K52F, specifications: Intel i3 370M @2.4GHz w/Intel HD Graphics (1st Generation, Q3-2010) 8GB DDR3 1066MHz RAM Mac OS 10.8.2 Everything works fine, sound, WiFi, etc, even Native resolution. I just can't get QE/CI working, at all. Steps I've done: 1) Delete all Graphics-related kexts 2) Download 10.8.2 QECI (attached) 3) Unzip, install with Kext Wizard 4) Shutdown 5) Boot with flags "-f -v UseKernelCache=No GraphicsEnabler=No" [and without -f] 6) Computer won't boot, wheel spinning EDIT: I used MacBookPro6,2 i5 520M SMBios, and it booted before installing the Graphical KEXTs EDIT 2: Tried with Natit.kext - nothing changed. Any help is appreciated! Thank you. 3792-Intel HD Graphics 10.8.2 QECI.zip
  9. Hello. I am trying to get my Intel HD Graphics 3000 to work with full acceleration support and full resolution. Currently I am stuck with 1024x768 when the display is capable of 1600x900. I am running Sierra 10.12.3 and I am unable to change the SMBios from iMac14,2 Specifications are as follows: Make: Lenovo Model: ThinkPad T520 CPU: Intel Core i5 2540M 2.4GHz GPU: nVidia NVS 4200M + Intel HD Graphics 3000 (nVidia disabled) RAM: 8GB DDR3 HDD: 320GB Seagate HDD I am fairly new to Hackintosh/Hackbooks and have never successfully hackintoshed a device. Any help would be greatly appreciated. If any extra information is required I can provide.
  10. Ciao a tutti carissimi colleghi di notti insonne!! Vi scrivo per chiedervi un piacerino: premettendo che per me la parte più divertente del tutto è la ricerca della soluzione (anche artigianale a volte) mi trovo costretto a chiedervi se qualcuno di voi ha percaso la soluzione all'annoso e nodoso problema della risoluzione video per quanto riguarda la mia scheda video: INTEL HD GRAPHICS IRONLAKE 128 MB. Il mio iatkos l2 è fantastico e funziona benissimo. Ci sono solo queste tre cosine che non riesco proprio a far andare, nonostante abbia rovesciato più e più volte la rete per trovare soluzioni: - risoluzione fissa a 1240 x 768 - wifi non riconosciuto - trackpad non riconosciuto per quanto riguarda il primo ho già provveduto ad installare i kext che mi consentono di vedere il nome e la vram giusti in informazioni di sistema, ma non il monitor. per il wifi non so più dove sbattere la testa, ma mi pare di aver capito che posso mettermi il cuore in pace. per il trackpad ho provveduto ad installare i kext appleacpips2nub e appleps2controller, ma nada. In realtà cosa che mi preme più di tutte e riuscire a sfruttare appieno la mia già miserrima scheda video! Vi ringrazio mille e ancora cento anticipatamente e spero vivamente che possiate aiutarmi nella mia ricerca della felicità, sempre conscio del fatto che una volta trovata ne cercherò un'altra. Evviva le nuove sfide!! Buonaserata, Oddo