Hervé

Last updated 13 May 2014 - - - - - - - - - - - - - - - - - - For those who would be interested, here are details to get & monitor native SpeedStep + stable Sleep/Wake on C2D Latitude D430 (tested on my U7700-based own model). The process consists of: replace existing FakeSMC kext (4.0 in most cases) with attached tuned-up version (based on Kozlek's 5.2.678 32/64bit) remove NullCPUPowerManagement + SleepEnabler + PState + CPUMonitor kexts remove PStateMenu utility keep VoodooTSCSync kext (this is critical or your laptop will run like a dead dog, thanks for the info Bronx Teck) activate CPU P-States & C-States generation at bootloader level use MacBook5,1 profile run HWMonitor tool to monitor CPU T° and frequency This basically makes use of MacBook5,1 SMBios and SMC value 1.32f8. Initially, MacBookAir3,1 (C2D SU9400 1.4GHz CPU) SMBIOS profile was used, but it turned out it was not supporting the full frequency range of the D430 CPU and it was not working under SL either. With MB5,1 profile, there is no issue at all. 1) EDP-based method: place attached FakeSMC kext in /Extra/include/Extensions modify Chameleon boot plist to select P & C states, then copy it + MB5,1 SMBios plist to /Extra/include do a System Build for Dell D430 with the following settings and reboot: in Kext/Drivers tab, select FakeSMC 5.x.xxx (Rehabman ...) / FakeSMC 6.x.xxx or whichever version is offered these days (it does not matter because EDP will not use that kext but the one you previously placed in /Extra/include/Extensions), the rest can be left as listed or changed according to your own wishes or needs in CPU & Power tab, set Install VoodooTSCsync to ON and all the rest to OFF in the other tabs, default options can be left as provided 2) Manual method: place the attached tuned-up FakeSMC kext in /E/E, replacing any existing version delete any existing CPUMonitor / VoodooPState / NullCPUPowerManagement / SleepEnabler kexts from /E/E delete any existing PStateMenu plist from /Library/LaunchAgents place the attached MB5,1 SMBios plist in /Extra edit the boot plist with Chameleon Wizard to select P & C states generation, as pictured below run myFix (quick) and reboot After reboot, copy HWMonitor application to Applications folder then start it. Click on the HWMonitor menu bar icon, go to Preferences by clicking on the Gear icon in top right corner and select Start HWMonitor at login in General tab. Keep update checking turned off. You can then adjust/modify displayed information in Menubar tab through drag & drop of individual monitored components. HWMonitor application is completely optional but very useful to monitor CPU T° and SpeedStep. Under Snow Leopard, use HWMonitor v2.3.20 as more recent versions are unsupported. You'll know it works if you see fluctuation of CPU multiplier and frequency. For instance, on a U7700 CPU @1.33GHz with FSB 533MHz, you can expect the following steps: x6 -> 798MHz x7 -> 931MHz x8 -> 1.06GHz x9 -> 1.20GHz x10 -> 1.33GHz You should now enjoy native SpeedStep, lower CPU T° (?) and, probably, improved overall responsiveness. I do! Sleep & Wake will work properly and totally stable as long as a System password has been set in BIOS setup. FakeSMC_v5.2.678_32:64bit.kext.zip smbios_MB5,1.plist.zip HWMonitor_v5.2.678.zip HWMonitor_v2.3.20(SL).zip This was tested successfully under Snow Leopard 10.6.8, Lion 10.7.5 & ML 10.8.4/10.8.5 (MLPF). PS1: This is totally similar to what was published in the article about native SpeedStep (with examples provided for D630 and D830). See here. The main difference here is that VoodooTSCsync must be retained with GM945 chipset. As such, this particular process also applies to D420, D520, D620 and D820 laptops for instance.

Well, to be on the safe (and legitimate) side, I can only advise you to purchase & download a copy of Lion from Apple; it's not as if it costs a fortune...

What are you using to create your USB installer? You wouldn't be using a Virtual Machine, would you?

Ladies & gents, we had a bug that caused our bootpacks to be stranded without FakeSMC kext. As such, those who tried an OS X installation these last few days experienced issues, whether KP or DSMOS problems or other issues such as hung installations. The problem has now been resolved and all should be back to normal. OSXL Crew

Problem fixed, all bootpacks should be Ok now.

Ok, the current bootpack has an issue (a major kext is missing). Try this one, I've just tested it successfully with a default myHack 3.1.2 USB installer (i.e. default Cham boot loader). Bootpack_D430.zip

Have a look at the "Performance tuning" article in the Articles page of the web site (you'll find the shortcut at the very top of your browser page).

I will try out a fresh Lion installation on my D430 later on and will let you know. Meantime, can you tell me which version of myHack you're using to create your USB installer and which version of Lion you're using for your installation (10.7.2, 10.7.4, 10.7.5?).

Download latest Chameleon from here: http://www.osx86.net/view/3856-chameleon-2.2svn-r2254.html and re-install on your HDD partition.

I guess you could be doing something wrong: I just downloaded the ML bootpack and got the expected "Extra" folder (with all expected files & folders) in my default Download folder. When you proceed with myHack's "Create Extra", make sure you point to that downloaded Extra folder.

Bear with us, we might be able to help, but no guarantee... The GMA 4500MHD was totally unsupported under Mac OS X. But clever people work on writing kexts for the various versions of it.

Use the OSXL bootpack when you build your myHack USB installer and when prompted for your "Extra" folder during installation. Once you've completed 1st boot installation finalisation, you can download+install+run EDP and do a system build.

From the Mac/Hack you used to create your USB installer, run one of the latest Chameleon Wizard app and update the Chameleon bootloader that's on your USB installer. You do this through the "Install" tab in the wizard, select your USB installer as target partition at the bottom, select your Cham version at the top (r2248 or above) then click "install". That should do it.

James, which DP are you running? I've looked at various folders with pictures since updating to DP3 and I can't reproduce your issue on my D630 nVidia. Can't say if I would have encountered the same as you before updating, I never really looked at that.

Seems Ok with DP3 (but then again, it's on my D630, not an E64xx).

The AppleEFI issue is sorted if you use a recent Chameleon version, starting at r2248.

It does not work at all. It's been mentioned many times before: the SD card reader shares IRQ with LAN interface and Mac OS X does not support that. If you disable the LAN in BIOS and use the SD card reader kext, all you'll ever get is your card icon on the desktop as you insert it but it won't readable, no matter what.

That'll be due to that particular 32bit FakeSMC kext version and/or the HWMonitor version you use. Kozlek has published several new versions since my article, so you may download the latest source code and compile it 32 or 64bit, according to your needs. http://sourceforge.net/projects/hwsensors/ https://bitbucket.org/kozlek/hwsensors/downloads https://www.assembla.com/code/fakesmc/git/nodes/master/FakeSMC

Good that you got there. It looks like the USB key itself is the surce of the problems.

Yep, I never did that quarantine thing. Will have to try that out too.

Yes, 25s is very good but I'm sure SL would fly on this drive provided your kext/boot cache is in order... I've just bought the adapter; 'might try to secure it with bluetack or chewing gum!

Yes, just follow the process detailed in p1 of this thread.

myHack + OSXL bootpacks are our recommended method for installing Mac OS X on systems listed under our compatibility chart. EDP is our post-installation fine-tuning tool that aims to activate those features that may not be functional after initial installation. In all cases, bootpacks + EDP only apply to models we have validated and included in our database. If you have a model that is not covered at the moment, then those matters don't really apply to you, but we can help you contribute to add your system to our list. In the case of your SSDT, if you need patching, place a request by following the process detailed here: https://osxlatitude.com/index.php?/topic/1945-dsdtssdt-patching/

Very useful info, thanks for sharing this. I've been looking at an SSD for my D430 since the Zif HDD really is too slow. I might give that solution a try. Am I right in thinking that the mSata adapter is not actually mounted in the HDD slot, but just placed and held there with the rubber cover?

I think the motherboard is irrelevant, I was hoping to get details like make and model of your laptop to see if there was something doable via BIOS. But if Wireless enabling/disabling is not do-able from system BIOS, then yes, I guess a DSDT edit might be the thing to look for.