Re: [Etherboot-developers] UNDI driver

[Georg B. <gb...@us...>]

Am Samstag, 31. Mai 2003 16:22 schrieb Michael Brown:
> This 52kB is at the top of base memory and so occupies the addresses
> [00093000, 000A0000).  The image you are trying to load wants to be
> loaded into this area, but this is not possible.
>
> The only solution is to create an image that doesn't want to be loaded
> into this area.  I believe it's possible for mknbi to create images that
> load elsewhere - Ken?

I tried mknbi with --relocseg 0x8000, and it works! Really nice work, and 
thanks very much for the nice explanations Michael!

> > > It's not seeing the PXE ROM.  Do you have LAN enabled as part of the
> > > BIOS boot sequence?  I have found that some BIOSes (or possibly some
> > > PXE ROMs) will hide the PXE ROM if LAN is not listed as a BIOS boot
> > > device.
> >
> > It was enabled, but not the first option. If I do PXE ->
> > Etherboot(eepro100) -> Etherboot(undi) the undi driver behaves exactly
> > as it does when loading directly from PXE.
> > The BIOS of this machine is even worse: It seems that the PXE ROM is
> > not shown unless it was successfully executed.
>
> I don't know what we can do about that; I'm not sure how Option ROMs can
> hide themselves.  Any ideas?

I don't know. Since the UNDI driver found the ROM when PXE was executed 
before and did not find it when it was enabled but not executed, I thought 
that in this case the BIOS did not show the PXE ROM, but this may be wrong.
But never mind, this BIOS is broken anyway (I have two menus where I can 
alter the boot sequence, one called something with "Network" and the other 
"Boot". It seems that the selected options in both must be identical).


Georg