Re: [Etherboot-developers] [COMMIT] 5.1.2+ boot from disk.

[Eric W B. <ebi...@ln...>]

"Timothy Legge" <tl...@ro...> writes:

> > Just to tripple check you are not loading a compressed image?
> 
> Just to clarify, do you mean is the file listed in /etc/dhcpd.conf
> compressed? 

No.  I mean the etherboot image that locks up.

> Since the 486 never gets to the point of recognizing the nic,
> it hardly matters.  The rom was created via make bin32/3c509.fd0 

O.k. not make bin32/3c509.lzfd0.  So it is not compressed.

> and file
> being grabbed from the dhcp server is either a ltsp kernel or a boot rom
> that was created via mknbi-linux bin32/3c509.rom > /tftproot/lts/bootrom.  I
> could not tell you whether either of those files are compressed if my life
> depended upon it.  However, etherboot was compiled with the default options.
> 
> > Other than that I would guess I accidentally introduced an instruction
> > that doesn't exist on your 486.
> 
> Any idea how to track it down?

What I normally would do is write a little assmebly routine that outputs
to the screen, or even better the serial port (if you have a null modem cable
setup).  And sprinkle it through the assembly.

The steps through:
loader.S start16.S and start32.S are not too difficult to trace.

Another option is include a ``.arch i386'' instruction in the assmebly files,
but I just tried that and I didn't get any warnings ;(

A second possibility is that the stack pointer is at an unfortunate location.
But in this case we use the stack from boot1a.s so that should be constant
across machines.

I don't have any good ideas but if you have a null modem cable I have a set
of easy to use serial port debug print statements.

Eric