[789] in Release_7.7_team
Re: Workaround for SGI camera problem
daemon@ATHENA.MIT.EDU (Ping Huang)
Tue Dec 3 15:02:16 1996
From: Ping Huang <pshuang@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
Cc: sipb-staff@MIT.EDU, sipb-prospectives@MIT.EDU, cfyi@MIT.EDU
Cc: release-team@MIT.EDU
In-Reply-To: Your message of "Tue, 03 Dec 96 14:40:01 EST."
<9612031940.AA24263@small-gods.MIT.EDU>
Date: Tue, 03 Dec 96 12:00:42 -0800
Greg Hudson <ghudson@MIT.EDU> wrote:
> For now, you should be able to fix the problem on a machine-by-machine
> basis by becoming root, running:
>
> /etc/init.d/autoconfig -f
>
> and then rebooting the machine.
If you want to autoconfig the machine by hand, /etc/autoconfig -f will
do the trick more directly.
> I believe that you can tell if an SGI Indy is r4600-based or
> r5000-based by looking at the position of the shiny decoration on the
> front case. If it's next to the "Indy" logo and above the ridge, it's
> r4600-based. If it's down below the ridge, it's r5000-based.
A surer way to tell is to run the hardware inventory program:
% hinv | grep CPU
CPU: MIPS R4600 Processor Chip Revision: 2.0
versus
% hinv | grep CPU
CPU: MIPS R5000 Processor Chip Revision: 1.0
Most R5000-based Indy's shipped in a case which has a logo on the
front that explicitly mentions the R5000. However, cases have a way
of not always staying with the systems they came with.
--
Ping Huang <pshuang@mit.edu>; more info: http://web.mit.edu/pshuang/.plan
Disclaimer: unless explicitly otherwise stated, my
statements represent my personal viewpoints only.
