Hervé

Voodoo battery manager works fine for me on all my D Series from SL to Mavericks. Place in /Extra/Extensions then run myFix (quick). You know, the usual process... VoodooBattery.kext.zip With Yosemite, I switched to patched AppleSmartBatteryManager as I found it worked better. AppleSmartBatteryManager.kext.zip

Ask Dell.

No; only the keyboard possesses backlight.

Following on another valuable advice from JakeLo and since we could get the SD card reader to work natively by patching the AppleSDXC kext, the following DSDT patch (under device RP08@1C,7, that's where it's found in IOReg) avoids all subsequent kext patches, especially as that was required after each OS X update: Device (SDXC) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x08) { "AAPL,slot-name", "Built-in", "device_type", Buffer (0x11) { "Media controller" }, "model", Buffer (0x18) { "O2 Micro SD card reader" }, "compatible", Buffer (0x0D) { "pci14e4,16bc" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } ... The Info.plist file of the vanilla AppleSDXC kext containing a specific reference to Broadcom BCM57765/57785 SDXC/MMC card reader (PCI device 14e4:16bc), a simple statement "compatible" referring to that device enables the 02 Micro SD card reader once and for all, the rest of the patch being cosmetic info for the SysProfiler! This applies to both Mavericks and Yosemite so kext packs updated accordingly (Mavericks pack #8 in post #1 and Yosemite pack #5 in post #9).

On top of what was cited above, you can try and run DVDPlayer and select "Show supported Features" in the Help menu. With full graphics acceleration, expect all features to be "supported".

If you want to configure TrackPad behaviour, try and use the System Preferences panel.

As a golden rule, you should not place kexts directly under /S/L/E on a myHack-based installation, only in /Extra/Extensions. myFix handles them for you afterwards. So, if you've added your kexts to /E/E, then you simply remove them from there, run myFix (quick) and that's it. Nothing else to do. If you have kexts of the same name in /E/E and in /S/L/E, then myHack/myFix automatically forces the OS to load the kexts placed in /E/E by doing 2 things: 1) upping their versions to 1111 2) copying the kexts as PlugIns to /S/L/E/myHack kext from which OS X will load them If you then remove the kexts from /E/E, myFix will consequentely remove them from myHack.kext PlugIns and the original/vanilla kexts placed in /S/L/E will automatically take over. You need to read about myHack to understand how it works, I posted about that very matter on the forum some time ago. You'll find the thread in the myHack forum subsection.

You can sure try those Elan or ALPS kexts in /Extra/Extensions, followed by myHack-myFix (quick). myFix ups the kexts version to 1111 and copies them as PlugIns of /S/L/E/myHack.kext. Do not play with plugins of /S/L/E/myHack.kext or remove kexts from /S/L/E unless you have placed them there.

I guess you could always temporarily use a wired USB mouse to get you started. Then, it's probably going to be a matter of identifying your built-in trackpad/mouse manufacturer & model to look for the correct kexts. Most laptops usually have an ALPS or an ELAN trackpad. This being said, if your mouse/trackpad worked suring intial installation, one would expect that you copy copy those PS2 kexts from your USB installer to your target ML partition in /Extra/Extensions. Then run myHack->myFix (quick) to install them and get things working.

A problem with the Lion installation app/package maybe? Legit copy or torrent download?

And up to 10.10.3, still using Bronya's 14.0.0 RC7 kernel. In order to safely reboot into Yosemite, I had to: reinstate AxmanA's or ToraChiyo's IOPCIFamily kext (fix for boot-to-white-screen issue with my GeForce 9800GT) replace pthread kext by ToraChiYo's rewritten 10.10.2's version (vanilla version gave me systematic KP) re-binpatch IOGraphicsFamily kext (to fix final stage bootscreen graphics glitches) ToraChiYo_IOPCIFamily.kext.zip ToraChiYo_pthread.kext.zip IOGraphicsFamily.kext.zip

Why don't you revert to our standard myHack v3.3.1 + bootpack proven method? Boot the installer, format your target disk partition "Mac OS X extended (journaled)" on a GPT partition scheme and let it run its course. You can then tune up using the complete pack I posted several times in recent months. EDP appears best avoided on D Series since many users reported problems after use... Lastly, don't forget to apply performance tuning actions as detailed here.

Ok, so it's a Haswell i7-4700MQ, nominal speed 2.4GHz and max Turbo speed 3.4GHz. Did you generate a SSDT with the usual script tool for your own CPU? If you didn't, please note that it is required/mandatory to obtain adequate CPU power management. You'll find the tool and detailed instructions at RampageDev's blog. The CPU Power Management setup process also requires that you use the correct SMBIOS profile (Clover normally selects the correct one, with Chameleon you need to select it manually). In your case, it could be MacBookPro6,1/6,2 or possibly 11,1; it really depends on your specs. This SMBIOS profile can have an incidence on the number of intermediate CPU multiplier you'll obtain between LFM frequency (say 800MHz for instance, I don't know which it is for the i7-4700MQ) and nominal frequency (2.4GHz). The SSDT should then provide all or most of the turbo multiplier between x25 (2.5GHz) and x34 (3.4GHz). Make sure you do not activate P States or C States generation, whether it be with Chameleon or Clover. You may not have to select option "DropSSDT", though it is often required. There are various tools to monitor Core "i" CPU SpeedStep; DCPIManager does provide a facility to monitor CPU multipliers for instance. And, of course, HWMonitor (choose the version that comes with FakeSMC) will display CPU speed/multiplier/voltage/T° on a (near) real-time basis.

Straight update on Chameleon-based installations, no particular issue, at least on the D630 nVidia. As usual, SSD Trim has to be reactivated through IOAHCIBlockStorage kext binary patching (replacement of string "APPLE SSD" by a string of "00"). Of course, AGPM kext also needs repatching to regain throttle of the NVS 135M GPU, following details described in dedicated thread. IOAHCIBlockStorage.kext.zip On the E6440 with Intel HD4600 graphics, things require a little more work due to the need to patch the Intel graphics-related kexts + OpenCL framework library. But it's the same as with previous Yosemite versions so no surprise there. On my Bronya's AMD kernel-based Precision 670, I had to replace the pthread kext by a rewritten version to avoid CPU-related KPs at boot time.

No, not as bad, but your CPU sounds like a low end T7100 or T5670 Merom C2D. Penryn T9x00 CPUs with larger L2 cache and higher frequencies are better suited for Mavericks and Yosemite which are more power hungry. Add an SSD and you'd have a decent enough Hackintosh laptop.

There it is: https://osxlatitude.com/index.php?/topic/1847-pcmcia-firewire-on-d620/?hl=%2Bd630+%2Bpcmcia&do=findComment&comment=13221

From memory, PCMCIA was supported up until 10.6.6 and died with 10.6.7 or 10.6.8. Something like that anyway; could be wrong with specific versions. I did some tests ages ago, there might be an old post/thread in the archive. SmartCard reader, I've never tried, never had the use for it.

It'll run but I think you already know the answer in terms of performance expectations.

If the CPU seems to operates at Turbo speed all the time, you clearly have an issue with CPU power management. How did you set that up? What exact CPU model is it? One thing to note is that your "basic" 2.4GHz frequency is probably the max nominal frequency, not the minimal speed of the CPU which should be way below. I invite you to research and read about Intel CPUs and things like SpeedStep, Low Frequency Mode, High Frequency Mode, etc.

You may not be aware of it, but there is a search facility on the forum at very top and very bottom of the browser page: http://www.osxlatitude.com/edp/compatibility/ http://www.osxlatitude.com/edp/documentation/pre-installation/ https://osxlatitude.com/index.php?/topic/6731-d630-nvidia-yosemite/ https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/

Meantime, you may try to boot with Chameleon flags and options -f -v PciRoot=4 GraphicsEnabler=Yes and see where that gets you.

Ok Goran, here are a few quick comments. 1) as expected, the DSDT uses a default PCI root value of 4; that's a pretty common thing on Dell workstations/high-end PCs: Device (PCI0) { Name (_HID, EisaId ("PNP0A03")) Name (_UID, 0x04) Name (_ADR, Zero) ... The _UID can usually safely be changed from 0x04 to Zero (or 0x00); that'll allow to boot Chameleon with its default PCI root value and avoid the need to specify boot option PciRoot=4. This is very important to get things like graphics cards working properly. 2) your IOReg output shows an AMD Radeon HD 6950 (device id 0x6719, vendor id AMD 0x1002) under PCI2@5. This means that if you need to inject cards properties in your DSDT, you'll have to do it under/within Device (PCI2) at address 0x00050000. You can consult RampageDev's blog for details on that particular part but basically, you'd need to add a Device (GFX0) section with full _DSM method to describe the required info using data available in the IOReg. It seems that personality is Lotus (a name that suits me fine... but for cars!).

if you got there with 10.8.3 AMD kernel, then fine. I would recommend you use Bronya's 10.8.5 kernel once you've updated to 10.8.5 (use the Combo Update). Can't really help you on the mouse/trackpad/keyboard issue, you'll need to identify your hardware (e.g.: Elan; ALPS) and use the appropriate kext set then .

No need for PCIRootUID=0, Chameleon uses 0 as default value... Did you install the PS2 kexts from myHack's generic pack (AppleACPIPS2Nub + ApplePS2Controller)? These usually work OOB.

Try Bronya's 10.8.5 RC5 kernel instead. You'll get it here: https://osxlatitude.com/index.php?/topic/2061-dell-precision-470-670-workstation-snow-leopardlionmountain-lionmavericksyosemite/page-2&do=findComment&comment=35008