Re: [Etherboot-developers] Tagged Test Image

[<ke...@us...>]

Ok, bad news. I've confirmed the results below with an eepro100, so the
problem is not the 3c509 driver. In both last night's test and today's a
Pentium was used.

>			Linux (tomsrtbt)	FreeDOS image	ROM image
>5.1.7 no RELOCATE	ok			ok		ok
>5.1.7 RELOCATE		fail(1)			fail(3)		fail(3)
>
>(1) Printed out first32 banner and location of ramdisk, then froze.
>(2) Rebooted.

(3) Froze.

(1) could be an error in the trampoline that mknbi uses, but with
FreeDOS and the ROM image it should be just straight jumps into 16-bit
code; Etherboot is supposed to just call xstart16. Which makes me
suspect that the 16-bit registers are messed up in RELOCATE mode. Or
maybe it's something to do with A20 routines? Any theories, Eric?

I should test this later with older 5.1 releases to try to see if this
ever worked with RELOCATE or it was my imagination.