IP22 is Silicon Graphic's software archicture name for the hardware sold as Indy, Indigo 2 and Challenge S. Modulo peripherals these systems are all very similar. Various Linux distributions will easily install on IP22, among them the [http://www.debian.org/ports/mips/ Debian MIPS port].

IP22 is Silicon Graphic's software architecture name for the hardware sold as '''[[Wikipedia:SGI_Indy|Indy]]''', '''[[Wikipedia:SGI_Indigo2|Indigo<sup>2</sup>]]''', '''POWER Indigo<sup>2</sup>''', '''Indigo<sup>2</sup> R10000''', '''Challenge S''' and '''Challenge M'''. Modulo peripherals these systems are all very similar. Various Linux distributions will easily install on IP22, among them the [[Distributions#Debian|Debian MIPS port]].

== Processor Options ==

== Processor Options ==

−

Over the years Indy systems have been equipped with a variety of MIPS processor starting with the 100MHz [[R4000|R4000PC]] over [[R4000|R4000SC]], [[R4000|R4400PC]], [[R4000|R4400SC]], [[R4600|R4600PC]], [[R4600|R4600SC]], [[R5000|R5000PC]] and [[R5000|R5000SC]]. Indigo 2 systems use the same system board as Indys but have only been been made with [[R4000|R4000SC]] and [[R4000|R4400SC]] processor modules.

+

[[Image:IP22-R4600SC-133MHz-CPU-module.jpg|thumb|120px|right|IP22 R4400 PM5 processor module]]Over the years '''Indy''' and '''Challenge S''' (main logic board IP24) systems have been equipped with a variety of MIPS processor modules starting with the 100MHz [[R4000|R4000PC]] over [[R4000|R4000SC]], [[R4000|R4400PC]], [[R4000|R4400SC]], [[R4600|R4600PC]], [[R4600|R4600SC]], [[R5000|R5000PC]] and [[R5000|R5000SC]].

−

The POWER Indigo 2 is based on the IP26 system board and comes with the [[R8000]] processor. The R8000 is in many ways a unique MIPS processor and currently only partially supported by Linux.

+

'''Indigo<sup>2</sup>''' and '''Challenge M''' (IP22) systems have only been made with [[R4000|R4000SC]] and [[R4000|R4400SC]] processor modules.

−

The architecturally very similar Indigo 2 R10000 is based on the IP28 system board and has a MIPS [[R10000]] processor. This system represents a very special case and therefore isn't supported yet by Linux.

+

The '''POWER Indigo<sup>2</sup>''' is based on the IP26 system board and comes with the [[R8000]] processor. The R8000 is in many ways a unique MIPS processor and currently only partially supported by Linux. As such, it is not possible to run Linux on this system at this time.

+

+

The architecturally very similar '''Indigo<sup>2</sup> R10000''' is based on the IP28 system board and has a MIPS [[R10000]] processor. Basic support for this system has been added to Linux 2.6.25. You will need a special gcc feature, which isn't merged with upstream yet. Patches for [[GCC]] can be found at http://www.pfrst.de/download.html

== Memory ==

== Memory ==

−

IP22 boards have two memory banks; each bank consists of 4 memory modules and if populated must be fully populated with fast page mode 36-bit wide PS/2 style memory modules from 4MB to 32MB size. Memory configurations between 16MB and 256MB are supported.

+

'''Indy''' IP24 boards have two memory banks; each bank consists of 4 memory modules and if populated must be fully populated with FPM (fast page mode) 36-bit wide, 60 or 70 ns, PS/2 style [[Wikipedia:SIMM|SIMM]] memory modules from 4MB to 32MB size. Memory configurations between 16MB and 256MB are supported.

−

The board in the Indigo 2 is similar but has third memory bank, therefore its maximum memory configuration is 384MB.

+

The memory in the '''Indigo<sup>2</sup>''' (IP22) is similar but board has three memory bank, therefore its maximum memory configuration is 384MB.

−

IP26 and IP28 boards also have 3 memory banks each 4 modules but support 64MB memory modules also increasing the maximum memory capacity to 768MB.

The Indy comes with the entry level XL ([[Newport]]) graphics which exists in 8-bit and 24-bit variants, and is basically a 2D card. There is also the XZ ([[Express]]) which is a 3D card with geometry processing and Z-buffering, and 24-bit color depth (and is unsupported under Linux). The Indigo 2 systems can use both of these options as well, however there is another one. The [[IMPACT]] is the best 3D graphics board available for these machines (and is also unsupported under Linux, although large parts of code might be shared with the [[Octane]] driver). Finally the Challenge S which is a headless compact server system (based on the Indy motherboard).

+

The '''Indy''' comes with the entry level [[Wikipedia:GIO|GIO32-bis]] XL ([[Newport]]) graphics which exists in 8-bit and 24-bit variants, and is basically a 2D card. There is also the XZ ([[Express]]) which is a 3D card with geometry processing and Z-buffering, and 24-bit color depth (and is unsupported under Linux).

+

+

The '''Indigo<sup>2</sup>''' systems can use both of these options as well ([[Wikipedia:GIO|GIO64]] version), however there is another one. The [[IMPACT]] is the best 3D graphics board available for these machines (and is also unsupported under Linux, although large parts of code might be shared with the [[Octane]] driver). An IMPACT-ready Indigo<sup>2</sup> must have an IMPACT-ready riser card and IMPACT-ready power supply.

+

+

Finally the '''Challenge S''' (based on the Indy motherboard) and '''Challenge M''' which are a headless compact server systems.

== Storage Options ==

== Storage Options ==

−

Challenge S, Indy, Indigo 2 and Indigo 2 R10000 are all equipped with an on-board WD33C93 SCSI controller. In addition to that the Challenge S has a second SCSI hostadapter supporting fast and wide SCSI, the WD33C95. Linux supports the WD33C93 but not the WD33C95.

+

Challenge S, Indy, Indigo<sup>2</sup> and Indigo<sup>2</sup> R10000 are all equipped with an on-board WD33C93B SCSI controller. Indigo<sup>2</sup> has two WD33C93B chips onboard, while Indy has only one. In addition to that the Challenge S has a second SCSI hostadapter IOPLUS, supporting fast and wide SCSI, the WD33C95A. Linux supports the WD33C93 but not the WD33C95A.

== Networking Options ==

== Networking Options ==

−

All IP22 systems come with an onboard Seeq 8003 network controller. The Challenge S being a server system comes with a second 8003. Note that the Seeq&nbsp;8003 offers less functionality than the Seeq&nbsp;80c03.

+

All IP22 systems come with an onboard Seeq&nbsp;8003 network controller. The Challenge S being a server system comes with a second 8003. Note that the Seeq&nbsp;8003 offers less functionality than the Seeq&nbsp;80c03.

== Video Input ==

== Video Input ==

−

Indy is equipped with video input unit based on [[VINO]] ASIC. Continuous capture is unsupported by Linux and a driver exists only for 2.4 kernel.

+

Indy is equipped with video input unit based on [[VINO]] ASIC.

+

A driver exists for both 2.4 and 2.6 kernels.

+

The driver for 2.4 is included in the kernel source, it has Video4Linux1-interface and it doesn't support continuous capture.

+

+

The new driver for 2.6 kernels has Video4Linux2-interface and it provides more functionality - almost every detail of the hardware is now supported. The driver can also be found from linux-mips.org kernel source (GIT).

Silicon Graphics, Inc. generously granted permission to distribute hardware documentation for the Indy. All files are as provided by Silicon Graphics except the ''virtual dma'' specification of which no electronic copy could be found, so it has been re-created.

+

Silicon Graphics, Inc. generously granted permission to distribute hardware documentation for the Indy. The postscript files in ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ are as provided by Silicon Graphics except the ''virtual dma'' specification of which no electronic copy could be found, so it has been re-created. The PDF files linked below were converted from the postscript files.

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/dmux1.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/dmux1.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/gio64.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/gio64.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/hpc3.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/hpc3.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ioc.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ioc.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/mc.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/mc.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/rb2.ps

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/rex3.ps

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ro1.ps

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/mc2.ps

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vdma.pdf

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vdma.pdf

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vdma.ps

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vdma.ps

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/xmap9.ps

+

+

Video:

+

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/rb2.pdf

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/rex3.pdf

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ro1.pdf

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/xmap9.pdf

The documentation for Vino is available in form of several postscript files, the bus timing diagrams being in separate files:

The documentation for Vino is available in form of several postscript files, the bus timing diagrams being in separate files:

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.01

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.01.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.02

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.02.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.03

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.03.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.04

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.04.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.05

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.05.pdf

−

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.ps.06

+

* ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/vino/vino.06.pdf

== IP22 has forgotten its ethernet address ==

== IP22 has forgotten its ethernet address ==

−

IP22 uses the Dallas DS1286 RTC chip to store time and firmware variables. This chip contains a builtin battery for ten years but by now this decade is almost over and experience has shown that some of these RTC batteries have a much shorter battery life, so the RTCs start becoming forgetful. Software may also accidentally have overwritten the RTC's content.

+

IP22 uses the Dallas DS1386-8K RTC chip to store time and firmware variables. This chip contains a builtin battery specified to have a 10 year lifetime but experience has shown that some of these RTC batteries have a much shorter battery life. So in practice by now two battery lifespans are over and RTCs start becoming forgetful. Software may also accidentally have overwritten the RTC's content.

−

If you have determined that a defective RTC chip is the cause of the problem you can get a new RTC from http://www.maxim-ic.com/ or other sources. Be paranoid, make sure you don't get a part that has been sitting on a shelf for long years. It is possible that this chip is no longer mass-manufactured, too.

+

If you have determined that a defective RTC chip is the cause of the problem you can get a new RTC from http://www.maxim-ic.com/ or other sources. Be paranoid, make sure you don't get a part that has been sitting on a shelf for long years. It is possible that this chip is no longer mass-manufactured, too.

−

This is how to reprogram the RTC chip. Assuming your ethernet address is aa:bb:cc:dd:ee:ff

+

This is how to reprogram the RTC chip. Assuming your ethernet address is aa:bb:cc:dd:ee:ff

fill -w -v 0xaa 0xbfbe04e8

fill -w -v 0xaa 0xbfbe04e8

Line 82:

Line 99:

Note this will print each byte of the MAC address repeated four times; this is normal an due to the way the chip is used in the Indy.

Note this will print each byte of the MAC address repeated four times; this is normal an due to the way the chip is used in the Indy.

−

The MAC address is also the system's serial number, so software licenses under IRIX might be bound to it. Also the ethernet standards specify certain meanings for certain values of the 48-bit address. Therefore you should reprogramm the old ethernet address. You may find the MAC address on the sticker on the machine. Below a bar code this sticker only contains a 12 digit hexadecimal number; it's typically located on the backside between the parallel port and and SCSI connectors on the left side and the power supply on the right side. In case this sticker has been lost, you probably also have the number somewhere in the bootmessages of Linux archived by syslogd or maybe a bootpd or dhcpd config file.

+

The MAC address is also the system's serial number, so software licenses under IRIX might be bound to it. Also the ethernet standards specify certain meanings for certain values of the 48-bit address. Therefore you should reprogramm the old ethernet address. You may find the MAC address on the sticker on the machine. Below a bar code this sticker only contains a 12 digit hexadecimal number; it's typically located on the backside between the parallel port and and SCSI connectors on the left side and the power supply on the right side. In case this sticker has been lost, you probably also have the number somewhere in the bootmessages of Linux archived by syslogd or maybe a bootpd or dhcpd config file, or in <tt>/etc/udev/rules.d/70-persistent-net.rules</tt>.

If you need to reprogram the ethernet address you will almost certainly have lost all other NVRAM settings, use the PROM shell's setenv -p command for that.

If you need to reprogram the ethernet address you will almost certainly have lost all other NVRAM settings, use the PROM shell's setenv -p command for that.

Revision as of 23:12, 30 January 2013

An SGI Indy system running Linux/MIPS

IP22 is Silicon Graphic's software architecture name for the hardware sold as Indy, Indigo2, POWER Indigo2, Indigo2 R10000, Challenge S and Challenge M. Modulo peripherals these systems are all very similar. Various Linux distributions will easily install on IP22, among them the Debian MIPS port.

Indigo2 and Challenge M (IP22) systems have only been made with R4000SC and R4400SC processor modules.

The POWER Indigo2 is based on the IP26 system board and comes with the R8000 processor. The R8000 is in many ways a unique MIPS processor and currently only partially supported by Linux. As such, it is not possible to run Linux on this system at this time.

The architecturally very similar Indigo2 R10000 is based on the IP28 system board and has a MIPS R10000 processor. Basic support for this system has been added to Linux 2.6.25. You will need a special gcc feature, which isn't merged with upstream yet. Patches for GCC can be found at http://www.pfrst.de/download.html

Memory

Indy IP24 boards have two memory banks; each bank consists of 4 memory modules and if populated must be fully populated with FPM (fast page mode) 36-bit wide, 60 or 70 ns, PS/2 style SIMM memory modules from 4MB to 32MB size. Memory configurations between 16MB and 256MB are supported.

The memory in the Indigo2 (IP22) is similar but board has three memory bank, therefore its maximum memory configuration is 384MB.

Graphics Options

The Indy comes with the entry level GIO32-bis XL (Newport) graphics which exists in 8-bit and 24-bit variants, and is basically a 2D card. There is also the XZ (Express) which is a 3D card with geometry processing and Z-buffering, and 24-bit color depth (and is unsupported under Linux).

The Indigo2 systems can use both of these options as well (GIO64 version), however there is another one. The IMPACT is the best 3D graphics board available for these machines (and is also unsupported under Linux, although large parts of code might be shared with the Octane driver). An IMPACT-ready Indigo2 must have an IMPACT-ready riser card and IMPACT-ready power supply.

Finally the Challenge S (based on the Indy motherboard) and Challenge M which are a headless compact server systems.

Storage Options

Challenge S, Indy, Indigo2 and Indigo2 R10000 are all equipped with an on-board WD33C93B SCSI controller. Indigo2 has two WD33C93B chips onboard, while Indy has only one. In addition to that the Challenge S has a second SCSI hostadapter IOPLUS, supporting fast and wide SCSI, the WD33C95A. Linux supports the WD33C93 but not the WD33C95A.

Networking Options

All IP22 systems come with an onboard Seeq 8003 network controller. The Challenge S being a server system comes with a second 8003. Note that the Seeq 8003 offers less functionality than the Seeq 80c03.

Video Input

Indy is equipped with video input unit based on VINO ASIC.
A driver exists for both 2.4 and 2.6 kernels.
The driver for 2.4 is included in the kernel source, it has Video4Linux1-interface and it doesn't support continuous capture.

The new driver for 2.6 kernels has Video4Linux2-interface and it provides more functionality - almost every detail of the hardware is now supported. The driver can also be found from linux-mips.org kernel source (GIT).

Firmware

Hardware Documentation

Silicon Graphics, Inc. generously granted permission to distribute hardware documentation for the Indy. The postscript files in ftp://ftp.linux-mips.org/pub/linux/mips/doc/indy/ are as provided by Silicon Graphics except the virtual dma specification of which no electronic copy could be found, so it has been re-created. The PDF files linked below were converted from the postscript files.

IP22 has forgotten its ethernet address

IP22 uses the Dallas DS1386-8K RTC chip to store time and firmware variables. This chip contains a builtin battery specified to have a 10 year lifetime but experience has shown that some of these RTC batteries have a much shorter battery life. So in practice by now two battery lifespans are over and RTCs start becoming forgetful. Software may also accidentally have overwritten the RTC's content.

If you have determined that a defective RTC chip is the cause of the problem you can get a new RTC from http://www.maxim-ic.com/ or other sources. Be paranoid, make sure you don't get a part that has been sitting on a shelf for long years. It is possible that this chip is no longer mass-manufactured, too.

This is how to reprogram the RTC chip. Assuming your ethernet address is aa:bb:cc:dd:ee:ff

Note this will print each byte of the MAC address repeated four times; this is normal an due to the way the chip is used in the Indy.

The MAC address is also the system's serial number, so software licenses under IRIX might be bound to it. Also the ethernet standards specify certain meanings for certain values of the 48-bit address. Therefore you should reprogramm the old ethernet address. You may find the MAC address on the sticker on the machine. Below a bar code this sticker only contains a 12 digit hexadecimal number; it's typically located on the backside between the parallel port and and SCSI connectors on the left side and the power supply on the right side. In case this sticker has been lost, you probably also have the number somewhere in the bootmessages of Linux archived by syslogd or maybe a bootpd or dhcpd config file, or in /etc/udev/rules.d/70-persistent-net.rules.

If you need to reprogram the ethernet address you will almost certainly have lost all other NVRAM settings, use the PROM shell's setenv -p command for that.