9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jecoz <danielmorandini@me.com>
To: 9fans <9fans@9fans.net>
Subject: [9front] Amazon Basics USB mice not working on RPi 2
Date: Sun, 26 Apr 2020 05:32:48 -0400	[thread overview]
Message-ID: <15878935680.1CedE24.37998@composer.9fans.topicbox.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]

Hi folks,
I have a RPi 2 with the latest NOTHINKPAD running [1]. Unfortunately the mice I’m using is not working as expected, it is an Amazon Basics USB 3 button wired mice [2]. This is not explicitly listed in the supported hardware list I know, but it works with miller’s legacy image [3], so... I guess it is supposed to work here too!

What I did:
- plugged keyboard and mice to the RPi
- powered the rasp
- logged in as glenda
- moved the mouse

Later on I also changed CMDLINE.TXT adding:
- mouseport=ps2intellimouse, as my mouse has the wheel [4]

What happens:
- buttons do not work in any form (neither 1, 2 or 3): pup-up window does not appear, I cannot resize, move, cannot chord
- when I hover the corners of a window, its content, e.g. "term%”, glitch as I move (I can provide a video of the screen if needed)

What is supposed to happen is straightforward I guess.
Everything else seems to be working (I cannot/am able to test it properly without mice though).

Messages I read from UART:
```
init: starting /bin/rc
aux/timesync: accessing /dev/rtc: '/dev/rtc' file does not exist
echo: write error: unknown control message "res 3"
nusb/usbd: usbcmd: /dev/usb/ep5.0: required 4 attempts (no data from device)
nusb/kb: usbcmd: /dev/usb/ep5.0: required 4 attempts (no data from device)
nusb/kb: usbcmd: /dev/usb/ep5.0: required 4 attempts (no data from device)
127 holes free
0x0034e000 0x1912f000 417206272
417206272 bytes free

Plan 9 from Bell Labs
board rev: 0xa01041 firmware rev: 1569854467
cpu0: 900MHz ARM Cortex-A7 r0p5
fp: 32 registers,  simd
fp: arm arch VFPv3+ with common VFP subarch v2; rev 5
998M memory: 402M kernel data, 596M user, 3580M swap
cpu1: 900MHz ARM Cortex-A7 r0p5
cpu2: 900MHz ARM Cortex-A7 r0p5
cpu3: 900MHz ARM Cortex-A7 r0p5
nusb/usbd: usbcmd: /dev/usb/ep4.0: required 4 attempts (no data from device)
nusb/kb: usbcmd: /dev/usb/ep4.0: required 4 attempts (no data from device)
nusb/kb: usbcmd: /dev/usb/ep4.0: required 4 attempts (no data from device)

/dev/sdM0: Arasan eMMC SD Host Controller 02 Version 99
/dev/sdM0/data
/dev/sdM0/dos	 dos
/dev/sdM0/fs	 hjfs
/dev/sdM0/nvram
/dev/sdM0/plan9
bootargs is (tcp, tls, il, local!device)[local!/dev/sdM0/fs]
user[glenda]: glenda
hjfs: fs is /dev/sdM0/fs
```
Any thoughts? :)

Ciao,
Daniel

[1] http://bell-labs.co/9front/iso/9front-7408.1d345066125a.pi.img.gz.torrent
[2] https://www.amazon.com/dp/B005EJH6RW/ref=cm_sw_em_r_mt_dp_U_c2dPEbWCW145Q
[3] https://9p.io/sources/contrib/miller/9pi.img.gz
[4] http://fqa.9front.org/fqa4.html

[-- Attachment #2: Type: text/html, Size: 3742 bytes --]

                 reply	other threads:[~2020-04-26  9:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=15878935680.1CedE24.37998@composer.9fans.topicbox.com \
    --to=danielmorandini@me.com \
    --cc=9fans@9fans.net \
    /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).