Hervé

Oh, you've been on Alexandervos's E6430?

If you have a proper installation, all subsequent upgrades are straight forward and trouble free. One only ever needs to re-apply the audio patches on non-Clover installation.

What "data" are you talking about? I've only ever applied patches to CellPhoneHelper. Stick to that to begin with.

You're getting warmer... So, now that you've identified that the card was based on a Sony Ericsson chip, you have to ask yourself why you picked a Sierra wireless profile for your WWAN patch? You did not confuse Sierra Wireless -a wireless communication equipment manufacturer- and macOS Sierra, did you? You may now refer to the other pointers of post #6.

1st of all, note that you obviously must not use the Legacy_sierra_qmi kext posted by Skvo under macOS Sierra because it's based on Yosemite's CellPhoneHelper kext. This kext is not compatible with Sierra and won't work under macOS 10.12. This extends naturally to any patch built on it. Secondly, you must not use Legacy_sierra_qmi kext AND patched CellPhoneHelper kext. You may use either/or but not both. Did you try the patch I detailed above? It was just a basic and rapid adaptation of Skvo's posted patch for macOS Sierra. I might have missed something in my code of course. Lastly, please note that, SIM inserted, if the reported WWAN module does not list software version and network name, it's simply not operating properly. 1st thing to do is get your module fully recognised. Skvo wasn't exactly thorough or generous with details in his thread so, not owning this particular WWAN module myself, I'm not in a position to undertake any tests and cannot be of much further help on this. I can only offer you to send me your module to try and get it working.

Well, I think you got it wrong somehow. I invite you to conduct some research about your hs2330 module so that you know what it's based on and then refer to the thread related to the HP hs2340. I'm pretty sure that, provided you collect the correct information, you should find certain similarities between the 2 modules. I'm sure you'll also find useful info and trends in the other WWAN guides I posted.

I guess your CellPhoneHelper patch is possibly incorrect. But we don't know what you did...

WWAN modules do not get listed as 3G cards but as modems or WWAN cards. Consult the existing threads on the matter if you want to get your card registered as a proper WWAN module and work out the necessary CellPhoneHelper patch (that you can inject into FakeSMC's Info.plist to avoid having to re-patch CellPhoneHelper kext after each OS update).

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