In article <3ECB2638.3050602@enseeiht.fr>
Emmanuel.Chaput@enseeiht.fr wrote:

> 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.

> # 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.

> # 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 !

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  |................|

>     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?

>  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
tsutsui@ceres.dti.ne.jp