-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lenovo T490: Erratic Mouse Pointer behavior in BootPicker #170
Comments
I'm wondering if the trackpad doesn't get reset into a basic PS/2 mouse. I can see if I can come up with something later (likely through VoodooPS2), but I'm busy for the next couple of days. |
I've also noticed that trackpad scrolling works as intended when using the official "Release" versions of off all the Voodoo kexts. Scrolling feels prettyy much like it behaves in Windows. I was using the latest nightly builds of the voodoo kext before and the trackpad felt really unresponsive in terms of scrolling. After reverting to release versions, srolling feels great, but "Tap on Click" doesn't work even though it's enabled in preference and the mouse issue in the boot menu remains. |
Is either scrolling or tapping more responsive when using my version of VoodooSMBus? |
Do you mean this one: https://github.com/1Revenger1/VoodooSMBus/actions/runs/4334161505 The link expired. I can try to compile it myself. |
"fatal error: too many errors emitted, stopping now [-ferror-limit=] ** BUILD FAILED ** Do you have a pre-compiled version somewhere? |
VoodooSMBus.kext.zip |
Thanks a lot. |
Test ResultsI've color coded the kext in my EFI to not confuse them:
I've tested these possible four combinations:
Unfortunately, with these kexts there's no combination which allows all 3 features to work properly at the same time. I hope this helps. |
Can you provide a log directly after scrolling using the VoodooPS2/SMBus in this thread and the latest debug build of VoodooRMI? |
The log is empty again. Do I have to use the OC debug versio as well or change any |
Uhh, is VoodooRMI loading? |
Everything is laoded |
Can you double check the IO Registry to see if those kexts attach? |
Ugh, the logging should be working. OpenCore debug settings doesn't have any effect here. Does |
Enter: Now it's working:
|
Ugh, I forgot that the debug version of VoodooPS2 can take too long to initialize, causing VoodooRMI to not find it. I've got a PR which should fix it eventually ™️ ( VoodooPS2Controller-2.3.6-RELEASE.zip Edit: VoodooPS2 also averages the finger coordinates over a few packets, which also probably explains the bad scrolling. |
Nice, Tapping works and scrolling works great as well. Mouse pointer still freaks out in BootPicker. Here's the log:
|
Don't know why this is so long. I just booted, tapped on one file and executed the command. sorry. |
After accidentally letting OCAT update all kexts I had to start over again. But this is what works now:
Results:
Thank you soooo much for your help! |
Hi. I am using VooodooSMBUS and VoodooRMI to control the TrackPad on my T490 Notebook. It's controlled via SMBUS. I am using these kexts with latest commit of OC 093 with OpenCanopy and MoisePointer support enabled:
Issue:
If I move the mouse cursor via the trackpad in the BootPicker, the mouse pointer jumps around erratically and unpredictably and produces "ghosting" as well. It's basically unusable in this state for selecting boot entries.
I also have a Wireless Logitech M570 mouse which can move the mouse pointer as expected without any glitches. So I am wondering if this might be related to the trackpad kexts.
Log
I've prepared the kexts and config as described but the generated log was empty. But I have attached an IOREG file and an OpenCore Debug Boot log. I hope this helps.
Thank you
MBP15,4_IOREG.zip
opencore-2023-06-09-064902.txt
EDIT:
After removing the "OC_ATTR_USE_POINTER_CONTROL" flag from
PickerAttributes
, the issue is gone. I don't know if it is clashes with thePointerSupport
in UEFI/Input but it rather seems to be an issue with OpenCannopy than VoodooRMI.The text was updated successfully, but these errors were encountered: