Hervé

Cham Wizard does nothing to kext cache. It simply allows you to update your bootloader or choose a specific version, adjust your boot plist parameters, select a given SMBIOS plist or select your Chameleon modules. Kext cache is something totally different and tools like Kext Wizard and myHack can help to rebuild it. If you use myHack, then you should always use myFix to rebuild your cache. Why? Because the kexts you have in /E/E need to be reflected in the PlugIns of the myHack kext placed in /S/L/E. Naturally, that has a direct impact on kext cache if you do any modification to kexts. Good to hear your down to a proper boot time now. As an order of comparison, my boot time on my D630 nVidia with ML went from 1min to 20seconds once I sorted out a kext cache issue! So it's very much worth to get kext cache in order. I'd keep that original ACPIPlatform kext away as it's often found to slow down shutdowns and restarts, but no harm trying again with that kext back in /S/L/E. You'll soon find out if it makes a difference or not. You could also probably check all those empty cases between C States and C4, especially the Drop SSDT if you have your own tables (like DSDT).

If you deleted the ACPIPlatform kext from /S/L/E, you should use version 1.3.5 from EDP and place it in /E/E. You mention Kext Utility, does it mean you're not using myHack ? Can you provide a screendump of your Chameleon boot plist opened in ChamWizard?

You can use EDP to set that up when you do your system build: it's the "emulated SpeedStep" option of the CPU&Power tab. Set it to ON. In your case, if you prefer the manual method, since you appear to already have the PState kext already installed in /E/E, just copy the PStateMenu plist from /Extra/Storage/LaunchAgents to /Library/LauchAgents... Brave man! You're running on conservative mode?

Mmm, a 3min boot is more likely the consequence of something wrong (incorrect boot settings, lack of kext cache) rather than a lack of SSD trim. For instance, on my D630, keeping USBBusFix set to Yes on a previous Lion partition caused a good 1-2min wait after the Chameleon background screen appeared and before the gray Apple logo appeared with the spinning wheel. Add lack of kext cache to that and that could easily exceeds 3mins boot time!

Do you have USBBusFix set to Yes in your Chameleon boot plist? If so, open the plist with Cham Wizard and uncheck it. See if that makes any difference.

Video card reported as 8400M GS is long known and the way to change this through simple DSDT text edit has been mentioned many times before. Nothing new here... You should have no problem whatsoever installing SL,Lion or ML on your WUXGA D830 with NVS 140M. It's totally supported with our OSXL process + specific bootpack.

Hi, the SD card reader is unsupported (IRQ conflicts with LAN NIC). PC Card slot is supported up to 10.6.6 if I'm not mistaken, then unsupported afterwards. Wake from sleep is supported as long as you setup your laptop the right way (BIOS + hibernation mode). Do a little search on the forum about it.

Try VoodooHDA (v2.8.1 to v2.8.4) instead of AppleHDA: remove AppleHDA + STAC9205 + IOAudio + LibKern kexts and replace by VoodooHDA + HDADisabler then re-run myFix (full).

EDP should be fixed now, so don't hesitate to give it a new try.

Configure as specified here: https://osxlatitude.com/index.php?/topic/1901-bios-settings-d830-nvidia-nvs-135m/

@daspazz: check your BIOS settings; it looks like you have IDA enabled...

Use one of the latest VoodooHDA instead (2.8.1 to 2.8.4).

That is indeed a good and valid process for a D830 nVidia with ML. I'll add a 5th one: - AFTER EDP system build: remove AppleACPIPlatform from /S/L/E and re-run myFix (full); that fixes the cache issue and takes care of the slow shutdown/restart.

When you do your EDP System Build, in the Fixes tab, you have to select Brightness Fix. That'll sort out your issue. Re: SL 10.6.8, you'd normally install SL 10.6.0 or SL 10.6.3, apply Combo update 10.6.8 but install EDP and run a SystemBuild before reboot. That last part is critical.

Ok, problem identified; will be fixed tomorrow. Meantime, please follow instructions added here: http://www.osxlatitude.com/edp/download/

No, if there is a problem with the EDP package, there's nothing you could have done to prevent it... We've identified the problem and it'll be fixed tomorrow. Meantime, don't use the EDP app in Applications but run it manually from /Extra folder (i.e. launch the EDP command script). -> PM

Absence of EDP would not normally be a source of system freeze when you still have your boot pack.

Ok, so you (should) have no problem installing ML, just having trouble with EDP at the moment...

Hi, you should be able to use the 'lspci' command and obtain full details of your hardware. PCI Vendor id + Device id will identify the exact model for each reported component.

You don't appear to have graphics acceleration (hint: the menu bar is not transluscent), so yes, graphics will be slow and possibly buggy. If you meet KP with ACPI, you could try the EDP ACPIplatform kext (v1.3.5), it's known to work well under ML (and other OS X version). It fixes kext cache issues too. I can upload it later. If you did your installation with myHack, just copy the kext to /E/E, then run myFix (full) to repair permissions & rebuild cache. As always, Intel wireless cards are not supported, so you'll need to change that by a supported model (Broadcom, Atheros) to get wifi. There's a non-exhaustive list of supported models in R&D -> Network section. For shutdown/sleep/restart & CPU power management, a dedicated DSDT/SSDT table would be required in all likelyhood. Make a request to Dinesh, following the process detailed in the dedicated thread in R&D -> DSDT section.

There could be an EDP problem that we're looking at right now. This being said, could you please specify which D630 model you have?

Guys, we're looking at it; thanks for reporting it.

'looks like a nice laptop to Hack... Have you thought about trying out a Vanilla install with myHack as opposed to a distro? This would help us re: EDP integration.

Yes, it's an acceleration/boost feature (i.e. a frequency/rate increase) available on some Core 2 Duo CPUs where 1 core can briefly run at a higher multiplier/speed than the maximum nominal speed whilst the other core is idle. A kind of ancestor to Turbo boost modes of Core "i" CPUs. Let's take the example of a Core2Duo T7500, a very common CPU on laptops such as the Dell D630: FSB: 800MHz quad-pumped (i.e. 4 x 200MHz) nominal max multiplier: x11 nominal max. frequency: 2.2GHz (i.e. FSB x multiplier -> 200 x 11 = 2200MHz) Dynamic Acceleration allows this T7500 CPU to briefly run 1 core at x12 = 2.4GHz whilst the other core is idle. More info at: http://en.wikipedia.org/wiki/Intel_Dynamic_Acceleration http://www.cpu-world.com/Glossary/D/Dynamic_Acceleration_technology.html http://www.intel.com/cd/channel/reseller/apac/eng/products/mobile/processors/core2duo_m/feature/index.htm The reason we mention IDA is because, although it's fully supported in Windows for all C2D that are IDA-capable, it's not the case with Mac OS X. For instance, with IDA enabled in BIOS, we notice reduced/lower (~10%) FSB and CPU speeds with Merom T7x00 CPUs in Mac OS X. However, FSB and CPU speeds are properly reported when IDA is disabled. On the other hand, we don't notice this misbehaviour at all if IDA is enabled with Penryn T9x00 or T8xxx CPUs.

Well, you should be ok with the OSXL procedure then. With Lion, I recommend booting wuth option "USBBusFix=No" to avoid keyboard issue.