From: Grant Mather <hcaulfield57@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi: won't recognize the USB mouse
Date: Thu, 27 Feb 2014 21:31:27 -0700 [thread overview]
Message-ID: <20140228043127.GA55171@Grants-MacBook.local> (raw)
In-Reply-To: <CAA6Yd9V1YTbLiWniUQCSq0wYkGxzs7iyGxHkE_55EQHpQ2bRBg@mail.gmail.com>
This probably won't help, but what happened when I installed Plan 9 onto
my Raspberry Pi, is the mouse worked but not the keyboard. So I ended up
going to store and buying the cheapest keyboard that I could find. I
plugged in the keyboard and it worked. It wasn't a power issue because
Linux worked with the previous keyboard/mouse combo. I then configured
the system as a cpu/fs/auth server so I don't have to worry about
keyboard or mouse anymore :)
Regardless, my solution was just trying different combinations of mouse
and keyboard until I found one that would work, your mileage may vary.
Hope this helps,
Grant
On Wed, Feb 26, 2014 at 10:52:20PM +0530, Ramakrishnan Muthukrishnan wrote:
> On Wed, Feb 26, 2014 at 9:57 PM, Ramakrishnan Muthukrishnan
> <vu3rdd@gmail.com> wrote:
> > Hello Plan9 hackers,
> >
> > I booted up the new raspberry pi I got last week with an SD Card with
> > the 9pi image from the Labs website. I realised that my monitor
> > doesn't have an HDMI input and only DVI, VGA and DisplayPort, so
> > instead, I connected the little board to my 32" TV and the glenda
> > appeared within 2-3 seconds, the fastest bootup I have ever seen! I
> > could see that the rc script gets executed and acme appears.
> >
> > But my USB mouse won't get recognized by Plan9. I tried two different
> > USB mouse and both of them didn't talk to plan9. Is there a way I can
> > see any logs in the kernel (like the /var/log/kern.log in the linux
> > kernel) to see what exactly happened? I will also try a DVI->HDMI
> > cable tomorrow to see if it can talk to my monitor.
>
> I found some previous discussion about the topic here:
> <https://groups.google.com/forum/#!msg/comp.os.plan9/bpd6snmwJAk/Vxsr24BdO7wJ>
>
> I will try these out tomorrow.
>
> --
> Ramakrishnan
next prev parent reply other threads:[~2014-02-28 4:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:27 Ramakrishnan Muthukrishnan
2014-02-26 17:19 ` Richard Miller
2014-02-27 16:27 ` Ramakrishnan Muthukrishnan
2014-02-27 16:35 ` Ramakrishnan Muthukrishnan
2014-02-27 17:05 ` Ramakrishnan Muthukrishnan
2014-02-27 17:08 ` Lyndon Nerenberg
2014-02-27 17:31 ` Ramakrishnan Muthukrishnan
2014-02-27 18:03 ` Bakul Shah
2014-02-28 11:10 ` Ramakrishnan Muthukrishnan
2014-02-28 11:28 ` Richard Miller
2014-02-28 14:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:35 ` Bakul Shah
2014-02-28 15:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:45 ` Anthony Sorace
2014-02-28 15:15 ` Ramakrishnan Muthukrishnan
2014-02-28 16:24 ` Bakul Shah
2014-03-04 14:12 ` Ramakrishnan Muthukrishnan
2014-03-04 14:27 ` erik quanstrom
2014-03-04 15:54 ` Ramakrishnan Muthukrishnan
2014-03-04 16:26 ` erik quanstrom
2014-03-04 18:18 ` Bakul Shah
2014-03-04 18:26 ` erik quanstrom
2014-03-08 14:56 ` Ramakrishnan Muthukrishnan
2014-03-08 14:59 ` erik quanstrom
2014-03-09 13:25 ` Ramakrishnan Muthukrishnan
2014-03-09 13:46 ` erik quanstrom
2014-03-05 10:57 ` Richard Miller
2014-03-05 10:59 ` Richard Miller
2014-02-27 17:10 ` erik quanstrom
2014-02-27 17:15 ` Steve Simon
2014-02-26 17:22 ` Ramakrishnan Muthukrishnan
2014-02-28 4:31 ` Grant Mather [this message]
2014-02-28 9:05 ` erik quanstrom
2014-03-01 5:43 Michael Hansen
2014-03-01 12:09 ` Richard Miller
2014-03-01 12:12 ` erik quanstrom
2014-03-02 10:46 ` Richard Miller
2014-03-02 14:57 ` erik quanstrom
2014-03-02 19:54 ` Richard Miller
2014-03-02 23:22 ` Winston Kodogo
2014-03-03 1:29 ` erik quanstrom
2014-03-03 11:05 ` Richard Miller
2014-03-03 11:24 ` Richard Miller
2014-03-03 13:39 ` erik quanstrom
2014-03-02 1:12 Michael Hansen
2014-03-02 1:39 ` 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=20140228043127.GA55171@Grants-MacBook.local \
--to=hcaulfield57@gmail.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).