Hi David,

I set DEBUG_MEMSIZE in getextmemx.c and copied the new /usr/mdec/boot to 
/boot.  Since it's the only part that changed I didn't re-installboot the 
/usr/mdec/boot_xxffsv1 to /dev/rwd0a.  Correct me if I'm wrong here...

Now what I see is this:

*******************
NetBSD/i386 ffsv1 Primary Bootstrap

 >> NetBSD/i386 BIOS, Revision 3.1
 >> (sanch@bovine, Thu Nov  6 12:16:08 UTC 2003)
extmem1: ffc0
 >> Memory: 639/65472 k
*******************

As you can see I don't get the "extmem2:" nor the "mementry:" lines...

thanks again,

Rob


David Laight wrote:

>>the bootstrap behaves the same way...
>>
>> >> NetBSD/i386 BIOS, Revision 3.1
>> >> (autobuild@tgm.netbsd.org, Mon Nov  3 07:44:09 UTC 2003)
>> >> Memory: 639/65472 k
>>
>>on the same machine, the 1.6.1 branch install boot disk does recognize all 
>>of the memory and looks like this:
>>
>> >> NetBSD/i386 BIOS, Revision 2.13
>> >> (autobuild@tgm.daemon.org, Tue Apr  8 11:27:33 UTC 2003)
>> >> Memory: 639/326592 k
>>
>>i noticed PR 21037 from back in April, but I was surprised that no one else 
>>saw this behavior.  anyone else see this since then?  what source files 
>>differentiate the bootstrap rev 3.1 from 2.13?
> 
> 
> The number generated by the bootstrap (and passed to the kernel) is
> generated by the code in src/sys/arch/i386/stand/lib/getextmemx.c
> 
> Setting DEBUG_MEMSIZE and rebuilding src/sys/arch/i386/stand/boot/biosboot
> wll give some diagnostic output (twice) that might be informative.
> 
> 	David
>