[Solved] Dell E7450: TrackPad issues under Catalina (with Clover)

[Justin Wallis]

Mobo: Latitude E7450 (Clover)
CPU: 2.9Ghz I7 5600U
Graphics: HD 5500, 1920 x 1080
Ram: 16GB DDR3

 

- The Trackpad functions don't work natively, although, it allows me to connect an Apple Trackpad. When I did get it working with (w/ ApplePS2SmartTouchpad.kext), it slowed the mouse way down to super slow speeds, and nothing would happen when I changed mouse speeds in the system settings.

 

Instead, I am using Karabiner Elements and Smartscroll, as @Jake Lo states to use on his  amazing e7450 Guide. So, i guess this is the only option still?

 

Kexts & Drivers I'm using

 

Kexts Not Using

 

 

My config.plst & EFI Folder is attached 

EFI.zipconfig.plist.zip

 

 

These are the kexts from @Jake Lo's tutorial @ e7450 Guide.

 

 

I had trouble with boot when i had the ssdt's on my EFI. Does anybody know why, and what i'm missing by not using them. And also the kexts, i use that Jake does not have listed, are they helpful? Thank you!!

[Justin Wallis]

@acquarius.13 Do you think it would be proper to try your Opencore config (E7450-OC060-BSb-EDIT2.zip) for Catalina 10.15.6 (19G73), in replace of clover? i wanted to start using OC if i can handle it since it seems to be superior with boot speed and bootcamp/filevault

 

I read over this tutorial last night, seems nice.
Why OpenCore over Clover and others https://dortania.github.io/OpenCore-Install-Guide/why-oc.html#opencore-features

So, did you just replace the  clover files in your EFI with the OC files you have above?  Do you know where do i put my s/n, uuid and mbsn so icloud still works correctly? i haven't came across this info. thank you!

[Hervé]

Clover setup shows several mistakes. For instance, you've installed SMCHelper.efi driver (which is only required if you use FakeSMC kext) when you use VirtualSMC set of kexts. If you want built-in ALPS TrackPad to work and be recognised, you need to use Dr Hurt's VoodooPS2Controller kext. It's available in Dr Hurt's dedicated thread and in the Clover packs posted in the various guides we have for the E7x50 models. I can't remember which ALPS version these E7x50 are fitted with but I don't remember specific issues with them when I had an E7250 in my hands.

 

Re: SSDT, if you're talking about the CPU power management one, you have to make sure you use one that was generated for your own specific CPU. If you (re)use an existing one meant for a different CPU mode, you'll encounter trouble, of course. If in doubt, boot without such SSDT and generate your own one using Pike R Alpha's well-known and good old generator script. 

[acquarius.13]

Justin,

 

I tried using OC on an external hard drive with USB caddy. I left my primary internal SSD untouched. I was curious to try OC and it was a good mess, honestly.

I recommend you to firstly solve your issues with clover, to read carefully dortania's OC guide (read it all, many times) and finally, if you feel quite brave try to "adjust" your files to OC.

I suggest also to test your future OC files using an external drive/stick before trying with your primary drive.

 

But, unfortunately, I'm not able to understand your issue.

 

Apologize

[Justin Wallis]

@Hervé Thank You!

 

- I took out SMCHelper.efi from my BIOS and UEFI folder. 

- I ran the available "latest Beta" version of "ssdtPRGen.sh" (https://github.com/Piker-Alpha/ssdtPRGen.sh) and got these results With Self Generated ssdt.aml file (after reboot):

CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 500 MHz
CPU Maximum non-Turbo Frequency....: 2600 MHz
CPU Maximum Turbo Frequency........: 3200 MHz


CPU P-States [ 15 28 (31) ] iGPU P-States [ (10) ]
CPU C3-Cores [ 1 2 3 ]
CPU C6-Cores [ 0 1 3 ]
CPU C7-Cores [ 0 1 2 3 ]
CPU P-States [ 15 28 29 (31) ] iGPU P-States [ (10) ]
CPU C3-Cores [ 0 1 2 3 ]
CPU C6-Cores [ 0 1 2 3 ]
CPU P-States [ (13) 15 28 29 31 ] iGPU P-States [ (10) ]
CPU P-States [ (13) 15 17 28 29 31 ] iGPU P-States [ (10) ]
CPU P-States [ 13 15 17 (26) 28 29 31 ] iGPU P-States [ (10) ]
CPU P-States [ 13 (15) 17 20 26 28 29 31 ] iGPU P-States [ (10) ]
CPU P-States [ 13 15 17 20 24 26 28 (29) 31 ] iGPU P-States [ (10) ]
CPU P-States [ 13 15 17 20 21 24 26 28 29 (31) ] iGPU P-States [ (10) ]
CPU P-States [ 13 15 17 20 21 24 25 26 28 29 (31) ] iGPU P-States [ (10) ]

 

- With Dr Hurt's REFINED ALPS TOUCHPAD DRIVER, I used: 

VoodooPS2-Alps-Debug.zip  (https://github.com/1Revenger1/VoodooPS2-Alps/releases/tag/1.0

And 3 other versions on Dr Hurt's Refined ALPS Touchpad Driver link, but still keep coming up with "No Trackpad Found" . 

   (I delete the VoodooPS2Keyboard.kext & VoodooPS2Trackpad.kext because they are located inside the VoodooPS2Controller.kext, correct?) 

 

 

[Hervé]

Re: DrHurt's VoodooPS2 kext, you were meant to take it from here:

https://osxlatitude.com/forums/topic/8285-refined-alps-touchpad-driver/

 

Use the kext's version recommended in post #1 and do consider generating your USBPorts kext with Hackintool app as I experienced a TrackPad issue last year in relation to that matter as detailed here.

[Justin Wallis]

Whoops, i just realized i didn't get rid of ApplePS2Controller.kext.

I got rid of it and the Trackpad works fine now, Thank You!!!!!!!!!!!!!!!!!  I disabled smartscroll as it isn't necessary for anything i think.

 

@Hervé, also, would it be safe to use this ssdt.aml i generated on other 2.6GHz i7-5600U E7450's? 

And similarly, generate one from, and to use on multiple 2.3GHz i5-5300U E7450's?

[Hervé]

Yes, the SSDT table generated for any given CPU can of course be re-used on any Hackintosh fitted with the exact same CPU model, i.e. no need to regenerate when you already have the applicable (generated) SSDT.

 

The platform on which you generate the CPU power management SSDT does not really matter. By default (i.e. without any parameters), the script generates a table for the host's CPU and active SMBIOS data (Mac model + board-id) but,  if you've installed the complete package with CPU models database, you can add parameters to target a totally different CPU & Mac model. All parameters and instructions are explained in the documentation available on that GitHub repo or if you type:

./ssdtPRGen.sh -help

 

For instance:

1) to generate the SSDT for an i7-3540M CPU fitted to an Ivy Bridge laptop running OS X/macOS with MBP10,2 SMBIOS

./ssdtPRGen.sh -target 1 -p i7-3540M -m MacBookPro10,2 -b Mac-AFD8A9D944EA4843

2) to generate the SSDT for an i5-5300U CPU fitted to a Broadwell laptop running OS X/macOS with MBP11,2 SMBIOS

./ssdtPRGen.sh -target 3 -p i5-5300U -m MacBookPro11,2 -b Mac-E43C1C25D4880AD6

You can get board-id of any Mac Model from Clover Configurator app, SMBIOS tab.

[Justin Wallis]

@Hervé , Good to know! Thanks, i'm going to look more into that more.

 

I have one question still.

If one were going to clone a drive to be connected eventually to a separate Apple ID / ICloud Account than the drive that i'm cloning;

 

1.  Is giving the computers unique Serial Number, SmUUID, MBSerialNumber the only thing i would have to do? Pretty much the steps required for iMessage. (Assuming both of the drives are going to be used on the same hardware obviously.)

 

2. And the SSDT would be the only thing one would have to switch, if they were switching to a different processor (same laptop or hardware otherwise)

[Jake Lo]

Yes, that's correct. Some cloning software might not clone the EFI partition, so just install Clover and copy the EFI folder over.