From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Keyboard regression by intel-vbtn
Date: Tue, 29 Sep 2020 10:48:54 +0200 [thread overview]
Message-ID: <s5hft71klxl.wl-tiwai@suse.de> (raw)
Hi Hans,
it seems that the recent update of intel-vtn broke the keyboard input
on some laptops with libinput:
https://bugzilla.opensuse.org/show_bug.cgi?id=1175599
Blacklisting intel-vtn fixes the issue, so it's likely the falsely
reported tablet mode switch that leads libinput misbehaving. The
affected machines are Acer E5-511 and ASUS X756UX laptops, and they
shouldn't have the tablet mode at all, AFAIK.
Could you take a look? I guess it's the commit cfae58ed681c that
broke. The chassis type is Notebook on those, and this type should be
excluded as well as Laptop.
The dmidecode outputs and other info are found in the bugzilla above:
https://bugzilla.opensuse.org/attachment.cgi?id=841999
https://bugzilla.opensuse.org/attachment.cgi?id=842039
The one for ASUS is embedded in hwinfo outpt:
https://bugzilla.opensuse.org/attachment.cgi?id=841157
thanks,
Takashi
next reply other threads:[~2020-09-29 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:48 Takashi Iwai [this message]
2020-09-29 9:21 ` Keyboard regression by intel-vbtn Hans de Goede
2020-09-29 9:29 ` Takashi Iwai
2020-09-29 9:59 ` Barnabás Pőcze
2020-09-29 10:17 ` Hans de Goede
2020-09-29 12:27 ` Limonciello, Mario
2020-09-29 12:54 ` Hans de Goede
2020-09-29 14:25 ` Limonciello, Mario
2020-09-29 16:53 ` Andy Shevchenko
2020-09-29 20:37 ` Limonciello, Mario
2020-09-29 20:47 ` Limonciello, Mario
2020-09-30 13:28 ` Hans de Goede
2020-09-30 15:12 ` Limonciello, Mario
2020-09-30 15:36 ` Hans de Goede
2020-09-30 16:02 ` Limonciello, Mario
2020-09-29 14:19 ` Hans de Goede
2020-09-30 13:21 ` Hans de Goede
2020-09-30 13:21 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hft71klxl.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox