Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #228043 > unrolled thread

Laptop keyboard and touchpad don't work after upgrading fromlinux-image-4.19.0-9-amd64 to any later kernel

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel Matt Roberds <mroberds@att.net> - 2020-10-21 02:10 +0200
    Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel David <bouncingcats@gmail.com> - 2020-10-21 02:50 +0200
    Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel Matt Roberds <mroberds@att.net> - 2020-10-21 04:00 +0200
      Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel David <bouncingcats@gmail.com> - 2020-10-21 05:00 +0200
        Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel David <bouncingcats@gmail.com> - 2020-10-21 05:10 +0200
        Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED] Matt Roberds <mroberds@att.net> - 2020-10-21 06:50 +0200
          Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED] <tomas@tuxteam.de> - 2020-10-21 09:50 +0200
            Re: Laptop keyboard and touchpad don't work after upgrading  fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED] David <bouncingcats@gmail.com> - 2020-10-21 10:30 +0200

#228043 — Laptop keyboard and touchpad don't work after upgrading fromlinux-image-4.19.0-9-amd64 to any later kernel

Hello all!

I think I'm experiencing a bug, but I'm not quite sure what package to
file it against, so I am looking for advice.

Short version:

After upgrading from linux-image-4.19.0-9-amd64 to
linux-image-4.19.0-10-amd64 , X can't see the keyboard or touchpad on my
laptop anymore.  Rebooting back to the -9- kernel image makes both the
keyboard and touchpad work again.  I think I should file against the
kernel, but I'm not quite sure which package that is.

Long version:

Hardware: Acer ES1-511 laptop with its built-in keyboard and built-in
touchpad.  The machine is about 5 years old.

Software stack: Kernel images (buster, amd64) as below, sysvinit, xorg,
lightdm, xfce.

Until early September, 2020, I was running linux-image-4.19.0-9-amd64 on
my laptop.  Everything worked as expected.

I then upgraded (via aptitude) to linux-image-4.19.0-10-amd64 .  I also
upgraded some other packages at the same time.  Now, when I boot the
laptop, the keyboard and touchpad don't work in X - when the lightdm
greeter comes up and asks me for my username and password, I can't type
anything, and I can't move the mouse cursor with the touchpad.

Since then, I have also installed linux-image-4.19.0-11-amd64 , and it
has the same problem as -10- : the keyboard and touchpad don't work in
X.

I don't think I have a hardware failure, for a few different reasons:

1.  I still have the -9- image installed and available in grub, and if I
go into grub at boot time and choose to boot it, the keyboard and
touchpad work again.  In other words, if I keep the updated versions of
all the other packages, but go back and boot with the older kernel, it
works again.

2.  When I boot the -10- or -11- image, during the time that the console
is still in text mode and init is starting up daemons (messages like
"[ ok ] Starting foobard" are appearing on the screen), I can type on
the built-in keyboard and whatever I type gets echoed on the screen.

3.  I can boot the -10- or -11- image and let it get to the lightdm
greeter, where I can't type in my user name.  I can then plug in an
external USB keyboard, and hit Control-Alt-F1 on the external keyboard
to get to text console 1, with a "login:" prompt.  If I then type on
the built-in keyboard again, I can type in my user name and password and
start a text console login session, type in commands to that session,
etc.

Also, I can boot the -10- or -11- image, plug in an external USB
keyboard, and type my user name and password on the external keyboard;
lightdm accepts these and I log in to X.  My saved X session includes an
xterm, which usually comes up with input focus.  If I then type on the
built-in keyboard again, nothing happens in the xterm.  (Typing on the
external USB keyboard works; what I type shows up in the xterm.)

I tried booting the -9- image, recording the output of dmesg and lsmod,
booting the -10- image, recording the output of dmesg and lsmod, and
then doing some "sort | uniq -c | sort -n".

The only module difference is that -10- has usbhid loaded and -9-
doesn't; I'm pretty sure that happens when I plug in the external USB
keyboard.

There are more differences in dmesg.  (I used dmesg -t, so I don't have
to worry about the *kernel* timestamps on each line.)  A lot of the
differences are due to things that contain process IDs, other
timestamps, memory sizes, or memory addresses, that will probably always
be slightly different.

Some dmesg differences that look interesting to me:

These are both (off) with one kernel and (on) with another:

ACPI: Power Resource [CLK0]
ACPI: Power Resource [CLK1]

The internal touchpad (and internal mouse, not shown) enumerate on a
different i2c connection - i2c-0 vs i2c-1 :

input: SYN1B7E:01 06CB:2970 Mouse as /devices/platform/80860F41:02/i2c-0/i2c-SYN1B7E:01/0018:06CB:2970.0001/input/input8
input: SYN1B7E:01 06CB:2970 Mouse as /devices/platform/80860F41:02/i2c-1/i2c-SYN1B7E:01/0018:06CB:2970.0001/input/input8

The -10- kernel says this, but the -9- does not:

broken atomic modeset userspace detected, disabling atomic

(I Googled this one and it seems to do with how X sets modes on your
video card.)

Looking for other packages that might be related to this problem,
/var/log/dpkg.log says that I upgraded to from 1.12.6-2 to
1.12.6-2+deb10u1 on libinput10 and libinput-bin at the same time I
upgraded to the -10- kernel image.  I tried using snapshots.debian.org
to downgrade just those two packages to the 1.12.6-1 version, and then
booted the -10- kernel image again, and I still have the same problem.

(I would have preferred to downgrade those packages to 1.12.6-2 instead
of 1.12.6-1, but I couldn't figure out how to do that.)

I also tried booting to the -10- kernel, doing an update-initramfs, and
rebooting; no change.  (I tried this because it's fixed odd issues
around kernel upgrades for me, once or twice in the past.)

I feel like I should file against the kernel image, because booting an
older version of the kernel makes it work again.  However, its bug page
( https://packages.debian.org/buster/linux-image-4.19.0-9-amd64 ) shows
no bugs, which makes me think I should file somewhere else.  Is that
the linux-signed-amd64 source package, or just the linux source package,
or something else?

Similar problems on debian-user recently:

This may be the same bug that Jose Mojada first mentioned on 5 Sep 2020,
in https://lists.debian.org/debian-user/2020/09/msg00115.html .  His
report on 10 Oct 2020 matches my experience; -9- is the last kernel that
works: https://lists.debian.org/debian-user/2020/10/msg00195.html

Thanks for your help!

Matt Roberds

[toc] | [next] | [standalone]

#228045

On Wed, 21 Oct 2020 at 11:03, Matt Roberds <mroberds@att.net> wrote:

> I think I'm experiencing a bug, but I'm not quite sure what package to
> file it against, so I am looking for advice.
>
> Short version:
>
> After upgrading from linux-image-4.19.0-9-amd64 to
> linux-image-4.19.0-10-amd64 , X can't see the keyboard or touchpad on my
> laptop anymore.  Rebooting back to the -9- kernel image makes both the
> keyboard and touchpad work again.  I think I should file against the
> kernel, but I'm not quite sure which package that is.

Hi Matt

I suggest to also test what happens if you start the system
without using lightdm or X.

One way to do this is to boot into multi-user text mode.

You can do this in grub by following the instructions here:
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/#sec-Making_Temporary_Changes_to_a_GRUB_2_Menu

Assuming that your system uses systemd, use the grub built-in
editor to add the below text at the end of the 'linux' line:
  systemd.unit=multi-user.target

And then boot. Let us know the results.

If the keyboard works at the text login prompt, then I doubt
that the kernel is the appropriate place to report this bug.

[toc] | [prev] | [next] | [standalone]

#228051

David wrote:
> I suggest to also test what happens if you start the system without
> using lightdm or X.

I tried this with three versions of the kernel: linux-image-4.19.0-9-amd64,
linux-image-4.19.0-10-amd64, and linux-image-4.19.0-11-amd64 .

Under all three versions, the built-in keyboard worked OK when booting
into text mode.  I could log in and issue commands.

Under all three versions, I also said "cat /dev/input/mouse0" (as root),
moved my finger around on the touchpad, and got various characters on
the screen whenever I moved my finger.  So the touchpad appeared to be
working as well.

> One way to do this is to boot into multi-user text mode.

I have the default configuration of sysvinit, which boots to runlevel 2
and starts everything (networking, X, etc).  /etc/init.d/lightdm does
tell me that if the word "text" is on the kernel command line, it won't
start lightdm.

This machine is configured for dual boot, so I already had grub
configured to give me a "which OS?" menu at boot time.  From that menu,
I just appended " text" to the kernel command line, and booted; that
got me into multi-user text mode.

Matt Roberds

[toc] | [prev] | [next] | [standalone]

#228052

On Wed, 21 Oct 2020 at 12:54, Matt Roberds <mroberds@att.net> wrote:
> David wrote:

> > I suggest to also test what happens if you start the system without
> > using lightdm or X.

> I tried this with three versions of the kernel: linux-image-4.19.0-9-amd64,
> linux-image-4.19.0-10-amd64, and linux-image-4.19.0-11-amd64 .

> Under all three versions, the built-in keyboard worked OK when booting
> into text mode.  I could log in and issue commands.

Ok, good. I don't feel that I have much expertise in this area to contribute
anything further, so I hope other readers will contribute ideas.

But I have a couple of final (from me) suggestions that you might explore:

1) Compare xorg.log and or ~.xsession-errors between working and
non-working cases.

2) Take a look at this and surrounding posts for troubleshooting ideas:
https://bbs.archlinux.org/viewtopic.php?pid=1925437#p1925437

That discussion relates to kernel 5.* versions but maybe Debian has
applied some patches earlier.

3) That discussion suggests that X, udev and libinput might be possible
suspects that you might bug report against their Debian packages to
get troubleshooting ideas from their maintainers. Check if those
packages changed on your system recently.

4) Debian's support channels on IRC are quite good too if it suits you to
try there as well.

[toc] | [prev] | [next] | [standalone]

#228053

On Wed, 21 Oct 2020 at 13:58, David <bouncingcats@gmail.com> wrote:

> But I have a couple of final (from me) suggestions that you might explore:

5) Try this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971839
(if that's your model laptop)

[toc] | [prev] | [next] | [standalone]

#228055 — Re: Laptop keyboard and touchpad don't work after upgrading fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED]

Quick version:

Blacklisting the "Intel Virtual Button driver" in udev, per a post in
the Arch user forum that David linked to, made it work again.  I created
/etc/udev/rules.d/99-acer-libinput.rules with the single line

ACTION=="add|change", KERNEL=="event[0-9]*", ATTRS{name}=="Intel Virtual Button driver", ENV{LIBINPUT_IGNORE_DEVICE}="1"

, ran update-initramfs (which I may not have needed to do), and rebooted;
the keyboard and mouse then worked again in X.

Long version: see below.

On Wed, 21 Oct 2020, David wrote:
> 2) Take a look at this and surrounding posts for troubleshooting ideas:
> https://bbs.archlinux.org/viewtopic.php?pid=1925437#p1925437
>
> That discussion relates to kernel 5.* versions but maybe Debian has
> applied some patches earlier.

This particular post ended up being the key to fix it; see below.

> 3) That discussion suggests that X, udev and libinput might be
> possible suspects that you might bug report against their Debian
> packages to get troubleshooting ideas from their maintainers. Check
> if those packages changed on your system recently.

In my original post, I mentioned that when the problem first showed up,
I had changed from linux-image-4.19.0-9-amd64 to
linux-image-4.19.0-10-amd64 , but I *also* changed from libinput10 and
libinput-bin 1.12.6-2 to 1.12.6-2+deb10u1 at the same time.  When I
downgraded those two packages back to 1.12.6-1 using
snapshots.debian.org , I still had the problem with the 4.19.0-10
kernel image.

I also looked at the log files from when I first started troubleshooting
this, and they were dated 26 August.  I remember Googling at that time
and not finding anything online about this problem.  I wrote the first
draft of my email around that time as well, but I didn't have much time
to spend on troubleshooting, so I didn't send it.

That Arch BBS post is from 9 September, and the Debian bug is from 8
October.

Conclusion: I should have Googled again before sending my
nearly-2-month-old email.  :D

(From David's second email:)
> 5) Try this:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971839
> (if that's your model laptop)

That is very close to my model.  That bug cites an "E5-511".  Both the
sticker on the bottom of my laptop, and some of the fields in the
dmidecode output, give the model I have as "ES1-511".  A Web search
shows that both should be valid Acer models; the E5-511 has a faster
CPU and bigger disk than the ES1-511, but the rest of the specs are
similar.

I tried the suggestion in that bug and got a little improvement: the
built-in keyboard worked in X, but the touchpad did not.  Strangely, I
could log into X with the keyboard, and say "cat /dev/input/mice" as
root, and get characters on the screen when I moved my finger on the
touchpad, but X still refused to recognize it for some reason.

In that condition (keyboard worked, touchpad didn't), looking in
/var/log/Xorg.0.log showed that libinput didn't understand that quirks
entry:

---
(EE) Unknown key ModelTabletModeSwitchUnreliable in [Acer E5-511] (50-system-acer.quirks)
(EE) Failed to load the device quirks from /usr/share/libinput and /etc/libinput/local-overrides.quirks. This will negatively affect device behavior. See https://wayland.freedesktop.org/libinput/doc/1.12.6/device-quirks.html for details.
---

A little digging around on freedesktop.org shows that the
ModelTabletModeSwitchUnreliable keyword is not mentioned in the libinput
1.12.6 documentation.  The first version where that option shows up in
the docs is 1.13.0 .

I put the 50-system-acer.quirks file back to its default condition,
without the extra entry suggested in the Debian bug.

I thought I would try disabling that device at the udev level.  As
suggested in the Arch BBS post, I created a new file

/etc/udev/rules.d/99-acer-libinput.rules

with the single line

ACTION=="add|change", KERNEL=="event[0-9]*", ATTRS{name}=="Intel Virtual Button driver", ENV{LIBINPUT_IGNORE_DEVICE}="1"

.

I don't know if I *needed* to do this, but I then ran update-initramfs,
for the 4.19.0-11 kernel.

Then, I powered the laptop completely off with the power button, turned
it back on with the power button, and booted into the 4.19.0-11 kernel.

Success!  Both the keyboard and touchpad work in X again.

They work when I first boot up the laptop into X, and they still work
after I close the lid, let the laptop suspend, open the lid, and let it
come out of suspend.

I'm still not sure why changing which *kernel* I booted made this bug
appear.  Perhaps the old kernel initialized (or didn't initialize) that
input device in a different way than the later ones.

Thanks for your help!

Matt Roberds

[toc] | [prev] | [next] | [standalone]

#228060 — Re: Laptop keyboard and touchpad don't work after upgrading fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED]

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 20, 2020 at 11:49:01PM -0500, Matt Roberds wrote:
> Quick version:

[...]

Thanks a lot for your detailed post-mortem. You made the world
a bit nicer :)

Cheers
 - t

[toc] | [prev] | [next] | [standalone]

#228061 — Re: Laptop keyboard and touchpad don't work after upgrading fromlinux-image-4.19.0-9-amd64 to any later kernel [SOLVED]

On Wed, 21 Oct 2020 at 18:40, <tomas@tuxteam.de> wrote:

> Thanks a lot for your detailed post-mortem. You made the world
> a bit nicer :)

You helped, actually :) I made use of the bug search methods
suggested previously, including yours:
https://lists.debian.org/debian-user/2020/06/msg00962.html

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web