From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 16 20:15:38 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F3261065693; Tue, 16 Feb 2010 20:15:38 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id BEC4D8FC21; Tue, 16 Feb 2010 20:15:37 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-8-131.flashcable.ch [91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id o1GKFXBp016832; Tue, 16 Feb 2010 21:15:34 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4B7AFCDB.2070002@fgznet.ch> Date: Tue, 16 Feb 2010 21:15:23 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B7970D7.4010702@freebsd.org> In-Reply-To: <4B7970D7.4010702@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: FreeBSD PowerPC ML Subject: Re: powerpc64 status and request for testers X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2010 20:15:38 -0000 Hi Nathan, On 15.02.10 17:05, Nathan Whitehorn wrote: > I have been working on a full 64-bit PowerPC port of FreeBSD which is > now mature enough that wider exposure and testing would be appreciated. > It boots multiuser and most ports seem to just work, etc. Note that this > is still very raw, however; building it remains tricky, and it may have > fatal bugs resulting in data loss. > > Caveats: > - Memory above 2 GB is not really supported yet, due to lack of IOMMU > support or bounce buffers. Is more memory ignored or does it hurt operation? > Then set up a DHCP server for netbooting, turn on tftpd, and issue a > command like boot enet:0,loader.ppc64 from open firmware on the target > machine. If you give this code a try, please let me know the results. I have my issues here, though I do not know if ppc related or DHCP/TFTP. The target is a Dual 1.8Ghz G5, 2.5GB Memory. The build host is an i386 which eports the installation on /exports/netboot/ppc64 The tftpboot directory contains the loader.ppc64 The dhcpd.conf looks like this: host bohrium { hardware ethernet 00:0a:95:bf:0f:de; fixed-address bohrium.andreas.nets; next-server 192.168.225.35; filename "loader.ppc64"; option root-path "192.168.225.35:/export/netboot/ppc64"; } I can issue the of boot command and I see that I can download the loader.ppc64. It 'starts' with my build machines name etc. But then I get repeated messages like below: xmt1 timeout , STAT=00002086, Txlist.status=efbeadde:efbeadde a lot of lines after it says 'bootp: no reply' and 'panic: arp: no response for 0.0.0.0' I had to manually type that down.... Any idea? Is my tftp/dhcp crap? Or is my G5 not ready yet ;) TIA, Andreas