Re: Which NetBSD on a VS3176?

[Holm Tiffe <holm%freibergnet.de@localhost>]

Johnny Billquist wrote:

[..]
> >>
> >>
> >>  On which disk do you want to install NetBSD?
> >>
> >>
> >>                      +-----------------------------------+
> >>                      | Available disks                   |
> >>                      |                                   |
> >>                      |uid 0, pid 6, command sysinst, on /: file system 
> >>                      full
> >>                      | b: sd1 (4.0G, IBM DCAS-34330)     |
> >>/: write failepid 6 (sysinst): user write of 16388@0x1a2000 at 93080
> >>failed: 28
> >>d, file system is full
> >>[1]   Illegal instruction     sysinst
> >>#
> >>
> >>The sd0 is a Fujitsu M2954S-512, that one with the +5V on the case (!),
> >>I'll try a smaller disk next, have n IBM0663 (?) here and a quantum, have
> >>to look if they work at all....
> >>
> >>Regards,
> >>
> >>Holm
> >>--
> >
> >Ok, I've tried to install on the IBM0663 disk (displayed as 995MB, sd0)
> >this makes no difference at all:
> 
> Did I miss something? Why did you expect any different result?
> You're getting an error about the root file system being full, and this 
> on the installation system, where the root file system is a ram disk.
> Makes no difference what harddrive you hook up.
>
>         Johnny


The Filesystem gets full since sysinst is core dumping with an illegal
instruction fault. After that I have a prompt, stty sane recovers the
terminal, I can remove the core and do commands be entering them in the
shell. Disklabel isn't really helpful then, it displays a "564" ??

I've tried the different disk size since the MV3100 M76 has a problem
with 12BIT SCSI cmds and some wrape around of sizes over 4 Gig in the
Bootroms.

I've now created the disklabel on the 0663 disk with OpenBSD and after
booting NetBSD again I could recreate the filesystems on th disk and
install the binary sets per hand on the disk. Now I'm here:

-DKA0
>> NetBSD/vax boot [1.11] <<
>> Press any key to abort autoboot 3
stray interrupt: vector 0x54, ipl 26
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
2590976+174136 [211456+201165]=0x308128
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 6.1.4 (GENERIC)
VAXstation 3100/m76
primary cache status: 0x20a<DPERR,REFRESH,ENABLE>
secondary cache status: 0xffe1<TPE,DPE,MISS,ENABLE>
total memory = 16124 KB
avail memory = 12060 KB
mainbus0 (root)
cpu0 at mainbus0: Rigel, 2KB L1 cache, 128KB L2 cache
vsbus0 at mainbus0
vsbus0: interrupt mask 8
le0 at vsbus0 csr 0x200e0000 vec 120 ipl 17 maskbit 5 buf
0x283ec000-0x283fbfff
le0: address 08:00:2b:23:c2:5a
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 304 ipl 17 maskbit 6
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 mux 1
lkms0 at dz0
wsmouse0 at lkms0 mux 0
si0 at vsbus0 csr 0x200c0080 vec 770 ipl 17 maskbit 1
si0: NCR5380, SCSI ID 6
scsibus0 at si0: 8 targets, 8 luns per target
si1 at vsbus0 csr 0x200c0180 vec 774 ipl 17 maskbit 0
si1: NCR5380, SCSI ID 6
scsibus1 at si1: 8 targets, 8 luns per target
smg0 at vsbus0 csr 0x200f0000 vec 104 ipl 17 maskbit 3
smg0: could not find 8x15 font
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <IBM OEM, 0663L12, s z> disk fixed
sd0: 958 MB, 2051 cyl, 15 head, 63 sec, 512 bytes/sect x 1962030 sectors
sd0: async, 8-bit transfers
sd1 at scsibus0 target 4 lun 0: <IBM, DCAS-34330, S65A> disk fixed
sd1: 4134 MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200 sectors
sd1: async, 8-bit transfers
cd0 at scsibus0 target 5 lun 0: <TOSHIBA, CD-ROM XM-5701TA, 0167> cdrom
removable
cd0: async, 8-bit transfers
sd1: no disk label
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs
/etc/rc.conf is not configured.  Multiuser boot aborted.
Enter pathname of shell or RETURN for /bin/sh: 
We recommend that you create a non-root account and use su(1) for root
access.
#

Again, that is NOT simh, that's on the iron and the miniroot had enough
space to work and install NetBSD to the disk. It is just sysinst that bails
out.

BTW: Miniroot is called miniroot because it should be so small to fit in
the memory of the smallest possible machine for installation purposes..,
just in Case someone doesn't know..
SCNR

So it seems to be exactly as I wrote before, You have a running System but
no one is able to install it on the VS3100 "the normal way".
Don't try to find the Bug using simh and the KA655, I've tried this, on
this "architecture" the sysinst is working flawlessly and doesn't core dump.

Last year I've tried to install over network so the network was up and
running when sysinst core dumped. Now I'm booting from CD. Lets see if I
can get up the network and copy the core dump for debugging purposes.

I tought sysinst may be compiled with the wrong CPU definition causing that
"illegal instruction" core dump, but the ka655 used in simh is also a CVAX.
It is possible that simh lets running instructions that should'nt,
emulating to much fp a CVAX? Really don't know..

Regards,

Holm

-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741