Hi
I wrote this text to #1722379, but I think it worth to mention it here
as well.
Recently, after some updates - unfortunatelly I don't know exactly which
updates, but in the last month - I also have the same problem.
The workaround above with the # rmmod i2c_hid && modprobe i2c_hid works, but
I don't think this is the same bug and new bug report should be opened.
I've reported problem here back in October 2017 with my laptop and
problem was solved with kernel upgrade on Artful. Recently I upgraded
same laptop to Bionic and I am not affected by the bug.
--
You received this bug notific
Can those affected by this bug in Bionic open a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
Title:
touchpad not working after resume on kernel 4.13
To manage notifications about
Here's dmesg after resume
** Attachment added: "dmesg after resume"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/5141807/+files/dmesg_after
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I too am affected now. After suspend+resume, my touchpad isn't found.
Rebooting doesn't help: I really have to turn the machine off and on
again.
I can attach mouse, and then if I try to open touchpad settings in Input
Devices settings (I use Kubuntu), it says that Touchpad isn't found, and
xinput
This bug has started affecting me on 4.15.0-20-generic #21-Ubuntu. Not
sure if it's been reported on that release, not sure how to report it on
the correct release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Artful)
Assignee
I can confirm that it works again on the latest kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
Title:
touchpad not working after resume on kernel 4.13
To manage notifications
This problem is fixed with latest kernel update on Ubuntu 17.10:
# uname -rv
4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
Title:
4.13.7-041307-generic fixes the issue also for me (Lenovo Yoga 3 11,
fresh Ubuntu 17.10 install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
Title:
touchpad not working after resume on ker
I did the same with:
$ uname -rv
4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017
and also this kernel works for me and touchpad works after resume. What
is also nice, Wi-Fi works after resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Could you also give the latest upstream stable 3.13 kernel a try? It is
available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.7/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
T
I did following:
dpkg -i \
linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \
linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
\
linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
and rebooted the system to new kernel
Let me know do you need anything else. Will be possible to backport
fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works
after resume on default Artful Aardvark install?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification beca
To see if this bug is fixed upstream, please test the latest upstream
kernel. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please
test the latest v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Per external references to RedHat's bugzilla solution for the problem
should be:
https://patchwork.kernel.org/patch/9858267/
however I didn't had a chance to test it yet on latest Ubuntu 17.10
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
errors from kernel after resume (same as one of my previous comments)
** Attachment added: "resume-failed-hid.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972614/+files/resume-failed-hid.txt
--
You received this bug notification because you are a member of U
** Attachment added: "dmesg-before-suspend.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972612/+files/dmesg-before-suspend.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "lsmod.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972615/+files/lsmod.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
Title:
to
** Attachment added: "dmesg-after-suspend.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972613/+files/dmesg-after-suspend.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Previous dmesgs are with 4.13.0-12-generic, as the same problem was
present with 4.13.0-12-generic, 4.13.0-15-generic and now is present
with 4.13.0-16-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
a bit more lines from syslog when issue happens:
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block:
timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block:
timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.
22 matches
Mail list logo
