NWS 3410 install : still trying

[Emmanuel Chaput]

Hi !

I am still trying to install NetBSD-1.6.1 on a 3410 ; I am using
snapshot 20030419. Here are some notes about the process :

I think I have finally installed NetBSD/NewsMIPS on my 3410 box !
Well ... It looks like ! As a matter of fact, I can not boot
the installed system :

NEWS> bo sd

Reserved instruction exception
cause=30000028, sr=40c404, badvaddr=80ffe50e, epc=a0000000
NEWS>

But if I "bo fh" with the install boot floppy, I can mount
the hard drive, and it looks good :

# mount /dev/sd0a /mnt
# mount /dev/sd0g /mnt/usr
# mount /dev/cd0a /mnt/mnt
cd0: no disk label
# mount
/dev/md0a on / type ffs (local)
mfs:13 on /tmp type mfs (synchronous, local)
/dev/sd0a on /mnt type ffs (local)
/dev/sd0g on /mnt/usr type ffs (local)
/dev/cd0a on /mnt/mnt type cd9660 (read-only, local)
# df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/md0a 2.4M 2.3M 125K 95% /
mfs:13 7.6M 1.0K 7.3M 0% /tmp
/dev/sd0a 62M 16M 43M 27% /mnt
/dev/sd0g 273M 167M 92M 64% /mnt/usr
/dev/cd0a 75M 75M 0.0B 100% /mnt/mnt
# ls /mnt/mnt
CHANGES CHANGES.prev README.files shared
CHANGES-1.6.1 LAST_MINUTE newsmips
# ls /mnt
.cshrc bin dev kern libexec netbsd root stand usr
altroot boot etc lib mnt rescue sbin tmp var
# ls /mnt/usr
bin games include lib libdata libexec lkm mdec sbin
share
#

So I wonder if there is a problem with the installed kernel or
with the bootloader, and if I could boot the system from the floppy
with an option like the "root=/dev/sda0" of linux. I've tried to
use installboot to re-install the bootloader :

# chroot /mnt
# installboot -v -m newsmips /dev/rsd0a /usr/mdec/bootxx /boot
File system: /dev/rsd0a
File system type: ffs (blocksize 8192, needswap 0)
Primary bootstrap: /usr/mdec/bootxx
Secondary bootstrap: /boot
Bootstrap start sector: 0
Bootstrap byte count: 4684
Bootstrap block table: 118 entries of 8192 bytes available, 7 used:
1136 1152 1168 1184 1200 1216 1106
Writing bootstrap
# halt

NEWS> bo sd

Reserved instruction exception
cause=30000028, sr=40c404, badvaddr=80ffe50e, epc=a0000000
NEWS>

No change !

By the way, the frame buffer seems to work fine ! I used it to
install NetBSD ... On the other hand I had problems with serial port
during install (something like the problems described by Mauricio a
few weeks ago ...).

Any hint ?

Thanks a lot !

[Izumi Tsutsui]

Post by Emmanuel Chaput
NEWS> bo sd
Reserved instruction exception
cause=30000028, sr=40c404, badvaddr=80ffe50e, epc=a0000000
NEWS>

Hmm, it seems bootloader is not loaded (or not installed) properly.

Post by Emmanuel Chaput
# chroot /mnt

BTW, you don't have to chroot before installboot.
The third arg of installboot(8) is the path in the
partition specified as the first arg.

Post by Emmanuel Chaput
# installboot -v -m newsmips /dev/rsd0a /usr/mdec/bootxx /boot
File system: /dev/rsd0a
File system type: ffs (blocksize 8192, needswap 0)
Primary bootstrap: /usr/mdec/bootxx
Secondary bootstrap: /boot
Bootstrap start sector: 0
Bootstrap byte count: 4684
1136 1152 1168 1184 1200 1216 1106
Writing bootstrap
# halt
NEWS> bo sd
Reserved instruction exception
cause=30000028, sr=40c404, badvaddr=80ffe50e, epc=a0000000
NEWS>
No change !

How did you create partitions on sd0?
At least, sd0a (root partition) must start at sector zero
to install bootblock which can be loaded by PROM.

You can see if boot loader is written properly by commands
like "dd if=/dev/rsd0c | hexdump -Cv" and the first 16 bytes
should be like this:
00000000 10 00 00 7f 00 00 00 00 19 90 01 06 00 00 00 00 |................|

Post by Emmanuel Chaput
By the way, the frame buffer seems to work fine ! I used it to
install NetBSD ...

Sounds good. What does dmesg say about frame buffer at boot?

Post by Emmanuel Chaput
On the other hand I had problems with serial port
during install (something like the problems described by Mauricio a
few weeks ago ...).

I've committed a workaround fix for this problem,
but when I tried to build a new snapshot,
makefs(1) had some strange problem and it failed.

I'll try it again with newer sources in this weekend.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Emmanuel Chaput]

[well, if you don't mind, please Cc: the list to share info..]

Ho yes ! Sorry, I thought I was replying to the list ...

Hmm, if you chose default parition, it should be Ok.

Post by Izumi Tsutsui
At least, sd0a (root partition) must start at sector zero
to install bootblock which can be loaded by PROM.

Here is the disklabel output. Looks good, no ? It says 8 partitions
while there are only 4 of them, is it OK ?

# disklabel sd0
# /dev/rsd0c:
type: unknown
disk: mipsbsd
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 9
sectors/cylinder: 567
cylinders: 1476
total sectors: 843284
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 131544 0 4.2BSD 1024 8192 16448 # (Cyl. 0 - 31)
b: 132678 131544 swap # (Cyl. 232 - 465)
c: 843284 0 unused 0 0 # (Cyl. 0 -
1487*)
g: 579062 264222 4.2BSD 1024 8192 46344 # (Cyl. 466 -
1487*)
#

You can see if boot loader is written properly by commands
like "dd if=/dev/rsd0c | hexdump -Cv" and the first 16 bytes
00000000 10 00 00 7f 00 00 00 00 19 90 01 06 00 00 00 00

|................|

It does ! The 16 first bytes look correct ! Maybe a wrong
bootloader ?

Hmm, then NWS-3410 should have the same frame buffer with NWS-3470.
I'll add the info into docs. BTW, what display do you use for your 3410?

An old B&w display Sony "gave" us with the 3410, it's written
"moniterm vcx1000" on its back ...

[Izumi Tsutsui]

Post by Emmanuel Chaput

Post by Izumi Tsutsui

Post by Izumi Tsutsui
At least, sd0a (root partition) must start at sector zero
to install bootblock which can be loaded by PROM.

Here is the disklabel output. Looks good, no ? It says 8 partitions
while there are only 4 of them, is it OK ?
# size offset fstype [fsize bsize cpg/sgs]
a: 131544 0 4.2BSD 1024 8192 16448 # (Cyl. 0 - 31)
b: 132678 131544 swap # (Cyl. 232 - 465)

Hmm, spg/sgs seems a bit strange, but it should be OK
if you can mount the partition.
"8 partitions" is no problem.

Post by Emmanuel Chaput

Post by Izumi Tsutsui
You can see if boot loader is written properly by commands
like "dd if=/dev/rsd0c | hexdump -Cv" and the first 16 bytes
00000000 10 00 00 7f 00 00 00 00 19 90 01 06 00 00 00 00

|................|
It does ! The 16 first bytes look correct ! Maybe a wrong
bootloader ?

Then we should check if these data are loaded into memory properly
by PROM. You can dump memory by "md" command:

---
NEWS> help
bf [.{b|w|l}] <bgn> {<end>|:<cnt>} <data> : Fill mem
bm <bgn> {<end>|:<cnt>} <dest> : Move mem
bo [/<bootsw>] [<devspec>[<file>]] : Boot
cls : Clear screen
cp <srcdev> <bgn> {<end>|:<cnt>} <dstdev> <dest> : Copy dev
di [<devspec>] : Disk info
eject : Eject floppy
format {fh|fd} : Format floppy
help : Display this
ld <devspec> <bgn> {<end>|:<cnt>} <addr> : Load from dev
md [.{b|w|l}] [<bgn> [{<end>|:<cnt>}]] : Display mem
ms [.{b|w|l}] [<addr> [<data>]] : Substitute mem
off : Turn power off
revarp : Get IP addr
set [<var>[=<val>]] : Set / unset var
sv <bgn> {<end>|:<cnt>} <devspec> <dest> : Save to dev
vers : Version number
NEWS> bo sd(2) <== no valid bootloader on ID 2 disk here

Reserved instruction exception
cause=30000028, sr=40c404, badvaddr=c0006438, epc=a0000000
NEWS> md .b a0000000 a00000ff
a0000000: 7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00 |.ELF............|
a0000010: 00 02 00 08 00 00 00 01 00 40 4a 00 00 00 00 34 |***@J....4|
a0000020: 00 03 df ec 00 00 00 05 00 34 00 20 00 07 00 28 |.........4. ...(|
a0000030: 00 19 00 18 00 00 00 06 00 00 00 34 00 40 00 34 |***@.4|
a0000040: 00 40 00 34 00 00 00 e0 00 00 00 e0 00 00 00 05 |***@.4............|
a0000050: 00 00 00 04 00 00 00 03 00 00 01 14 00 40 01 14 |***@..|
a0000060: 00 40 01 14 00 00 00 13 00 00 00 13 00 00 00 04 |***@..............|
a0000070: 00 00 00 01 70 00 00 00 00 00 01 60 00 40 01 60 |....p......`***@.`|
a0000080: 00 40 01 60 00 00 00 18 00 00 00 18 00 00 00 04 |***@.`............|
a0000090: 00 00 00 10 00 00 00 01 00 00 00 00 00 40 00 00 |***@..|
a00000a0: 00 40 00 00 00 03 49 38 00 03 49 38 00 00 00 05 |***@....I8..I8....|
a00000b0: 00 00 10 00 00 00 00 01 00 03 50 00 10 00 00 00 |..........P.....|
a00000c0: 10 00 00 00 00 00 17 98 00 00 64 30 00 00 00 06 |..........d0....|
a00000d0: 00 00 10 00 00 00 00 02 00 00 01 80 00 40 01 80 |***@..|
a00000e0: 00 40 01 80 00 00 47 e8 00 00 47 e8 00 00 00 04 |***@....G...G.....|
a00000f0: 00 00 00 10 00 00 00 04 00 00 01 28 00 40 01 28 |...........(***@.(|
NEWS>
---

BTW, what SCSI ID is your sd0 disk? If your disk is not ID 0,
you have to specify SCSI ID of the disk on boot command like
"bo sd(2)" etc.

NWS-3410 was designed for diskless use, so it might have
some other quirks. At least the default bootdevice on 3410
is rd (remote disk) and "set bootdev=scsi" command is needed
to change default bootdev. "set" command will print current settings.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Emmanuel Chaput]

Post by Izumi Tsutsui
BTW, what SCSI ID is your sd0 disk? If your disk is not ID 0,
you have to specify SCSI ID of the disk on boot command like
"bo sd(2)" etc.

Shame on me ! I knew my disk has SCSI ID 5, but I think I have
be confused by the sd(x,y,z) notation and by the fact that I had
different results ("device not ready" and "Reserved instruction
exception").

I think I must apologize ....

So now it works fine !

I'll have to find out why my le0 does not work now !

[Izumi Tsutsui]

Post by Emmanuel Chaput
So now it works fine !

Yeah, good news.

Post by Emmanuel Chaput
I'll have to find out why my le0 does not work now !

Maybe you should check Ethernet fuse, but I don't know
3410 has such fuse on its board.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Emmanuel Chaput]

Post by Izumi Tsutsui
Maybe you should check Ethernet fuse, but I don't know
3410 has such fuse on its board.

Well, it seems that you are right (once again !). I finally
found out a small fuse hardwired on the main board, near the
AUI connector. I have replaced it, and everything works fine !

Intall ... OK
Network ... OK

Next step seems to be X Window System ;-)

Thanks again for your help !

[NAKAJI Hiroyuki]

Post by Emmanuel Chaput
Next step seems to be X Window System ;-)

I'm afraid that no X server is available for news{mips,68k}.

Of cource, libraries and clients can be built and can work on another
host's X server.

[Emmanuel Chaput]

Post by NAKAJI Hiroyuki
I'm afraid that no X server is available for news{mips,68k}.

It was a joke, sorry ...

[Mauricio]

Hmmm, it seems there has not been any activity in this list.
So, let me stir things up a bit:

Stupid question: I have a FH 3GB HD here doing nothing. Can
I use it in my 3710 or it has one of those 2GB limit issues?

[Mauricio]

Which bootdisk to use nowadays? Can I use
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.1/newsmips/installation/floppy/boot.fs
or there is a bootdisk that would work happier in my 3710? I am
wondering because right now I am using an old boot image that has
worked before but seems to be giving now interesting error messages
regarding gzip:

Status: Running
Command: progress -zf /mnt/usr/INSTALL/misc.tgz tar -xepf -

--------------------------------------------------------------------------------
gzip: unknown option -- l
6599 KB 194.03 KB/s

[Izumi Tsutsui]

Post by Mauricio
Which bootdisk to use nowadays? Can I use
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.1/newsmips/installation/floppy/boot.fs
or there is a bootdisk that would work happier in my 3710?

NetBSD/newsmips 1.6.1 still has a bug which prevents booting
on serial console. This bug has been fixed on -current
and netbsd-1-6 branch, so boot.fs of fothcomming 1.6.2
should work. You could try 1.6.2_RC3 binaries on releng server:
ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-1-6-PATCH002-RC3/

Post by Mauricio
gzip: unknown option -- l

-current sysinst has been quite improved and now it uses
gzip -l option, but bootdisk for newsmips uses
src/distrib/utils/x_gzip and it doesn't have -l support
though now non-GPLed src/usr.bin/gzip does.
I'll commit the fix the bootdisk to use it later.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio
Which bootdisk to use nowadays? Can I use
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.1/newsmips/installation/floppy/boot.fs
or there is a bootdisk that would work happier in my 3710?

NetBSD/newsmips 1.6.1 still has a bug which prevents booting
on serial console. This bug has been fixed on -current
and netbsd-1-6 branch, so boot.fs of fothcomming 1.6.2
ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-1-6-PATCH002-RC3/

So, you mean to install using releng as the ftp site?

Post by Izumi Tsutsui

Post by Mauricio
gzip: unknown option -- l

-current sysinst has been quite improved and now it uses
gzip -l option, but bootdisk for newsmips uses
src/distrib/utils/x_gzip and it doesn't have -l support
though now non-GPLed src/usr.bin/gzip does.
I'll commit the fix the bootdisk to use it later.

Do let me know when that happens! =)

[Izumi Tsutsui]

Post by Mauricio

Post by Izumi Tsutsui
ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-1-6-PATCH002-RC3/

So, you mean to install using releng as the ftp site?

Yes.

Post by Mauricio
Do let me know when that happens! =)

If you can build binaries from sources, please try this patch:

Index: distrib/newsmips/floppies/ramdisk/list
===================================================================
RCS file: /cvsroot/src/distrib/newsmips/floppies/ramdisk/list,v
retrieving revision 1.14
diff -u -r1.14 list
--- distrib/newsmips/floppies/ramdisk/list 19 Jan 2003 12:26:56 -0000 1.14
+++ distrib/newsmips/floppies/ramdisk/list 5 Jan 2004 05:51:55 -0000
@@ -59,7 +59,7 @@

SPECIAL dmesg srcdir distrib/utils/x_dmesg
SPECIAL ed srcdir distrib/utils/x_ed
-SPECIAL gzip srcdir distrib/utils/x_gzip
+#SPECIAL gzip srcdir distrib/utils/x_gzip
SPECIAL ifconfig srcdir distrib/utils/x_ifconfig
SPECIAL more srcdir distrib/utils/more
SPECIAL ping srcdir distrib/utils/x_ping

---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio

Post by Izumi Tsutsui
ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-1-6-PATCH002-RC3/

So, you mean to install using releng as the ftp site?

Yes.

Ok, I did so and it did not complain during the installation.
Now, how do I tell it to reboot from the HD?

NEWS> eject
NEWS> bo sd0
Bad device specification.
NEWS>

does not seem to do the trick.

Post by Izumi Tsutsui

Post by Mauricio
Do let me know when that happens! =)

Index: distrib/newsmips/floppies/ramdisk/list
===================================================================
RCS file: /cvsroot/src/distrib/newsmips/floppies/ramdisk/list,v
retrieving revision 1.14
diff -u -r1.14 list
--- distrib/newsmips/floppies/ramdisk/list 19 Jan 2003 12:26:56
-0000 1.14
+++ distrib/newsmips/floppies/ramdisk/list 5 Jan 2004 05:51:55 -0000
@@ -59,7 +59,7 @@
SPECIAL dmesg srcdir distrib/utils/x_dmesg
SPECIAL ed srcdir distrib/utils/x_ed
-SPECIAL gzip srcdir distrib/utils/x_gzip
+#SPECIAL gzip srcdir distrib/utils/x_gzip
SPECIAL ifconfig srcdir distrib/utils/x_ifconfig
SPECIAL more srcdir distrib/utils/more
SPECIAL ping srcdir distrib/utils/x_ping

What do I need to build binaries from source? Until I get
this 3710 to work with netbsd, what I have is:

o Sparc 20 running Solaris 9
o Sparc IPX running Debian 3
o DEC 5000/25 running netbsd 1.6.1

[Izumi Tsutsui]

Post by Mauricio
NEWS> bo sd0
Bad device specification.

Maybe "bo sd(0)" (or just "bo sd") works on news3xx0 machines.

Post by Mauricio
What do I need to build binaries from source?

All sources under pub/NetBSD/NetBSD-current/ dir.
Please see FAQs and src/BUILDING doc for details:
http://www.netbsd.org/Documentation/current/
http://www.netbsd.org/Documentation/
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/BUILDING

In short, "sh build.sh -m newsmips -R [somewhere] -D [somewhere] release"
on srcdir should work. The fastest machine would be better.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio
NEWS> bo sd0
Bad device specification.

Maybe "bo sd(0)" (or just "bo sd") works on news3xx0 machines.

Let me try that. Incidentally, I usually have all dip
switches in the off position. Just now, I had switch 5 in the on
position (autoboot?) and nothing happened. So, I then tried your
suggestion:

NEWS> bo sd(0)
Device off line.
NEWS> bo sd
Device off line.
NEWS>

Post by Izumi Tsutsui

Post by Mauricio
What do I need to build binaries from source?

All sources under pub/NetBSD/NetBSD-current/ dir.
http://www.netbsd.org/Documentation/current/
http://www.netbsd.org/Documentation/
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/BUILDING
In short, "sh build.sh -m newsmips -R [somewhere] -D [somewhere] release"
on srcdir should work. The fastest machine would be better.

From what I read I can then build the binaries for the NEWS
3710 box in my sparc/Sol9 or DEC/netbsd box? Cool!

[Izumi Tsutsui]

Post by Mauricio
NEWS> bo sd(0)
Device off line.
NEWS> bo sd
Device off line.

What is SCSI ID of your disk? You have to put ID number of the disk
in parenthesis after device (default is zero).

Post by Mauricio
From what I read I can then build the binaries for the NEWS
3710 box in my sparc/Sol9 or DEC/netbsd box? Cool!

Yes. At least, it should. If it doesn't work, please send-pr.
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio
NEWS> bo sd(0)
Device off line.
NEWS> bo sd
Device off line.

What is SCSI ID of your disk? You have to put ID number of the disk
in parenthesis after device (default is zero).

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:

NetBSD 1.6R (INSTALL) #9: Sat Apr 19 20:49:23 JST 2003
***@mirage:/sys/arch/newsmips/compile/INSTALL
total memory = 12256 KB
avail memory = 7216 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
[...]
wskbd0 at kb0 (mux ignored)
sc0 at hb0 addr 0xbfe00100 level 0
scsibus0 at sc0: 8 targets, 8 luns per target
md0: internal 2560 KB image area
scsibus0: waiting 2 seconds for devices to settle...
SC(t): [istatus=0x80, tstatus=0x2]
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
SC(t): [istatus=0x80, tstatus=0x2]
[...]

and

We now have your BSD-disklabel partitions as (Size and Offset in MB):

Size Offset End FStype Bsize Fsize Preserve Mount point
--------- --------- --------- ------ ----- ----- -------- -----------
a: 64 0 63 4.2BSD 8192 1024 No /
b: 64 64 128 swap
c: 1010 0 1009 unused
g: 881 129 1009 4.2BSD 8192 1024 No /usr


Ok, we are now ready to install NetBSD on your hard disk (sd0). Nothing has
been written yet. This is your last chance to quit this process before
anything gets changed.

Post by Izumi Tsutsui

Post by Mauricio
From what I read I can then build the binaries for the NEWS
3710 box in my sparc/Sol9 or DEC/netbsd box? Cool!

Yes. At least, it should. If it doesn't work, please send-pr.

I will try that later on today (or in the week ;).

[Izumi Tsutsui]

Post by Mauricio
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
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?
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio
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
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
(***@tgm.netbsd.org, 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

***@tgm.netbsd.org:/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 =)

[Izumi Tsutsui]

Post by Mauricio
Ok, almost as I think the password I gave it is not what I thought.

BTW, you could boot a kernel into single user by "bo /2 sd(6)".

Post by Mauricio
Will it be smarter to have its ID = 0?

I think so.

Post by Mauricio
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 don't know newsmips machines can autoboot from disk with ID
other than 0. Some models (NWS-3410 etc.) autoboots via network
by default, but you may be able to change default by
"set bootdev=scsi" command on PROM. (but I haven't confirmed it though)

Post by Mauricio
I am pretty excited now =)

Yeah, congratulations. I'm also glad to see actual NetBSD/newsmips users :-)
---
Izumi Tsutsui
***@ceres.dti.ne.jp

[Mauricio]

Post by Izumi Tsutsui

Post by Mauricio
Ok, almost as I think the password I gave it is not what I thought.

BTW, you could boot a kernel into single user by "bo /2 sd(6)".

Thanks for the info! I will try to remember that for next
time. For now,s ince I replaced the HD and reinstalled netbsd in
this larger drive, I have no problems logging in as root.

Post by Izumi Tsutsui

Post by Mauricio
Will it be smarter to have its ID = 0?

I think so.

Done!

Post by Izumi Tsutsui

Post by Mauricio
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 don't know newsmips machines can autoboot from disk with ID
other than 0. Some models (NWS-3410 etc.) autoboots via network
by default, but you may be able to change default by
"set bootdev=scsi" command on PROM. (but I haven't confirmed it though)

It seems it was a bit confused using "scsi" as the target:

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

Post by Izumi Tsutsui

Post by Mauricio
I am pretty excited now =)

Yeah, congratulations. I'm also glad to see actual NetBSD/newsmips users :-)

Me too! However, right now I still am not able to turn on
the machine and have it boot itself. I enabled autoboot (jumper 5 =
on) and turned the machine on but it has not booted on me: my
console window (connected to its serial port) reports nothing. And,
after having the machine on for the night, I cannot ping (IP
#10.0.0.19 ) it either (I decided to do that in case it simply did
not want to write to console):

Last login: Wed Jan 7 14:22:10 from tisalaj.kushana
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
11:44am up 7 day(s), 18:02, 1 user, load average: 0.05, 0.02, 0.02
***@kushana-1>ping 10.0.0.19
no answer from 10.0.0.19
***@kushana-2>

[Mauricio]

The 3710 has space to put a cdrom drive in it. Does it worth
doing that?

[Izumi Tsutsui]

Post by Mauricio
Stupid question: I have a FH 3GB HD here doing nothing. Can
I use it in my 3710 or it has one of those 2GB limit issues?

I guess NEWS-OS had 2GB limit of file system size
and boot PROM might also the same limit, but it means
that root partition (sd0a) should be smaller than 2GB,
and there is no limit of whole disk size.
---
Izumi Tsutsui
***@ceres.dti.ne.jp