Date: Fri, 26 Aug 2005 08:11:09 +0200 From: Emanuel Strobl <Emanuel.strobl@gmx.net> To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: BTX failure [Was: Re: pxeboot problems with BETA2] Message-ID: <200508260811.18644@harrymail> In-Reply-To: <200508251406.57099.jhb@FreeBSD.org> References: <200508161405.18729@harrymail> <200508231534.31390@harrymail> <200508251406.57099.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2425683.G6fTkIhkur Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 25. August 2005 20:06 CEST schrieb John Baldwin: [...] > > I have no ideay why, but over night I recompiled my PXEROOT system > > (BETA3 now) and the problem vanished. I can't see any changes in the > > cvsweb, so I have absolutely no idea what the problem was. Hardware is > > exactly the same. > > What have I missed? > > Maybe you had a corrupted pxeboot binary somehow? I'm quiet sure that this can't be. I played arround with several CFLAG=20 options (-Os, -marchi486 etc.) and with several -DPXELDR_ALWAYS_SERIAL=20 etc. so I'm sure I had tested some dozends of different pxeboot binaries. And I can't imagine that corrupted source file can cause such an error,=20 remember that all these pxeboot binaries worked fine on PIII boxes, just=20 not with the Elan SC520. I'm glad that it works now, but it was really interesting what in the chain= =20 of libs/dependend boot/loader stuff was the reason... Thanks for your help, =2DHarry --nextPart2425683.G6fTkIhkur Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDDrKGBylq0S4AzzwRAum3AJ40niCE59yhiEkerq+BjiPnBqJVnACeLxyw /56Dr6c6dfEhvdBWdHNIC5Q= =RV+1 -----END PGP SIGNATURE----- --nextPart2425683.G6fTkIhkur--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508260811.18644>