From: Ramakrishnan Muthukrishnan <vu3rdd@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: Fri, 28 Feb 2014 16:40:27 +0530 [thread overview]
Message-ID: <CAA6Yd9WcYagFNAWRMMtLA11+uJHMKHgfMsuioOMmc8DAtyoFSg@mail.gmail.com> (raw)
In-Reply-To: <CAA6Yd9UU1=B2gVRHGrnXcZA6NB9ZD1EBQvSyu2obtRpdR8Tj2w@mail.gmail.com>
Okay, I tried another keyboard/mouse (Logitech Classic New Touch
keyboard) and a Logitech mouse (Logitech RX300) and they didn't work.
When I connect keyboard alone, the booting proceeded and I got the
acme screen. But the keyboard didn't work. When I connect keyboard and
mouse, booting is stuck at the same place as yesterday: "etherusb
smsc: b827ebf340cd".
On Thu, Feb 27, 2014 at 11:01 PM, Ramakrishnan Muthukrishnan
<vu3rdd@gmail.com> wrote:
> On Thu, Feb 27, 2014 at 10:38 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>>
>> On Feb 27, 2014, at 9:05 AM, Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> wrote:
>>
>>> I tried a USB hub (not a powered one though) and it hangs after
>>> printing the following lines:
>>
>> Always use a powered hub with the Pi – it can't supply bugger all for power out its USB ports.
>
> Thank you Lyndon, Steve and Erik. I will try a powered hub tomorrow
> and also get another keyboard/mouse. I also found a previous
> discussion about the USB keyboard/mouse support in Plan9 here:
>
> <https://groups.google.com/forum/#!topic/comp.os.plan9/fhAWlpd2NVs>
>
> --
> Ramakrishnan
--
Ramakrishnan
next prev parent reply other threads:[~2014-02-28 11:10 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 [this message]
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
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=CAA6Yd9WcYagFNAWRMMtLA11+uJHMKHgfMsuioOMmc8DAtyoFSg@mail.gmail.com \
--to=vu3rdd@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).