From: Eric Kimminau <eak@detroit.sgi.com>
To: Vince Weaver <weave@eng.umd.edu>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: identifying sgi system type under Linux
Date: Thu, 13 Jan 2000 14:18:40 -0500 [thread overview]
Message-ID: <387E2510.43D52D70@detroit.sgi.com> (raw)
In-Reply-To: Pine.GSO.4.21.0001131258320.25401-100000@z.glue.umd.edu
Vince Weaver wrote:
>
> Hello again
>
> I was trying to see if I could get this Indigo2 to display that it is an
> Indigo2 under /proc/cpuinfo [instead of current behavior, which assumes
> all SGI's are indy's].
>
> Is it possible to figure out what system type it is from this info? Is
> there another way to find out sgi system type? Or is this just not
> possible?
Howdy Vince!
I can give you a bit of info but I am not sure how helpful it will be.
Booting into the IRIX command monitor (esc on boot)
To perform system maintenance instead, press <Esc>
(then option 5)
System Maintenance Menu
5) Enter Command Monitor
You have available the hinv command:
>> hinv
System: IP22
Processor: 200 Mhz R4400, with FPU
Primary I-cache size: 16 Kbytes
Primary D-cache size: 16 Kbytes
Secondary cache size: 1024 Kbytes
Memory size: 128 Mbytes
Graphics: Indy 8-bit
SCSI Disk: scsi(0)disk(1)
SCSI Disk: scsi(0)disk(2)
SCSI Disk: scsi(0)disk(3)
SCSI Disk: scsi(0)disk(6)
Audio: Iris Audio Processor: version A2 revision
4.1.0
Also try:
hinv -v
hinv -t
hinv -v -t
hinv -t -p
hinv -v -t -p
The problem is that IP22 could be an Indy or an Indigo/2. Even under
IRIX if you run hinv it doesn't tell you that a system is an Indy or
an Indigo/2. Your only clues come from knowing additional bits about
what is or is not Indy or I2 hardware. For example you would never
see Impact graphics on an Indy and you would never see an Indy 8-bit
graphics board on an Indigo/2 (although there were 8 bit boards on an
Indigo/2 - I have been looking aorund internally to see if I can find
one to see what it actually reports at command monitor for graphics).
Further confusion would be to try and identify an older Indigo with an
R4000 upgrade from an Indy.
If you actually got booted to IRIX, you would have even more options
available using the "-c" option to hinv:
Option requires an argument -- c
usage: hinv {-v -m -s -c class -t type -d dev -u unit -a file}
where class can be:
processor
disk
memory
serial
parallel
tape
graphics
network
scsi
audio
iobd
video
bus
misc
compression
vscsi
display
unconnected scsi lun
PCI card
PCI no driver
prom
IEEE1394
rps
tpu
type can be:
fpu
cpu
dcache
icache
memory
qic
a2
dsp
dev can be:
cdsio
aso
ec
et
ee
ecf
ef
eg
enp
fxp
ep
hy
ipg
rns
xpi
fv
gtr
mtr
mtr
atm
hippi
vfe
gfe
gsn
divo
xthd
but again, hinv -c processor will only tell you that it is an IP22 :
Indy1 % hinv -c processor
1 200 MHZ IP22 Processor
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
CPU: MIPS R4000 Processor Chip Revision: 2.2
Indy2 % hinv -c processor
CPU: MIPS R4600 Processor Chip Revision: 2.0
FPU: MIPS R4600 Floating Point Coprocessor Revision: 2.0
1 133 MHZ IP22 Processor
ChalS% hinv -c processor
CPU: MIPS R4400 Processor Chip Revision: 6.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 200 MHZ IP22 Processor
Indigo2 % hinv -c processor
CPU: MIPS R4400 Processor Chip Revision: 6.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 250 MHZ IP22 Processor
Where graphics would yield more information:
Indy1 % hinv -c graphics
Graphics board: Indy 8-bit
Indy2 % hinv -c graphics
Graphics board: Indy 24-bit
Indigo2% hinv -c graphics
Graphics board: Solid Impact
I am asking around internally to see what if any portions of kernel
probe related code might be releaseable but the problem with even
attempting that (from the few limited conversations I have had with
kernel engineers) is that none of the IRIX hardware identification
code is in one central place. It is really all over the place and
dynamically builds this type of information in the hardware graph unde
IRIX based on all of the hardware the kernel finds in the system.
Short of identifying every possible piece of SGI hardware and doing
the same kinds of things under Linux as are done in IRIX to build the
hardware graph, I think this is probably going to be a fairly
difficult proposition. I am BCC'ing a few people on this message in
hope that they may respond to you singularly with additional
information.
I wish I could tell you more. I will let you knwo if I do find
something more useful.
Eric.
--
.--------1---------2---------3---------4---------5---------6---------7.
Eric Kimminau eak@sgi.com SGI Extranet Services
Vox:650-933-6441 Fax:248-618-9178 VNET:6-933-6441
"I speak my mind and no one else's."
"I am a bomb technician. If you see me running, try to keep up..."
http://support.sgi.com
next prev parent reply other threads:[~2000-01-13 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-12 16:27 cross-compile fails Vince Weaver
2000-01-12 20:04 ` Vince Weaver
2000-01-12 22:31 ` Vince Weaver
2000-01-13 18:09 ` identifying sgi system type Vince Weaver
2000-01-13 18:32 ` Status Indigo2 Beowulf project Avi Bercovich
2000-01-14 17:01 ` Andrew R. Baker
2000-01-13 19:18 ` Eric Kimminau [this message]
2000-01-13 20:31 ` identifying sgi system type under Linux Vince Weaver
2000-01-13 21:15 ` William J. Earl
2000-01-13 21:45 ` identifying sgi system type under Linux [patch] Vince Weaver
2000-01-14 12:25 ` Ralf Baechle
2000-01-13 23:19 ` identifying sgi system type William J. Earl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=387E2510.43D52D70@detroit.sgi.com \
--to=eak@detroit.sgi.com \
--cc=eak@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=weave@eng.umd.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox