Status: 29 July 2021 - Slit into Part I & Part II

I have some very old high watt, low computational power SGI / IRIX machines. These have been under my care for sometime, and over the years I was member on "Nekochan", as the go to place for various tips on keeping these machines going.

To the great disappointment of many old time SGI geeks "Nekochan" has now gone to the internet graveyard.

If you are have an SGI / IRIX problem then a lot of the Nekochan refugees are now over on "IRIX Network".


So why this interest in old SGI / IRIX machines?

The reasons are N fold:

  1. These machines were the coolest things since sliced bread when I was first out of uni and doing my post graduate studies at RMIT which included both Graphics and AI units. Both Graphics and AI are still relevant today
  2. I went to a "Performance Co-Pilot" birds of feather session earlier in the year (2020). The core "Performance Co-Pilot" team are a bunch of Melbourne based ex-SGI employee's who have been working on this for over 20 years! So it was really interesting to hear what they had to say. My observation is that the collectd and Fluentd are treading over the same ground still.
  3. Many of things that are critical to working with NFVi and cloud infrastructure were available in old SGI machines well before anywhere else including: NUMA (non-uniform memory architecture) which is part of cpu / multi-core Intel server architecture (understanding NUMA is essential to getting best performance from NFVi platforms), L1/L2 seperate systems monitoring and control systems which provide ability to remotely manage and partition the physical infrastructure, Graphics and Video Processing acceleration using specialise CPUs and FPGAs.
  4. I turn on my old machines periodically to see if they are still working, as I expect that at some point, leaky capacitors or dead batteries will kick in and kill them...

This post is not in anyway trying to emulate the wealth of useful information that was on "Nekochan" rather it is just my personal links and tips so I can avoid having to relearn / retest this stuff should I need to redo any of this in the future...

As I was finding it hard to reference my own notes I have split up my SGI / IRIX notes, into the following blogs:


Adaptec AUA-3020 (Blue / Rev. B) - 3 USB + 2 Firewire & AFW-4300B (Red / Rev 1.1) cards

These two variations of Adaptec Firewire boards work (to a lesser and greater extent) with IRIX on Fuel, Tezro (not tested), O350 & Octane. When working correctly they will report as DM10 and IEEE1394 SCSI in hinv.

Correct installation requires 6.5.29/30 and IRIX Firewire 1.1 (Beta) and if install is working then should mean that fwprobe reports board without any additional "hacking" or work arounds.

The two variations are:

  • Adaptec AUA-3020 (Blue / Rev. B) - has 3 x USB + 2 x Full Size FireWire. There is another variation of this board which has 1 x Full Size FireWire + 1 x Mini FireWire (this is kwown as Rev. A). Both of these boards have NEC USB and Texas Instruments FireWire chips.
  • Adaptec AFW-4300B (Red / Rev. 1.1) - has 3 x Full Size FireWire. This board has Texas Instruments FireWire chips. There is another variation of this board with blue PCB which is known not to work with SGI / IRIX.

To use the AUA-3020 on Fuel / O350 you need to set the "systune" kernel configuration parameter:

systune pciio_multimaster_override 1
reboot

See "Internet Archive - Way Back Machine"  - "USB Card and the Fuel"

NOTE #1: In testing on Octane2 adding card to PCI Cage and configuring "systune" parameter causes a kernel crash at boot. Only way to fix is to remove the card from PCI Cage. Without systune "fix" card is not recognised.

NOTE #2: In testing with Fuel with multiple PCI cards installed I have found that AUA-3020 causes kernel crash irrespective of "systune" configuration. So given that Fuel already has USB built in I would just use AFW-4300B (see below).

The AFW-4300B works and reports as DM10 and IEEE1394 SCSI on Fuel, Tezro, O350 and Octane.

However operation on Octane is problematic and fwprobe does not report finding the board and connected devices. I have found that on Octane only IEEE1394 SCSI appears to work and IIDC FireWire Camera does not report correctly. Getting fwprobe to report correctly requires considerable hacking of HW / FW filesystem.


IRIX 6.5.X Network Install

Here is high level summary of IRIX 6.5 network install. See Ian Mapleson's SGI Depot and IRIX TechPubs for additional information;

This installation was for Tezro. IRIX Tezro support starts at 6.5.21 (so I used 6.5.22 to allow for bug fixes). The boot process uses BOOTP and rsh:

  1. Follow Ian Mapleson instructions to get Install Server setup (this involves copy each of IRIX Software Library CD's to disk and optionally creating symlink short cuts to these (to avoid having retype long names all the time)
  2. Use 6.5.22 /miniroot/unix.IP35 as boot image for Tezro
  3. Ensure there is "guest" account access to images by editing: /etc/hosts.equiv and ~guest/.rhost
  4. Use fully qualified host names when referring to source files
  5. Once at PROM select "clean install"
  6. Start with: 6.5.x/overlay-1/CDROM/dist
  7. Proceeed through: ol-2, ol-3, apps, foundations-1, foundations-2, nfs-v3
  8. Then select "done"
  9. At "INST>" prompt:
keep *
install standard
go

10. Address conflicts. Generally the <N>a option is always faster path to resolution

NOTE: Once you have bootable machine you can install additional software via GUI


Resetting Graphics Resolution

The IRIX graphics resolution settting can be managed via UI Display Setting panel, but if you set them to a particular resolution (1600x1200 @ 60HZ) and then change monitors to once that does not support the settings, then you might find you cannot get to GUI any more.

Here are some useful tips:

  • The utilities for graphic are in: /usr/gfx , including gfxinfo (get current graphics pipeline info) and setmon (set the resolution for monitor)
  • The set of valid resolutions are in: /usr/gfx/ucode/<YOUR-TYPE>/vof
  • Graphics types include: ODSY - Odyssey/VPro (V12/V10/V8/V6), IMPACT - Impact (MXE/SSE/SE)
  • X11 Monitor Settings are in: /var/X11/Xvc

So to reset you graphics you can:

  • Reboot machine in single user mode (results in default resolution: 1280x1024 on VPro) and set do /usr/gfx/setmon -x <1600x1200_60> – for example (see /usr/gfx/ucode for valid options)
  • Simply delete the: /var/X11/Xvc/<TYPE>0_TimingTable file and it will regenerate using default on reboot
  • If you can't get into single user mode, then telnet into machine and delete TimingTable file
  • Here are sample Timing Table's:
 -- here is V12 in 1280x1024 @ 60 SAFE
# cat Odyssey0_TimingTable
1280x1024_60_safe
16
1
--- and V12 when in 1600x1200 @ 60
# cat Odyssey0_TimingTable     
1600x1200_60
16
1
-- and here is IMPACT (MXE) in 1600x1200 @60
# cat Impact0_TimingTable
1600x1200_60

Reading IRIX CD ROM on Ubuntu (Linux Box)

If you need to read an IRIX OS or other cd and do not have a CD/DVD drive connected to your SGI machine, here is simple workaround:

  1. Ensure you have xfsprog package installed (XFS == eXtensible File System)
  2. Copy the entire CD to an image file (using dd)
  3. Do a loop mount of image specifying type as efs (== extent file system)
# sudo apt install xfsprogs
# sudo dd if=/dev/cd0 of=irix-cd-01.img
# sudo mkdir /mnt/IRIXCD
# sudo mount -t efs -o ro,loop irix-cd-1.img /mnt/IRIXCD
# ls /mnt/IRIXCD
CDgrelnotes  CDrelnotes  dist  installtools  relnotes  stand  WhatsNew

NOTES 1: Why efs rather than xfs type ?

  • EFS preceeded XFS and all SGI OS cds, have been formatted as EFS to allow booting by older machines

NOTE 2: What about RedHat ?

  • SGI and RedHat co-developed the Linux EFS/XFS file system support so RedHat has XFS built in and uses it as default file-system (rather than ext4 like Ubuntu)

NOTE 3: The RedHat / SGI connection runs deep as SGI did a lot of porting to RedHat Linux, including the "Performance Co-Pilot" tool set


Old SGI IRIX comes with DatMan DAT Audio Player

Old SGI's where the only machine that was available that could play DAT Audio tapes. To do this you needed to have a DAT/DDS drive that had special SGI firmware.

There were two main tape drives that were available:

  • Connor Archive - DAT/DDS-2
  • Sony SDT-9000 - DAT/DDS-3 that came in two varieties, one with firmware version 12.2 and one with version 13.1 .

You can flash Sony SDT-9000 drives with SGI software. The tools for this include "Sony Tape Fireware Upgrade Utility. Here is version 1.1 of this that runs on Windows XP and there are more recent and even a linux version available if you do search. There is also a DOS based flashing tool that you ran from a boot floppy. This cames packaged with SDT-9000 12.2 firmware. To use this you also have to have the DOS ASPI drivers on the boot floppy with appropriate CONFIG.SYS loader file.

My Sony SDT-9000 is an original SGI version, with 13.1 firmware. Using IRIX scsicontrol you get:

/dev/scsi/sc1d1l0:  Tape          SONY    SDT-9000        13.1
ANSI vers 2, ISO ver: 0, ECMA ver: 0; supports:  synch
Device is  not ready

The 13.1 firmware used to be available from http://forums.rpc1.org but this site is now long gone and unfortunately I seem to have lost my version...

NOTE: Having looked at my SDT-9000, I saw that it is an original SGI part with F/W 13.1 clearly stamped on it. I will see if I can use SCSI tool to extract firmware in non-distructive way.


Network Setup on IRIX

The following files are used to set the main IRIX (6.5) network configuration:

  • /etc/sys_id - the host name (not qualified) such as "frog"
  • /etc/hosts - the more complete host name and IP address, ensure you have line such as: "XXX.XXX.XXX.XXX. frog.MYDOMAIN.COM frog" (also check that localhost is defined (127.0.0.1)
  • /etc/config/netif.options - if you have mutltiple network cards and you want to change which is default then you will need to change the network interface / name configuration (typically required if you add a 1GbE or 10GbE card to your machine
  • /etc/config/ifconfig-N.options - if you need to change the network mask (defaults to 255.255.255.0) or other interface specific options. Each interface needs it own file with N=1 provided and others needing to be created explicitly
  • /etc/config/static-route.options - define the default (static route) with a line like: "$ROUTE $QUIET add net default XXX.XXX.XXX.XXX"
  • /etc/resolv.conf - to configure your DNS resolution (as per other Unix platforms)
  • /etc/nsswitch.conf - the network services switch file, make sure that the host line is using file, dns (and not yp - yellow pages, which is now obselete)
  • /etc/config/proclaim.options - if you want to configure interfaces via DHCP. Note that you must have an ip address/host name entry in the "/etc/hosts" file for proclaim to correctly configure the interface
  • /etc/ethers - provides mapping between MAC address and host name. To find MAC address of interfaces: "netstat -ian"

Locale and other IRIX configurations

IRIX shell and systems behaviour is strong affected by the Locale settings. Having incorrect Locale setting can result in strange behavior including:

  • EZsetup Account - not working
  • Infosearch - puts the wrong title on the Browser window

There are two primary environment variables that you need to make sure you have configured: TZ & LANG. The default configurations for these are in:

  • /etc/TIMEZONE - look at /usr/lib/locale/TZ for the set of defined Time Zones or you can just create you own withing the TIMEZONE configuration file
  • /etc/default/login - make sure that this has LANG=C or something else as otherwise EZsetup will not find language and location and so will automatically log out session
  • /var/sgi_apache/httpd-outbox/etc/httpd.conf - is the Apache config file and Server name here will result in what is put on the Browser title page with Infosearch (web based help)

IRIX Device ID Allocations & Serial Port Setup

IRIX generally does a good job of setup up your device configuration. However sometimes things can go a bit funny when you pull devices in and out of your system and the result is that the Device ID allocations change and your various configuration file that need to matches there for get broken.

Examples are ethernet interfaces, which by convention ussually start from 0 and are incremented sequentially (i.e. tg0, tg1, tg2, tg3 ... or ef0, ef1, ef2).

These interface names are then reference in various network startup scripts.

So what happens when these change unexpectedly ?

So what was previously tg1 & tg2 become tg3 & tg4.

You can either change the scipt that references then or you can reset the allocations which are managed via: /etc/ioconfig.conf

This is generated automatically during the hardware graph enumeration, here is an example of a large file from O350:

3 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/tty/1
4 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/tty/2
5 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/tty/3
6 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/tty/4
0 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/keyboard
0 /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/mouse
1 /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/1/mad_subsys
1 /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/2/rad_subsys
0 /hw/module/001c02/IXbrick/xtalk/12/xtdigvid
7 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/tty/1
8 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/tty/2
9 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/tty/3
10 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/tty/4
3 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
2 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/1/ei
4 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
5 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
1 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/4/tg
6 /hw/module/001c02/IXbrick/xtalk/15/pci-x/1/1a/scsi_ctlr/0
7 /hw/module/001c02/IXbrick/xtalk/15/pci-x/1/1b/scsi_ctlr/0
1 /hw/module/001c02/IXbrick/xtalk/15/pci-x/1/2/xframe
11 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/tty/1
12 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/tty/2
13 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/tty/3
14 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/tty/4
8 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
3 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/1/ei
9 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
10 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
2 /hw/module/001c03/IXbrick/xtalk/15/pci-x/0/4/tg
15 /hw/module/001c03/IXbrick/xtalk/15/pci-x/1/1/tty/1
16 /hw/module/001c03/IXbrick/xtalk/15/pci-x/1/1/tty/2
11 /hw/module/001c03/IXbrick/xtalk/15/pci-x/1/2/ohci/0/scsi_ctlr/0
17 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/tty/1
18 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/tty/2
19 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/tty/3
20 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/tty/4
12 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
4 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/1/ei
13 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
14 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
3 /hw/module/001c04/IXbrick/xtalk/15/pci-x/0/4/tg
21 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/tty/1
22 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/tty/2
23 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/tty/3
24 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/tty/4
15 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
5 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/1/ei
16 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
17 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
4 /hw/module/001c05/IXbrick/xtalk/15/pci-x/0/4/tg
18 /hw/module/001c05/IXbrick/xtalk/15/pci-x/1/2/scsi_ctlr/0
25 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/tty/1
26 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/tty/2
27 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/tty/3
28 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/tty/4
19 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
6 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/1/ei
20 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
21 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
5 /hw/module/001c07/IXbrick/xtalk/15/pci-x/0/4/tg
22 /hw/module/001c07/IXbrick/xtalk/15/pci-x/1/2/scsi_ctlr/0

The format is: <id> <hw-tree-device>

So that for a particular device type as as: tg where have:

  • "1 /hw/module/001c02/IXbrick/xtalk/15/pci-x/0/4/tg" - this will be tg1

So if you want to change the device id then you need to edit the file and change the corresponding <id> numbers.

The <id> device numbers need to unique within a given device type family.

I have found that serial port ids are very prone to getting changed.

The serial port family are of type: tty

To get serial ports running correctly you will need to use the following configuration files"

  • /etc/ioconfig.conf  - the id allocations
  • /etc//etc/inittab - to make the port available for use
  • /etc/uucp/Devices - to configure the modem or direct connect behavior for port and the available speed it can connect with...

NOTE: I was forced to delve into this due to miss behavior Fuel console port. See this thread on Irix Network


MIDI via SGI Serial Port

SGI of at least the Octane era have very versatile Serial ports that can be controlled via sofware to support:

  • RS-232 - the default serial coms
  • RS-422 - balanced serial comms that is basis for AppleTalk / LocalTalk networking
  • AppleTalk - as SW on top of RS-422 and
  • MIDI - again on top of RS-422

To support RS-422/AppleTalk/MIDI you will need to solder together special cable.

Traditional serial MIDI (1.0) used a DIN (European standard) plug that was totally foreign go computer communiations (though used extensively in audio applicatios) which used RS-232, DB9 (PC's) and mini DIN (Mac). So to connect a computer to MIDI the first thing you needed as either a special cable, a conversion unit or most likely both.

For my SGI Octane2 I leveraged a simple passive converter made by Opocode. The Opcode Translator Pro and cut open a Macintosh LocalTalk/Serial cable  and wired it up with RS-422 / MIDI wiring compatible DB9. Here are the pictures of the MIDI interface parts for SGI setup:

Opcode Translator Pro with DB9 to mini DIN-8
Opcode Translator Pro - Front Panel
Opcode Translator Pro - Back Panel (Model / CPU - mini DIN-8 & Modem - Out DIN to Keyboard)

If you are looking to use such a set up, read about connecting old Macintosh's to MIDI and this post on MIDI on O2 which was what I referred when setting up Octane over 10 years ago.

NOTE 1: Officially the DB9 is a DE-9, but it is ubquitously referred to as DB9 including in SGI documentation

NOTE 2: Do a "man serial" to get comprehensive of description of wiring and control of the SGI serial ports and how these vary across machines.


Using "Browservice" as Proxy for Modern Web via SGI / IRIX

One area of frustration for retro-computing is that the old Web browser is pretty much useless. A nice workaround is to use a proxy server than handles modern web broswer rendering and then passes result but to retro-browser as something they can use (jpgs or png bitmaps).

"Browservice" is one such solution that is simple to set up and use. To set it up you need to compile the proxy on Ubuntu server and the start up the proxy:

  • Installation - for me went mostly without a hickup
  • Running - the proxy I used guideance from "defaultrouteuk" via the YouTube he posted on his experience.
---
--- 1. Browservice Intall on Ubuntu, starting with pre-requisites
---
$ sudo apt install cmake g++ pkg-config libxcb1-dev libx11-dev libpoco-dev libjpeg-dev zlib1g-dev libpango1.0-dev libpangoft2-1.0-0 ttf-mscorefonts-installer xvfb xauth libatk-bridge2.0-0 libasound2 libgbm1 libxi6 libcups2 libnss3 libxcursor1 libxrandr2 libxcomposite1 libxss1
[sudo] password for USR:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package ttf-mscorefonts-installer is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package libpoco-dev
E: Package 'ttf-mscorefonts-installer' has no installation candidate
E: Unable to locate package xvfb

---
--- Install issues as per github guide for Ubuntu so
---     remove ttf-mscorefonts-installer and do manual install via
---     debian package
---

$ sudo apt remove ttf-mscorefonts-installer
$ wget https://www.nic.funet.fi/debian/pool/contrib/m/msttcorefonts/ttf-mscorefonts-installer_3.7_all.deb
$ sudo dpkg -i ttf-mscorefonts-installer_3.7_all.deb
Selecting previously unselected package ttf-mscorefonts-installer.
(Reading database ... 70776 files and directories currently installed.)
Preparing to unpack ttf-mscorefonts-installer_3.7_all.deb ...
Unpacking ttf-mscorefonts-installer (3.7) ...
dpkg: dependency problems prevent configuration of ttf-mscorefonts-installer:
 ttf-mscorefonts-installer depends on cabextract; however:
  Package cabextract is not installed.
 ttf-mscorefonts-installer depends on xfonts-utils; however:
  Package xfonts-utils is not installed.

dpkg: error processing package ttf-mscorefonts-installer (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 ttf-mscorefonts-installer
 
 ---
 --- Now missing cabextract so install this
 ---   this was not found, so did apt update and then install.
 ---   Install failed again indicating need to do:
 ---    $ apt --fex-broken install
 ---
$ sudo apt install cabextrat
$ apt search cabextract
$ sudo apt update
$ sudo apt-get install cabextract
$ sudo apt --fix-broken install
$ sudo apt-get install cabextract

---
--- Now go back to debian install that failed
---

$ sudo dpkg -i ttf-mscorefonts-installer_3.7_all.deb

---
--- And back to pre-requistite install...
---

$ sudo apt install cmake g++ pkg-config libxcb1-dev libx11-dev libpoco-dev libjpeg-dev zlib1g-dev libpango1.0-dev libpangoft2-1.0-0 ttf-mscorefonts-installer xvfb xauth libatk-bridge2.0-0 libasound2 libgbm1 libxi6 libcups2 libnss3 libxcursor1 libxrandr2 libxcomposite1 libxss1

---
--- Prequisites installed so now clone repository and build
---

$ mkdir src
$ cd src
$ git clone https://github.com/ttalvitie/browservice.git
Cloning into 'browservice'...
remote: Enumerating objects: 24, done.
remote: Counting objects: 100% (24/24), done.
remote: Compressing objects: 100% (17/17), done.
remote: Total 1284 (delta 10), reused 15 (delta 7), pack-reused 1260
Receiving objects: 100% (1284/1284), 2.55 MiB | 1.28 MiB/s, done.
Resolving deltas: 100% (966/966), done.
$ cd browservice
$ ./download_cef.sh
$ ./setup_cef.sh
$ make -j5
$ sudo chown root:root release/bin/chrome-sandbox && sudo chmod 4755 release/bin/chrome-sandbox

---
--- All built so start the proxy.. on port 8080
---   with jpg generation
---

$ release/bin/browservice --http-listen-addr=0.0.0.0:8080 --use-dedicated-xvfb=YES --default-quality=100

Point your browser at proxy and you should get modern web via jpgs:

Modern Web via Browservice on IRIX 6.5

Thanks you "defaultrouteuk" I hope the packet get home ok ;-)


References & Links:

  • Irix Network - working to take up hole left with demise of Nekchan, populated by many passionate and knowledgeable SGI users
  • irix7.com - keep an archive of lots and lots of original SGI technical documents
  • SGI Depot - keeps an archive of various sgi related materials and provides parts. run by Ian Mapleson one of the original sgi/irix community members and all round helpful person
  • techpub.jurassic.nl - another SGI TechPubs archive, link and thanks for keeping this high quality document (via HTML and PDF), while irix7 above is PDFs
  • Opcode Translator Pro - was a simple Macintosh targetted MIDI interface and can be used with correctly wired cable provide MIDI keyboard interface for Octane and other SGI machines that support MIDI via serial port. See the following site for various other retro-Mac MIDI stuff.
  • MIDI on O2 - this page is the one that I referred to over 10 years ago when setting up MIDI on Octane
  • Past Echos the Future (Part II) - O350 / Chimera Stuff... - is where I have collected all the SGI Chimera mateial

HINVs

hinv -mv (hardware inventory) is the start of understanding what your SGI machine is and what's inside it. Here are a couple of samples, starting with Tezro the last "Desktop" IRIX / MIPS SGI.

This type if data is simillar, but much easier to decipher than that you get from ipmi (BMC) interface.

The never changing hinv reports from my sgi machines... is here.


NOTES 1: Thanks to Mark Whithouse from Red Hat for invitation to "Performance Co-Pilot" birds of a feather session.

NOTES 2: Photo is of Numalink'ed Origin/Onyx O350.