Hervé

BCM5722D is available in all D630/D830 packs posted on the forum or in the bootpacks repository. There are several versions which work differently in 64bit-only OS X versions, so make sure to use the latest version available. Look at my D630 El Capitan thread in the R&D section for instance.

Afaik, installing or running OS X on PC hardware has never killed a motherboard! You'd have to run on seriously incorrect settings to damage the underlying hardware, like incorrect power management leading to sustained/prolonged overheating or something to that effect.

Check your hibernation mode in Terminal with command: sudo pmset -g Make sure to disable hibernation as it's a prerequisite to get sleep & wake to work Ok on a Hackintosh. If you have a sleepimage file in /var/vm, delete it: sudo pmset hibernatemode 0 sudo rm /var/vm/sleepimage For additional tranquility, you may even set your sleep image to null device so that no file ever exists and prevents wake/reboot: sudo pmset hibernatefile /dev/null

Like most Intel CPUs since Sandy Bridge, power management is not entirely natively obtained, it requires the generation of a CPU-specific SSDT. Improved power management and boost mode management can then be enjoyed. You don't need NullCPUPM with a Haswell CPU, just the kernel patch. Your poor 3D performance will be due to lack of suitable GPU power management.

Let's keep this thread to its's own topic please: DSDT fix.

+1 You should be Ok running SL or Lion in 32bit mode but you probably won't have any graphics support from ML. It's old hardware...

Yes, it would be most useful to load this 3rd party kext and rebuild the cache.

Make sure to use a SSDT created for your own Sandy bridge CPU, do not use a SSDT table generated for another CPU model.

It only seems to be difficult with the combination of Clover and UEFI mode. I've never had any issues with Chameleon/Enoch and legacy mode on Sandy Bridge or Haswell-based models such as E6220, E6320, E6420 or E6440.

Oh well, with a little 5min search, here you are: https://wikidevi.com/wiki/Netgear_WNA1000M http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true Use the 10.8 package. If the app won't run due to OS X version difference, just extract the kexts from it or modify the Info.plist of the app so that it matches your OS version.

We have a non-exhaustive list of supported/unsupported wireless devices here. The NetGear USB dongle that was tested and reported (by me) is the WNA3100M. You've mentioned a WNA1000M, can you post the PCI device id to identify the chip it's built on? This will greatly assist in establishing whether it is supported or not under OS X and finding the eventual driver. If the laptop is fitted with a RealTek RTL8111 LAN card, you may try the 10.7 drivers posted on their support web site.

Your /S/L/E folder is empty, i.e. the kext files are not written to the USB installer. But I see a lot more is missing in /System/Library... I'd say you either missed a step in the procedure or there is something very wrong with the installation package you're using or the process you're following.

None that was discussed or reported here... Please post your M6700 hardware specs (exact CPU model, graphics, audio, LAN, wireless, bluetooth, card reader, etc. Battery, RAM, DVD, we don't care). I suspect it'll be close to the M4700 for which I've seen an existing thread listing an Ivy Bridge CPU and some unsupported discrete AMD GPU. This meant only the integrated Intel HD4000 GPU could work. But, on paper, this kind of laptops can theoretically run Mavericks 10.9, Yosemite 10.10 or El Capitan 10.11. Mountain Lion 10.8 is a bit old and obsolete these days...

Yes, PCs with Sandy and Ivy Bridge CPUs require AICPUPM kext to be patched to avoid kernel panic. Using NullCPUPM voids the vanilla AICPUPM that causes the panic.

Please provide your own E5520-specific hardware specs for items that may vary such as wireless card and bluetooth module. LAN, audio, graphics, are all already known.

Erm... You browse through the USB key file system! I assume you know how to tick the case to display disks in Finder preferences, right?

Ideally, LAN interface should be en0 and wifi en1. This to prevent issues with AppStore, FaceTime, etc. You can easily fix that by deleting the interfaces from Network PrePane and all the plist from /Library/System/Preferences, reboot and let the system auto-discover/install the network elements.

Dual booting has extensively been discussed on the forum; please use the Search facility before posting.

https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/

Please read existing threads and articles on "performance tuning" or Pokenguyen's AIO guides at IM. https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ http://www.insanelymac.com/forum/topic/298027-guide-aio-guides-for-hackintosh/?do=findComment&comment=2019604 Then, there is the existing X201 power management literature on this forum. Eg: https://osxlatitude.com/index.php?/topic/7756-x201-power-managment/ This being said, your CPU speed stepping appears to work Ok since your 1st screenshot shows a CPU speed of 2.0GHz with a x15 multiple (which is a correct speed/multiplier arrangement on your Arrandale CPU) and an average CPU speed of 1.43GHz...

Nothing new; all security updates are like OS version/combo updates: they re-instate vanilla kexts + kernels. As such all Sandy + Ivy Bridge systems need to repatch/replace AICPUPM and all Haswell systems need to replace the kernel with the patched one after this new security update.

From what kind of system do you use that Carbon Copy image?

You sure it's not the Haswell CPU reset? You need the Haswell-patched kernel...

Initial issue obviously solved. Please open up a separate thread if you have issues. However, most matters have long been discussed wide and large for these D Series laptops, so please use the Search forum facility and read up existing threads beforehand to try and find an existing solution.

The old Protector Suite software worked fine with older Latitude D Series + Precision M Series laptop up to Snow Leopard (those laptops use a totally different fingerprint scanner hardware then the E Series though). For Lion and ML, you had to switch to Authentec TrueSuite software. When Apple released Mavericks, TrueSuite support was affected and I remember reading that login through finger scanning no longer worked. Authentec was bought by Apple in July 2012, then all support and software development ceased at the end of that year. I can't say if TrueSuite would install or run in recent OS X versions such as Mav/Yos/EC or if it would support the BCM5880 chip (though I doubt it) but there's only one way to know I guess... http://web.archive.org/web/20130306124038/http://support.authentec.com/Downloads/Mac/TrueSuite.aspx