> > ...(dmsg stuff)...
> > no dev/console

Are you on a sun3x? I just tried unpacking netbsd-RAMSDISK.gz to / on my sun3
and when I boot it here's what I get:

>b netbsd-rd

EEPROM boot device...sd(0,0,0)netbsd-rd 
>> NetBSD ufsboot [$Revision: 1.7 $]
ufsboot: loading netbsd-rd
710184+293984+140296+[52584+59019]=0x132a87
Starting program at 0x4000
console is ttya
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.4P (RAMDISK) #0: Thu Jan  6 08:13:40 PST 2000
    toddpw@dagobah:/usr/src/sys/arch/sun3/compile/RAMDISK
Model: sun3 60
fpu: mc68881
total memory = 20480 KB
avail memory = 17872 KB
using 140 buffers containing 1120 KB of memory
mainbus0 (root)
obio0 at mainbus0
zsc0 at obio0 addr 0x0 ipl 6: (softpri 3)
kbd0 at zsc0 channel 0
zsc0:  channel 1 not configured
zsc1 at obio0 addr 0x20000 ipl 6: (softpri 3)
zstty0 at zsc1 channel 0 (console)
zstty1 at zsc1 channel 1
eeprom0 at obio0 addr 0x40000
clock0 at obio0 addr 0x60000 ipl 5
memerr0 at obio0 addr 0x80000 ipl 7: (Parity memory)
intreg0 at obio0 addr 0xa0000
le0 at obio0 addr 0x120000 ipl 3: address 08:00:20:00:4c:5a
le0: 8 receive buffers, 2 transmit buffers
si0 at obio0 addr 0x140000 ipl 2: options=0xf
scsibus0 at si0: 8 targets, 8 luns per target
enabling interrupts
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST41600N SUN1.3G, 0040> SCSI2 0/direct fixed
sd0: 1307 MB, 2099 cyl, 17 head, 75 sec, 512 bytes/sect x 2676846 sectors
 fixed, 512 blocksboot device: sd0a
device md0 (0xd00) not configured
root device (default md0a): 
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST41600N SUN1.3G, 0040> SCSI2 0/direct fixed
sd0: 1307 MB, 2099 cyl, 17 head, 75 sec, 512 bytes/sect x 2676846 sectors
 fixed, 512 blocksboot device: sd0a
device md0 (0xd00) not configured
root device (default md0a): md0a
dump device (default md0b): 
file system (default ffs): 
root on md0a dumps on md0b
/: bad dir ino 4 at offset 0: mangled entry
panic: bad dir
syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up


The only weirdness I see in the log for the ramdisk builds is this:

netbsd-tmp: warning: non-standard entry point: 0x0e004000
        expecting entry=0x2000

Anyone know if this is significant?

Todd Whitesel
toddpw @ best.com