Hervé

Or one can check his syslog/dmesg... In Sierra, one may use: log show | grep ALPS

Your desktop computer being fitted with a Pentium E5700, it's a no go for Sierra. You need a SSE4-capable CPU to install and run Sierra. Until you swap out your CPU by a Sierra-compatible model (e.g. Core2Duo E8xxx), you're limited to El Capitan. Your nVidia GeForce G210 remains supported all the way to Sierra. It's a long time since I installed anything on a desktop but I guess the same principles used on laptops should apply. You'll have to start by patching your DSDT and rename your USB2.0 controllers from EHCx to EH0x + create or use a USBInjector kext in order to retain fully functional USB ports. After that, you can follow the process detailed in any of my laptop guides to create your own USB installer. Regarding your kexts, I don't see why you would ned to retain NullCPUPM as long as you use a correctly tuned FakeSMC. You should be able to enjoy native CPU SpeedStep. Patched_10.7_AppleRTC is obviously obsolete in Mav/Yos/EC/Sierra so replace it with the correct version if you still need it (probably not since it's of no effect in Mavericks). Pre-patched copies are available here. If you wish to retain lspci facility, you'll also have to manually install the package that myHack used to install transparently. You can extract the necessary files from the myHack app (they're in the Resources folder) and copy them to the destination folders shown in myHack's tree structure. Once done, update your local database through Terminal command sudo update-pciids. Details are available here. Most people don't bother with lspci these days and just use tool DPCIManager.

Yes, you can copy the existing SSDT for the i5-3320M and paste ("drop") it in your own installation. Or you can follow the final statement of the 1st guide you referred to and generate your own The latter would have been quicker than the time it took you to pop the question.

Not under OS X...

If the Intel is 82579LM, it's the same as fitted to E6x20/E6x30 models. The AppleIntelE1000e kext should therefore work. If the Ethernet is not showing in DPCIManager, there's a good chance it's disabled in BIOS...

On E5x30/E6x30, BIOS must not exceed a given version beyond which graphics artefacts is systematic. If BIOS does exceed the maximum recommended versions, downgrading to the desired version requires to first downgrade to the lowest possible version before subsequently upgrading to the desired one. Eg: E6230 with say BIOS A16. Maximum BIOS version for OS X is A11. To downgrade to A11 and have fully supported graphics, it's necessary to 1st downgrade to say A02 version then upgrade to A11. A direct downgrade from A16 to A11 does not fix graphics defects. It appears that Jake recommended not to exceed BIOS A06 for the Latitude 6430u. As such, downgrade to A02, then upgrade to A06. This may sound like a silly remark, but in case the 6430u did actually boot to OS X desktop, try [Fn-Insert] several times in case the backlight was set to dark...

As usual, please post your hardware specs (PCI ids) in order to identify your LAN card and the likely kext to drive it. Manufacturer's support web site is usually a good starting point...

You'll also be able to boot without cache, provided you inject mandatory kexts such as FakeSMC from /E/E through boot option KernelBooter_kexts=Yes.

Try to manually inject the various values of the Capri Framebuffer until you find out the correct one. It's usually 3 or 4 on laptops with HD4000 graphics. With Enoch, you can inject these values via boot parameter IntelCapriFB=xx, where xx is in the range 0 to 11. If you use Clover, you can adjust this in the Config.plist through the Clover Configurator.

You need to follow the guide a little better: you did not check CoreStorage presence and you clearly have a logical drive in place.

Seems your graphics are not initialising. You seem to run a really old BIOS version on that 6430u. I'd invite you to update but remember that you may not be able to run past a given version like on the E6x30 Series. Try out latest version A11 anyway. Bear in mind that the Latitude 6430u is not an 'E' model even though it's close in terms of specs (it's specifically based on ULV CPUs). As such, I'm not 100% certain that you can re-use the DSDT of the E6x30 series. Have a look at the existing threads related to the Latitude 6430u in this very section. Refer to this old Mavericks guide for reference (especially DSDT): https://osxlatitude.com/index.php?/topic/7133-dell-latitude-6430u-with-i7-3667u-hd-4000-mavericks-1094/?hl=6430u

Boot in verbose mode to se when it hangs.

No, do not attempt to upgrade to anything past Lion. OS X last supports the D620 GPUs (whether Intel GMA950 or nVidia Quadro NVS 110M) in Lion 10.7.5 and in 32bit kernel mode. Beyond Lion, you'll have no graphics support/acceleration so do not bother. Pleased read the thread I linked to previously. To get fully functional Sleep/Wake operations, you'll need to: 1) set hibernate mode to 0 2) remove any sleepimage file in /var/vm I also recommend you align screen sleep on computer sleep in the Energy Savings PrefPane. Reason for that is that if you let the screen sleep on the D620 nVidia, it only wakes to a dark screen and you'll have to put the laptop to sleep, then wake it to recover display.

Try the following: Delete myHack.kext from /S/L/E Delete your /Extra folder Run myHack ans install your Extra again (pointing to the downloaded pack that you'll keep in, say, the Download folder).

It's a well know fact that every update installs a vanilla AppleHDA which therefore requires re-patching. The alternative is indeed to replace the new vanilla kext by an earlier pre-patched Sierra version.

You can manually update the database file as specified on Pike R Alpha's repo.

You update through combo update or via Apple menu. As simple as that.

There's no need for the nv_disable=1 parameter, that laptop has no nVidia GPU. The AMD GPU is not supported so it won't affect the system in any way. You've got the Intel GPU injection correct but you've not mentioned the Azul Framebuffer. The E6x40 laptops with HD4600 graphics require you to inject Azul FB #12, i.e. layout-id 0x0a260006. With your HiRes LCD, you may also need to set DualLink to 1.

It normally works with the PS2 kexts provided in the pack. Make sure you've run myFix after applying the pack.

Are you using myHack with the posted pack? Try and specify -f -v flags at Chameleon prompt.

1st make sure to use the latest D620 BIOS version A10 and a Core2Duo CPU (most D620 have a FSB667 Merom T7x00 CPU). Then configure the BIOS parameters as per the recommended settings posted here. To build your Lion USB installer, use myHack v3.1.2 or v3.3.1 + the Lion bootpack available here. This will get you to a known working installation.

You would not need to re-install the OS from scratch... Just the bootloader.

You gotta love Chameleon!

Erm... your SysProfiler output is from Mavericks... Not really what I was looking for. There is no sign of your DW1550 built-in BT module in your SysProfiler so it's clearly not registering as a USB device. I also note that you don't appear to use the latest optimised Mavericks' pack available here. Can you please post the saved SysProfiler output taken from El Capitan or Sierra with the DW1550 installed and the CSR dongle taken off? Whilst you're at it, also post: 1) your complete zipped /Extra folder (you're using Enoch, right?) without the Themes subfolder to minimise size 2) a saved IOReg output from IORegistryExplorer (both from El Capitan or Sierra) If you have an internal Bluetooth module such as a DW350 or DW360, disable the Internal Bluetooth in BIOS; otherwise, it'll take precedence... Your USB ports & devices should look like this under Sierra: As a test, I installed a spare Apple BCM94360CD (Combo Wifi 802.11ac + BT 4.0 card) in the WWAN slot of my D630. As expected, the Bluetooth module of the card is properly detected and listed as an internal USB device:

Yes, you can run El Capitan and/or Sierra with CsrActiveConfig set to 3. That's what I use on all my Hacks, E6230 included. Reboot without cache when you 1st call on the revised value and rebuild your cache thereafter.