Hervé

You have not generated your CPU-specific SSDT and, as such, have no native CPU SpeedStep. Yet, you have a copy of the SSDT generator script in the ACPI folder. Why don't you run it?

Does the guide say you need a different DSDT for different CPUs? No. Does it say you need a different SSDT for different CPUs? Yes. Of course, it does; this is directly linked to obtaining CPU SpeedStep... Guys, please follow the guides and don't look for complications where there are none. Thank you.

Sounds like you do not have CPU native SpeedStep in place and that sure will cause quicker battery drainage... On an IvyBridge platform such as yours, CPU SpeedStep is obtained through AICPUPM patch (patched kext or Clover on-the-fly AsusAICPUPM patch) and generated CPU-specific SSDT (using the well-known generator script of Pike R Alpha). You still have not uploaded your zipped EFI folder (you can leave out the Themes subfolder).

https://osxlatitude.com/index.php?/topic/8006-sierra-wireless-qmi-modules-mcem73xx8805-dell-dw557058085809/ You can rule out a USB port issue, your module is clearly listed in SysProfiler, i.e. detected and correctly reported in IOReg. So, it's more to do with CellPhoneHelper patch (if it's supported on this 4G module) or the QMI kext posted by Skvo. You have to base the patch on Sierra's vanilla kext, not an older version such as Yosemite's because Apple tends to modify these kexts from one OS X version to another (like they also like to do for Bluethooth kexts). For instance Skvo's patch made references to Yosemite's AppleUSBMergeNub kext as per CellPhoneHelper kext whereas, in Sierra, that kext does not exist and was replaced by AppleUSBHostMergeProperties. Try the following patch in Sierra which you can simply add to FakeSMC's Info.plist through any text editor: <key>0x413C Dell Wireless (based on Sierra QMI) modules</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBHostMergeProperties</string> <key>IOClass</key> <string>AppleUSBHostMergeProperties</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>IOProviderMergeProperties</key> <dict> <key>DeviceModemOverrides</key> <dict> <key>AccessPointName</key> <string>Obtain From Service Provider</string> <key>ConnectionPersonality</key> <string>Sierra GSM Personality</string> <key>ConnectionScript</key> <string>WWAN.ccl</string> <key>DeviceContextID</key> <string>1</string> <key>DeviceModel</key> <string>GSM</string> <key>DeviceVendor</key> <string>Sierra Wireless</string> </dict> <key>DevicePPPOverrides</key> <dict> <key>LCPMTU</key> <integer>1450</integer> </dict> <key>InfoCommands</key> <dict> <key>ATCommands</key> <dict> <key>DirectoryNumber</key> <string>+cnum</string> <key>IMEI</key> <string>+cgsn</string> <key>IMSI</key> <string>+cimi</string> <key>Manufacturer</key> <string>+cgmi</string> <key>Model</key> <string>+cgmm</string> <key>ModemSW</key> <string>+cgmr</string> <key>Serial#</key> <string>+gsn</string> </dict> <key>HiddenProperties</key> <dict> <key>CommandPortBaseName</key> <string>wwan</string> <key>ControlPortBaseName</key> <string>wwan</string> <key>DataPortBaseName</key> <string>wwan</string> <key>StatusType</key> <string>CellPhoneGSM</string> </dict> </dict> <key>Initializing</key> <true/> <key>InterfaceMapping</key> <dict> <key>0</key> <string>wwanDM</string> <key>2</key> <string>wwanGPS</string> <key>3</key> <string>wwan</string> </dict> <key>WWAN</key> <true/> </dict> <key>bcdDevice</key> <integer>6</integer> <key>idProduct</key> <string>*</string> <key>idVendor</key> <integer>16700</integer> </dict> -

Or try this Enoch guide... It works.

Difficult to say really. Power management can't be 100% identical in OS X than Windows. In addition, OS X is more graphics hungry. For the rest, let's not try any guess until you post your EFI folder to have a look.

No idea, try and experiment by yourself. Please use a separate thread for your M6800 issue.

No, you just have to make sure you've disabled hibernation. The process is detailed in existing E6x30 guides.

You should just read again that thread you found or do another search with the essential part of the title you used for this thread.

Well I suggest you read post #11 above and the guide(s) you got the kext from... starting with mines...

You'll find it in the boot pack posted in all recent or fairly recent guides for E6x30 laptops.

You can use the Forum Search facility for a start. To give you a hint, no Ethernet interface (and as en0)= no AppStore.

Guys, please pretty please (with sugar on it), read the Dr Hurt's VoodooPS2Controller thread. It's all in post #1. That'll save us having that same TrackPad/TouchPad PrefPane question being asked on and on.

Well... it's already set to 12 in the DSDT. So, all you're left to check now is the presence if the IDT 92HD93 kext in /L/E, install it if missing then repair permissions and rebuild your cache.

As I thought, your IOGraphicsFamily patch is the obsolete version for Yosemite. Modify it as detailed above. You should also choose where you place your Clover injected kexts: EFI/CLOVER/kexts/10.12 or EFI/CLOVER/kexts/Other. I don't think you should have kexts in both, to avoid confusion if nothing else... Afaik, the E6430s does not have any discrete graphics card, only the integrated HD4000. As such, the nv_disable=1 boot parameter is not necessary, though it won't do any harm.

Did you verify the HDEF layout-id? 'should be set to 12 (0x0C) afaik. You may also want to select AppleRTC patch. Could save a little slowness after reboot on BIOS POST completion. But it remains reasonably quick on the E6xxx series compared to the older D series.

I think you've got an obsolete IOGraphicsFamily patch in your config.plist. I did ask your EFI folder, but... The IOGraphicsFamily patch for Sierra is: Find: 0100007525 Replace by: 010000EB25

As long as it works for you...

You're gonna have to post a picture of your KP or tell us what it says... If you use Clover, make sure to select AsusAICPUPM or you'll get KP on CPU power management. That's mandatory on all Sandy Bridge and Ivy Bridge laptops. If you re-use the Clover config.plist from a previous version, the existing set of binary patches may also be the source of the KP. It'd be a good idea to post your complete EFI folder.

That doesn't work either; I've tried adding the "compatible" statement in DSDT ARPT device or adding the "pci14e4,4311" id to the AirportBrcm4331 kext; 'makes no difference whatsoever. Apple definitely dropped support for those old Broadcom cards in Sierra.

Yup. Above patch is obsolete for Sierra and patched El Capitan AppleHDA will not work under Sierra. For VoodooPS2Controller, you're now supposed to use Dr Hurt's version; I recommend Release 4 on the E6xxx series and it's available in Dr Hurt's thread in R&D section or in my recent E6220/E6230 Sierra guides. For audio, the correct AppleHDA patch for IDT 92HD93 is: Find: 8419D411 Replace by: 00000000 Find: 8A19D411 Replace by: 00000000 Find: 8B19D411 Replace by: DF761D11 There are no instances of 8319D411 in Sierra's AppleHDA. The patched kext must go to /S/L/E; the IDT definition kext can go to /L/E. Repair permissions and rebuilt cache after your kexts modifications.

Yes and with EC 10.11.6's version but it does not work either. Best thing to do will be to replace the DW1390 by a supported full size card such as the AR5B91 or a supported 1/2-size card+bracket like the DW1510 for instance.

Laptops can only be woken through lid opening, PWR button or, if set in BIOS, network activity or USB. Desktops can be woken through PWR button or, if set in BIOS, network activity or USB. But sheer keyboard or Touchpad action won't wake a Hackintosh afaik.

Remove the AppleACPIPlatform + VoodooSDHC kexts, they're not needed and will cause harm. If you use the patched AICPUPM kext, you can also put NullCPUPM aside (keep it somewhere but don't use it). You should not need the GenericUSBXHCI kext for USB3.0. the USB3.0 port of my E6230 works OOB with the right DSDT settings. You should use only one battery manager, so you must choose between AppleSmartBatteryManager and ACPIBatteryManager. I recommend you use Dr Hurt's latest kext Release R4. Remove Patched_10.7_AppleRTC kext, it's obviously not applicable to Sierra. There a thread about this in the Support->Apple OS X folder. Patched AppleHDA.kext will only load from /S/L/E so...

Still had a DW1390 in the D630i. 'been a long since I last played with it and I can confirm that it last works OOB in El Capitan. I experience the same as you when I boot Sierra with the DW1390 in my D630n. One has to assume that support for that old Broadcom chip has been dropped... There certainly ain't no AppleAirportBrcm43224 kext any more as PlugIn of IO80211Family kext in Sierra.