From: Arazil Songweaver <arazil@arazil.net>
To: linux-input@vger.kernel.org
Subject: Re: BUG: Framework Laptop 16 i2c-hid Based Touchpad Sometimes Fails To Initialize Properly On Early Boot
Date: Tue, 14 May 2024 11:30:51 +0000 [thread overview]
Message-ID: <0111018f76de9aab-52df4770-44d1-4a1a-9e81-d1c955ee9107-000000@us-west-1.amazonses.com> (raw)
In-Reply-To: <e7d0def9-a785-420d-81bf-2502ec89e961@arazil.net>
This issue is also now available on Kernel Bugzilla under:
https://bugzilla.kernel.org/show_bug.cgi?id=218836
-Arazil
On 5/13/24 9:57 PM, Arazil Songweaver wrote:
> We are experiencing an issue where the touch pad on the Framework
> Laptop 16 fails to initialize properly when the "i2c-hid" is loaded
> early in the boot process. This issue is especially prominent when
> "i2c-hid" is built directly into the kernel. When the "i2c-hid" module
> is built in, the issue occurs roughly 50% of the time.
> (https://community.frame.work/t/touchpad-not-working-since-update-archlinux/50304)
> Moving the module load to later in the boot process appears to resolve
> this issue by making initialization more likely to succeed.
> (https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v39.1)
>
next parent reply other threads:[~2024-05-14 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e7d0def9-a785-420d-81bf-2502ec89e961@arazil.net>
2024-05-14 11:30 ` Arazil Songweaver [this message]
2024-05-14 2:57 BUG: Framework Laptop 16 i2c-hid Based Touchpad Sometimes Fails To Initialize Properly On Early Boot Arazil Songweaver
2024-05-21 10:57 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-21 13:31 ` Arazil Songweaver
2024-05-21 13:44 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-22 17:34 ` Arazil Songweaver
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=0111018f76de9aab-52df4770-44d1-4a1a-9e81-d1c955ee9107-000000@us-west-1.amazonses.com \
--to=arazil@arazil.net \
--cc=linux-input@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).