Re: [Etherboot-developers] Problems Booting 5.1 cvs

[<ebi...@ln...>]

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

> > >There are some versions of binutils noticeably common in Redhat 7
> > >in which as puts junk at the end of assembly files.  In start16.S
> > >And possibly some of the others I count on being able to drop off
> > >the end of an assembly file and have it work correctly.  With
> > >a broken version of binutils/as this code may not work correctly.
> 
> Ok, I have a workaround/fix for the issue.  I am not sure what it is
> because I don't know what it does. :-)
> 
> I patched arch/i386/prefix/boot1a.s as follows:
> 
> Index: arch/i386/prefix/boot1a.s
> ===================================================================
> RCS file:
> /cvsroot/etherboot/etherboot/etherboot-5.1/src/arch/i386/prefix/boot1a.s
> ,v
> retrieving revision 1.2
> diff -r1.2 boot1a.s
> 72c72
> < blockcount:	.word	36			# if unmodified loads
> 18kB
> ---
> > blockcount:	.word 64				# if unmodified
> loads 18kB
> 
> I assume that 64 means something over 18kB, but as I said I don't know
> what it means.  I think the value can go lower, but more importantly
> does this mean any thing to you?
> 
> In my spare time I am reading up on assembly, one day I may even know
> what some of this means.

Ok how are you building the floppy image?
make ????.fd0

or cat boot1a.bin blah ?

Ken perl script should be setting that value so either:
- boot1a.s is being compiled so blockcount is showing up at a different
  address
- The perl script builddsk.pl is not setting that value properly.
  (Could this be a rounding issue?)


Eric