Re: Install Indy R4600 100Mhz IP22
- To: email@example.com
- Subject: Re: Install Indy R4600 100Mhz IP22
- From: firstname.lastname@example.org
- Date: Thu, 9 Oct 2003 13:04:26 -0700
- Message-id: <20031009200426.GO20048@storm>
- In-reply-to: <20031009025342.GB17298@storm>
- References: <20031009025342.GB17298@storm>
I thought I would answer my own question. Just in case anyone is
having the same problems on Indy.
I basically turned off Hardware Flow Control in minicom, which fixed
my problem, I am now able to continue with my installation.
Funny though, Hardware Flow Control was never a factor with my other
Indy R4600 or my Indy R4000SC. Although it was with my Indigo2.
On Wed, Oct 08, 2003 at 07:53:42PM -0700, email@example.com wrote:
> I am trying to install Debian/Mips on an Sgi Indy, R4600 100MHZ IP22
> machine. I did see that there are some known problems with perl, and
> R4600 V1.7 (how does one know if they have an R4600 V1.7?).
> Anywyas, I have successfully installed Debian on an R4000SC, and R4600
> before, and they are working great as nameservers (the R4600 works
> perfectly and has had an uptime for over 1 year).
> Here is my problem with my current machine.
> When I bootp()tftpboot.img, everything loads fine. I can see the kernel
> messages come up as usual, and I even get to the fist screen of the
> install which is titled "Reloase Notes". However, I try to press
> "enter" to Continue, and nothign happens. It seems as if the install
> has frozen.
> Does anyone know how I can get more debuggin info, or has anyone had
> this problem and know how to resolve it?
> Here is the "hinv" from the Command Monitor:
> System: IP22
> Processor: 100 Mhz R4600, with FPU
> Primary I-cache size: 16 Kbytes
> Primary D-cache size: 16 Kbytes
> Memory size: 64 Mbytes
> Graphics: Indy 8-bit
> SCSI Disk: scsi(0)disk(1)
> Audio: Iris Audio Processor: version A2 revision 4.1.0
> Any help is greatly appreciated.
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com