Hervé

The software only seem to support the Upek biometric readers of the Dell D Series (I have it running on my old D430). It does not work for readers fitted to more recent Dell laptops such as the E Series for instance. It's a totally different piece of hardware. I should have a copy of the software somewhere. If it fits as a post attachment, I'll upload it. Obviously this Upek application only ran on laptops fitted with Upek's hardware accessory (older Dell, Lenovo, Sony, Acer and Asus models). I understand Upek was subsequently acquired by Apple and product support ceased.

Last time we looked at the specs, they were pretty much alike any IvyBridge E6x30.

The mini PCIe slots of the Dx30 do operate in combo PCIe/USB mode. Oherwise the WWAN modules would never work and they can be use in any slot. EDIT: WRONG: Ok on the D430 (both slots) but not on the D630 in which only the WWAN slot is combo PCIe/USB; the WLAN slot is PCIe only.

Why do you use that kext?

Never assume that a 3rd party component such as combo wireless/bluetooth card will work OOB. 1st identify the Bluetooth chip used on the DW1550 then refer to the Wireless and Bluetooth section of the forum. You may also want to read the existing literature on your Bluetooth matter. You also confuse USB ports and USB devices. The USBInjector kext only serves one purpose: get the built-in USB ports to be recognized and work, not the connected USB devices...

You can refer to my D630 guide if you need anything. I use a tuned USBInjector kext that matches the D630 USB2.0 ports arrangement under the chosen SMBIOS profile. Watch because I use a different SMBIOS profile between OS X versions up to EC (MBP5,1) and macOS Sierra (MBP7,1). I can't guarantee that the USBInjector kext I use for the D630 will also apply directly to the D830, but you can use IORegistryExplorer to identify all your ports and adjust the kext Info.plist file as needed. The packs also include FakeSMC kext tuned for GPU throttling (AGPM patch) and native CPU SpeedStepping. SSD/HDD speed is limited to SATA II performance, i.e. 3Gb/s max, not 6Gb/s; nothing you can do about it, that's the chipset specs...

Cache did not rebuilt properly: Error 77... Re-type the touch + kextcache commands.

It would appear there is no bootloader installed on the media you attempt to boot (USB key or HDD). Start with that before installing/replacing the EFI folder.

You should enable integrated NIC, but that's not what causes the issue you experience. System reset on a Haswell platform is often due to absence of kernel power management (PM) patch. Make sure you enable KernelPm patch in your Clover config.plist (AsusAICPUPM patch is not required on Haswell and later platforms). If you used JakeLo's bootpack, you should be Ok, as long as you installed it in the right place of course: the hidden EFI partition that you'll 1st mount with Clover Configurator.

KP due to vanilla AICPUPM kext... If you use Clover, enable the AsusAICPUPM patch. If you use Enoch, you should either use NullCPUPM kext or the pre-patched AICPUPM kext. You may refer to my E6220 guide (and pack).

Please try and list your own computer's true specs, not those published on the Lenovo brochure.

Wifi with this card is discussed at great length on the forum. You can use the Search facility. Trackpad works fine with Dr Hurt's driver Release 4. You can look ut the thread in the associated R&D forum subsection. The files for the TrackPad PrefPane are also mentioned and provided.

Again, what des the KP say??? You will get audio if: 1) you use the correct patched DSDT (HDEF layout-id set to 12 / 0x0C) 2) you install the IDT 92HD93 definition dummy kext, ideally in /L/E (/S/L/E will do to) 3) replace the vanilla AppleHDA in /S/L/E by the patched version (details of patch provided before) or configure the on-the-fly patches in Clover config.plist Again, repair permissions and rebuild cache after any mod to kexts in /L/E or /S/L/E.

If your KP refers to AppleIntelCPUPowerManagement, then you need to install the patched AIPCUPM kext in /S/L/E (overwriting the vanilla kext), repair permsissions and rebuild the cache. If you get an "error 77..." message, retype the touch + kextcache commands.

Why don't you try to create your new USB installer directly on the E6230? It makes no difference that it already runs EC.

This patch applies to PCIe SD card readers only, not USB readers. It's known to work with several O2 Micro devices but may not work with all of them. It does not appear to work with non-O2 Micro devices (Ricoh or Realtek for instance). To patch your DSDT, use the following process: 1) Using IORegistryExplorer, identify your DSDT device (pay good attention to displayed PCI vendor and device ids). The device will differ from one system to another. 2) Open up your DSDT with MacIASL 3) look for your SD card device identified in step #1 (for instance: device PXSX under RP05) 4) paste the following code under the _ADR and _PWR sections: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "AAPL,slot-name", // Optional Buffer (0x09) // Optional { // Optional "Built-in" // Optional }, // Optional "device_type", // Optional Buffer (0x11) // Optional { // Optional "Media Controller" // Optional }, // Optional "model", // Optional Buffer () // Optional { // Optional "<specify your model here>" // Optional }, // Optional "compatible", Buffer (0x0D) { "pci14e4,16bc" } }) } 5) Recompile your DSDT and replace your initial table. Below is an example for the Latitude E6230 (with original DSDT device "PXSX" renamed to "SDXC"):

Just apply the CellPhoneHelper patch, whether in the kext itself or in FakeSMC. No guide has ever mentioned anything else so don't get ahead of yourself and stick to known working patching methods that have been published so far.

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).