Re: HD size & NWS-3710

[Mauricio <raub%kudria.com@localhost>]

At 02:19 +0900 1/6/04, Izumi Tsutsui wrote:
> In article <a06002003bc1f479260b0@[10.0.0.10]>
> raub%kudria.com@localhost wrote:
>
> >         It's ID is zero (I just checked it again =).  During the boot
> >  process fromt he floppy (and the installation) the drive ID and type
> >  is correctly recognized:
>  :
> >  sd0 at scsibus0 target 6 lun 0: <SEAGATE, ST31230N, 0290> disk fixed
> >  sd0: 1010 MB, 3992 cyl, 5 head, 103 sec, 512 bytes/sect x 2069860 sectors
>
> "sd0" doesn't mean SCSI ID zero, but means just the first scsi disk.
> dmesg says "sd0 at scsibus0 target 6" so your disk ID is six, isn't it?
> ---

	You are absolutely correct!  For some reason I was 
confused... something that embarasses me specially since dmesg's 
output is almost in perfect solaris lingo.  Shame on me!  Anyway, I 
then tried the SCSI ID = 6 and all seems to be well:

Testing memories: done.
12288K bytes available, 32K bytes reserved.

SONY NET WORK STATION R3000 Monitor Release 2.0A
Model NWS-3710, Machine ID #30145, Ethernet address 08:00:46:00:79:e7

NEWS> bo sd(6)
NetBSD/newsmips Primary Boot
NetBSD/newsmips Secondary Boot, Revision 1.7
(autobuild%tgm.netbsd.org@localhost, Fri Nov 28 21:51:43 UTC 2003)
Booting sd(6,0,0)
2187392+206184 [87920+75310]=0x27059c

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
    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.6.2_RC3 (GENERIC) #0: Fri Nov 28 22:07:45 UTC 2003

autobuild%tgm.netbsd.org@localhost:/autobuild/netbsd-1-6-PATCH002-RC3/newsmips/OBJ/aut
obuild/netbsd-1-6-PATCH002-RC3/src/sys/arch/newsmips/compile/GENERIC
total memory = 12256 KB
avail memory = 8560 KB
using 178 buffers containing 712 KB of memory
SONY NET WORK STATION, Model NWS-3710, Machine ID #30145
mainbus0 (root)
cpu0 at mainbus0: MIPS R3000 CPU (0x220) Rev. 2.0 with MIPS R3010 FPC Rev. 2.0
cpu0: 64KB/4B direct-mapped Instruction cache, 64 TLB entries
cpu0: 64KB/4B direct-mapped write-through Data cache
hb0 at mainbus0
le0 at hb0 addr 0xbff80000 level 1: address 08:00:46:00:79:e7
le0: 8 receive buffers, 2 transmit buffers
mkclock0 at hb0 addr 0xbff407f8
zsc0 at hb0 addr 0xbfec0000 level 1
zstty0 at zsc0 channel 0 (console i/o)
zstty1 at zsc0 channel 1
kb0 at hb0 addr 0xbfd00000 level 2
wskbd0 at kb0 (mux ignored)
ms0 at hb0 addr 0xbfd00004 level 2
wsmouse0 at ms0 (mux ignored)
sc0 at hb0 addr 0xbfe00100 level 0
scsibus0 at sc0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
SC(t): [istatus=0x80, tstatus=0x2]
sd0 at scsibus0 target 6 lun 0: <SEAGATE, ST31230N, 0290> SCSI2 0/direct fixed
sd0: 1010 MB, 3992 cyl, 5 head, 103 sec, 512 bytes/sect x 2069860 sectors
SC(t): [istatus=0x80, tstatus=0x2]
boot device: sd0
root on sd0a dumps on sd0b
WARNING: preposterous clock chip time
root file system type: ffs
Sat Apr 19 19:11:02 GMT 2003
swapctl: adding /dev/sd0b as swap device at priority 0
Starting file system checks:
/dev/rsd0a: file system is clean; not checking
/dev/rsd0g: file system is clean; not checking
Setting tty flags.
Setting sysctl variables:
Starting network.
Hostname: karas
IPv6 mode: host
Configuring network interfaces: le0le0: lost carrier
.
add net default: gateway 10.0.0.1
Adding interface aliases:
le0: lost carrier
le0: lost carrier   <-- I forgot to connect the transceiver to the machine =)
Building databases...
kvm_mkdb: machdep.booted_kernel: the value is not available: No such 
file or dir
ectory
Starting syslogd.
Checking for core dump...
savecore: no core dump
Mounting all filesystems...
Clearing /tmp.
Checking quotas: done.
Setting securelevel: kern.securelevel: 0 -> 1
Starting virecover.
starting local daemons:.
Updating motd.
Starting inetd.
Starting cron.
Sat Apr 19 15:12:10 EDT 2003

NetBSD/newsmips (karas) (console)

login:

Ok, almost as I think the password I gave it is not what I thought. 
Not that it really matters as the HD in the machine (a 3 1/2" HH 1GB 
one) will be replaced with the 3GB 5 1/4" FH one I mentioned in the 
beginning of this thread.  Will it be smarter to have its ID = 0? 
Also, if I set the jumper 5 to autoboot (on), would I see that 
happening in console or I will just have to have faith *or* I need to 
boot as above (manually)?

        I am pretty excited now =)