Actually, the infinite chainloading is expected, the problem is when I first load the remote iPXE from the BIOS PXE build 83. The iPXE driver doesn't detect the network card unless it was loaded by the CD iPXE.
On Tue, Feb 8, 2011 at 4:13 PM, Andrew Bobulsky <[email protected]> wrote: > Hello Thiago, > > You're actually getting expected behavior in the last case there. The CD > or USB versions work via a native iPXE driver, which in turn should be > providing a proper PXE stack and UNDI driver, hence the infinite > chainloading :) > > -Andrew Bobulsky > > On Feb 8, 2011, at 12:53 PM, Thiago Arruda Padilha < > [email protected]> wrote: > > Now I tried something different: > > I configured the the TFTP server to always serve the undionly.kpxe image > and booted the computer using the iPXE cd, and somehow it entered on an > infinite loop. It appears that if I chainload iPXE from iPXE everything > works normaly, but not if I load the legacy PXE first. Probably the build 83 > of PXE leaves the network card in a state that makes it undetectable by > iPXE. > > > On Tue, Feb 8, 2011 at 2:23 PM, Thiago Arruda Padilha > <<[email protected]> > [email protected]> wrote: > >> It still doenst work, I did 'make bin/undionly.kkpxe' and replaced by the >> old, along with the configurations, but the result is the same. >> Something I did notice, is that PXE 2.1 build 83 is present in the >> computers where undionly.kpxe doesn't work, but when I try to chainload in >> a network card that has PXE 2.1 build 82 , no problems occur. >> This problem only happens when I try via chainloading iPXE, with the cdrom >> or usb stick everything works; >> >> >> On Tue, Feb 8, 2011 at 1:32 PM, Michael Brown < <[email protected]> >> [email protected]> wrote: >> >>> On Tuesday 08 Feb 2011 16:30:01 Thiago Arruda Padilha wrote: >>> > I'm trying to chainload iPXE from a network card that has a legacy >>> intel >>> > PXE, however when iPXE is loaded( undionly.kpxe ), it prints a few >>> messages >>> > about !PXE and then stops printing : "No more network devices" and I >>> have >>> > to reboot. Strangely, if I "burn" ipxe.usb to a flash drive, the boot >>> > succeeds normaly. What could be happening to cause this error? >>> >>> Does undionly.kkpxe (note the extra "k") work for you? >>> >>> Michael >>> >> >> > _______________________________________________ > ipxe-devel mailing list > [email protected] > https://lists.ipxe.org/mailman/listinfo/ipxe-devel > >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo/ipxe-devel
