From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi help
Date: Mon, 10 Dec 2012 18:55:10 +0000 [thread overview]
Message-ID: <65c2af2d38a9e7e576b437b7601da10c@hamnavoe.com> (raw)
In-Reply-To: <bef5e4b9-1ccc-4c52-8ada-42ec28d7d898@googlegroups.com>
> I cannot
> get the mouse or keyboard to work (including with the 7 December
> kernel).
See if you can get a bit more diagnostic information than just
"doesn't work", by editing your cmdline.txt to something like this:
readparts=1 kbargs=-d ipconfig=
By removing the 'user=glenda' parameter you'll stop it from
loading the rio desktop; the 'ipconfig=' parameter will make
it look for a DHCP server on your network to give it an ip
address; and the 'kbargs=-d' asks for debugging information
from the usb keyboard+mouse driver.
next prev parent reply other threads:[~2012-12-10 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 17:40 Adrian McMenamin
2012-12-10 18:55 ` Richard Miller [this message]
2012-12-11 9:36 ` Luke Evans
2012-12-17 9:40 ` Adrian McMenamin
2012-12-17 10:01 ` Richard Miller
2012-12-17 9:40 ` Adrian McMenamin
2012-12-17 10:23 ` Bakul Shah
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=65c2af2d38a9e7e576b437b7601da10c@hamnavoe.com \
--to=9fans@hamnavoe.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).