[Top] [All Lists]

Re: Trying to boot an Indy

To: Ralf Baechle <>
Subject: Re: Trying to boot an Indy
From: Dave Gilbert <>
Date: Sun, 21 Jan 2001 13:27:12 +0000 (GMT)
In-reply-to: <>
On Sun, 21 Jan 2001, Ralf Baechle wrote:

> On Sun, Jan 21, 2001 at 02:01:15AM +0000, Dave Gilbert wrote:
> > 2) So I ftp'd the file over under Irix, gzip -d'd it and then rebooted and
> > from sash did boot indyvmlinux - this immediatly after starting gave
> > 'Exception: <vector=UTLB Miss>' plus details (available on request).
> > (This is kernel vmlinux=001027-test9-r4x00.gz off
> >
> > 
> > This is an Indy R4600PC with 64MB RAM.
> You may have become a victim of a sash bug which makes the firmware report
> used memory as free memory and in the end results in the kernel overwriting
> itself.  The solution is easy; don't use sash.  This means you either
> have to boot the kernel via ``bootp() -f ...'' from the network or you
> use IRIX's dvhtool to write it into the volume header, then boot it from
> the kernel prompt by just entering the kernel name.

Well the bootp() stuff still won't respond so that is out, and dvhtool is
saying there isn't enough room for my linux image. Hmph.

Running bootpc under Irix seems to give sensible results.

Is there any other mechanism for loading other than bootp ?


 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert      | Running GNU/Linux on m68k, |  Happy  \ 
\   gro.gilbert @ |  Alpha, x86, ARM and SPARC |  In Hex /
 \ ___________________________|___  |________/

<Prev in Thread] Current Thread [Next in Thread>