From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Issues with USB mouse in 9atom
Date: Mon, 21 Sep 2015 17:04:56 -0700 [thread overview]
Message-ID: <d2b7af5cefd12ab9814e7d3308021c9e@lilly.quanstro.net> (raw)
In-Reply-To: <CA+VQh+zssYGOH8QSv64UpwC3w76En--bjL8cL3LO_K79Lrg=fw@mail.gmail.com>
> After obtaining a disk drive for an old PC I've had for a little while, I
> was overjoyed to turn it into a dedicated 9 machine. I realized could have
> a second server as part of my 9junk grid! However, it seems the original
> site from bell labs is down, and that since 9front apparently can't find a
> bootstrap processor, so I decided to give 9atom a try. It installed
> successfully, minus this "spurious interrupt 39" message everywhere.
>
> However, there seems to be an issue using the mouse. It's just a generic
> black dell USB mouse. Whenever I right click to open a window (or use the
> menu at all), it seems as if it detects the release much too early, and
> doesn't always give me time to choose the correct option. Before I go out
> to buy a new mouse (which I don't mind at all, considering money is no
> object for my love for 9), is there anything I can write into a config file
> of some sort, or edit and recompile in a driver?
i don't see any confirmation, but it looks like the install was from the cd image?
if so, i recommend using the usb install image instead
http://ftp.9atom.org/other/usbinstamd64.bz2
this *should* fix all those issues. posting a few details on the processor might
be helpful in figuring out any issues.
- erik
next prev parent reply other threads:[~2015-09-22 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 22:38 Roswell Grey
2015-09-22 0:04 ` erik quanstrom [this message]
2015-09-22 11:21 ` cinap_lenrek
2015-09-22 20:38 Roswell Grey
2015-09-22 21:58 ` erik quanstrom
2015-09-23 0:44 ` erik quanstrom
2015-09-23 2:23 ` erik quanstrom
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=d2b7af5cefd12ab9814e7d3308021c9e@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--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).