"Jonathan A. Kollasch" wrote:

> #    create  instkernel/diskimage
> Calculated size of `diskimage.tmp': 3145728 bytes, 3 inodes
> Extent size set to 4096
> diskimage.tmp: 3.0MB (6144 sectors) block size 4096, fragment size 512
>         using 1 cylinder groups of 3.00MB, 768 blks, 32 inodes.
> super-block backups (for fsck -b #) at:
>  32,
> Populating `diskimage.tmp'
> nbmakefs: Writing inode 3 (work/netbsd), bytes 3104768 + 1252: No space left on device
> 
> *** Failed target:  diskimage
> *** Failed command: [ "work.built" = work.built -a -f diskimage -a ! diskimage -ot work.built ] || { echo '# ' " create " instkernel/diskimage; rm -f diskimage diskimage.tmp; /mnt/wd2e/jakllsch/sgimips-current/src/tooldir.NetBSD-2.0-i386/bin/nbmakefs -t ffs -B be -s 3m -F work.spec -N /mnt/wd2e/jakllsch/sgimips-current/src/etc -o bsize=4096,fsize=512 -o optimization=space,minfree=0 diskimage.tmp work && mv -f diskimage.tmp diskimage; }
> *** Error code 1

This looks like a ramdisk has filled up.  Can you try bumping the size
in the IMAGESIZE= line to "4m" in distrib/sgimips/instkernel/Makefile
(and you may need to in distrib/sgimips/ramdisk/Makefile as well) and
see if that works?  You'll also need to change the ramdisk size in
sys/arch/sgimips/conf/INSTALL32_IP2x to 8192 to match (that one's in
512-byte blocks so you can't use the "4m"-style shorthand).

I don't know if SGIs have constraints on the size of the kernels they
can boot, but we should at least let it build first.

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD Support and Service:         http://www.wasabisystems.com/