Date: Wed, 30 Jan 2002 12:19:29 +0100 From: Espen Skoglund <esk@ira.uka.de> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Espen Skoglund <esk@ira.uka.de>, freebsd-ia64@freebsd.org Subject: Re: EFI loader problems Message-ID: <15447.54977.322077.139805@i30nb20.ira.uka.de> In-Reply-To: <20020129200539.A386@dhcp01.pn.xcllnt.net> References: <15446.56138.273576.286815@i30nb20.ira.uka.de> <20020129200539.A386@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[Marcel Moolenaar] > I recently upgraded my server to 4.5-RC and as such destroyed the > tftp version I was using. I forgot that I use -current sources for > tftp, because the -stable version doesn't work. > If you tftp server runs on -stable, try using one built from > -current sources. I know of this problem (I was the one who submitted the patches to support the tftp TSIZE extension ;-) and do of course use the -current version. As I said, I get the same problem if I boot the loader image from a local disk. > I always forget the failure mode, but I think a "not found" is what > I got as well... 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. eSk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15447.54977.322077.139805>