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 20:42:53 +0530 [thread overview]
Message-ID: <CAA6Yd9V7_Vnt73+5wUY9TWF1d9goShjv+DmQ3ask1Q4WN2SZ1g@mail.gmail.com> (raw)
In-Reply-To: <4AA9D73E-127B-427E-A2B6-0FD8348CADC6@bitblocks.com>
On Fri, Feb 28, 2014 at 8:05 PM, Bakul Shah <bakul@bitblocks.com> wrote:
>
>> When mouse+keyboard is connected, it shows this:
>>
>> ...
>> #u/usb/ep1.0: dwcotg: port 0x0 irq 9
>> #l0: usb: 100Mbps port 0x0 irq -1: 000000000..00
>> 496M memory: 101M kernel data, 395M user, 1877M swap
>> usb/hub... usb/ether...
>> etherusb smsc: ...
>> usb/kb...
>>
>> and it hangs.
>>
>> When I connect only the keyboard, it goes past this screen, but I
>> can't read it, it was too fast for me to read.
>
> This seems like a power problem. If you're using the USB port of a computer to power the RasPi, it is not going to provide enough current. Use a supply that can provide an amp or more such as an apple iPhone charger (or a powered USB hub). Check out the FAQ and newbie forums at the raspberrypi site. This is also why you should try bringing up raspbian first.
Thank you Bakul. I am downloading Raspbian distro now. I guess USB
hosts need not provide more than 100mA is it is not enumerated (and
500mA once enumerated). I will try my cell phone charger with RPi +
Rasbian.
--
Ramakrishnan
next prev parent reply other threads:[~2014-02-28 15:12 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 [this message]
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=CAA6Yd9V7_Vnt73+5wUY9TWF1d9goShjv+DmQ3ask1Q4WN2SZ1g@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).