Hervé

https://osxlatitude.com/index.php?/topic/2467-dell-latitude-d430-intel-gma950-ml-with-full-qeci/ --> EDIT - 20Aug 2014: ------------------------- Bootpack edited following report of missing Broadcom LAN kext. Pack is now fully loaded with all necessary kexts, modules and plists and no post-install EDP is really required for hardware fine tuning.

Which card do you have? Are you sure it's enabled in BIOS and that the left-hand side switch is not on the Off position?

Yes, I confirm.

Identify your card and patch accordingly if necessary... https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/

Look for the SSDT generator script at Piker Alpha or RampageDev's blogs. For audio, did you try the VoodooHDA + AppleHDADisabler at all?

You battery drain issue could be due to lack of proper CPU power management. 3 things to consider/check/deploy: . the use of a suitable/recent FakeSMC kext . generation of a CPU-specific SSDT file (for Turbo boost + intermediary CPU multipliers) . use of HWMonitor tool to monitor CPU speed stepping/power management

Are you using a SSDT file generated for your specific i5-3320M CPU? If not, you're highly likely to encounter CPU power management issues for sure. You can generate your own SSDT using the well-known generator script. It's available from Piker's or RampageDev's blogs. You'll easily find it along with full instructions. Then, to avoid the need to boot without cache (-f flag), I suggest you manually rebuilt your kext cache. From Terminal, run the following commands: sudo touch /System/Library/Extensions sudo kextcache -Boot -U / Of course, make sure to boot with the option kext-dev-mode=1.

Good. You can ignore the "ML update/installation failed" messages, most of our Hackintoshes experience that with ML.

When I output display to my Sony HD TV through HDMI, I have to use the underscan feature to adjust the picture so that it fits properly on screen.

I would expect you to need a serial number that appears like a real Mac one. They do not start with "VM". Download Chameleon Wizard and go to the SMBIOS tab and you'll see the type of number AppStore will expect.

What's the problem with the battery indicator? Percentage charge indicator is something you can hide through the Finder bar icon. No DSDT patch involved...

For those who need an extracted copy of the Yosemite kernel to build their manual Chameleon/Enoch-based USB installers, here are copies of the various kernels that have come out so far (pre-release/DP kernels excluded): Vanilla kernels for Core2Duo/Core2Quad, Arrandale and Sandy/Ivy Bridge CPUs: Vanilla_kernel_10.10-10.10.1.zip (Darwin 14.0.0) Vanilla_kernel_10.10.2.zip (Darwin 14.1.0) Vanilla_kernel_10.10.2_SecUpd2015-002-003.zip (Darwin 14.2.0) Vanilla_kernel_10.10.3.zip (Darwin 14.3.0) Vanilla_kernel_10.10.4.zip (Darwin 14.4.0) Vanilla_kernel_10.10.5.zip (Darwin 14.5.0) Patched kernels for Haswell, Broadwell and Skylake CPUs: Haswell_patched_kernel_10.10-10.10.1.zip (Darwin 14.0.0) Haswell_patched_kernel_10.10.2.zip (Darwin 14.1.0) Haswell_patched_kernel_10.10.2_SecUpd2015-002-003.zip (Darwin 14.2.0) Haswell_patched_kernel_10.10.3.zip (Darwin 14.3.0) Haswell_patched_kernel_10.10.4.zip (Darwin 14.4.0) Haswell_patched_kernel_10.10.5.zip (Darwin 14.5.0) Good working AMD kernels: Bronya_kernel_10.10_RC7.zip (Darwin 14.0.0 - works extremely well from 10.10 to 10.10.4) Bronya_10.10.5_kernel.zip (Darwin 14.5.0) -> more of those available at InsanelyMac Patched AppleIntelCPUPowerManagement kexts for Sandy/Ivy Bridge CPUs: 10.10.3-10.10.5_patched_AICPUPM.kext.zip Patched IOGraphicsFamily kexts for Intel HD GPUs: 10.10.5_patched_IOGraphicsFamily.kext.zip NB: kernels go to /System/Library/Kernels as "kernel"; patched kexts go to /System/Library/Extensions Patches courtesy of Rehabman & Pimentel and his tools as published at InsanelyMac. perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x00\x00\x00\x00|g' kernel perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x00\x00\x00\x00|g' kernel perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x00\x00\x00\x00|g' kernel

HDMI certainly is. Jake having provided details for the Azul framebuffer patch, I was able to verify HDMI operation on my mobile HD4600-based Latitude E6440 laptop as described here.

On a 'native' Hackintosh, a SMBIOS plist is used to simulate a real Mac model and generate a serial number. You're probably missing that specific part and it's one of the key components required to be able to run/log in AppStore.

So you already have your answers.

It's not universal, no. Wireless support totally depends on the wifi hardware fitted to the computer. Some cards work OOB, some work with patched kexts, some work with dedicated added software/kexts and some do not work. So you need to identify what you currently have. Please note that Intel wireless cards are not supported under OS X (Apple not using such Intel hardware in real Macs, there are no drivers). If you can't replace the existing card, you may opt for a small USB dongle. There's a non-exhaustive list of supported/unsupported cards in R&D->Hardware->Wifi forum sub-section.

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.