Hervé

MLPF hack only applies if you can 1st successfully install and run vanilla 64bit ML, without graphics acceleration of course. You need to get that essential part working before you can envisage running ML in 32bit mode with MLPF. With an Intel 965GM chipset, I would not have expected you to need the patched IOATAFamily kext on the 1520, only the AppleACPIPlatform kext from 10.6.7/10.6.8. That's a prerequisite to running ML on these machines. For the rest, the usual D630/D830 X3100 kexts should suffice: FakeSMC, VoodooHDA, VoodooBattery, PS2 controller, AppleRTC, etc. I recommend to stick to myHack as that'll give you more control thereafter.

If it's a desktop PC, the SMBIOS profile you're using seems inadequate...

Cache issue, see answer above.

Thanks to JakeLo who passed on the details for testing, the Yosemite Azul frame buffer kext can now be binary patched to support HDMI output: the patch consists of replacing Hex code 01050900 00040000 87000000 by Hex code 01051200 00080000 87000000 in binary file AppleIntelFramebufferAzul through perl script or via a binary editor such as 0xED. HDMI output is then fully supported with hot plug/unplug. The only thing weird is the reported TV screen size (73.5" for an actual 40" screen!) 10.10.2_HDMI-bin-patched_AppleIntelFramebufferAzul.kext.zip I have also verified that HDMI output can be sole video output when booting up the laptop with lid closed; it worked perfectly but system then hung when I opened up the lid... Best to avoid such mode in those conditions. Updated Yosemite pack loaded to post #15 (pack #4).

Depending on your LCD resolution (WXGA or WXGA+), you have to use a different DSDT file. Make sure you use the correct one: the LoRes or the HiRes.

In computing terminology, numbers starting with prefix "0x" are hexadecimal numbers, i.e. base 16. In hexadecimal, numbers range is 0 1 2 3 4 5 6 7 8 9 A B C D E F. By analogy, in decimal, i.e. base10, numbers range is 0 1 2 3 4 5 6 7 8 9. PID = Product id = idProduct = 0x1823 (in hexadecimal) = 6179 (in decimal) VID = Vendor id = idVendor = 0x0B05 (in hexadecimal) = 2821 (in decimal) Please note that the "key" info/line of a plist is more like a chapter title and that the real applicable data is the one stated below that line. With all this info, you should now easily derive what you need to do to your plist, again without any guarantee that it'll work of course... NB: Product id is also often refered to as Device id or Dev id 6091 (dec) = 0x17CB (hex)

No, PID 0x1823 does not correspond to 6091. You need to identify the exact nature/type of those different numbers to find the relation between them. It's all in the key... Once you've sussed these out, read the plist entries with all due attention so that you don't miss anything. You do at the moment. Open the plist with TextEditor rather than PlistEditPro, things should get clearer... Ask yourself those 2 questions: what does "VID" mean? what does "PID" mean? You may not realise it, but you actually already have all the answers... It's just hard to see the forest with all those trees! <key>PID 6091 0x17CB VID 2821 0xB05</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string> <key>Dongles</key> <dict> <key>Asus</key> <string>USB-BT400</string> </dict> <key>IOClass</key> <string>BroadcomBluetoothHostControllerUSBTransport</string> <key>IOProviderClass</key> <string>IOUSBDevice</string> <key>idProduct</key> <integer>6091</integer> <key>idVendor</key> <integer>2821</integer> </dict>

SysProfiler->Software->Extensions will list the various kexts installed and loaded along with version numbers and file location. You'll then be able to eventually remove the extra/unecessary duplicate FakeSMC.

You've gone all that way but did not suss out how to add your own entry? Very easy and here's a hint: to find the solution, find the key... Then keep everything in the family! No guarantee that having the correct entry in that plist will bring the device to life of course. PS: no double posts please.

Specifications: BIOS A08 (needs HDD set to AHCI mode) Intel Greencreek 5000X chipset with ICH10R controller Intel dual-core Woodcrest Xeon 5140 2.33GHz FSB-1333MHz 8Go DDR2-533 ECC RAM nVidia Quadro FX 4600 (PCI ven id 0x10de, dev id 0x019e) attached to 1680x1050 widescreen LCD Broadcom BCM5752 Gigabit Ethernet (PCI ven id 0x14e4, dev id 0x1600) Sigmatel STAC9200 + Intel Azalia ESB2 AC'97/High Def audio (PCI ven id 0x8086, dev id 0x269a) CD/DVD drive USB 2.0 + Firewire ports Mac-Pro:usr rjjd$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 5000X Chipset Memory Controller Hub [8086:25c0] (rev 12) 00:02.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 [8086:25e2] (rev 12) 00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 [8086:25e3] (rev 12) 00:04.0 PCI bridge [0604]: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 [8086:25fa] (rev 12) 00:05.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 [8086:25e5] (rev 12) 00:06.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 [8086:25e6] (rev 12) 00:07.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 [8086:25e7] (rev 12) 00:10.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 12) 00:10.1 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 12) 00:10.2 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 12) 00:11.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f1] (rev 12) 00:13.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f3] (rev 12) 00:15.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f5] (rev 12) 00:16.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f6] (rev 12) 00:1b.0 Audio device [0403]: Intel Corporation 631xESB/632xESB High Definition Audio Controller [8086:269a] (rev 09) 00:1c.0 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 [8086:2690] (rev 09) 00:1d.0 USB controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 [8086:2688] (rev 09) 00:1d.1 USB controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 [8086:2689] (rev 09) 00:1d.2 USB controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 [8086:268a] (rev 09) 00:1d.3 USB controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 [8086:268b] (rev 09) 00:1d.7 USB controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller [8086:268c] (rev 09) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d9) 00:1f.0 ISA bridge [0601]: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller [8086:2670] (rev 09) 00:1f.1 IDE interface [0101]: Intel Corporation 631xESB/632xESB IDE Controller [8086:269e] (rev 09) 00:1f.2 SATA controller [0106]: Intel Corporation 631xESB/632xESB SATA AHCI Controller [8086:2681] (rev 09) 00:1f.3 SMBus [0c05]: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller [8086:269b] (rev 09) 01:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port [8086:3500] (rev 01) 01:00.3 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge [8086:350c] (rev 01) 02:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 [8086:3510] (rev 01) 02:01.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 [8086:3514] (rev 01) 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation G80 [Quadro FX 4600] [10de:019e] (rev a2) 0b:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express [14e4:1600] (rev 02) 0c:02.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW322/323 [11c1:5811] (rev 61) I assisted forum member rjjd to install Yosemite on his Precision 490 workstation. Target OS X release: Yosemite 10.10.2Installation fully successful with manually-built 10.10 USB installer + Chameleon v2.2 r2401 bootloader and attached Precision 490 bootpack on a SATA HDD partitioned GUID and formatted Mac OS X (journaled). Initial build in 10.10, followed by 10.10.2 Combo update. Working: full QE/CI with Quadro FX 4600 (with known Dell-specific PciRoot=4 boot option or DSDT patch to set PCI root to 0) audio output (with VoodooHDA v2.8.1 or later + AppleHDADisabler) built-in Gigabit Ethernet (with BCM5722D kext, ideally v2.3.5) display & system sleep/wake (with hibernatemode set to 0 + deletion of /var/vm/sleepimage). wireless with compatible mini PCIe card/USB dongle native SpeedStep (with Kozlek's FakeSMC v5.2.678 tuned up for MacPro3,1/SMC keys 1.24f15/smc-napa + SMBIOS MacPro3,1 - later versions of FakeSMC + HWMonitor should provide much more hardware info) all USB2.0 ports OOB Yosemite full /Extra pack: Precision490_Xeon5140_QuadroFX4600_Yos-Pack#1.zip DSDT patches applied: PCI root (_UID of Device (PCI0)) changed from 4 to 0 to enable full QE/CI using Chameleon's default PCI root value NB: This Yosemite installation being done using the usual manual method (i.e. no myHack or Clover tool), the (extracted) Yosemite vanilla kernel has to be copied to /System/Library/Kernels, the kexts provided in the bootpack are to be copied directly to /System/Library/Extensions and the cache rebuild with usual Terminal commands: sudo chmod -R 755 /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions sudo touch /System/Library/Extensions sudo kextcache -Boot -U / This particular process applies to the USB installer + target installation.

Indeed, that's what I use on my D630n; works OOB from SL to Yos.

Which version of the kext do you have? The attached is supposed to work Ok without the well-known cut-off (but I can't certify 100% as I never use the LAN connection). BCM5722D.kext.zip

Check the kernel logs available through Console app in Utilities.

Do not use VoodooPState, you don't need that. You need to post us a picture of your KP or post the details of the message.

Tried removing the HPET kext (keep a backup) from /S/L/E? It's known to sometimes interfere (though usually in cases where USB3.0 ports are natively supported)...

Hi, first of all, those tools and methods are not supported here but at TMX own web site, they develop them afterall, we don't know what's behind... Then, 3 comments: you may have to proceed with a DSDT patch to inject your nVidia card info to the OS and get it recognized. Or maybe adjust your BIOS settings if that's at all possible. what's the reason for rolling back to 10.9.5 AppleACPIPlatform kext? assuming the option does what its name implies, do not opt for Generate CPU States (P and C states) on Ivy/Sandy/Haswell CPUs.

if you have a corrupt cache, you can simply run myFix (quick) and that normally rebuilds it. Alternatively, use the following Terminal commands: sudo chmod -R 755 /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions sudo touch /System/Library/Extensions sudo kextcache -system-prelinked-kernel On rare occasions, we've had reports from users who had to delete the myHack.kext in /S/L/E and, in that case, you must run myHack and proceed with Install Utilities to restart the whole process again which includes the kexts installation and cache rebuild.

Your BT module radio must be disabled... https://osxlatitude.com/index.php?/topic/1824-bluetooth-adapters-latitude-d-series-inspiron-laptops/

Have a look inside the PS2Controller kext you've used. You might be able to remove the trackpad kext without affecting mouse operation. It certainly works on older laptops with ALPS trackpad.

If you use a patched DSDT, one other thing to keep in mind is the possible mismatch between the info in the DSDT and the features disabled in BIOS. I've experienced this on my Precision 670 workstation: I use a patched DSDT made of a raw table extracted with the SCSI controller set to ON. If I then disable the SCSI controller in BIOS, boot will end up in KP. You may try and verify this by manually bypassing the DSDT when you boot Yosemite, having disabled the trackpad in BIOS.

You could ignore Clover (it's kind of difficult unless you're an experienced Hackintosher) and use Chameleon instead. Install a recent version such as v2.2 r2377 or r2401. You'll have to manually do all those things that tools like myHack did for us in the background: create Extra folder and copy DSDT + boot plist + SMBios plist in it copy all add-on kexts previously placed in /E/E directly to /S/L/E manually repair permissions and rebuild cache with the usual Terminal commands: sudo chmod ... sudo chown ... sudo touch ... sudo kextcache ... You have those in details in my aforementioned thread. Good luck.

If you right click on the kext and select "Get Info", you'll see the version...

What was the error you got? The pack from the D620 will probably work as long as you have same screen res; otherwise, you may experience corrupted screen. Make sure you install Chameleon once you've booted OS X. At worst, boot your HDD via the USB installer bootloader, then install Chameleon. Grab a recent version like v2.2 r2377 or r2401, they work Ok on those systems with all existing OS X versions. They're all available at InsanelyMac.

I'm pretty sure one of the PS2 options of EDP does it, but I'll be damned if I could tell you which one… You could try them one by one, but you may lose keyboard and trackpad in the process, so make sure you have a backup method of some sort to fall back on your feet if/when things go wrong and revert to working set of kexts.

I've just achieved identical results on my D620 nVidia model, using the exact same principles but a different device id for the Quadro NVS 110M GPU (id 0x01d7). I've no monitoring other than the kernel logs though... <_> <key>MacBookPro5,1</key> <dict> <key>Vendor10deDevice01d7</key> <dict> <key>BoostPState</key> <array> <integer>0</integer> <integer>1</integer> <integer>2</integer> <integer>3</integer> </array> [...] [...) [...] Provided ControlLog parameter is set to 1 in the AGPM Info plist, the kernel log shows entries such as the following even after wake: Mar 18 13:55:22 d620_nvidia kernel[0]: AGPM: GPU = VID G-state set to 1 from 0, ControlID = 18. SW occupancy updated. Mar 18 13:55:24 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(2, 0): fHwPstate = 1 fFB = 0x8039c00 Mar 18 13:55:24 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()... Mar 18 13:55:24 d620_nvidia kernel[0]: AGPM: GPU = VID G-state set to 2 from 1, ControlID = 18. SW occupancy updated. Mar 18 13:56:28 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(1, 0): fHwPstate = 2 fFB = 0x8039c00 Mar 18 13:56:28 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(): state = 1. Calling fFB->setAggressiveness()... Mar 18 13:56:28 d620_nvidia kernel[0]: AGPM: GPU = VID G-state set to 1 from 2, ControlID = 18. SW occupancy updated. Mar 18 13:56:30 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(2, 0): fHwPstate = 1 fFB = 0x8039c00 Mar 18 13:56:30 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()... Mar 18 13:56:30 d620_nvidia kernel[0]: AGPM: GPU = VID G-state set to 2 from 1, ControlID = 18. SW occupancy updated. Mar 18 13:56:35 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(0, 0): fHwPstate = 2 fFB = 0x8039c00 Mar 18 13:56:35 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(): state = 0. Calling fFB->setAggressiveness()... Mar 18 13:56:35 d620_nvidia kernel[0]: AGPM: GPU = VID G-state set to 0 from 2, ControlID = 18. SW occupancy updated. Mar 18 13:56:38 d620_nvidia kernel[0]: AGPM: updateGPUHwPstate(1, 0): fHwPstate = 0 fFB = 0x8039c00 It's pretty safe to say this extends to other D830, M2300 or M4300 of similar specifications.