On Tue, Feb 16, 2010 at 9:43 PM, Peter Scheie <[email protected]> wrote: > I may have done something incorrectly, I added the DEBUG option to 'make > bin/gpxe.lkrn'. Booting with that, it just says 'No device found: net0' (or > was it interface?). Should it say more than that?
Yes, there should be debug output. When the UNDI EBUSY patch refuses to load multiple UNDIs the following debug message is printed: UNDI 0xXXXXXXXX cannot load multiple instances I looked at the patch again and spotted a trivial mistake: it was refusing to load the first UNDI rather than all UNDIs after that (the logic was inverted). The patch in git is updated to correct my mistake. Sorry for that hickup, this new patch should allow the first UNDI device to load. You can grab the latest change by cloning again: git clone git://git.etherboot.org/scm/people/stefanha/gpxe.git cd gpxe && git checkout origin/stefanha-50-undiebusy (The changes can be pulled into an existing repo, but the commands depend on how the repo has been set up. That's why I give these commands which are guaranteed to work but clone a new repo.) You can try enabling PCI debug messages (that includes probing devices and you should definitely get output): make DEBUG=undiload,undi,undinet,undirom,pci If you see no PCI debug messages then config options need to be checked (any customizations in config/* like CONSOLE_SERIAL?). Thanks again for testing this, Stefan _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
