Hervé

Well, I would not really expect a HDD cloned from a 745 to work straight away on a 755, especially if keeping the DSDT and things like that, that are totally specific to the original build. As a minimum, the /Extra config would need to be adjusted according to the specs of the target 755 (DSDT, boot plist, SMBIOS, kexts, etc.). List the specs of both machines and we'll possibly be able to give you pointers.

Use the attached fully tuned pack for 10.6.8. Needs nothing else other than your own particular wireless kext, if at all required. The included DSDT was patched to display "DW1395" but it's just cosmetic. Use DSDTEditor (or decompile through Chameleon Wizard and use TextEditor) to adjust as/if required. D620i_LoRes_tuned_pack.zip

Which OS X version?

If the 2 systems are of fairly similar specs, boot with -f UseKernelCache=No since the HDD should have the cache for the 745 and that may not be suitable for the 755. After that, you'll probably have to adjust your /Extra folder to fit the 755's own hardware.

Difficult to see any relation between the 2, but I'd suggest you re-run myFix (quick). Everything working fine here (with VoodooHDA v2.8.1 + AppleHDADisabler).

Ok, good. I have mixed feelings about selecting P and C states in the Chameleon boot plist in fact. Reason for this is that I noticed a different behaviour a few days ago when re-doing a Mavericks installation on my wife's E6420 (yes E6420, not E6320). Booting without P & C states in the boot plist, I noticed the CPU was always running in the turbo boost/post-nominal speed frequencies, never idling at low speed. However, if I added P & C states in the boot plist, CPU would idle at a few hundred MHz as expecting, boosting to Turbo speed only on heavy load. That's my own very recent experience on the matter, I don't have the E6320 any more, so can't check that out.

Compress them 1st and it should be Ok.

If your laptop is able to boot OS X without any DSDT file (you may not have a fully working system but that's irrelevant), you can use tools such as DSDTEditor or Chameleon Wizard to extract your raw DSDT from BIOS. For the IOReg, you can use IORegistryExplorer (v2 is often better than v3) and save the IOReg output, again having ideally booted without a DSDT file.

They are very different laptops with little hardware in common in fact: E6400 is based on G45 chipset, Penryn Core2Duo CPUs, DDR2-800 RAM, Intel GMA 4500MHD or nVidia NVS160M graphics E6410 is based on QM57 chipset, 1st gen Arrandale i5/i7 CPUs, DDR3-1066 RAM, 1st gen Intel HD or nVidia NVS 3100M graphics Yes, you may find certain "accessories" like LAN card, SD card reader or TouchPad to be common, so indeed "some kext will work", but that's not the same as using an E6400 guide/bootpack for reference. In that respect, kexts from say a working Asus or Lenovo system may apply to the E6410 as much as kexts from a working E6400. In a similar way, yes, "steps are the same", but this principle applies to all Hackintoshes, so the general way one installs Yosemite on say an E6400 is the same as one installs Yosemite on say a D630. I think Ako is after a E6410-specific guide with factual experience and feedback...

Yes, that could be the reason; I thought both cards were based on same chip but I probably misread things in fact. Out of interest, you may want to give the MBP5,1 profile (SMC keys=1.33f8), you never know; it's probably unlikely it fixes things, but nothing to lose I suppose.

That's a thread for E6400, not E6410, which is the topic here...

Could also be due to syntax errors before that bracket. Quotes, in particular, can be an issue if you use a text editor in which Smart Quotes are selected. They're not supported in DSDT source code.

Look pretty good to me, GPU throttling excepted but may be MBP(6,1) does not do it, I don't know. Did you give any thoughts to the Cuda driver? Did you also remove your AGPM patching? For battery management if VoodooBattery does not seem to work, try another kext like AppleSmartBatteryManager.

You may have to try a few (v2.8.x/2.7.x). Start with the latest and try older ones if problems. All are available through Google searches and/or at the usual well-known places.

Mmm, didn't we say SMC 1.57f18/smc-piketon for MacBookPro(6,1) and SMC 1.58f17/smc-piketon for MacBookPro(6,2)? 1.57f16 is an older SMC value for MPB6,2 by the way. You did not include your /E/E folder either, so I can't check things entirely... Why do you have the following config in your boot plist? Enable C2 State Enable C2 State Enable C2 State Bus Ratio 18 Ignore Boot Cache (-f) No UseKernelCache No Ethernet Built-in No SystemType set to laptop Get rid of the 1st group and enable the 2nd, carefully read the article/thread I mentioned before (about performance tuning), fix your FakeSMC settings (there are 3 keys, not just one + smc-compatible parameter) and you may have a system running better thereafter. Your kernel and DSDT settings are not required either, these are the default values. No harm though I suppose. I see you've used the patched AICPM, you've got the correct SSDT for your CPU too? Finally, you probably don't need that older AppleACPIPlatform kext (v1.3.5 or v1.3.6 I suppose), Mavericks runs perfectly on its own original kext (well it does on the 3 different systems I have running 10.9.4).

Can you post your /Extra (/E/E + boot plist + SMBIOS plist)?

Up to 10.10 DP5 (build 14A314h) now and still booting via good old Clover USB key. Still no return to 3D dock though...

I've come to realise that some E6320 models are apparently fitted with a different webcam from Sunplus Innovation Technology: PCI ven id 0x1bcf, dev id 0x2980. That model works OOB. The Sonix webcam 0x6433 is just not supported.

I think we need to look no further: this is clearly different hardware which appears to identify as some integrated webcam from Sunplus Innovation Technology Inc. (PCI ven id 0x1bcf, dev id 0x2980). Maybe the other Sonix HD Webcam (PCI ven id 0x0c45, dev id 0x6433) model would work Ok with a DSDT patch if that's at all feasible. In fact, the DSDT provided in the packs may actually apply to this particular Sunplus model, not the Sonix one, hence the issue. It's already all on p6 of this very thread but it's typical example of a thread that's gone too long, in all senses of the words... i don't have the E6320 any more but if someone with the Sonix camera could provide a raw IOReg + a raw DSDT and same for Sunplus camera, I'd be happy to look at the tables and try and patch things accordingly.

No fix for this, which does not prevent OS X installation to proceed or the D430 to work properly in any way.

If you have a myHack installation, you should always 1st try new kexts in /E/E, followed by myFix (quick).

D830 came with FSB 800MHz Merom (T7x00) or Penryn (T9x00) CPUs. Nothing odd with your model. Use the attached kexts for TrackPad/Keyboard. PS2_kexts.zip

Usually, you need to patch the Bluetooth kext of the running OS X version, not carry a patched kext from a previous version. Well, that's the behaviour I've noticed since ML for all my DW350/DW360 edits.

The output of a lspci -nn Terminal command on adrianb's E6320 would be useful too, to compare hardware.

It's been mentioned in the past: this system is close to D630/D830 Intel GMA X3100. Try those packs. For the rest, read up the forum announcements!