From: Sean Hinchee <henesy.dev@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] r-pi usbotg error
Date: Wed, 18 Feb 2015 14:10:00 -0600 [thread overview]
Message-ID: <54E4F198.5010503@gmail.com> (raw)
In-Reply-To: <4C8305E6-9F42-4CBC-9CBE-528929E51EE2@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
I've had mixed results between keyboards. From what I have experienced
the keyboards that have usb hubs built into them drop, but the keyboards
without hubs (or with the hub wire unplugged) didn't drop connection. ymmv
On 2/18/15 12:37 PM, Quintile wrote:
> I use a standard dell keyboard with my b, not b+, and never had a problem.
>
>
>
>
>
> On 18 Feb 2015, at 16:48, Steven Stallion <sstallion@gmail.com
> <mailto:sstallion@gmail.com>> wrote:
>
>> On Sun, Mar 9, 2014 at 11:15 AM, Ramakrishnan Muthukrishnan
>> <vu3rdd@gmail.com <mailto:vu3rdd@gmail.com>> wrote:
>>
>> On Sun, Mar 9, 2014 at 9:11 PM, Rubén Berenguel
>> <ruben@mostlymaths.net <mailto:ruben@mostlymaths.net>> wrote:
>> > Sounds like the keyboard went idle (on its own!?) and the Rasp lost
>> > connection to it. ep6.1 is the name of a USB device (something
>> about logical
>> > unit devices or something,) you can try unplugging something
>> and you'll see
>> > similar things pop up. kb is complaining the keyboard went
>> away, and since
>> > there is no keyboard, died. You could try ungplugging it and
>> plugging it in.
>>
>> Yes, indeed, it came back to life after unplugging and
>> re-plugging. Thanks.
>>
>>
>> Last night I finally got around to getting a B+ I've had sitting in
>> the closet and converted it to a terminal. I'm seeing this same
>> problem. I've tried unplugging multiple keyboards and have also tried
>> using a powered hub. I'm at a loss. Has anyone else figured out how
>> to deal with this issue?
>>
>> Steve
[-- Attachment #2: Type: text/html, Size: 3443 bytes --]
next prev parent reply other threads:[~2015-02-18 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 15:34 Ramakrishnan Muthukrishnan
2014-03-09 15:39 ` erik quanstrom
2014-03-09 15:41 ` Rubén Berenguel
2014-03-09 15:44 ` erik quanstrom
2014-03-09 15:47 ` Rubén Berenguel
2014-03-09 16:15 ` Ramakrishnan Muthukrishnan
2014-03-09 16:21 ` erik quanstrom
2014-03-09 16:24 ` erik quanstrom
2015-02-18 16:48 ` Steven Stallion
2015-02-18 17:17 ` Joe Bowers
2015-02-18 18:37 ` Quintile
2015-02-18 20:10 ` Sean Hinchee [this message]
2015-02-18 22:00 ` Steven Stallion
2015-02-18 22:04 ` Steve Simon
2015-02-19 7:06 ` k0ga
2015-02-18 20:50 ` Bakul Shah
2015-02-18 22:00 ` Steven Stallion
2015-02-19 3:42 ` erik quanstrom
2015-02-19 3:43 ` erik quanstrom
2015-02-19 12:14 ` Richard Miller
2015-02-20 3:04 ` sstallion
2015-02-20 3:25 ` erik quanstrom
2015-02-20 13:27 ` Steven Stallion
2015-02-20 14:13 ` erik quanstrom
2015-02-20 15:39 ` sstallion
2015-02-19 5:07 ` Ramakrishnan Muthukrishnan
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=54E4F198.5010503@gmail.com \
--to=henesy.dev@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).