From owner-freebsd-ppc@FreeBSD.ORG Thu May 28 14:48:04 2009 Return-Path: Delivered-To: ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 224161065672 for ; Thu, 28 May 2009 14:48:04 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id E0A228FC16 for ; Thu, 28 May 2009 14:48:03 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n4SEm2cl006710; Thu, 28 May 2009 08:48:02 -0600 Message-Id: From: Rafal Jaworowski To: Marcel Moolenaar In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 28 May 2009 16:48:00 +0200 References: X-Mailer: Apple Mail (2.935.3) Cc: ppc@FreeBSD.org Subject: Re: MPC8555CDS: U-Boot vs loader compatibility 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: Thu, 28 May 2009 14:48:04 -0000 On 2009-05-26, at 21:15, Rafal Jaworowski wrote: > On 2009-05-26, at 18:50, Marcel Moolenaar wrote: > >> I think I recently updated the FreeBSD loader on my CDS >> that has U-Boot version 1.3.2-rc1 on it (yes, that sounds >> rather fuzzy :-) In any case, the latest PowerPC U-Boot >> loader is having a problem with netbooting. I see packets >> being transmitted (BOOTP), but none of the responses seem >> to arrive at the loader. Then the ARP resolution is >> attempted, which fails as well. > > I'll try the latest loader tomorrow and let you know how this work > here. I checked a freshly built loader from HEAD and it works fine with U- Boot 2008.10-rc2-00091-g2f4342b. One other random thought: I don't know if you were altering your set- up, but make sure the Ethernet cable is physically connected to the socket, whose MAC address you expect to be recognized/served by DHCP/ BOOTP. U-Boot silently switches to a next phy on the list in search for the active link if the given one is not active, so when the found- to-be active does not match you could observe things like this... Rafal