From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 209011] asus-wmi always reports tablet mode on a ZenBook UX390UAK
Date: Wed, 28 Jul 2021 11:39:48 +0000 [thread overview]
Message-ID: <bug-209011-215701-AfpBpBNnIk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209011-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209011
--- Comment #7 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
Julius, thank you for your bug report.
5.13.5 does contain the fix for the origin bug reported here. For a while now
the kernel's asus-wmi code will only report SW_TABLET_MODE on devices on which
it is explicitly enabled by a DMI match, on all other models the asus-wmi code
will not report SW_TABLET_MODE at all.
So I wonder if the SW_TABLET_MODE is perhaps being reported by another driver
such as the intel-hid or intel-vbtn code.
If you look at the libinput output in comment 0:
-event7 DEVICE_ADDED Asus WMI hotkeys seat0 default
group9 cap:kS
event7 SWITCH_TOGGLE +0.000s switch tablet-mode state 1
Then the "event7" on the beginning of the line is the same for both devices. I
suspect that if you look-up the DEVICE_ADDED line for the "event#" with which
the SWITCH_TOGGLE which you are seeing is prefixed, then it will be another
device then the "Asus WMI hotkeys" device.
If the DEVICE_ADDED with the matching "event#" is the "Asus WMI hotkeys"
device, then something weird is going on with the DMI matching, in that case
please provide the output of: "cat /sys/class/dmi/id/sys_vendor
/sys/class/dmi/id/product_name"
If the DEVICE_ADDED with the matching "event#" is for another device, which I
expect, please provide the following info:
1. Can you please add "wmi.debug_event=1 wmi.debug_dump_wdg=1" to your kernel
commandline (see your distro's documentation) and then reboot and fold the
device into tablet-mode and back to laptop-mode once. After this run "dmesg >
dmesg.txt" and attach the generated dmesg.txt file here.
2. Run "sudo acpidump -o acpidump.txt" and attach the generated acpidump.txt
file here.
3. Run "ls -l /sys/bus/iio/devices > ls-bus-iio.txt" and attach the generated
ls-bus-iio.txt file here.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-07-28 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209011-215701@https.bugzilla.kernel.org/>
2021-07-26 22:20 ` [Bug 209011] asus-wmi always reports tablet mode on a ZenBook UX390UAK bugzilla-daemon
2021-07-28 11:39 ` bugzilla-daemon [this message]
2021-07-28 12:31 ` bugzilla-daemon
2021-07-28 12:35 ` bugzilla-daemon
2021-07-28 12:43 ` bugzilla-daemon
2021-07-28 13:02 ` bugzilla-daemon
2021-07-28 13:20 ` bugzilla-daemon
2021-07-28 18:10 ` bugzilla-daemon
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=bug-209011-215701-AfpBpBNnIk@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).