Hervé

Considering the regularity at which kextcache command ends up with errors when rebuilding cache, I'm recommending NOT to use those tools any more but to revert to good old manual line commands: For kexts placed in /L/E: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / For kexts placed in /S/L/E: 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 / If an error 77 is returned, repeat the last 2 x commands (touch + kextcache) or replace the kextcache command by: sudo kextcache -system-prelinked-kernel ` Caution: placing the PS2 controller in /E/E will probably not get it loaded, unlike placing it in /L/E or /S/L/E. myHack uses /E/E as a source location from where it retrieves kexts that are subsequently upped to version 999 and then copied as PlugIns to a kexts called myHack.kext placed in /S/L/E.

You may use the PS2 controller kexts available in the pack of my E6220 guide. It'll work no problem on the E6230.

Indeed, it's unsupported afaik.

Dr Hurt, Release 4 RC2 is nearly perfect on my E6440 with Rushmore V3. Trackstick working nearly Ok, yeah! Just one "little" issue which, I'm sure, will be easy to fix: pushing the tracktstick up moves the pointer down on screen and vice-versa. Other than that, everything is great, including speed. Thank you so much for your brilliant work.

Is it Intel graphics HD 4600? If so, graphics acceleration is obtained through: 1) DSDT injection or Clover faking of desktop HD4600 device id 0412 + Azul framebuffer #12 0x0a260006. For example: Device (IGPU) { Name (_ADR, 0x00020000) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x06) { "device-id", Buffer (0x04) { 0x12, 0x04, 0x00, 0x00 // fakes Desktop HD4600 id }, "AAPL,ig-platform-id", Buffer (0x04) { 0x06, 0x00, 0x26, 0x0A // injects Azul framebuffer #12 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } [...] 2) Use of Rehabman's FakePCIID + FakePCIID_Intel_HD_Graphics kexts If you want HDMI audio, you'll also have to patch HDEF + HDAU devices in DSDT, use patched AppleHDA and Rehabman's FakePCIID_Intel_HDMI_Audio kext.

Which BIOS version do you run? It's usually better to stick to versions A16 or A17, not the very last ones which only brought BIOS security changes. I cannot explain your HDD behaviour, I've never encountered it, yet I've used many different HDDs and SSDs on the various D630 I got into my hands. Disk mode was always set to AHCI and I do not recall ever using ATA mode. If you can advise on the HDD model, we can try and have a look but I'd be very surprised if you had a SATA HDD that did not support AHCI mode. D630 supports SATA-II (3.0Gb/s) by the way. You are talking about an internal HDD by the way, right? Not the USB disk you're apparently using? If you have a Merom CPU (T7xxx), make sure IDA is disabled. If enabled with a non-Penryn CPU, it causes problems under OS X. Re: hanging, when is this happening? At startup or is it a KP? If you're still running the Chameleon version installed by myHack, update the bootloader to something like r2395 or r2401. Those work perfectly. You may use the Chameleon Wizard tool to update or download the relevant package off InsanelyMac for instance. I haven't tried recent Enoch versions on the D630 X3100 with SL or Lion but I would also expect those to work since they work Ok on the D630 nVidia.

With lastest RC, trackstick still operates same way as reported with previous versions. Once trackstick is used, TouchPad dies. Happy to (re)test bpedman's driver if you can remind me which one. Edit: TouchPad actually randomly dies after a few minutes.

much faster than what?

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/