[gPXE] Dell T300 w/Broadcom chip: gpxe hangs during dhcp
Peter Scheie
peter at scheie.homedns.org
Tue Feb 23 16:14:02 EST 2010
Stefan Hajnoczi wrote:
> On Tue, Feb 16, 2010 at 9:43 PM, Peter Scheie <peter at scheie.homedns.org> 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
>
Grrr. It was working: I booted the Dell multiple times with it, loading from a
flash drive. Today, the day before I give a presentation on gpxe to all the
tech managers, I tried it again, and now it's failing with this output:
...using driver undipci
UNDIROM 0x858c4 matched PCI 14e4:165a (00000000)
UNDI 0x589d4 loading UNDI ROM 0x858c4 to CS 93d4 DS 9007 for PCI 02:00.0
UNDI 0x859d4 loader failed: Error 0x000000c8
...probe failed
Why would it work one day and then stop the next day (aside from the obvious
Murphyesque "Because you were going to demo it tomorrow.")?
Peter
Loading undi
More information about the gPXE
mailing list