Subject: Re: Trouble building -current
To: Michael Wolfson <michael@nosflow.com>
From: Jochen Kunz <jkunz@unixag-kl.fh-kl.de>
List: port-hp700
Date: 11/14/2004 23:54:18
On Sat, 13 Nov 2004 16:02:23 -0800
Michael Wolfson <michael@nosflow.com> wrote:

> > The current boot loaders can not switch boot devices during boot.
> > I.e. if you loaded the bootloader via network, you have to load the
> > kernel via network too.
> Oh well.  I guess I was figuring it was like the hp300 bootloader
> which can do that.
The hp700 boot loader could do it too, if someone implements it / fixes
the current code.

> Ah, that only works once I have my system running NetBSD.  Too bad=20
> installboot doesn't work, since that can be run from another NetBSD=20
> platform.
Yes, hp700 installboot MD parts need work.

> OK, so what you're saying is that even if I got NetBSD onto a had=20
> drive, it wouldn't run from it,=20
Yes, at the moment.=20

> so I'd need to use an nfs root filesystem.  And since when I netboot a
> kernel it doesn't find the nfs root, I'd need to have a root
> filesystem on disk, which doesn't work.
OK, it some time that I had time to work on hp700, but NFS root worked
well and the kernel had no problem finding the NFS root. I did some
improvements to that code last summer.

> That kinda makes it difficult for me to try playing with this platform
Well. It is still an experimental port.

> So, how exactly do you have your setup running?  Or is it simply an=20
> ethernet issue with iee?
What exactely is your problem? tftp the LIF images with boot loader and
kernel. The kernel should do a DHCP query and mount the NFS directory
specified via DHCP.

> Nevertheless, build.sh release ought to bundle up the GENERIC kernel=20
> into a netbootable format, so first-time users don't need to install=20
> all the source code and cross-compile a toolchain just to get=20
> nbhp700-mkboot.
As said: This is an experimental port. Please don't expect that
everything works out of the box. This things will be fixed some time,
but we have to live with current situation. There are more serious
problems then missing installation kernels, see the problem when booting
from disk. Unfortunately this bug is quite hard to find. I and other
developers tried to debug this, without success. :-(
--=20


tsch=FC=DF,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/