From owner-freebsd-ppc@FreeBSD.ORG Thu Mar 18 04:48:06 2004 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BBDB16A4CE for ; Thu, 18 Mar 2004 04:48:06 -0800 (PST) Received: from liberty.onthenet.com.au (liberty.OntheNet.com.au [203.22.124.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1532343D1F for ; Thu, 18 Mar 2004 04:48:06 -0800 (PST) (envelope-from grehan@freebsd.org) Received: from freebsd.org (CPE-31-248.dsl.onthenet.net [203.144.31.248]) i2ICm3ZG040196; Thu, 18 Mar 2004 22:48:04 +1000 (EST) (envelope-from grehan@freebsd.org) Message-ID: <40599B49.8020706@freebsd.org> Date: Thu, 18 Mar 2004 22:51:21 +1000 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "David S. Besade" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-ppc@freebsd.org Subject: Re: Problems Installing FreeBSD-PPC X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 12:48:06 -0000 Hi David > Okay tried that new kernel in my setup and all. Thought you might like to > know that I finally got DHCPD, TFTP and NFS all running off my Mac, properly > it seems, the DHCPD is finally sending all the BOOTP info. Did you have to do much different than the posted instructions for FreeBSD ? > (the load comes up, says it can't find/load the kernel) > I type (at the loader prompt) > > Load kernel/kernel.dc I should have mentioned that kernel.dc has to be renamed to 'kernel', or the manual load command used as you did. > mountroot> nfs > Mounting root from nfs > nfs_diskless: no interface ... > Welp what next? Looks like the PCI ID for the 21143 eth chip isn't being matched by the driver, so that has to be determined. Try a 'boot -v', and hopefully you will see the PCI IDs of all devices go past and be able to see the eth ID before it scrolls by. I might have some more detailed instructions tomorrow when I can get to a test system and give you some expected text. later, Peter.