From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <140e7ec30802250905t689d929cmfa5e59e1790b471@mail.gmail.com>
Date: Tue, 26 Feb 2008 02:05:05 +0900
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
In-Reply-To: <405dc979e7c6cd32b74a77f5347b5df4@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <140e7ec30802250737v773aaeedwf72f01e510bd18fb@mail.gmail.com>
	<405dc979e7c6cd32b74a77f5347b5df4@coraid.com>
Topicbox-Message-UUID: 615a3b78-ead3-11e9-9d60-3106f5b1d025

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