Hervé

Tried MBP9,1/10,1 SMBIOS? They're IvyBridge but those models have nVidia graphics. All MBP8,x have HD3000-only or dual HD3000/AMD graphics.

Make sure you define the correct path in BIOS if you choose UEFI mode. Caution with the OP's config file though because it carries some incorrect settings and that can lead to confusion. For instance: on the graphics side, he used the discrete nVidia GPU and correctly activated nVidia injection but kept some incorrect Haswell HD4600 Azul framebuffer layout-id at the same time, something obviously not applicable on a SandyBridge HD3000 platform. on the audio side, he used AppleHDA patches for ALC292 codec when the laptop appears fitted with IDT 92HD90 codec so it's quite normal he could not get audio through AppleHDA. on the SMBIOS side, he used MBP10,1 which is an IvyBridge platform with nVidia GPU. One could have expected SandyBridge models such as MBP8,1 (HD3000) or MBP8,2/8,3 (HD3000 + AMD). But maybe that was necessary to get the nVidia dGPU to work.

It's a research section so can you describe what have you done so far and where you got or what you achieved? If your thread is just to call on people to provide with instructions/files/guidance to install Sierra on your M6600, then you're in the wrong section. The EDP section does show: Models under research for EDP Want EDP support for your model? Create a thread with your progress and let's get started! As you gathered yourself, no Intel wireless are supported. Check the R&D->Wireless & Bluetooth re: compatibility for your Broadcom model. Unfortunately... The Intel 82579LM LAN card is very common to Sandy and Ivy Bridge laptops and fully supported with Mieze's driver or the older AppleIntelE1000e driver. You'll find those through a quick Google search or in the packs posted in E6x20/E6x30 guides. Re: audio, you'll have to identify the exact IDT codec fitted to your laptop. Dell often list it in the BIOS Info page. Did you check that? I've got a funny feeling you're going to tell us it's IDT 92HD90 in which case there are details of the AppleHDA patch all over the place, including in the packs posted in E6x20 guides. Alps Touchpad should be supported with Dr Hurt's recent driver versions (R4, R5, R6). They're available in his dedicated ALPS driver thread posted in the R&D->Keyboard & Touchpad section. Copies of those working drivers are also available in the packs posted in E6x20/E6x30/E6x40/... guides. Installation of OS X/macOS on an mSATA is no issue at all, as long as the laptop supports them. Not all systems are actually fitted with an mSATA or a combo mini-PCIe/mSATA/USB slot. Failing that, you can use a standard SATA-adaptor or a standard SATA SSD instead. I can't remember if that AMD dGPU is supported or not but if it isn't by default, the HD3000 iGPU will be. You'll probably have to patch your DSDT to inject the mobile SNB layout-id to the device listed at address 0x00020000 (could be called IGPU or GFX0 or VID or whatever). I would invite you to read and familiarise yourself with Sierra installation on other Sandy Bridge laptops so that you get to known the necessary requirements (such as DSDT patches for USB ports and so on). There are also existing threads for the M6600 which I believe you already found. Integration of computers into EDP relies on owners who have successfully installed OS X/macOS on their systems to provide us the necessary pack (bootloader config files, patched BIOS tables, drivers). It does not work the other way round... Someone has to be the 1st to do the dirty work for the benefits of the others. That's the spirit; all on a voluntary and free of charge basis.

Afaik, VGA/DVI/DP outputs off the HD3000 iGPU require the patched SNB FB kext. The necessary details are provided in post #5 of my E6220 guide. The port numbers of each individual output may be different on your dual-GPU E6520 of course, so follow the port identification process. Bear in mind that DP/HDMI outputs may only be available through the nVidia dGPU so disabling it through SSDT mod may be the root cause of your issue. You'd probably need to run only off the nVidia GPU to get all output ports working.

Safari is an integral part of OS X; the latest available version for any given release of OS X is always offered through the AppStore update.

You may have a duff physical connection. I'd remove the card and clean the connector + the slot.

Instead of Find: 01 00 00 75 17 Replace by: 01 00 00 75 25 which is obsolete in Sierra, the IOGraphicsFamily kext patch should be Find: 01 00 00 75 25 Replace by: 01 00 00 EB 25

Security updates often/usually re-instate vanilla kexts so if you had patched kexts in SLE, it's possible they got overwritten. You may want to rebuild your cache to begin with. Can't say I've used eSATA much but those ports usually work OOB afaik.

Just in case backlight got turned off, try [Fn-Insert] several times. Normally, there is no issue with HD3000 graphics and output to built-in LCD. Did you check the Display PrefPane and the SysProfiler Graphics tab to see if the built-in screen is registered?

I guess the patch is not compatible with that SD card reader then and you'll have to make do with VoodooSDHC kext.

If/when you get the "exit with status 77" message, just re-type the touch + kextcache commands to properly rebuild your cache. It did not so you won't have audio until cache is rebuilt. The IDT dummy kext can go to /L/E but the patched AppleHDA must go to /S/L/E or it won't load and get cached.

Try the attached revised DSDT. I suggest you save it alongside your existing one under a name like "DSDT2" and that you manually call it at bootloader level. It's been patched with a new device SDXC added under RP08 at address 0x01 as per IOReg info, i.e. it applies to O2 Micro device 1217,8320. Test this with VoodooSDHC kext removed but no guarantee it'll work of course... Revised_DSDT.aml.zip I wouldn't mind a zipped copy of your saved SysProfiler output. I'm wondering if your SD card reader wouldn't be USB-internal. Do you have a copy of your raw BIOS tables too (DSDT + SSDTs)?

1st thing 1st. Which model is it in term of graphics? Intel HD or nVidia? You cannot get full graphics acceleration on this model with 1st gen Intel HD due to unsupported eDP LCD connector type. As such, it's not worth wasting time installing OS X on those models. If you have the nVidia model, great; just make sure to use a patched DSDT where all references to EHCx USB controllers are renamed to EH0x and you install the USB injector kext.

Is wireless enabled/activated on the computer (BIOS, side on/off switch, keyboard soft switch)?

I invite you to browse the the numerous threads about the E6x20 before you post.

Ok, can you remove the VoodooSDHC kext, rebuild your cache then post a new IOReg output?

You'll find what you need in the guide section.

1st gen Intel HD based laptops need to follow this procedure to ascertain graphics support. You audio is based on codec IDT 92HD87B1/3.

Please refer to existing E6x20 guides. From El Capitan 10.11.4, please use Dr Hurt's PS2 controller kext.

I've reproduced the behaviour in my D630 by trying my Novatel WWAN module and my Apple BRCM94360CD in the WLAN slot. No WWAN module and no BT controller detected when cards fitted there! Unlike the D430's, the D630's WLAN slot is indeed only PCIe, not combo PCIe/USB like its WWAN counterpart.

Hmm, MacBook9,1 SMBIOS...

You'll find out if it works once you've tried it and you can do no harm in trying. If your device is directly attached to a device called IOPP, then patch that. Do not focus on any device called PXSX, that was just what the OP's DSDT device was called and, as it happens, it's a device name under which SD card readers are often defined in the DSDT of many Dell laptops. However, it's not systematic. If in doubt, please post zipped copies of your saved IORegistry output and of your DSDT.

Can't say whether it has adverse effect or not but why do you "Inject ATI" in the Graphics section of your Clover configuration file when you're clearly trying to run off the HD530 ?

There's a chance it could be listed in the BIOS settings; check it out. You may also try to update your local PCI ids database. Try the Update IDs button in DPCIManager app. Should it fail, install the lspci package as detailed here and make sure to update your local database through Terminal command sudo update-pciids. You may then re-run DPCIManager.

In the DSDT, make sure: 1) that your USB3.0 device @00140000 is named/renamed to XHC (rename all instances as necessary) 2) that you set OSYS to 0x07D6 for Darwin or Win2006: Scope (_SB.PCI0) { Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { If (_OSI ("Windows 2001")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP1")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP2")) { Store (0x07D2, OSYS) } If (_OSI ("Windows 2001.1")) { Store (0x07D3, OSYS) } If (LOr (_OSI ("Darwin"), _OSI ("Windows 2006"))) { Store (0x07D6, OSYS) } If (_OSI ("Windows 2009")) { Store (0x07D9, OSYS) }