Hervé

#1 -> only applies to Mavericks 10.9.1->10.9.3, so not of your concern here. #2 -> You may have a syntax error in your SSDT-7.dsl source code somewhere above that line which is reported with an unexpected "}". You need to identify that error and fix it. Could be an error from your part or a result from having "Smart Quotes" enabled in the editor you used. As a general rule, smart quotes/smart dashes are best kept disabled in text editors when doing DSDT/SSDT edits. But it could also be that the version of ACPI you use to recompile the table is not appropriate. From memory, MaciASL supports v4.0 and 5.0, so try and switch to the other one before recompiling. Failing that, you may want to try another DSDT tool such as DSDTEditor. #3 -> Not having SSDT-8 and -9 may not necessarily be a problem.... Did you actually extract your raw tables from BIOS using a tool like Aida64?

I'll bring my E6220 at work to try it out, it's the same family, just smaller 12" version. No problem with the E6440 for sure.

Latest version 9.5 appears to work perfectly in Yosemite and El Capitan.

Folks, just a conclusion word to confirm all has returned to normal; the IP.Board license is renewed, the Copyright removal license is now activated and we can continue our OSXL journey! Many thanks to all of you who donated and helped us get out of the crisis; truly a mark of confidence in the site, its crew, the OSXL philosophy and the Hackintosh community as a whole.

For Hackintosh purposes, there are 3 models of D620 to consider: D620 with Intel GMA950 graphics and 1280x800 LoRes display D620 with Intel GMA950 graphics and 1440x900 HiRes display D620 with nVidia graphics and whatever display Ideally, you'd build a myHack-based installation USB key with our appropriate bootpack. However, this requires access to an existing Hack or Mac, something you may not have. Instead of boot (which we won't support here, it has its own special web site and support team), I'd recommend that you use Nawcom's ModCD with your retail Snow Leopard disk. If it's a DVD, you won't be able to use our bootpack. In that case, what you can do is boot the NawCom ModCD CD/DVD with display set to an external display (and external display only), then proceed to install SL with flags -f -v and option arch=i386. I suspect that, when the OS X installer launches graphical screen, display would revert to the built-in LCD but in a functional way. You would then be able to install SL on your HDD and then proceed in the exact same way to boot your freshly made SL installation. What you could then do is create your myHack-based SL installer with our bootpack, re-install SL altogether but obtain a fully functional Hackintosh this time. http://www.osxlatitude.com/edp/documentation/pre-installation/ https://osxlatitude.com/index.php?/topic/8081-full-packs-for-d620d630-snow-leopard-lion-mountain-lion-mavericks-yosemite/ For pointers, you may refer to my old maiden post on this forum regarding installation of SL on a D430 but the EDP part is no longer applicable as the tool evolved a lot since 2012. https://osxlatitude.com/index.php?/topic/147-dell-latitude-d430-thread/page-14&do=findComment&comment=9243

No SOL computer was ever supported by EDP, no. I don't believe you can run OS X on those new generation types of Celeron. If you could, I'm not sure the integrated Intel HD would be supported; it's not the same as the 1st gen Intel HD of the Arrandale CPU. But, by all means, give it a try, it's the only way to know... EDP is a package used to fine-tune/finalise a basic/minimal OS X installation made with a minimalist bootpack. It's made out of full vanilla installations made by people who bring details of their successful builds to the forum with all used files (drivers, patched BIOS tables, etc.).

CoolBook only worked on Core2Duo CPUs and I think was last supported in Lion. Probably nothing to consider outside native speedStep under Yosemite... Tuning AGPM to throttle the nVidia 8400GS will also help to cool it down (you're obviously not running Yos on a X3100-based model). Lookup the Performance tuning + AGPM tuning thread in R&D forum subsection. The Vostro 1400 is a close relative of the D630/D830 family. https://osxlatitude.com/index.php?/forum/16-other-research/

You can follow the well-known Yosemite USB installer creation + Yosemite installation as detailed in many threads on the forum. You can look up the various Sandy/Ivy Bridge E6xxx guides available here for instance. Obviously, do not use any DSDT or SSDT from an existing pack (they don't apply to your machine and would cause problems), you'll create your own tables in due course.You may simply use a default boot pack with FakeSMC + PS2 controller + NullCPUPM or patched AICPUPM (necessary for Sandy/Ivy Bridge CPUs to avoid Kernel Panic at boot time). For SMBIOS profile, pick-up iMac 13,1 or 13,2 but you may also test with iMac 12,1 or 12,2.

[1002:6759] -> so it would appear to be the Radeon HD 6570 then. That should be natively supported since it is covered by the AMD6000Controller kext: <key>IOPCIMatch</key> <string>0x67681002 0x67701002 0x67791002 0x67601002 0x67611002 0x67501002 0x67581002 0x67591002 0x67401002 0x67411002 0x67451002 0x67381002 0x67391002 0x67201002 0x67221002 0x67181002 0x67191002 0x68401002 0x68411002 0x67041002</string> You may only have to play around with framebuffer personality. If you use Chameleon bootloader, you'll be able to do this from the Chameleon Wizard tool by picking the appropriate frame buffer from the list of ATI config. Refer to RampageDev's blog for details: http://www.rampagedev.com/?page_id=82&page=4

As far as I know, the Radeon HD 6570 is natively supported but you probably have to play around with framebuffer personalities. Can you please post the card device id to be sure of the model? In Linux, use Terminal command lspci -nn; in Windows, go to the Device Manager->Driver tab for the card.

You would assume correctly. There are two things you may want to try: 1) identify your SDHC device in IOReg, then patch your DSDT to pretend it's compatible with OS X's default model (details are available in various E6xxx guides, for instance here). This has low chances of success on an old system such as the E6400 2) use VoodooSDHC kext, patched with your SD card device id (you'll find details in same various E6xxx guides, for instance here). This has higher chances of success on the E6400

Your Sandy Bridge CPU is compatible with any recent OS X versions, the oldest you could run being Lion 10.7. You should be able to install and run Yosemite 10.10.5 without problems and El Capitan 10.11 once it comes out in a few months. Your integrated Intel HD Graphics 2500 is not supported in recent versions of OS X (at least not beyond ML as I understand). You'll therefore have to make sure your discrete add-on Radeon HD is. What exact model is it, can you post the vendor/device id? If your Radeon HD turns out unsupported, you'll have no other choice but replace it by a supported nVidia/AMD model or replace the CPU by a Sandy Bridge with integrated HD3000 or an Ivy Bridge with integrated HD4000...

You can use 10.10.5.

Not if it runs through Optimus technology, which I expect it does. That's not supported on Hackintosh.

Try the various Azul framebuffer layout-id values to get full graphics acceleration. You can find value details at RampageDev's blog in his Intel HD guide. When you specify the ig-layout-id in Clover (or in Chameleon to that effect), bear in mind that you enter the values in reverse order. For instance for ig-layout-id 0x0a260006, you'd enter: 0600260A.

According to Dell's specs, the variants are only on CPU. The E6330 supports Sandy Bridge i3 CPU with HD3000 graphics and Ivyy Bridge i3/i5/i7 with HD4000. The rest is the same. http://www.dell.com/downloads/global/products/latit/dell_latitude_e6330_spec_sheet.pdf

i3, i5 or i7 CPU (not chipset - a chipset includes memory controller, disk controller, etc.), it should make absolutely no difference in terms of installation process if the guides all apply to the exact same laptop. It's the same Intel QM77 chipset and same hardware accessories such as USB controller, LAN card or audio device. Only the SSDT (for CPU power management) is specific to each CPU. Maybe you followed guides for nVidia models. You may follow guides for other Ivy Bridge/HD4000-only laptops of the same family, .i.e. E6230, E6430 or E6530. Only the DSDT and SSDT will differ. You're not very specific regarding the troubles you've met, so difficult to say more until you do.

Of course there will be an alert on this kext signature, that's perfectly normal: the kext is patched to support Sandy/Ivy bridge CPU on the locked-MSR BIOS, therefore it's no longer vanilla! Without this patched kext, you'd need to use NullCPUPM (and obtain no CPU power management at all as a consequence) to avoid KP. However, unrecognized kext signature is not a problem in Yosemite as long as you use the boot option kext-dev-mode=1 and that's already included in the pack I posted. Bottom line is that this has nothing to do with your BOOT error, which is due to an incorrectly installed bootloader. Maybe you are facing the well-know 4K-sector HDD issue, in which case look it up to apply the fix.

You probably need some DSDT patches. Look at Rehabman's repository, he's got patches for LID fixes re: sleep & wake. They work fine and I use them on the E6440. I think I also posted details in my E6440 guide, look it up.

Patched the SNB framebuffer kext for VGA & HDMI. It's the same usual patch as described in Enabling VGA & HDMI on HD3000 thread. Edit - 19/08/2015: revisited the old SNB patch to add DVI output when docking the laptop to docking stations such as E-Port/E-Port plus. This now extends video output to DVI in addition to VGA and HDMI. For reference, patched code is as follows: 01 02 04 00 10 07 00 00 10 07 00 00 // Nb of connectors -> "04" 05 03 00 00 02 00 00 00 30 00 00 00 // Built-in LCD display 02 05 00 00 00 08 00 00 06 00 00 00 // HDMI output port 06 02 00 00 00 04 00 00 09 00 00 00 // VGA output port 04 06 00 00 00 04 00 00 09 00 00 00 // DVI output port located at offset 2B650. 10.11DB6_new-patch_AppleIntelSNBGraphicsFB.kext.zip

You'd also need to remove any sleepimage file in /var/vm.

AR9380 works OOB -> https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/ Ensure Wifi is enabled in BIOS and that wireless On/Off switch is not set to off position.

So far, I've not suggested any ways to fix sleep, I've merely asked you to check hibernation mode... This being said, hibernation must be disabled on a Hackintosh, i.e. you just run plain old sleep; currently it is on (hibernate mode set to 3), hence your trouble. Hibernation mode can be defaulted back by an OS X update. Fix sleep with the following Terminal commands: sudo pmset hibernatemode 0 sudo pmset hibernatefile /dev/null sudo rm -f /var/vm/sleepimage

Up to DB6 and, again, encountered trouble with the cache/prelinked kernel. Basically, FakeSMC kept getting omitted due to unsigned/unverified status. In the end, I had to reboot in single-user mode, load the kext manually and then, result normal boot. Once system was up and running, I was then able to manually fully rebuild the cache/prelinked kernel. 10.11DB6_patched_AppleIntelFramebufferAzul.kext.zip 10.11DB6_patched_AppleIntelHD5000Graphics.kext.zip 10.11DB6_patched_IOGraphicsFamily.kext.zip

What's the current hibernate mode? Check it out with Terminal command: sudo pmset -g You may also check presence of an hibernation file: ls -la /var/vm and, if found, delete it: sudo rm -f /var/vm/sleepimage