Hervé

Build 14D131 = Yosemite 10.10.3. You must therefore use kernel 10.10.3, not 10.10.0/10.10.1. As I said, forget about Yosemite DP... The guide I linked you to for installing Yosesmite on the D630n refers to Yosemite DP package because of the time at which it was written. Use your downloaded 10.10.3 app obviously. In other words, when you see the reference to Yos DP app at the beginning of there guide, use your 10.10.3 installation package instead. I recommend that you use only the full pack I uploaded, that's guaranteed to work with my guide. Due to persisting problems, I've stopped using EDP and the published boot packs.

You can avoid using the NullCPUPowerManagement kext (which should be placed in /S/L/E for Yosemite) if you use the patched AICPUPM kext since you have a SandyBridge CPU. Patched kext is available here, along vanilla and patched kernels. Replace the vanilla kext in /S/L/E (keep a backup somewhere if you want) by the patched version and repair permissions with usual Terminal commands: sudo chmod -R 755 /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions sudo touch /System/Library/Extensions sudo kextcache -Boot -U /

With Chameleon, copy the kernel files to /System/Library/Kernels folder as "kernel" but you may also use the old referencing, i.e. place it at partition's root as "mach_kernel". What you called "DOS screen" is default Chameleon bootloader screen when you have no "Themes" folder in /Extra. You can grab one from any packs I have posted in the past like in the D6xx section or in my guides of the "EDP -> Supported models with Guides" forum subsection for instance.

Follow the guide I had posted here using your own specific Yosemite installation app (not the DP installation app of course). The D630n does not require any patched kernel. Use the vanilla kernels that are available here. The full D630n Yosemite pack is available here. For Chameleon, use an older version such as r2401. It works perfectly.

Less likely to be a kernel issue with an Ivy Bridge than a CPUPM issue; but, as usual, we need to know the system specs...

So, according to that CPU-Z output, your system's specs are as follows: BIOS A18 Intel Q65 chipset Intel Sandy Bridge quad-core i7-2600 3.40GHz (turbo boost up to 3.8GHz) Integrated Intel HD 2000 graphics ATI Radeon HD 5450 PCIe x16 graphics card (or is it a 6450?) 16Go DDR3-1333 Realtek ALC269Q HD audio Intel 82579LM Gigabit Ethernet 1To SATA HDD 1 x RJ45 10 x USB 2.0 ports 1 x DB9 serial port 2 x line-in mini-jack ports 2 x line-out mini-jack ports 1 x VGA output 1 x DP output PS2 keyboard + mouse ports You should get Yosemite up and running with the following: MacPro3,1 SMBIOS IntelE1000eEthernet kext for LAN card specific patched AppleHDA or VoodooHDA+HDADisabler for audio As usual, check default DSDT for PCI0 _UID value and set to 0 if found at 4 (or other) The integrated Intel HD 2000 is unsupported afaik but the Radeon HD 5450 should work OOB though it may require a DSDT patch to inject it properly. The patch should look fairly similar to this (DSDT patch from Jake's 780 pack), knowing that you'll have to specify your own hardware ids (your card was listed as ven id 0x1002 with dev id 0x68F9): Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x0E) { "device-id", Buffer (0x04) { 0xE0, 0x68, 0x00, 0x00 }, "ATY,DeviceID", Buffer (0x02) { 0xE0, 0x68 }, "vendor-id", Buffer (0x04) { 0x02, 0x10, 0x00, 0x00 }, "ATY,VendorID", Buffer (0x02) { 0x02, 0x10 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "@0,AAPL,boot-display", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Look here too. Initially, boot with NullCPUPM, then generate your SSDT specifically for your i7-2600 CPU using the well-know SSDT-generator script. You'll then enjoy full native CPU SpeedStep + Turbo boost.

IM = InsanelyMac By reformat, I mean you right click on the partition and reformat it! Can't describe it better I'm afraid. Then you reboot OS X through your USB installer and reinstall Chameleon.

That may not actually work but you could indeed try that, having booted your Yos partition through your USB installer. Re-install the complete Chameleon package, they're available from IM download area for instance. If that does not work, it's likely that the EFI partition would have to be reformatted/recreated. I think it might be possible to mount it from Windows with DISKPART and reformat it. Normally it's a plain FAT32 partition. Open up a command (DOS) window with administrator's rights run DISKPART identify the partition with LIST PART select the partition with SELECT PART n, where 'n' is the identified EFI partition assign it a letter with ASSIGN LETTER=p, where 'p' is the desired Windows drive letter (use a letter towards the alphabet end such as X, Y or Z) Exit diskpart and return to Windows; you should now see your EFI partition listed among your computer drives/disks. You may then reformat it.

To clarify a few points and, hopefully, explain things a little: Clover and Chameleon are essentially bootloaders: they allow bog standard PCs to boot Apple OS X, something PCs cannot do natively Clover has enhanced features such as on-the-fly patching of kexts and/or BIOS tables myHack is a multi-purpose tool to: create Snow Leopard, Lion, Mountain Lion or Mavericks USB installer from a retail OS X installation app fine-tune the USB installer/OS X installation on the target machine through the use of a bootpack (i.e. the "Extra" folder) install OS X on the target machine in a clever vanilla manner install or maintain kexts, kext cache and/or kext permissions though built-in myFix utility myHack uses/installs the Chameleon bootloader EDP is OSXLatitude post-install fine-tuning utility for supported systems, relying on myHack/myFix for SL, L, ML and Mav OS X versions

What about the patched kext? Did it work for you?

Use the full pack I posted and you won't need EDP for fine-tuning. Could save a lot of hassle as EDP has been troublesome for some time due to ongoing major re-engineering. But it's up to you... There really is no questioning to be had about the ability for the D620 to run OS X these days... You're simply limited to SL with your 32bit CPU.

Yes, but don't worry, no reason for your hair to turn white over this. It's the well-known final boot stage corrupt screen, right before the Yosemite desktop appears. You can live with it or patch IOGraphicsFamily kext to fix it. Try the patched version I posted in my Dell Latitude E6440 guide. Clover may also have an on-the-fly patch for this. The patch is documented in other Hackintosh forums, including IM.

Intel Bluetooth may work reliably if you remove AppleHPET.kext. No guarantee though, so keep a back-up somewhere .

For wireless, please consult the non-exhaustive list of supported/unsupported cards & USB dongles. Jake gave you the link in post #15. If your USB dongle is not in the list, identify the chip, see if it's on the list and/or look for drivers on the manufacturer's site. You know, a bit of basic home work... It's been said and repeated many times: Intel wireless cards are not supported.

The old EDP versions are unlikely to succeed downloading the required files these days. It'd be better to contact Dinesh and ask him to reinstate this model.

Make sure to build your myHack USB installer with your retail SL installation app/package because you did not (myHack screenshot clearly shows 10.6.2). Which version is it by the way? You have to mount the dmg before myHack can use the app. Only retail versions are suitable for installing SL on a Hackintosh, i.e. versions 10.6.0, 10.6.3 and 10.6.8. Non-retail versions do not possess the necessary installation files. This has been indicated on the forum many times in the past and your myHack screenshot clearly showed incorrect SL version + errors with the installation package; you did not pay sufficient attention to that... Your current USB installer is useless. To obtain your legit copy of SL, follow the info posted here. You've seen the BIOS article, but missed the thread about full packs. It's right above it, i.e. here. NB: 1Go of RAM... that's a little short to run OS X, you really should increase that to 2Go minimum. If you can upgrade your CPU to a 64bit Merom T7xxx FSB667 4Mo L2, even better! graphics chip of Intel 945GM chipset is GMA950 http://www.dell.com/downloads/global/products/latit/en/spec_latit_d620_en.pdf

1st of all, Mavericks would be a "downgrade" since it preceded Yosemite. You can "upgrade" an existing installation by doing a fresh installation over the existing one. The new OS will overwrite the existing installation but will retain all applications and user & data files. El Capitan 10.11 is only at beta stage at the moment, so you may want to wait until it's officially released before you install it. I also recommend you make a full back of your existing Yosemite installation (a partition image for instance or a disk clone) before you start anything.

Well, things depend on the partitioning scheme you've used on the HDD. For instance, if it's MBR, you need to apply the MBR patch to install OS X. If GPT/GUID, you're Ok. In terms of format, OS X target partition should always be formatted "Mac OS Extended (journaled)".

Mifune, I appreciate this might be a little difficult, but you need to be specific in terms of the problems you encounter. What makes you say you cannot install on the internal HDD? What error message are you getting, it any at all? One very useful good practice on the E Series is to reset BIOS to default settings and set HDD mode to AHCI before you attempt installing OS X.

This is kind of daft! One hand you say you've installed Snow Leopard on that system and on the other you want to install from Windows because you "don't have MAC". if you have an existing SL installation, then you have a valid base to create a myHack Lion/Mountain Lion/Mavericks or even build a manual Yosemite installer. All you'll need to do then is attempt installation on a separate HDD partition. If you got rid of SL, re-install it.

No obvious reason for the automatic reboot you experience. It most definetelty should be Ok to boot all those OS on your Core2Duo laptop. 'could be something weird with your CPUPM settings but you also said you were using a torrent image, so you never know what you got... It'd be much better to download a legit Mavericks or Yosemite installation package off the AppStore, especially as they cost nothing... For Mavericks, I would suggest to try a myHack-based installation with the default bootpack; it's kind of well-proven on Core2Duo systems.

The device reported in IOReg is 168c/002b, i.e. what I was expecting for an AR5B95 card, but I'm not seeing 168c/0027 at all. Anyway, it should be all ok now with the patch inserted by Jake.

It's probably the line above that erroneous, maybe expecting Arg0 () rather than just Arg0 Furthermore, a Return statement is usually the last one in any part of DSDT code with nohing right immediately after except a closing "}".

There are BIOS tests you could run, but a failed GPU usually gives some seriously distorded/corrupt display and hangs the laptop rather than a plain black screen. If you suspect the nVidia GPU, you can always just bake the mobo into your oven. The process has been described several times on the forum before in the D6xx section. The GPU chip does not totally fail per sé, it's atually a BGA balling issue: http://www.tfixrepairs.com/services/hardware/graphic-card-repairs/ Then the LCD wire/ribbon cable is known to wear as well. This tends to give a blinking or blurred display or missing lines, sometimes a black screen. If you wobble the display panel, it may recover. I've personally experienced such a worn cable on 2 different D6xx models and had to replace the cables. It's wear and tear. These old lappies were very popular and most have endured a good and plentiful life...

Nothing to add, you've done your home work and have pretty good T° for the model.