From: David Leimbach <leimy2k@gmail.com>
To: erik quanstrom <quanstro@quanstro.net>
Cc: 9fans@9fans.net
Subject: Re: [9fans] plan 9 on the guruplug
Date: Tue, 31 Aug 2010 08:07:09 -0700 [thread overview]
Message-ID: <AANLkTimwhjmzV=LK7e9ttUz=Sa73M5q3YJEEUXxVrTr4@mail.gmail.com> (raw)
In-Reply-To: <1aed5215dbf1142433aaa801b6585199@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Tue, Aug 31, 2010 at 6:07 AM, erik quanstrom <quanstro@quanstro.net>wrote:
> On Tue Aug 31 03:27:52 EDT 2010, leimy2k@gmail.com wrote:
>
> > Ok, now I can't remember what I just did, but it's working.
> >
> >
> >
> > On Mon, Aug 30, 2010 at 11:59 PM, David Leimbach <leimy2k@gmail.com>
> wrote:
> >
> > > I found something on a french Plan 9 translation site about dd'ing my
> nvram
> > > from my PC to a file in /sys/src/9/kw then building.
> > >
> > > This seems to have gotten me past the point where it crashes because it
> > > can't write to nvram, but it crashes all the same anyway :-)
>
> is there any chance that you either haven't resync'd
> /sys/src/libauthsrv/readnvram.c or that you haven't rebuilt
> your kernel or other auth-related stuff since this change?
>
> Jul 23 18:49:34 EDT 2010
> /n/sourcesdump/2010/0726/plan9/sys/src/libauthsrv/readnvram.c 10695 [geoff]
> 47a48
> > "power", "#F/flash/flash", 0x440000, sizeof(Nvrsafe),
> 50a52
> > "arm", "#F/flash/flash", 0x100000, sizeof(Nvrsafe),
>
> - erik
>
I decided to blow everything away last night and start over, including the
Plan 9 CPU server I am pxe booting from. The plan 9 installation I worked
from was from the ISO available last night.
Looking over my notes it appears the only thing I had to do to prevent the
crash was enable my fossil FS's listening capabilities. Now the guruplug
gets a kernel and an FS every time.
I'm probably going to plan 9 wikify my notes either tonight or tomorrow.
Dave
[-- Attachment #2: Type: text/html, Size: 2187 bytes --]
next prev parent reply other threads:[~2010-08-31 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 1:45 David Leimbach
2010-08-31 2:01 ` erik quanstrom
2010-08-31 3:35 ` David Leimbach
2010-08-31 3:46 ` Skip Tavakkolian
2010-08-31 3:48 ` David Leimbach
2010-08-31 3:52 ` David Leimbach
2010-08-31 6:43 ` David Leimbach
2010-08-31 6:59 ` David Leimbach
2010-08-31 7:26 ` David Leimbach
2010-08-31 13:07 ` erik quanstrom
2010-08-31 15:07 ` David Leimbach [this message]
2010-08-31 18:19 ` David du Colombier
2010-08-31 19:52 ` David Leimbach
2010-08-31 23:06 ` hiro
2010-09-06 11:49 ` Christian Neukirchen
2010-08-31 23:14 ` David Leimbach
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='AANLkTimwhjmzV=LK7e9ttUz=Sa73M5q3YJEEUXxVrTr4@mail.gmail.com' \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
--cc=quanstro@quanstro.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).