Hervé

-f is not necessarily required on 1st boot. A myHack installation does rebuild permissions and cache... Everytime you add a kext to /E/E, you subsequently "install" it through myFix (quick) and reboot. That's it, that's all. You'll find documentation about myHack in the corresponding section of the forum.

Can you please post your /Extra folder? Personally, I've had no issue on any of my Latitude D or E Series, nor even on my desktops. Can't see why it would be different with your M4400. it's always worked OOB on those systems without any specific actions (except a DSDT patch maybe) NB: Wake from keyboard or mouse has never been feasible on any Dell laptops I've hackinstoshed (I've done a few by now). This is more a desktop feature, configurable in BIOS.

Did you install EDP immediately followed by an EDP build for your system or did you just install the EDP package? The build is required before any reboot or your /Extra will be totally messed up... PS: I vouch for my above Extra for a 10.6.8 installation on D620 GMA950 LoRes with BIOS A10 configured as per dedicated forum thread. Your KP might be due to something wrong in /S/L/E.

Did you just install the VoodooHDA kext or did you add the AppleHDADisabler kext too; these 2 go in pair, or Voodoo clashes with AppleHDA, so it's undoubtedly the reason for your KP. No need to re-install -> read our article on removing kexts when KP at boot time!

When you want to install kexts, you have to rebuild permissions and cache. Vanilla kexts are located in /S/L/E. However, myHack makes use of /E/E and combines kexts placed there with those from /S/L/E, rebuilds permissions and cache. This is done with the myFix utility of myHack. As such, place your kexts in /E/E and run myFix (quick). You got wifi to work with "-f" bootflag because that bypasses kernel cache. Once you rebuild it with myHack, you won't need that flag again and boot time will be shorter too.

If you search a little on this forum, you'll find your answer. All pointers were given to you in post #14...

The card just needs to be detected, recognised and installed in Network Pref Pane as 1st LAN interface en0 for AppStore to work. It does not have to actually work. There are plenty of similar cases in the Hackintosh world (like I have on my Precision 670 with its old Intel Pro 1000/MT LAN card). There is a Yukon kext (driver) for slightly different LAN interface models, I suggest you patch it and try it.

Verified to work with BIOS versions A19 and A21 too.

Ok, well I afraid that Yukon 88E8059 LAN interface is unsupported. Do a search on the Net and you'll find out. I understand you might be able to get it detected but that's about it. This means that apps such as AppStore and/or iMessage may never work on your system. Whilst iMessage is probably not too much of a bother, AppStore would be more annoying because you wouldn't be able to easily do software updates. At best, you'd have to download Combo updates and install them through the downloaded .dmg image. For audio, try with the various VoodooHDA 2.7x/2.8.x to begin with. Other than that, no idea. To me, this is linked to your nVidia GPU, so provided that works OOB (and it should), you ought to look into your Sound Pref Pane and check if any audio device is listed. You would then select that nVidia device for output (and input?).

Post us the output of Terminal command lspci -nn (needs lspcidrv.kext. If you don't have it, copy it to /E/E and run myFix (quick) and reboot). That'll give us your full system specs. For your wireless card, there's an entire thread dedicated to that card and a non-exhaustive inventory both in R&D section of this forum. I invite you to browse the forum and use the search facility before posting.

'can't see why it would not boot with good old v4.0 or any unmodified more recent Kozlek's versions. Same goes for whatever version was used on the E6400. I don't think your problem is there. At worst, remove the plugins, keeping only the core FakeSMC kext.

If you're after potential dual boot with an existing Win7 installation, then you may consider MBR of course. Otherwise, for a single OS X installation, head for Apple GUID scheme. If you don't know about MBR or GPT/GUID, read up about those on the Net.

You should repair permissions and rebuild cache manually. Current versions of myHack/myFix will always try to merge /E/E kexts with /S/L/E within my hack.kext, so if you did not install myHack utilities beforehand, you're heading for trouble. You can't just copy the myHack app to your Hack and run myFix.

Guys, myHack does not support Yosemite yet, so don't use it on 10.10! I don't think krzysztofc10 used myHack at all and if he did, he'd have to explain how...

There's on going work with EDP and it's going to last a little. Stick the the pack I've posted, it's fully tuned and provide everything you need without anything else to do, other than possible wireless kexts installation if required. I came to realise I had forgotten the DSDT patch I had made for my own wireless card; it's been deleted so the pack should now be safe to use on any D630 nVidia.

I did not set screen res to 1440x900 in DSDT, I used a pre-made DSDT; can't remember where I got it from. If you meant the Chameleon boot plist, I guess you already know it's just cosmetic for the Apple Logo startup screen and the reason for such resolution is that I use Cham Wizard to manage by boot plists... For the rest, you did not forget the very last lines of the guide, did you?

Correct.

I'd choose "Other" then.

Large Disk Access Mode -> DOS What other settings do you have for that parameter? On another note, the MBR patch of myHack v3.3.1 is buggy, so don't use it. It's probably the reason for your failures. If you have to install on an MBR partition, download an MBR patch from elsewhere on the net (InsanelyMac, HackintoshOSX, etc.), but it'd be better to target GPT/GUID partition.

Ok, so it's a 1st gen Arrandale i3 processor with 1st gen Intel HD graphics. You did not say which SMBIOS profile you used, but I'd say MacBookPro (6,1)/(6,2) will be your closest match. I don't know if you can somehow limit your graphics in BIOS to either the GeForce 310M or the integrated Intel HD because you can't have both working at the same time. That's unsupported on Hackintosh. Also, make sure your HDD mode is set to AHCI, it is usually/often required. Did you use a specific boot pack or just the Generic one? You 1st said you had GeForce 320M graphics, then 310M. Which is it? 320M is based on GT216 chip, i.e. same chip as 330M used in MBP 6,1/6,2 which would pretty much guarantee full graphics acceleration, whereas 310M is based on GT218 chip and some people have recently reported graphics sluggishness with that GPU... NB: I think there are numerous models of R530 (initial ones had Celeron/Pentium/C2D CPUs with GMA4500MHD graphics), so bear in mind that what worked for some may not actually work your particular model.

Can you please post your full and detailed specs? For instance, "Core i3 @2.16GHz" is insufficient, we need to know the exact model to identify CPU generation, it's important as it may require to use a patched kernel.

Correct. And use the provided HWMonitor app if you want to monitor T° and CPU speed stepping.

There you are: fully tuned up Lion pack for D630 X3100 LoRes. Needs only any wireless card driver that may be required. Adjust DSDT table if necessary as Device (ARPT) section was tuned for DW1390 -> change PCI ids (dev & vendor) & description. D630i_LoRes_10.7.5_Tuned_Pack.zip

Depending on your BIOS version and built-in LCD res, this guide may (or may not) apply to you... If you have a lower res screen, I'm pretty sure all you need is the correct DSDT.

Mmm, if the camera was working up to 10.9.3 and not after 10.9.4, it could be a bug or indeed it could be that a DSDT patch is required. Maybe Apple changed something again in their code... I've seen similar issues on my Vostro200 but with Yosemite: for instance, no problem sleeping and waking in SL, L, ML or Mav but no such thing in Yos.