Hervé

You don't need any graphics kexts other than the vanilla ones. If the kexts mentioned in post #1 are kexts you added yourself, remove them and return to the original one.

The "installed failed" messages were very common with ML but could usually be ignored as false negative.

Needs 32bit kernel mode for graphics support, then P & C states need enabled for native speedstep & optimum performance.

Looks like you need to turn the laptop's wifi button to On position...

Maybe you should just use the full pack I've posted several months ago. No need to use EDP then.

Seems you're booting in 64bit kernel mode, not in 32bit mode. Reboot and manually enter Chameleon option arch=i386. Once booted, if that indeed fixes the problem, make sure to add that to the Chameleon boot plist. Use Chameleon Wizard to select that option.

Read the documentation available through the EDP menu at top of page..

You need to add the Extra to your USB installer using myHack. Select my own and point to the D830 boot pack you'll have previously downloaded. Please read up the documentation found under EDP menu at top of the page.

Difficult to say, I'm not in front of your D630 and have no visibility of your files. Maybe wrong choices in EDP...

GMA X3100 means you're limited to 32bit-mode SL or Lion. You may try ML with MLPF hack to run a bastardised version of ML in 32bit mode.

There you are. D630i_LoRes_SL_Extra.zip

I'd appreciate if you would share details of the fiddling you did so that we can add that wireless device to the list.

It does, I have one.

You can't "update" from one OS X version to another on a Hackintosh unless you use Clover. Otherwise, it requires a re-installation, but you can re-install over an existing installation.

Wireless will depend on the card you possess. Consult the non-exhaustive wireless card inventory located in R&D section. For audio, the Mavericks pack contains the HDA kexts that you'll probably need to copy to /E/E, followed by myHack->myFix (quick). Basically, read the guides.

Erm, can you rephrase that?

It's been mentioned and explained before... https://osxlatitude.com/index.php?/topic/1824-bluetooth-adapters-latitude-d-series-inspiron-laptops/&do=findComment&comment=22213

A few points on graphics glitches experienced in Yosemite on this system with the GeForce 9800GT: even though Bronya's 10.10 RC2.1 sorts out corruption of desktop icons, it causes very buggy behaviour of Safari and it does not support Duran Keeleys's fixes for AppStore issue (no contents display in app). Same goes with RC3. As such, it's better to revert to Bronya RC1 and apply Duran's AppStore + LaunchPad fixes Edit 11Mar2015: Obsolete now use attached patched IOGraphicsFamily kext to avoid final boot screen graphics corruption In all cases, rebuild cache before reboot: sudo chmod -R 755 /S/L/E sudo chown -R 0:0 /S/L/E sudo touch /S/L/E sudo kextcache -Boot -U / Bronya_10.10_RC1.zip IOGraphicsFamily.kext.zip

As stated many times before, don't use EDP, use the packs I've posted. Full stop.

Then you need to base your CellPhoneHelper patch on an existing Gobi/Qualcomm entry. From memory, there aren't that many in the Info plist. You may also look for other devices that could be based on that chipset.

Well, what chip vendor did you use? What's the chip used on that card? Do not confuse programmed PCI ids of WWAN modules with real identity of the underlying hardware... The real hardware determines the card model to select for subsequent kext patching. You can't just pick any existing model, change the PCI ids and expect the WWAN module to work.

No, not really. A fresh install is a fresh install, regardless of the target HDD. The current one is GUID partitioned, i.e. no MBR patch involved? I'll try a fresh install of 10.6(.0) myself later on and will give you the complete pack that will not require any subsequent EDP involvement.

And you're starting from 10.6(.0), right?

Do you have the LoRes or the HiRes LCD model?

Then your /Extra folder is incorrect. Can you post it up? You've downloaded & used the correct pack, right? Try and boot with -f -v flags and tell us where system KPs.