From: fiatisdead <fiatisdead@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Goodix Touchscreen support?
Date: Thu, 21 Oct 2021 17:12:21 +0200 [thread overview]
Message-ID: <20211021151221.tyNlQlio9wDjn-8w3QK0RXm5U9jDY541ant6ur8yPDQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33277@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
New comment by fiatisdead on void-packages repository
https://github.com/void-linux/void-packages/issues/33277#issuecomment-948715001
Comment:
Thanks Wesley
Current Kernel: 5.13.19_1
I installed linux5.6 but it appeared to make no difference at all even after a reboot.
I then blacklisted as per your point 2.
The dmesg still gives the same error as https://github.com/void-linux/void-packages/issues/33277#issuecomment-932994793
https://github.com/void-linux/void-packages/issues/33277#issuecomment-932994793After blacklisting and following a reboot checking dmesg output.
I also tried manually loading by issuing modprobe goodix and nothing happens. The dmesg output doesn’t really change. Same errors as previously mentioned.
Appreciate your efforts in trying to assist.
On Thu, Oct 21, 2021 at 14:17, Wesley ***@***.***> wrote:
> Hi, ***@***.***(https://github.com/fiatisdead). Would you please try the followings?
>
> - Kindly tell us the version of the kernel you are using with uname -a. Try to install version 5.6 (sudo xbps-install linux5.6) or earlier to see if that brings the touchscreen back to life.
> - Try to blacklist (# echo "blacklist goodix" >> /etc/modprobe.d/blacklist) Goodix module, then manually load it after boot (# modprobe goodix), see if it does anything. You may want to monitor dmesg output in the process.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, [view it on GitHub](https://github.com/void-linux/void-packages/issues/33277#issuecomment-948607518), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AV4NVKS7LOPPALGLI4IOILDUIAHFNANCNFSM5FG4XFHQ).
> Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).
next prev parent reply other threads:[~2021-10-21 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 23:16 [ISSUE] " fiatisdead
2021-10-03 14:09 ` fiatisdead
2021-10-03 17:08 ` biopsin
2021-10-03 17:12 ` biopsin
2021-10-03 17:40 ` fiatisdead
2021-10-03 17:40 ` fiatisdead
2021-10-03 21:04 ` biopsin
2021-10-04 10:55 ` fiatisdead
2021-10-10 11:11 ` biopsin
2021-10-21 13:17 ` Wesley-Chan
2021-10-21 15:12 ` fiatisdead [this message]
2021-10-23 23:53 ` Wesley-Chan
2022-06-06 2:15 ` github-actions
2022-06-21 2:12 ` [ISSUE] [CLOSED] " github-actions
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=20211021151221.tyNlQlio9wDjn-8w3QK0RXm5U9jDY541ant6ur8yPDQ@z \
--to=fiatisdead@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).