Hervé

That's not the correct way to install it and that's not going to work. I assume you use a myHack USB installer and you need to run myHack to install the Extra folder on the key. It's the only way kexts will be taken into account and the old ones removed. NB: there's no need to quote every single message you directly reply to.

So you used the pack I had posted in post #11 of that thread you linked? How did you install it on your USB installer? You could probably upgrade your BIOS to the latest version A10. Make sure it's configured as per the D620 recommended settings provided here.

Restart and when Chameleon kicks in, press any key to interrupt the bootloader and manually add -f -v flags; this should then show you where it hangs. You did not say so I'll ask: do you have the GM950 model or the nVidia?

Well go through the file and list your various hardware components in a similar fashion to those posted here for Dell E6220 or here for HP 8560W for instance. There are sites on the Web that'll help you identify hardware by PCI ids and vice-versa.

The overall process used for those laptops is fully applicable to your HP laptop, not the bootpacks. Those bootpacks contains BIOS tables specific to the models + drivers (kexts) specific to the hardware components fitted to them, so you cannot reuse them. Only some drivers may be re-used if you have the same hardware. Other than your IDT 92HD81 (codec 7605) HDA audio (different from what is fitted to the E6x20 or E5x20) and your unsupported Intel wireless card, you've not listed the rest of your hardware specs; maybe you can start with that: LAN, bluetooth, USB, card reader, video outputs, trackpad, etc. List the exact model specs, ideally the vendor + device PCI ids. Example: Intel 82579LM GigEthernet, O2 Micro 0Z600GJ0 SD card reader, ALPS V3 Rushmore TrackPad. Please note that your HP laptop will probably require the lapic patch to avoid a lapic KP. Can be applied on the fly through Enoch or Clover or by limiting CPU to 1 single core (not the desired long term/permanent option).

Lookup existing guides for SandyBridge/HD3000 laptops in our EDP->Guides section. Obviously the DSDT/SSDT specific parts won't be applicable to you at this stage. You'll have to extract and patch or get your tables patched in due course. You will need to mess with your laptop (it's the only way to learn and you will fail several times before you succeed) but you can't break or damage anything. I suggest you experiment using a dedicated hard drive.

Well anything related to wireless and bluetooth obviously! I cannot guess what you may have done in that respect with your Clover configuration, what kexts you might be injecting through Clover or what kexts you might have added to /S/L/E or /L/E. I've no crystal ball...

Other than the Intel wireless which will need replacement (keeping in mind the likely HP whitelisting), your listed specs are compatible. Post your progress and results as you go along.

Please open up your own separate thread if you require support on that matter. SNB FB patches for HD3000-only models are well known and documented.

Well, it seems you got closer since the app icon with the little phone appears on your Hack now. Check your Config.plist and/or set of kexts for any rogue entry/driver.

'seems it's unsupported under Sierra then... Desktop GT610 has similar issue and is based on same/similar GF119 Fermi chip.

I let you do your homework to begin with but: 1) check the Extensions section of your SysProfiler 2) do a forum/Google search on USB ports under El Capitan/Sierra

Is Mieze's kext loading? Check the in your SysProfiler. Re: USB, did you patch the DSDT USB controllers and install a USB injector kext?

Jake gave you the correct patch for Sierra. Your initial patch is obsolete.

Hmm, it works fine between my E6230 (Sierra + Apple BCM94360CD card) and my iPhone 6s for compatible apps such as Safari or Maps for instance. Assuming: both devices are on the same wireless network (watch between 2.4/5GHz networks with same SSID, they're different networks) both devices are connected on iCloud with same id both devices have BT enabled both devices have handoff enabled you should be Ok. http://appleinsider.com/articles/15/04/18/how-to-enable-apples-handoff-feature-between-your-ios-devices-and-mac Which SMBIOS are you using on your E6530? Should be MBA5,2/MBP9,2 or similar. Seems more like a configuration issue somewhere imo.

Avoid these tools to rebuild the cache because they probably do not report errors on failed rebuilds. It's written all over the forum if you bothered searching but you manually rebuild the cache in Sierra with the following commands: sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / Re-enter the command if you get and error 77 something. Ok with 17. Alternatively use: sudo touch -f /S*/L*/E* sudo kextcache -system-prelinked-kernel ` What makes you say Handoff only works in 1 direction?

Rebuild your cache. Clover on-the-fly patches only apply to cached kexts.

Start with NullCPUPowerManagement until you've applied the AsusAICPUPM patch and generated your own CPU-specific SSDT. If you re-use an existing one that was made for another CPU, you'll have problems. You should not have anything at all to patch in DSDT re: CPU. If you want to disable the AMD dGPU, extract your raw BIOS tables and identify the SSDT where it's defined. That's where you're likely to find _ON / _OFF functions that you can call as externals in your DSDT. I would not waste much time on a modded BIOS re: MXM graphics cards. Most of the time laptops use their own specific physical connectors. So if you want to swap your AMD model by another one, look for the nVidia alternative that can be fitted to the M6600.

How do you actually apply the patch? You may do it wrong...

For Ethernet card, it appears your're using Mieze's driver, so you should be Ok as long as you use v2.1.0 or above. But the kext may not inject through Clover so move it to /L/E, repair persmissions and rebuilt your cache. Reboot and check if you then have the Ethernet port working. I assume it's enabled in BIOS.

What model of wireless & bluetooth device do you have fitted to your E6530?

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.