Re: AW: [Etherboot-developers] etherboot Ver. 4.7.23

[Ken Y. <ke...@nl...>]

>>In other words, please fill in this table:
>
>		<4.7.23		4.7.23		4.7.24
>eepro100	no, no prompt	yes,valid prompt	no, no prompt
>82559er	no, no prompt	no, valid prompt	no, no prompt
>
>the eepro100 works with both drivers fine.
>the 82559er print a valid prompt and wait for DHCPServer but the 82559er
>makes no request and wait for ever.

I think for the eepro100, it's one of the following reasons:

1. You have a PnP conformant BIOS but you did not select the network
device as a bootable device. The bug in 4.7.23 bypasses the BIOS
mechanism. When the BIOS is conformant, it will, in the first
enumeration pass, detect the net device as a bootable device. In the
second pass, it will attempt to boot from the detected devices in the
order specified in the BIOS configuration, e.g. NET, A, C. If the net
device is not specified in the configuration, then it will not be tried.

2. You do not have a PnP conformant BIOS.

It seems that, from a couple of reports, some people have non-conformant
BIOSes. I will edit loader.S in the next version so that by defining
NON_PNP_BIOS, they can use the INT19H mechanism to hook the boot entry
point, i.e. the mechanism used by "legacy ROMs".

>I think i need this bug on my hardware and one more for the 82559er :-)

The 82559er bug is a different issue not yet understood. My guess is a
media selection issue.