9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Philip Silva <philip.silva@protonmail.com>
To: 9front@9front.org
Subject: Re: [9front] mnt reform trackball stops responding
Date: Thu, 20 Jul 2023 16:36:47 +0000	[thread overview]
Message-ID: <7PQ9n200ftvgU2F5Cs1PkzmubiLeIRvrNmOSaEViNQQx0kxWPaG7HK5s3HahKFcNGbyupYpYxKY3oc8ya9zvQsG_VWih41nqBVndIKMv0ps=@protonmail.com> (raw)
In-Reply-To: <78B0EA9030BFDE1E7310CF0B0703D330@gaff.inri.net>

Actually I had the same problem (but also problems with the screen) and this was done: https://community.mnt.re/t/trackball-v2-with-rp2040-requires-a-trace-cut/1473

Although it was the other way around for me, I usually connected any external mouse after the internal trackball stopped working


  reply	other threads:[~2023-07-20 16:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  3:19 sl
2023-07-19  3:32 ` sl
2023-07-20 16:36   ` Philip Silva [this message]
2023-07-20 18:59     ` Stanley Lieber
2023-07-21  2:46       ` sl
2023-07-22 16:31         ` Philip Silva
2023-07-22 17:24           ` Stanley Lieber
2023-07-26 19:51             ` Sigrid Solveig Haflínudóttir
2023-07-26 23:39               ` cinap_lenrek
2023-07-27 15:10                 ` sl
2023-07-27 16:32                   ` Sigrid Solveig Haflínudóttir
2023-07-26 23:48               ` [9front] 9front Boots Into "No Config" -- The Most Bizarre Error Of Them All Jay F. Shachter
2023-07-27  0:55                 ` Jacob Moody
2023-07-27  0:25               ` [9front] mnt reform trackball stops responding sl
2023-07-31 23:43                 ` cinap_lenrek
2023-08-02  1:17                   ` sl
2023-08-02  3:03                     ` ieliedonge
2023-08-02  3:36                       ` sl
2023-08-02 20:52                     ` cinap_lenrek
2023-07-31 23:48                 ` cinap_lenrek

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='7PQ9n200ftvgU2F5Cs1PkzmubiLeIRvrNmOSaEViNQQx0kxWPaG7HK5s3HahKFcNGbyupYpYxKY3oc8ya9zvQsG_VWih41nqBVndIKMv0ps=@protonmail.com' \
    --to=philip.silva@protonmail.com \
    --cc=9front@9front.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).