Hervé

If you're building an Enoch-based USB installer with the manual process I've detailed in all that guide, then yes (of course) you need to manually add the kernel to your USB installer. And yes, you can use the kernel files I posted. Just follow the process listed in the guides.

If you could specify exactly what you've tried/done rather than let us guess...

You need to pay attention to the commands you were provided with... You were given: sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / You typed: sudo -Rf 755 / S * / L * / E * sudo chown Rf 0:0 / S * / L * / E * sudo contact -f / S * / L * / E * sudo kextcache -Boot -U / That ain't gonna work... ever. If in doubt, copy/paste the commands posted on the forum...

I'm afraid that version kills TouchPad after TrackStick.

Can't remember and I don't have that old lappy at hand any more. Which telco are you with?

What's this "Boot Graphics" boot option? 'never seen that before... Make sure you use the PS2Controller posted here.

Try to revert to patched CellPhoneHelper.kext and make sure to patch your current vanilla kext (it varies slightly between OS X versions and releases). Your injector header is a little different from the full header of the vanilla kext, though I cannot say if that's an issue per sé. One other thing. You have: <key>AccessPointName</key> <string>connect</string> when El Capitan 10.11.6 vanilla kext has: <key>AccessPointName</key> <string>Obtain From Service Provider</string> Why don't you try the vanilla settings instead? One last thing. Although it only happened to me once and under ML when I 1st played with WWAN modules a few years ago, I had to specify a username + password in the WWAN module PrefPane tab. I never had to do it again with subsequent installations. You could be in that same situation. All details are here. Check your telco/service provider's published APN settings, they're usually available on the web. Examples here or here.

I'd say Speed is definitely Ok with beta10. Though and on double checking with the other versions too, movement to the right seems slower than the other directions. Major issues of UP/LEFT movement unchanged... Maybe something to do with a filter with right movement. This being said, since I never use trackstick, it's not a problem for me and I'm definitely sticking to this driver for my Latitude laptops. Many thanks for your efforts!

Try and boot in safe mode because you still have to sort out the graphics. You can refer to this bible thread for details. You'll see that the Inspiron N5010 is in the list of laptops that support full QE/CI with 1st gen Intel HD graphics, so good news!

It's a little faster but I guess you can easily go to x4. No difference re: UP and/or LEFT: trackstick still goes in diagonal UP-LEFT. No diagonal movement UP-RIGHT or DOWN-LEFT.

I would suggest you add all H5321gw entries to the list of installed interfaces and try to connect using the specific WWAN entry. NB: I have not looked very deep into the difference between models 5321gw and 5521gw but the H5321gw is half-size model of F5321gw, not F5521gw. H5321gw datasheet specifies it was designed for tablets, which meant reduced size and very-low power consumption. I also saw that the 5321gw model supports HSPA Evolution, not the 5521gw. Other than that, these modules appear indeed quite similar (21Mbps download, 5,76Mbps upload).

Yes, see attached screen recordings. Trackstick cannot go UP-RIGHT or DOWN-LEFT. Trackstick_right.mov Trackstick_down.mov Trackstick_up.mov Trackstick_left.mov Speed could gain by x2 possibly x4; x8 may be too much. Can't see any ALPS messages in Syslog. I can't recall ever using bpedman's driver, or at least not for years.

Trackstick left + right buttons are fully operational on my E6440. Middle button appears to work also (it opens a new tab in Safari for instance) though I admit not knowing how it's meant to operate (I never use trackstick at all...) Trackstick movements are another story: very slow when moving down and right. When trying to move left or up, pointer goes in diagonal to the left and up; and still very slowly.

Post your patched kext + a screenshot of your WWAN settings. There's usually more than the 3 little lines you've posted.

Very well. Good luck then.

You obviously have the WWAN module correctly setup since it's clearly detected by the OS and you initiate connections. I'd say it's your apn settings that are probably incorrect. May be you can post details of those settings.

Please make the effort to search the forum and refer to the guides. Eg: https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-el-capitan-clover-guide/

It's basically the exact same process as for El Capitan and you would normally re-use the same add-on kexts and patches. The most notable difference will be that the VoodooPS2Controller that you may have used under EC no longer runs under Sierra. But Dr Hurt recently re-worked on the whole kext package and you may use his latest beta available here. If you use nVidia Web driver, of course you'll have to update to the Sierra-compatible version.

I can confirm that, on the E6440, Trackstick is in a little crazy mode with beta6 and not working at all with beta7. Trackstick buttons (i.e. those directly under Kbd but above TouchPad) are inoperative. NB: No Trackstick on E6220/E6230.

USB issues is a well-know problems since El Capitan. Problems are usually solved by: 1) renaming EHCx devices to EH0x in DSDT 2) using a USB injector kext (own made -not difficult- or USBInjectAll kext) If you can post your existing DSDT, we can try to work this out.

works great on my systems. Single-finger side scrolling with inertia is great indeed.

If you use Clover, why do you seek the file? You're expected to use the hot/on-the-fly patching facility of Clover. Use CloverConfigurator tool (Google for it). However, if you're attempting direct patching of the kext file, then: AirportBrcm4360 is a PlugIn of IO80211Family use a hex editor on the binary file of the kext (the file found inside the kext package, under Contents/MacOS folder) to replace the strings

You forgot the attachment!

Ok, so this seems to be an Arrandale platform (1st gen Core i3-350M with 1st gen Intel HD graphics on HM57 Series 5 chipset). As such, in your Clover config.plist, you should have: P-States + C-States generation activated SSDT/DMAR tables drop removed KernelPm / Asus AICPUPM / KernelLAPIC disabled InjectIntel activated in Graphics tab SMBIOS set to MacBookPro6,1 or 6,2 You may also want to remove those DSDT fixes (in ACPI tab) to begin with. In a subsequent phase, I'd also recommend you tune your FakeSMC kext to MBP6,1/6,2 keys (1.57f18/smc-piketon) as detailed here. This will ensure that, once you get rid of NullCPUPM, you enjoy full native CPU power management.

Try to unplug your USB installer, then plug it again, either in the same USB port or other ones.