From owner-freebsd-ia64 Wed Jan 30 11: 6: 1 2002 Delivered-To: freebsd-ia64@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 3828137B416 for ; Wed, 30 Jan 2002 11:05:55 -0800 (PST) Received: (from marcel@localhost) by kayak.xcllnt.net (8.11.6/8.11.4) id g0UJ5Eh32639; Wed, 30 Jan 2002 11:05:14 -0800 (PST) (envelope-from marcel) Date: Wed, 30 Jan 2002 11:05:13 -0800 From: Marcel Moolenaar To: Espen Skoglund Cc: freebsd-ia64@freebsd.org Subject: Re: EFI loader problems Message-ID: <20020130110513.A32617@kayak.xcllnt.net> References: <15446.56138.273576.286815@i30nb20.ira.uka.de> <20020129200539.A386@dhcp01.pn.xcllnt.net> <15447.54977.322077.139805@i30nb20.ira.uka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15447.54977.322077.139805@i30nb20.ira.uka.de> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jan 30, 2002 at 12:19:29PM +0100, Espen Skoglund wrote: > > I think the failure mode was something different. Hmm... Well, it > doesn't really matter. Point is that tftpd is *not* the problem. The > problem seems to be more of the nature of what you desribed in a > posting to this list in November. Booting a newly compiled loader > failed with "not found", but booting an old loader image worked fine. Ok. I must admit I'm avoiding this problem by not recompiling the EFI loader and if I do, use an older toolchain. Maybe it's time to nail it down... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message