Re: Upgrading 3.0.1 to 4.0 on IP22

["Stephen M. Rumble" <stephen.rumble%utoronto.ca@localhost>]

Quoting Stephen Borrill <netbsd%precedence.co.uk@localhost>:

> On Fri, 20 Jun 2008, Stephen Borrill wrote:
> > On Fri, 20 Jun 2008, Michael Lorenz wrote:
> > > > Should the 3.0.1 bootloader happily boot 4.0?
> > >
> > > Probably not - should be easy to try, noting keeps you from having  
> > >  more than one loader in the volume header.
> >
> > Copied the one from NetBSD 4 as boot4, but boot4 /netbsd4 was just the same.
> >
> > I'll try -current now.
>
> To followup myself, -current works better (current bootloader won't
> load netbsd-4 kernel, BTW). The INSTALL kernel boots, but after
> creating the mfs /dev it reports tset: command not found and I could
> proceed no further. Key presses were being accepted but nothing
> happened. With a -current GENERIC kernel and my 3.0.1 userland it gets
> as far as swapctl before hanging.

Do you have a hinv output for this? I've not used -current in a long  
time (no SGIs here), so I've no idea how well the mips stuff is  
working, but I've not seen problems like this before...

> Console is still wrong though (as it was on 3.0.1). There's no cursor
> and backspace doesn't wipeout the previous character (on the terminal,
> it does as far as input is concerned), so it can be tricky to use.

This is an Indy? That is, it's using newport(4), and not the ARCS console?

Steve