Guidelines for "hinv"-Thread

A place to post hardware inventories.
Forum rules
Please post your 'hinv' in the following format:

Topic: Kind of machine (O2, Octane, Tezro, Onyx2, etc.), CPU (R10k 250MHz, R12k 300MHz, R16k 1GHz, etc.), RAM, graphics option (Example: Tezro V12 4xR16K 700MHz 4GB)

Body: output of hinv -v (hinv -vm if possible) and /usr/gfx/gfxinfo.

Please wrap the output in BBCode "code" blocks to improve legibility.
User avatar
Thomas W.
Posts: 402
Joined: Tue Sep 09, 2003 11:54 pm
Location: Germany/NRW/Bonn

Guidelines for "hinv"-Thread

Unread postby Thomas W. » Mon Jan 12, 2004 3:56 am

Hello to all,

i do not want to be the master/teacher/instructor.

But i have a small problem with the "hinv"-Thread.

On the Forum-Mainpage you can read:


A place to post hardware inventories; format is topic: basic system description; body: output of hinv -v

Does it not mean something like that:

Tezro V12 4xR16K 700MHz
O2000 6CPU R12K
O2 R10000 175MHz, 384MB RAM

Body: output hinv -v bla,bla,bla

But what kind of machine is this:

me too ;-)
my Octane and my O2
Dev system/video editing, O2 webserver O2
just upgraded Octane
Home Origin 2000 :)

and so on, and so on.

Could we standardize it?


Kind of machine (O2, Octane, Tezro, Onyx2, etc.)
CPU (R10k 250MHz, R12k 300MHz, R20k 1000MHz, etc.)
RAM (in MB)

And one topic for ONE MACHINE.

So you can see at first sight if the machine is interesting for you.

(i have to apologize to you for my horrible english)

User avatar
Posts: 2112
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Unread postby dexter1 » Mon Jan 12, 2004 5:09 am

You have a valid point. I will try to reedit that particular posting.

User avatar
Posts: 263
Joined: Fri Jan 24, 2003 1:32 pm
Location: France

Re: Guidelines for "hinv"-Thread ???

Unread postby bobflappy » Mon Jan 12, 2004 5:21 am

Thomas W. wrote:(i have to apologize to you for my horrible english)

Don't care about it, it's not as horrible as mine with my french-english words. ;)

And for this thread rules, you're absolutely right.

Posts: 495
Joined: Mon Oct 20, 2003 6:49 am
Location: NRW, Germany

Unread postby schleusel » Mon Jan 12, 2004 5:34 am

while we're at it.. i'd also suggest posting hinv -mv instead of only -v as most people did so far..
-m gives quite a bit additional interesting output on most newer machines (part numbers and such)

so long,

User avatar
Site Admin
Site Admin
Posts: 8091
Joined: Thu Jan 23, 2003 1:31 am
Location: Pleasanton, California

Unread postby nekonoko » Fri Jan 16, 2004 4:34 pm

Also don't forget to check 'Disable Smiles in this post' on hinv output; this prevents something like the following line from being munged:

Disk drive: unit 8 on SCSI controller 4 (unit 8)

i.e. the "8)" at the end becomes a smiley face if this is not checked (it's been checked on this post).

I went through and fixed a couple posts already.
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

User avatar
Posts: 3075
Joined: Tue Aug 21, 2007 10:12 pm
Location: Kentucky, United States

Re: Guidelines for "hinv"-Thread ???

Unread postby guardian452 » Fri Feb 20, 2009 10:23 am

1. irix version
2. maybe a picture?

Google: Don't Be Evil. Apple: Don't Be Greedy. Microsoft: Don't Be Stupid.

User avatar
Posts: 103
Joined: Thu Nov 11, 2010 1:43 pm
Location: Sao Paulo, Brazil

Re: Guidelines for "hinv"-Thread ???

Unread postby Tabalabs » Tue Dec 14, 2010 7:07 am

I'd include, for fun factor, a picture of the machine and/or actual setup
THE dream come true: Silicon Graphics' Octane
Image Octane R10000 225MHz, 2GB RAM, 1x36GB HDs, 21" monitor, SSI (no TRAM) graphics
:Indy: Indy R5000 (specs to be determined)

User avatar
Posts: 1490
Joined: Mon Nov 12, 2007 7:54 pm
Location: Berkeley, CA, USA, NA, Earth, Sol

Re: Guidelines for "hinv"-Thread ???

Unread postby smj » Wed Dec 15, 2010 1:43 am

So to recap... These hinv listings are important in a number of ways:

  • They can be useful records of factory configurations
  • They provide useful compatibility information about non-factory configurations
  • They can help identify working or incompatible firmware or board-level revisions
  • They provide fun hints of what's possible to somebody thinking of buying one
  • Mining these listings can help solve problems posted in other forums

So for all of these reasons, as well as a little healthy bragging about your shiny new toy, please consider posting and maintaining a "hinv" thread for your SGI machines.

Your thread topic or subject should follow this general format: Model, CPU(s), RAM, graphics, storage, and other options. Some examples:

Within the body you can talk about how you acquired the machine and what you'd like to do with it, but please include as much of the following as possible/applicable:

  • hinv -v (-vm if you can)
  • gfxinfo -v (-vv if possible)
  • uname -a (-aR if appropriate)
  • scsicontrol -i /dev/scsi/* (change path as needed)
  • /sbin/diskpatch -v
  • L1/L2 serial all
  • L1/L2 flash status
  • L1/L2 env
  • L1/L2 pci

Enclosing the output from these commands in "Code" blocks using the "full editor" can help keep things organized and easily readable. Also consider checking the "Disable smilies" option below the editing window, as some machine output may be interpreted as a smiley and won't display properly otherwise.

Pictures of the machine(s) are encouraged, but please keep in mind the fact that the board doesn't have infinite storage. Unless you're posting a detailed close-up for a specific reason, consider limiting your image to at most 1k pixels high or wide, and use an image format that supports compression like JPEG. Posting a 10MB RAW or JPEG image straight from the camera means some poor moderator will have to download it, reduce the size, and then replace it - best to keep "creative control" and edit it before you upload it. ;)
Then? :IRIS3130: ... Now? :O3x02L: :A3504L:- :A3502L: :1600SW:+MLA :Fuel: :Octane2: :Octane: :Indigo2IMP: ... Other: DEC :BA213: :BA123: Sun, DG AViiON, NeXT :Cube:

Return to “SGI: hinv”

Who is online

Users browsing this forum: No registered users and 2 guests