9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 on Fit-PC
Date: Tue, 26 Feb 2008 02:05:05 +0900	[thread overview]
Message-ID: <140e7ec30802250905t689d929cmfa5e59e1790b471@mail.gmail.com> (raw)
In-Reply-To: <405dc979e7c6cd32b74a77f5347b5df4@coraid.com>

On Tue, Feb 26, 2008 at 12:57 AM, erik quanstrom <quanstro@coraid.com> wrote:
> >  I also tried to netboot from my existing cpu/auth/file server. The
>  > netboot ROM on the ethernet downloads the kernel but couldn't seem to
>  > find a spot in memory to put it[1], so I grabbed gPXE 0.9.3 from
>  > http://www.etherboot.org/ and built an ISO. The last thing I see there
>  > is "Booting from /386/9pc..." and then the machine reboots. I'm not
>  > sure if this is even getting the whole kernel... last line in
>  > /sys/log/ipboot is:
>
>  that went by a bit fast for me.
>
>  do you mean that you are pxe loading 9pxeload but the bios pxeloader
>  can't find a place for 9pxeload in memory?  or that 9pxeload loaded but
>  couldn't load the kernel?  the plan 9 kernel can't be pxe loaded directly.
>  it's too big & l.s doesn't handle real mode.

 Ahh, that's what I'm doing wrong. Doesn't surprise me, I'm new to netbooting ;)
 Also, /lib/ndb/local.complicated has bootf arguments that refer to
real kernels so it didn't occur to me to look for something else. With
bootf=/386/9pxeload, the netboot gets as far as the cd boot - ie it
freezes after "ELCR: 0E20".
 Thanks.
-sqweek


  reply	other threads:[~2008-02-25 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 15:37 sqweek
2008-02-25 15:57 ` erik quanstrom
2008-02-25 17:05   ` sqweek [this message]
2008-02-25 16:19 ` ron minnich
2008-02-25 16:56   ` sqweek

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=140e7ec30802250905t689d929cmfa5e59e1790b471@mail.gmail.com \
    --to=sqweek@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).