Alright so 4.14.4 and .11 actually resulted in worse behaviour from the
touch pad, and even some system wide instability. I'm back to 4.15-rc6
(Mint Cinnamon) and, although it will not initiate at boot, suspending
gets me full functionality including multi touch gestures - and it
doesn't randomly
That's fair enough. I'll be sure to try 4.14.3 as well as the newer .11
variant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244
Title:
Touchpad stops working after reboot on
@Brad - As much as I dislike using "old" kernels, this is definitely
worth testing. I'll try as you've suggested tonight and report back
ASAP.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Adding some information obtained last night:
On my YEPO 737A I flashed both Lubuntu and Elementary images to test if
the suspend/wake "trick" would initialize the trackpad, and it did not.
Both flashes making use of 4.15rc6.
Attacking this problem via BIOS seems problematic, as so many brand
@bbaker6212/Brad, weirdly enough it does work after a suspend/wake but
will cease working after any sort of interaction with the touchpad
settings including on/off.
modprobe commands have no effect.
Requested Info:
theyield@Keyloggertop ~ $ uname -a
Linux Keyloggertop 4.15.0-041500rc6-generic
I just thought I would add that I too am affect by this on my system:
SYNA3602 device on a YEPO 737A Laptop - Linux Mint 18.3 Cinnamon respun,
as OP describes. The touchpad doesn't work live, and has never worked
after install.
I'm currently on 4.15 RC6 which was respun into the install ISO via
6 matches
Mail list logo
