Hervé

There used to be a bootpack for the D520. Maybe Dinesh kept a copy somewhere in the archive data. I would not expect any specific kexts for GMA950. All D420/D430/D620/D820 ran SL with vanilla kexts as far as I know (and I've had 2 of those between my hands for some time now with a brief spell with a D420).

Battery indicator should work Ok with one of the latest ACPIBatteryManager from RehabMan (v1.6x).

And by now, you should know that Intel wireless are not supported in OS X... Do not confuse Wireless card and on-board LAN/Ethernet card.

It's not just legacy BIOS mode that's required. HDD mode is expected to be set to AHCI for OS X installation to succeed. On these laptops, the HDD default mode is often set to RAID...

You misunderstood: I'm not talking about the partitioning of the USB installer but that of the target installation disk... I've assumed your USB installer was created properly and could be booted up to OS X installation screen.

But bear in mind that Dogbert's published code/tool will not work on Latitude E Series BIOS lock... It only works on older Latitude D Series and/or older Inspiron models.

Try to post us the details of your LAN hardware as detected so that we can identify what you have; these details can be obtained through tools such as DCPIManager or lspci -nn Terminal command if you've got the lspci package installed (myHack does that). For example: or E6220:~ admin$ lspci -nn pcilib: 0000:00:02.0 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) 00:16.3 Serial controller [0700]: Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4) 00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4) 00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b4) 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation QM67 Express Chipset Family LPC Controller [8086:1c4f] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04) 02:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [8086:0082] (rev 34) 09:00.0 Network controller [0280]: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) [168c:002a] (rev 01) 0a:00.0 SD Host controller [0805]: O2 Micro, Inc. Unknown device [1217:8221] (rev 05) 0a:00.1 Mass storage controller [0180]: O2 Micro, Inc. Unknown device [1217:8231] (rev 03) E6220:~ admin$

Indeed, you have full graphics acceleration.

Is this an Optimus system?

2nd (or final) stage boot issue is just a short screen garbled. It does not prevent reaching OS X desktop or enjoying full graphics acceleration. Make sure the patch you've posted above applies to EC because, as far as I remember, it differs between versions of OS X.

This is a typical message returned either when attempting a full vanilla/standard installation on a disk not partitioned GPT. Either use GPT partitioning of the MBR patch to be able to install OS X on an existing MBR-partitioned disk.

2nd boot stage garble is a well-known glitch affecting most if not all Hackintoshes since Yosemite. It needs IOGraphicsFamily kext to be binary patched. In EC, it should be something like replacing hex string 0100007517 by 0100007417.

Sorted. No hardware monitoring possible without FakeSMC plugins... and no AGPM tuning if kext has typos or duplicate reserved words...

I guess your FakeSMC kext is not tuned properly and you don't have SpeedStep anymore.

Your revised AGPM kext patch is now correct: Vendor set to 10de, device set to 06eb and control-id set to 18. I can't really say why HWMonitor would no longer display the CPU and/or GPU info, other than it's probably due to an error you made in your FakeSMC tuning.

Your AGPM patching is incorrect. You need to read the thread throughly and apply the right modifications. If you've retuned FakeSMC to MBP5,1 keys, make sure to switch SMBIOS to MBP5,1 too.

Did you configure AGPM according to the info detailed here? I see you're using MBP5,2 profile and, I presume, associated SMC keys. Any reason for that? We usually recommended MBP5,1 with SMC keys 1.33f8/smc-mcp for that Latitude model. Your CPU T° look very high at LFM (x3, 800MHz)! Male sure you actually select P States + C States activation in your Clover config file. It's required for proper Core2Duo CPU power management.

Is there a reason why you boot in safe mode (-x)? On the other hand, I would recommend you initially bypass the cache (-f flag).

It'll work without the typos (and without the text between brackets)! Is it really that difficult to properly type a couple of command lines?

Dell workstation often use a default PCI root value of 4 instead of 0 in their DSDT. A such, try and add bootloader option PciRoot=4.

Ok, that's much better. You can now refer to the list of supported and usupported wireless cards available in thread I linked to in post #13.

Unfortunately, that specific section of the SysProfiler does not necessarily reflect the true device id of the fitted Atheros card. You would need to use a tool such as DCPIManager or the lspci package to use lspci -nn Terminal command. 0x147c is not the real device id of your card.

It's not a system we already have in support here, so you'll be the guinea pig. You may follow a classic Clover installation process or a classic manual process with Enoch bootloader. You'd have to start with a minimal bootpack using just the basics such as FakeSMC + PS2 controller kexts. Once you identify the rest of your hardware (LAN, audio, etc.), you may add any necessary kexts as required. Typical manual installation, with Enoch bootloader, from an existing Mac or Hack, would include the following: 1) 10.11 USB installer creation Double click on InstallESD.dmg found in Install OS X 10.11 El Capitan.app/Contents/SharedSupport to mount the dmg image Then, using Terminal app, mount BaseSystem.dmg (hidden file) open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg Use Disk Utility to restore the contents of BaseSystem.dmg on a USB key (or HDD partition) formatted Mac OS extended (journaled). Remove link for Packages in folder System/Installation of your USB key rm /Volumes/OS\ X\ Base\ System\ 1/System/Installation/Packages Copy folder Packages located in InstallESD.dmg to folder System/Installation of your USB key cp -R /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System\ 1/System/Installation Copy the 2 hidden files (BaseSystem.dmg & Basesystem.chunklist) of InstallESD.dmg to the root of your USB key cp /Volumes/OS\ X\ Install\ ESD/BaseSystem.* /Volumes/OS\ X\ Base\ System\ 1 USB installer should now have all the required OS X files and packages installed 2) USB installer finalisation: Enoch bootloader + bootpack installation Run Enoch r2795 (latest at time of writing) and install on the USB installer Enoch-rev.2795.zip Copy the Enoch r2795 installer package to the root of the USB installer Unzip the attached minimal bootpack and copy the resulting Extra folder to the root of the USB installer Essential_bootpack.zip Copy all kexts from folder Extra/Extensions of the pack to folder /Library/Extensions of your USB installer, then repair permissions sudo chmod -Rf 755 /Volumes/OS\ X\ Base\ System\ 1/Library/Extensions sudo chown -Rf 0:0 /Volumes/OS\ X\ Base\ System\ 1/Library/Extensions Create a folder called Kernels under /System/Library (normally, it won't exist at that stage) Copy the El Capitan kernel to /System/Library/Kernels. Copies of the kernels are available here. 3) 10.11 installation on target system Boot the 10.11 USB installer (it may take a little time to kick in) If/when prompted for USB keyboard and/or mouse at installer startup, just press [ENTER] or [sPACE] twice At OS X installer main screen, open up Disk Utility in Utilities menu If applicable, partition your target disk in GPT/GUID scheme Create your target 10.11 partition and format it as OS X Extended Close Disk Utility and proceed with OS X 10.11 installation as usual 4) Post-installation fine-tuning Reboot the 10.11 USB installer (it may take a little time to kick in) If/when prompted for USB keyboard and/or mouse at installer startup, just press [ENTER] or [sPACE] twice At OS X installer main screen, open up Terminal in Utilities menu Identify your freshly made 10.11 partition df Copy the Extra folder from the USB installer to the target 10.11 disk partition cp -R /Extra /Volumes/<your 10.11 partition name>/ Reboot the 10.11 USB installer, press a key at delay bar (or F8) to interrupt boor process and select your freshly made 10.11 disk partition to boot El Capitan for the 1st time Complete the 1st boot installation finalisation Once at the 10.11 desktop, run the Enoch r2795 package from your USB installer to install Enoch on your disk drive; it should be installed on the 1st partition Eject the 10.11 USB installer and put it aside Copy all kexts from /Extra/Extensions to /Library/Extensions, where all kexts should go from now on. Ignore and acknowledge the error pop-up messages related to kext incorrect permissions/installation Rename /Extra/Extensions to /Extra/Old_Extensions Open up Terminal to repair permissions and rebuild cache sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / Reboot your finalised El Capitan installation NB: this is a kind of generic installation process and does not obliterate any requirement you may have to use a patched DSDT or add bootflags or options I have not mentioned.

Afaik, Cookbook only supports Core2Duo CPUs and nothing else. It's quite an old tool nowadays. If you have an Arrandale CPU, it just won't work... But you should be able if you tune your system with SMBIOS + FakeSMC and activate P States + C States generation.

Generally speaking, Yosemite is easier to install than El Capitan, mostly due to significant changes Apple brought in EC with regards to USB management. Motherboard and CPU models won't be any issue. Things that may not work depending on hardware are items such as LAN, audio or SD card reader. Post your hardware specs if you want more feedback on likely compatibility of your NUC with OS X, but, on paper, it should be Ok.