Hervé

Yes, on paper it should but some HP laptops can be difficult... Your Intel wireless card will have to be replaced because it's not supported. It can be a problem because many HP laptops have a hardware whitelist so you probably won't be able to fit any replacement card compatible with Mac OS X. You'll have to make sure the laptop will also take it. Broadcom-based card usually have a better chance of being accepted by HP laptops as HP used those. You have an older system build around the Intel GM945 chipset but the nVidia 8600M graphics card means you can still install recent OS X versions such as ML or Mavericks. If you manage to complete installation, it won't be the best Hackintosh performer around but should run Ok nevertheless.

Correct me if I'm wrong but it looks like booting the installer and completing initial installation is Ok but you're having problem after EDP System Build? If this is the case, you're probably experiencing the same issue as what was recently experienced by D6x0 users where you need to manually select the 'ACPI Fix' option in EDP to install the patched ACPIPlatform kext on your laptop. It's explained in the following posts: https://osxlatitude.com/index.php?/topic/5821-d630-nvidia-freezes-after-pre-configured-edp-5/page-2 https://osxlatitude.com/index.php?/topic/5884-d630-boot-issues-after-updating-with-edp/

Google is your friend...

If you still have the ML installation, do try and compare the contents of your /Extra/Extensions to see if there are any differences. Also check that you have DSDT + Chameleon boot plist + SMBIOS plist in /Extra with identical settings as you had in ML.

I have roughly identical T° readings. my GPU T° can even get higher. I clean the fan regularly, I've renewed thermal paste and even used a copper shim over the nVidia chip but none of this made any difference as far as lowering T° is concerned. D630 keeps on running, so I just live with it...

myHack is what we support and advocate here. Try it with Generic bootpack. That's how it all starts... Naturally, you may use whatever else might get your fancy, but we won't really be able to support you through installation.

It looks like you need to re-install EDP as something went wrong.

Well, it's built with Intel GMA 4500MHD graphics, so you'll be facing the usual challenge of being able to obtain full QE/CI. You should be able to install Mavericks on the laptop though, then we'll see how we can help you with getting full graphics support, knowing that we may be able to provide you a set of graphics kexts, but there's no guarantee. We've got kexts that work on some GMA4500-based systems, but not on others... Getting wireless to work could also be difficult because HP often have a whitelist of cards so, if your existing wireless card turns out to be unsupported, it can be quite another challenge to find out which model would be supported in the laptop whilst compatible with OS X...

Available directly from Dell: http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=621F7

Well, all looks Ok from a hardware point of view: you have the nVidia model and a Broadcom-based Dell wireless card (Intel cards are listed as "Intel wireless") which you'll need to check in terms of compatibility with OS X. It'll be safe to turn to ON in your BIOS setup once you have ML installed. Wireless is of course supported in OS X, provided you have a supported wireless card model as OS X does not support every model on earth unfortunately. Many (but not all) Broadcom-based and Atheros-based cards are supported, as well as some RealTek or Ralink USB dongles too. We have a non-exhaustive liste here and you can also consult the wiki pages of InsanelyMac.com. Make sure to configure your BIOS as per recommended settings in the dedicated pinned thread in this D8xx section. Regarding the copy of your /Extra folder, I noticed that you have neither the DSDT, nor the SMBIOS plist file and that your Chameleon boot plist is not what I would expect for the D830. Did you actually use the bootpack from our site when you made up your ML installer? It just does not look right. Kexts in /E/E appear Ok though. Download the D830 nVidia ML bootpack off our EDP->Bootpacks menu at the top of the OSXL page, then re-run myHack->Create Extra, select "your own..." and point towards the downloaded bootpack (should be "Extra" folder under "Download").

Can you confirm: the D830 model that you have: Intel X3100 Crestline or nVidia 135M/140M the model of your Wifi card (Intel is not supported and should be disabled to avoid issues)

You need to use the Intel binary version of the BCM5751 kext, not the universal binary one (PPC + Intel). If you right click on the kext and select "Get Info" you'll see which it is. The Intel binary version if 147KB vs. 664KB for the Universal one. Anyway, it's all detailed here and the kext is provided too. PS: I think I said it before but BCM5722 kext is not for the Ethernet fitted to the D620.

If you can, try and optimize performance on the Inspiron 9400 and Precision 690 as we have the others fully covered.

The SMC keys to use for the BacBookPro5,1 model/profile is 1.33f8, not 1.42f4. I don't know where you got that from http://www.osxlatitude.com/tuning-performance-with-fakesmc-smbios-plist/ https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ I've verified these settings as fully functional with Kozlek's FakeSMC v5.2.678 and more recent version such as 6.0.1011 for instance. This being said, if HWMonitor shows no sensors, it probably means your FakeSMC is invalid or incorrectly installed. Are you using a myHack installation? If so, success could depend on the manner in which you installed your version of FakeSMC. If you simply execute Kozlek's package, the kext will go to /S/L/E by default and HWMonitor app in Applications folder. What you really ought to do is: 1) modify the Info.plist of FakeSMC kext to reflect SMC compatible to "smc-mcp" and all 3 keys to 1.33f8 2) copy all 4 (or 5) FakeSMC plugins (ACPISensor, CPUSensor, GPUSensor, etc.) to the PlugIns folder inside FakeSMC kext 3) place modified FakeSMC kext in /E/E and re-run myFix (quick) 4) modify your SMBIOS plist to MBP5,1 5) remove all instance of NullCPUPowerManagement + CPUMonitor + VoodooPState + VoodooTSCSync kexts from /E/E 6) enable P+C States in Chameleon boot plist (keep other settings underneath unticked) Regarding Bluetooth, do you know the model of the module you got out of that D820? I would expect it to be a DW350 or DW360. You would normally see it under the USB section of a System Report (via Apple Menu). Have a look at the Bluetooth thread in R&D->Hardware->Wifi/Bluetooth section; you may find that the BT radio was disabled when D820 ran Windows and that will render the module unusable under Mac OS X. You would need to re-enable radio from within Windows or you can try to patch the CSR plugin of IOBluetoothFamily kext and there's a good chance your module could be reactivated from within Mac OS X. The shutdown issue is most likely due to cache not being built and this extra long time you're experiencing will be the system's attempt to rebuild the cache. Are you using the patched AppleACPIPlatform kext at all? In fact, I'm beginning to wonder if you did an EDP System Build on this laptop?

Look at the list of supported cards in R&D->Hardware->Wifi

Nothing to worry about unless you were often getting into the 80-90°C.

Indeed, not all WWAN modules appear as such in OS X; however, this does not prevent them from running well as USB modems… I have one of those in my D630 and although I never managed to get it registered as a WWAN module (which would give me the nice little GSM signal strength icon on the menu bar), I can still get it on the menu bar as a 3G dial-up modem and it'll work fine.

Thanks for your explanations and files; they're most useful and the comments in those DSDT patches are great. A very valuable contribution here folks.

There is no "best" version per sé, it's often a matter of taste or required/desired features but Snow Leopard will run fastest without a doubt. All the other versions will run well, but users often report that Mav 10.9 runs faster than ML 10.8 which itself is often reported to run faster than Lion 10.7. With a SSD, sufficient RAM and a decent CPU (T7500 or better), all recent OS X versions will run pretty decently on a D830 nVidia.

It means the feature may be supported after replacement of hardware provided as standard.

Hi, please explain how you solved your shutdown/restart + sleep issues as it may help others in the future.

CPU T° of 50°C and running "only" 5°C more than Windows is not what I would call a system running too hot. That all looks pretty normal to me. How high do temperatures get to when you run your CPU at full speed?

Did you use the D630 DSDT at all?

I perfectly got what you mean, but we also already know what is required for our D series Latitude as partially listed in the following post: https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ This was not implemented in EDP because EDP, until now, uses a common set of kexts for all integrated systems and the performance tuning changes that concept. It therefore makes everything far more difficult to maintain and manage, notwithstanding the additional tests that the exercise requires. An additional difficulty is the extremely rapid pace at which Kozlek makes new versions of the FakeSMC kext. We just can't keep up with it and EDP needs some degree of stability. We just can't re-test all our integrated models with every new FakeSMC release... You should also take into consideration the fact that these benchmarking tools are far from being entirely reliable and you should not base performance evaluation on them. Eg: https://osxlatitude.com/index.php?/topic/2088-cant-restartshutdown-lion-or-mountain-lion/?p=15973. Also note that comparing a system running Lion with a different system running ML is meaningless, if only due to the difference in graphics management within both OS X versions.

Sorry, but what's the point of all this again? Because, you've confirmed things run as expected with tuned settings, so I'm not really following the purpose of those tests, especially with what you call "default EDP " and which we'll change very soon...