Hervé

Correct. https://www.intel.com/content/www/us/en/support/graphics-drivers/000005556.html

Did you disable hibernation? You can check status with Terminal command pmset -g. Also check your EnergySaver PrefPane and disable any option that may wake the computer from time to time. Also make sure that BIOS parameters such as Wake on LAN are disabled. Difficult to say anything about your wireless until you specifiy the model of the card you use. No reason why you would not be able to regenerate a CPU PM SSDT but you can re-use the table you used in El Capitan. There's no need to regenerate a new table each time.

As stated in post #1, it's the IO address of the audio device. You'll find it in the DSDT or in IOReg via any explorer tool such as IOJones, IORegistryExplorer, ioreg command line (e.g.: ioreg | grep HDEF) or similar. * DSDT example: Device (HDEF) { Name (_ADR, 0x001B0000) // _ADR: Address [...] }`* IORegistryExplorer example: * command line example: E6230:~ admin$ ioreg | grep HDEF | | +-o HDEF@1B In the above examples, HDEF audio device is found at address 0x001B0000. In the Info.plist file, this will be reflected as follows: [...] <key>HDEFAddress</key><array> <string>1B</string> [...] If the device were at address 0x001F0003, the entry in Info.plist would be: [...] <key>HDEFAddress</key> <array> <string>1F,3</string> [...] Basically, it's written as a single byte (without heading zeroes) or a pair of comma separated bytes (without heading zeroes) if lower byte is not null (0x0000).

'says it all in the D630 thread: For models with Penryn CPUs only - - - - - - Please note that: Sierra requires a Penryn CPU with SSE4 instructions set [...]. Merom CPUs [...] do not have such instructions set and do not allow Sierra installation. - - - - - - As such, as long as your laptops have the required CPUs, you can proceed exactly the same way as for Yosemite and/or El Capitan, adjsting the SMBIOS if necessary.

No, it's more a matter of having the correct/supported Bluetooth module in place. https://support.apple.com/en-us/HT203106

Moving to the non-E forum section... You don't need an earlier OS X version to begin with, no. I invite you to consult the other 6430u topics found in this section where you'll find indication of the highest BIOS version to use (I think it's A06). Use the forum Search facility on "6430u".

Why don't you download Sierra installation app off AppStore and proceed with a full vanilla installation rather than keep trying with a distro? You can easily create a fresh USB installer and practice vanilla installation on a separate partition.

https://osxlatitude.com/index.php?/topic/7554-broadcom-bcm4360cd-80211-ac-wifi-and-bluetooth-combo-card/

Yup, see previous answers.

When you plug HDMI in, do you then manually select HDMI audio at all? Isn't it visible in the audio PrefPane? The HDMI display has audio capabilities, right?

DW380 ids are listed in my E6230 guide... It's a simple matter of creating a new model entry in the kext's Info.plist file by copying/pasting an existing entry and adjusting the device ids to the DW380's (in decimal). But don't expect all macOS Bluetooth functionalities to work or work well. If you want full AirDrop and full BT functionalities, opt for an Apple BCM94360CD with adapter board. That'll work 100% OOB. Re: HDMI audio, erm, you do have audio with patched AppleHDA, right? CapsLock is an old and known matter. No fix for it.

Try using the forum Search facility or browse through this specific Lenovo section.. Thank you. https://osxlatitude.com/index.php?/topic/9687-help-me-install-sierra-on-z51-70/

Moving to the right place...

You're using the HiRes Capri layout 0x01660004, therefore you need to patch the Capri framebuffer kext as per the recommended setup in your Clover config. See here for details. As detailed in my E6230 guide, DW380 will work once you inject its device id in the Broadcom transport kext. This can be done either through FakeSMC (you add the necessary entry to the kext's Info.plist) or through direct patching of the IOBluetoothFamily PlugIn kext. Patching principles are explained here. An example of how you can inject info through FakeSMC is available here. This make for a much better and far more sustainable patch than direct Broadcom transport kext patching which would need to be repeated after each update and/or upgrade. NB: Remember to compress (zip) files before you attach them. JPEG can be attached "as is", they're already compressed.

Make sure you've setup your system for HiRes LCD: 1) Capri layout 0x01660004 2) DualLink set to 1

Dell no not whitelist their laptops; that's specific to HP and Lenovo. So you can insert any card you want in your E6430.

All cards based on Atheros AR9285 chip will work once you inject the compatible statement in DSDT or once you patch the Atheros40 kext and inject the necessary PCI id.

You can disable USB ports in BIOS. But if your PC suffers from physical damage after a fall, you ought to wonder if it's worth using it...

Explain "it does not work"... You'd obviously only repair permissions to /L/E and/or /S/L/E and rebuild your cache if you'd added or made modifications to kext(s) there. If you're injecting kexts through Clover EFI folder, then you'd indeed be wasting your time rebuilding your cache. Anyway, you stated you "finally discarded" the OS X/macOS installation, so matter's closed I guess.

https://osxlatitude.com/index.php?/topic/9690-yosemite-on-z51-70/

It would be nice of you to do so without anyone asking and also explain the changes you made. This way, you can pro-actively contribute favourably to this thread and the community.

Try and copy your driver to /L/E and rebuild your cache as opposed to inject the kext. R4 (or is it R5?) works perfectly for me under 10.13 DP1 on Dell E6230 and E6440. Same once you replace the TrackPad PrefPane to be able to configure add-on stuff like TouchPad clicking.

Just to confirm that cDock v2 which worked perfectly under Sierra still runs perfectly under High Sierra 10.13 DP.

And the old D630 girl rolls again! There too, I just re-used files from my Sierra pack.

We'll assume it's the nVidia model. Based on your short description, it sounds like you're not initialising graphics. I don't understand why you would need or want to replace after an update from 10.9.4 to 10.9.5 when it's actually part of the update. You also seem to be using Enoch so rather than boot without cache (-f or KernelBooter_kexts=Yes), rebuild it!