Subject: Progress With 1.4 But Still Boot Problem
To: None <port-vax@netbsd.org>
From: Kevin McQuiggin <mcquiggi@sfu.ca>
List: port-vax
Date: 07/10/1999 12:45:23
Hi port-vax Folks:
I am installing 1.4 on a MicroVAX II. I have the distribution sets
installed on my drive (ra1), and have written a bootblock using
disklabel -B ra1 from the miniroot.
I halted and rebooted the machine, said B DUA1 at the chevron prompt,
and NetBSD 1.4 starts to come up:
>>> b dua1
2..1..0..
>> NetBSD/vax boot [Apr 18 1999 06:50:17] <<
>> Press any key to abort autoboot 3
> boot netbsd
834728+43864+161316+[64440+72735] total=0x11f603
Copyright (c) 1996, 1997, 1998, 1999
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 1.4_BETA (GENERIC) #2: Thu Apr 29 03:21:07 CEST 1999
ragge@vs4000:/usr/src/sys/arch/vax/compile/GENERIC
MicroVAX II
realmem = 13619200
avail mem = 10403840
Using 166 buffers containing 679936 bytes of memory.
mainbus0 (root)
cpu0 at mainbus0: KA630
uba0 at mainbus0: Q22
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 5 model 3
mscpbus0: DMA burst size set to 4
mt0 at mscpbus0 drive 0: TK50
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 5 model 13
mscpbus1: DMA burst size set to 4
ra0 at mscpbus1 drive 0: RA81
ra1 at mscpbus1 drive 1: RA81
uda1 at uba0 csr 160334 vec 764 ipl 17
mscpbus2 at uda1: version 5 model 13
mscpbus2: DMA burst size set to 4
ra2 at mscpbus2 drive 0: RA81
qe0 at uba0 csr 174440 vec 760 ipl 17
qe0: deqna, hardware address 08:00:2b:07:b6:1e
dhu0 at uba0 csr 160440 vec 300 ipl 17
dhu0: rom(1) version 2 rom(0) version 2
boot device: ra1
root on ra1a dumps on ra1b
ra1: size 633672 sectors
root file system type: ffs
warning: no /dev/console
Note how the system (or at least the console) hangs on the "warning: no
/dev/console" message.
The file /dev/console does in fact exist, but perhaps it has to be
configured somehow.
Any suggestions? I'm almost there.
TIA,
Kevin
PS If I get a chance I will reboot using the miniroot tape, mount the ra1
partitions, get the network setup stuff into rc, and then reboot off of DUA1,
wait for the message, and then after a suitable period try getting into the
box via telnet. I think that the machine is simply hanging after the warning
message, though - can't hear the hard drives/system activity as there are too
many machines running in my machine room right now...