The collected works of Voralyan - Page 1

Quote:
Aeon


:) My Indy also has this name, but inspired by http://www.aeonthegame.de/

Quote:
Fafner


There is a big VAX 7000/820 in Germany with this name, impressive machine :o
http://fafner.dyndns.org/

Ok, the other machines floating around here:

The "Scifi-inspired" group:

Octane #1: trinity, from the "Matrix" character
Octane #2: lexa, from Lexa Doig
VW320 : 7o9, from the StarTrek Voyager character obviously ;)
Apple ibook: andromeda from the ship in "Gene Roddenberrys Andromeda"
IBM Thinkpad 760EL: neo, "Matrix" again

The "MYST" group:

Origin200 4CPU: isyeer, from the D'ni word for 'revere'
Origin200 2CPU: bilaris, an age in the Myst series
Lantronix print server: riven, another age
AMD Athlon PC: shimar, yet another age
AMD Geode PC: atinor, D'ni word most likely for 'source'
Compaq Notebook: lakiahn, an age

The "machine name = host name" group (which was my original naming scheme):

DEC Vaxstation 3100: VAX3100
DEC Vaxstation 4000/60: VAX4000
Apple Mac LC: MAC

The "other name" group:

Indigo2 : proxima
IBM Intellistation R: fhui
Intel PII server: bathor
Early i386 PC (DTK): trevor
Cisco 2514 router: spider
Cisco WRT54G: vl_prime
Brocade 2800: nova

Yet unnamed machines:

Sony PSP
Apple Newton MessagePad 130

So, thats all. Hope i didn't forget anything...

_________________
:O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
shadowless wrote: Adaptor for 13w3 to hd15 for a non-sog monitor is complicated.


But not too complicated ;)
I've modified Sun 13W3 Cables 3 times now for separate H/V Sync now. All you need is a sharp and stable
xacto knife, a wire cutter and a soldering iron. Not to mention the readiness for some sensibly used violence :)
You have to cut away all the molded plastic so you can reach the pins. If I remember correctly you only need
to deal with the upper row. Then you have to cut the two H and V sync wires and re-route them to the correct
pins. Most times you need some wirewarp wire to extend the H/V-wires. If you are done you wrap the inner
plastic mold core with a thin layer of insulating tape.
The hardest part is to a DSUB-shell which will take the mold core. Industrial or MIL Spec shells are
often of the right size, but not exactly cheap...

If anyone have a working wiring circuit please let me know. I tried the few pins options mentioned in other threads on the forum but no luck so far in make one that work between a Octane and 1600sw.


The "Hardware Developer Handbook" has the pinouts, but they should also be in the techpubs.
But I can post a wiring diagram if you wish... but it will be not before the beginning of the next week...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Some more cards:

Sorry for the picture quality, have to make new ones...

[edit (03.01.2012): Just saw that the pictures are still absent, will search for the files...]
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
As long as your display resolution is higher than the
native PAL or NTSC resolution there is no known way
to yield fullscreen output on the display. To get this,
an upscaler of some sort would be required to blow
the "video in" data up... and it doesn't seem that
there is something like that in the IRIX tools.
You will have to make your own :roll:

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
And another one, "proxima", the Indigo2:

hinv:

Code: Select all

thoweh@proxima $>hinv -v
CPU: MIPS R4400 Processor Chip Revision: 6.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 200 MHZ IP22 Processor
Main memory size: 384 Mbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Instruction cache size: 16 Kbytes
Data cache size: 16 Kbytes
Integral SCSI controller 0: Version WD33C93B, revision D
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version WD33C93B, revision D
On-board serial ports: 2
On-board bi-directional parallel port
Graphics board: GU1-Extreme
Integral Ethernet: ec0, version 1
Iris Audio Processor: version A2 revision 1.1.0
EISA bus: adapter 0



gfxinfo:

Code: Select all

thoweh@proxima $>/usr/gfx/gfxinfo
Graphics board 0 is "GR2" graphics.
Managed (":0.0") 1280x1024
8 GEs, 2 REs, 24 bitplanes, 4 auxplanes, 4 cidplanes, Z-buffer
GR2 revision 6, VB2.0
HQ2.1 rev A, GE7 rev B,  RE3.1 rev A, VC1 rev B, MC rev C
unknown, assuming 19" monitor


Other hardware:
- SGI granite keyboard & mouse
- Eizo FlexScan L567 (I'm an Eizo fan...) via the self made cable
- 3com fast ethernet card in EISA slot (Phobos E100 drives)

Planned upgrades:
None.
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Nice machine!

If you can find a GigaChannel it should be possible to add a graphics
head (SE+Tex max.) to it.
Tried that with my twin O200 but it didn't worked with the 180Mhz R10k :(
But it's the loudest machine in the house... :twisted:
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Yesterday I finally had some spare time to play with my Altix 350 (had to move to a new
location in August with all that stuff... Everthing went well, besides some new minor scratches
in skins (SGIs and mine, of course :roll: )

However, I tried to install the current debian distribution. Doing this I discovered that the PROM
version is too old to support newer kernels. The kernel tries to boot and after loading the initrd
I find myself at the POD mode prompt...

The situation is very much like the one described here:
http://forums.nekochan.net/viewtopic.php?f=3&t=16718710

At the moment I've PROM version 4.04, dated something/2004 (pretty old...)
Seems that this is the version which comes with ProPack 4.
So updating to the one from ProPack 5 will cure the problem (I hope so...)

To no surprise the links mentioned in the thread are dead.

Is there somebody who can help me out? ;)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
I'm just scanning Supportfolio and found:
"Linux Patch 10550: Recommended update for snprom in SGI ProPack 5"

Maybe it's in there. But access is for full account members only... :(

edit: "Linux Patch 10385: SGI ProPack 5 Service Pack 1 Release" and
Linux Patch 10548 : PROM 5.04/1.54 Update for SGI PP3SP6,PP4SP2,PP4SP3,SLES9SP3,SLES10,RHEL4,RHEL5 seem
to be interesting too...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
SAQ wrote: Support is in the kernel, but it's likely that not all distributions have it in the default boot.
SuSE and RedHat are the SGI supported distros, but rumor has it that CentOS will work if you have the correct console set.


Debian also supports it when you set the right console device.

But there is a dependence between the PROM and the kernel version you can run. For newer kernels (> 2.6.17 for what
I've found) you need a at least the PROM update from ProPack5 flashed in.

My machine has currently 4.04 and runs SLES9 which is kernel 2.6.5
Of course I would like somethink newer but don't have the PROM update available... :roll:

At least I just got the SLES media so I can install a compiler (and other things) now.
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
aperezbios wrote: I'm having the same problems, albeit years later, and the links above are dead. SLES10 CD1 boots but hangs at "freeing kernel memory" even when I supply console=ttySG0

Help!


I already wrote to toxygen concerning the PROM files. He doesn't have them at hand but he will look for them as soon as time allows...
The files are on Supportfolio, but only downloadable with full access. One chance will be that somebody with full access downloads them
for us or I succeed to find them elsewhere...
I let you know when I something turns up.

btw, have you tried SLES9 ?
After free registration the CD images are downloadable from the Novell website.
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Some more observations (may have nothing to do with the firmware):

Upon every reboot I get very different bogomips readouts from dmesg.
One or two CPUs often have a very low value while the others have
around 2000... I know its named bogomips because its just that, so maybe
it has nothing to say. Which CPUs have a high and which have a low
readout is always different after every reboot. This time it is

Code: Select all

CPU 0: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
Console: colour dummy device 80x25
Memory: 3879872k/3935760k available (5833k code, 66208k reserved, 2242k data, 400k init)
McKinley Errata 9 workaround not needed; disabling it
Calibrating delay loop... 2077.40 BogoMIPS
Security Scaffold v1.0.0 initialized
SELinux:  Disabled at boot.
Dentry cache hash table entries: 524288 (order: 8, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 7, 2097152 bytes)
Mount-cache hash table entries: 1024 (order: 0, 16384 bytes)
Boot processor id 0x0/0x0
task migration cache decay timeout: 10 msecs.
CPU 1: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
Calibrating delay loop... 2094.88 BogoMIPS
CPU 2: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
Calibrating delay loop... 2094.88 BogoMIPS
CPU 3: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
Calibrating delay loop... 16.44 BogoMIPS
Brought up 4 CPUs
Total of 4 processors activated (6282.60 BogoMIPS).


Other phenomenon observed:

I plugged a Qlogic QLA 2202 dual 1Gbit FC HBA in the 2nd PCI bus (the one that is not shared with the IO9).
In fact this card is two QLA2200 one one card together with a PCI-PCI bridge.

On bootup I see nothing concerning this HBA...
lspci shows:

Code: Select all

0000:01:01.0 Co-processor: Silicon Graphics, Inc. IOC4 I/O controller (rev 4f)
0000:01:03.0 SCSI storage controller: QLogic Corp. ISP12160 Dual Channel Ultra3 SCSI Processor (rev 06)
0000:01:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)
0000:02:01.0 PCI bridge: Intel Corp. 21154 PCI-to-PCI Bridge
0000:11:01.0 Co-processor: Silicon Graphics, Inc. IOC4 I/O controller (rev 4f)
0000:11:03.0 SCSI storage controller: QLogic Corp. ISP12160 Dual Channel Ultra3 SCSI Processor (rev 06)
0000:11:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)


So it seems that only the PCI bridge

Code: Select all

0000:02:01.0 PCI bridge: Intel Corp. 21154 PCI-to-PCI Bridge

is visible to the OS.
To me it looks like the same situation I know from the Origin family: PCI-PCI bridges are not supported behind the
XIO-PCI-bridge (Ok, in IRIX you can enable "experimental" support in the kernel). Or is it something different here?
Most likely I'll exchange the card for two QLA2200's or two QLA2340's (depending on what I can find in my spare part
boxes)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Thanks to files send to me by guruace I was able to flash the PROM to a more recent version.
A detailed report on this will follow as soon as I managed to write everything together (next 2
days I hope.)

Debian install is just running in this very moment, but I made backups of the SLES inst so it can
be reactivated. debian will be the "production" distro simply because it fits more for my needs and
the jobs the machine should do in future. Its used in a pure private environment so I don't have to
rely on professional support etc...

I'll write some comments on installing debian in another thread when everything is up and running...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Ok, recipe for Altix 350 PROM update (as I did it):

You need:

- PROM image to be flashed (shub1snprom.bin for newer vesions x.xx-snprom.bin for older)
- HDD with FAT filesystem on it (I used a partitioned ZIP100 for this)
- most likely a well sorted box of SCSI adapters and cables

Copy the PROM image to the FAT file system on the disk. I tried CD-Rs with a FAT fs on it, but to no success (I must admit
that I don't put too much effort in this because the method with the ZIP seemed to be easier). Be sure that the file is correctly
written to the disc.

btw: Its always a good idea to check if the SCSI path is working flawlessly, especially when a lot of fancy cables and/or adapters
are used. I bricked a CD-burner once this way...

Attach the disk to the Altix and let it boot to the EFI menu. Select the "EFI shell" menu item.
If everything is well your FAT filesystem should be accessible as fs n :/
For me it is fs4:/
Then you should be able to:

Code: Select all

EFI Shell version 1.02 [12.38]
ValidMBR: LastBlock 196575 < MIN_MBR_DEVICE_SIZE 524288
Device mapping table
fs0  : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part1,Sigg1)
fs1  : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part1,Sigg2)
fs2  : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part2,Sigg3)
fs3  : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part3,Sigg4)
fs4  : Pci(1|2)/Scsi(Pun0,Lun5)/HD(Part1,Sig00000000)
blk0 : Pci(1|1)/Scsi(Pun0,Lun1)
blk1 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part1,Sigg1)
blk2 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part2,Sigg5)
blk3 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part3,Sigg6)
blk4 : Pci(1|1)/Scsi(Pun0,Lun2)
blk5 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part1,Sigg2)
blk6 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part2,Sigg3)
blk7 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part3,Sigg4)
blk8 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part4,Sigg7)
blk9 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part5,Sigg8)
blkA : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part6,Sigg9)
blkB : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part7,Sigg10)
blkC : Pci(1|2)/Scsi(Pun0,Lun5)
blkD : Pci(1|2)/Scsi(Pun0,Lun5)/HD(Part1,Sig00000000)
Shell> fs4:
fs4:\> ls
Directory of fs4:\
08/20/08  01:37a            6,291,456  shub1snprom.bin
08/20/08  01:32a            6,291,456  4.07-snprom.bin

2 Files   12,582,912 bytes
0 Dir              0 bytes

fs4:\> flash -a shub1snprom.bin
SGI PROM Flashing Utility
Flashing all nodes
Start flashing?  Press 'y' to begin, any other key to abort: Flashing node 0
...erasing sectors
................................................................................................Done.
...copying prom
source address     : 0x000000b079b7d008
destination address: 0x8000000fffa00000
size (bytes)       : 0x0000000000600000
...programming
................................................................................................Flash of node 0 complete.
Waiting for all flash operations to complete...DONE.
Flashing node 2
...erasing sectors
................................................................................................Done.
...copying prom
source address     : 0x000000b079b7d008
destination address: 0x8000008fffa00000
size (bytes)       : 0x0000000000600000
...programming
................................................................................................Flash of node 2 complete.
Waiting for all flash operations to complete...DONE.
Done flashing.


Ok, flash was successfull. The next step is important: Go to POD mode and clear all logs...
Beware: All PROM variables and EFI settings are lost after this...

Code: Select all

fs4:\> pod
POD entered via EFI command, using Cac mode
0 000: POD SysCt (RT) Cac> initalllogs
*** This must be run only after NUMAlink discovery is complete.
*** This will clear all previous log variables such as:
*** moduleids, nodeids, etc. for all nodes.
Clear all logs environment variables, and aliases ? [n] y
Clearing nasid 0...
Clearing nasid 2...
Clearing nasid 0 EFI variables...Clearing nasid 2 EFI variables................................
Clearing nasid 0 error log........
Clearing nasid 2 error log.............
....
All PROM logs cleared!
0 000: POD SysCt (RT) Cac>


Now you can

Code: Select all

0 000: POD SysCt (RT) Cac> reset


and the system should come up fine with the new PROM.

Before the flash I had

Code: Select all

001c01#0c: SGI SAL Version 4.04 reorg041203 IP41 built 03:13:26 PM Dec  3, 2004


now I am at

Code: Select all

001c01#0c: SGI SAL Version 4.87 rel070913 IP41 built 06:02:37 AM Sep 13, 2007


This version boots all newer kernels without problems (up to 2.6.30, for what I've tested).
It should be mentioned that it therefore cannot boot that older kernels anymore (e.g. the one which is shipped with the original SLES9 release)
So you have to choose what you want... ;)
But it should be possible to downgrade if one wishes to run SLES9 once again (I've 4.07-snprom.bin for this.)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Some notes for installing debian IA64 on the Altix 350:

1. Forget to do the install with the 6.X.X CD/DVD's. The major problem is that it doesn't contain the firmware for
the QLA12160 anymore so you won't be able to write to any HDDs. The installer detects the QLA correctly and comes
up with a dialog to load the missing firmware from "removable media". Of course "removable media" contains "USB sticks" and
"floppies" as quoted by the installer. And it means exactly that: No optical media here. Sorry... :roll:

Out of curiosity I plugged a PCI USB card in the first node, second PCI bus of the machine. It had a VIA chipset. So no high
expectations here. Of course it didn't work at all. No surprise I thought...

I wasn't in the mood to fumble the firmware files into the inst media, so I tried the 5.0.8 "lenny" media set.

To do a basic install you need the first CD of the full CD set. The "netinst" CD won't work (YMMV).
It can be booted as is, no need to specify a special console device.

Running the debian installer it fails to detect the CD-ROM after configuring your keyboard layout. That is because it
doesn't load the "sgiioc4" module by default. So select "Go back" in the current installer window and select "Run a shell" in
the appearing menu. At the shell do "modprobe sgiioc4" and it loads the module and all the depending modules. You should see
that the CD-ROM is detected. Exit the shell. Now you can continue the install as usual.

After the system is installed and booted you should add "sgiioc4" to "/etc/modules".

As long as you are at the serial console be sure to do editing work in an editor that doesn't rely on "CTRL+..." keystrokes
as some of these are caught up by the L1 what can be very disturbing.

When you are about to upgrade to 6.X.X after the successful install be aware that the firmware issue arises again when
you install the new kernel. To stay on the safe side you can only upgrade the userland and stay with the old kernel.
I'm currently happy with lenny and will do the upgrade when I'm in a adventurous mood :roll:

As I said YMMV with the install ( it seems the it comes with integrated witty mood by default)...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
aperezbios wrote: I too was successful in getting my firmware updated from the broken/buggy original version to 4.07, at which point I can now successfully boot something other than SLES9. Can you please let me know how you managed to get Debian installed?


See: http://forums.nekochan.net/viewtopic.php?f=3&t=16718710&p=7342876#p7342876

You will need something even newer than 4.07 to boot the kernel...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
jan-jaap wrote: What if you dist-upgrade to the current stable release from the running system rather than the CD-ROM?
Just make sure you install the QLogic firmware package before you reboot into the new system.


Should work I think. I will try it tomorrow...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Had some spare time this evening and upgraded to squeeze without major problems.
Now I have:

Code: Select all

fireball:~# uname -a
Linux fireball 2.6.32-5-mckinley #1 SMP Fri Sep 9 22:48:44 UTC 2011 ia64 GNU/Linux


:D

P.S. to me this is more a software topic, so maybe the thread should be moved to a better suited category?!
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Hi,

I'm fumbling around with this for days now but I don't get anything usable...
I've some anamorphic MPEG2 PAL videos here (SAR 4:3, 720x576; DAR 16:9, mplayer says 1048x576)
which I like to convert to 4:3 letterboxed in either DV or MJPEG or PhotoJPEG to play it on "video
out" of the O2. The least would be best since it can be played with dmplay from the CLI
(I usually don't have a graphics head on the machine).

The conversion to DV worked perfectly with ffmpeg but I just get something squeezed in ugly
ways...

Maybe there is somebody which is more fluent with ffmpeg/mencoder/transcode than I am..?

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Played around with ffmpeg a lot the last days and got something
that basically works. I used neko_ffmpeg-SVN-r6775 on my O2k
for this:

Code:
ffmpeg -y -threads 4 -i somefile.mpg -target pal-dv -s 720x576 -aspect 4:3 outfile.dv -padtop 86 -padbottom 86


Input file has a 1024x576 DAR.

It produced a file that plays perfectly via the Video Out on my O2. Seems that hardware decompression is used
during playback.
The quality of the DV file is not optimal, it's rather blocky. I'm about to do some tuning to achieve better results.
A shell script to automate things is also about to be written...

Next step is to produce a file with Quicktime Container and PhotoJPEG compression which can be played back
via dmplay.

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
For DVDs without CSS encryption mplayer should do the job just fine...
Even the most basic Fuel should have enough power do play DVDs
without any hickups.
AFAIK there is no way for DVDs with CSS at the moment...

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
I'm curious how this turns out...
Are you planning to use a raised floor in the room? It's the first thing I'll do when
I get a computer room... All the cables lying on the floor building up dust traps
everywhere are a real pain. Not to speak of the bad aesthetics it gives...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
madmax wrote: It seems that the 3 barebones units have the same serial, while the unit with the IO9 has a different system serial and consequently they won't link up.


In theory it should be possible to get the serial numbers matched. But I haven't done it yet since my two bricks came with matching serial numbers.
First step is to get the PROM firmware up to date and matched on all bricks; maybe the serial number issue will go away. But that's a bit too optimistic I think. Anyway it's more than suboptimal to run a numalinked system with different firmware on the bricks.
I wrote detailed instructions flashing the PROM some time ago, you can find it here:
http://forums.nekochan.net/viewtopic.php?t=16725651#p7342874

Is there anything i can do, or will i have to move the cards, risers and disks from that unit to one of the others and operate the altix with just 3 nodes?


It may be annoying, but for flashing you'll have to move the IO9 card to the brick which has to be flashed. With your setup I would do the following procedure:
- First, flash the single brick with the IO9 card to the most recent PROM.
- Then, install the card in one of the three bricks with matching serial numbers, numalink all together and flash the remaining bricks.

If you have really old firmware chances are good that the L1 firmware is also old. I think it will be a good idea to also flash the L1 to a more recent one. That's possible from the L2 emulator. I'll have to do it on my bricks since on shutdown the OS complains about not being able to communicate with the L1 for storing the current time and date... but unfortunately I'didnt have the time for setting up the L2 emulator until now. The last days I began setting up the L2 the last days, so it's possible that I figure out how to do it in the next days (weeks?)...

[EDIT]
It would be nice to have more details on your hardware. Can you post PROM bootup messages from the differnt bricks?
L1 output is also interesting, especially from 'serial all'.
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Hi,

I just scanned through the Altix 350 manual (which should be similar enough to the 330)
and it says that ECC memory is required. Interesting enough, it is rather unspecific when it
comes to memory. But it says "Only use SGI approved DIMMs", which, as I think, should
compensate for this... :roll:

Short: If I interpreted the manual the right way, non-ECC is a no go... but if you have some
non-ECC bars lying around it's worth a try maybe...

(edit: typos)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Nice experiment. I was always interested myself in this unusual config and if it would work.
There was some speculation going on in the past in this forum if I remember correctly...
But until now nobody tried it...

The build-in PS/2 ports work at least in one release of IRIX, beginning with 6.5.15 if I
remember correctly. Later they seem to be disabled at default or support was broken in
a more unfriendly way. From my mind: They don't work in 6.5.22 anymore. But I've to look
up the details on this...

If you choose the CADDUO board you've one less source of worry and anger, thats for sure ;)

Anyway, I'm curios if all this results in a working IR graphics head, so please go on...!
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Nice :)
I will definitely try this if I ever get a Onyx 2 KCAR (this is what the IR "bricks" of the Onyx 2 were named
before they were actually bricks...?!).
I'm curious if it will work if the O200 has the older R10k PIMMs... I tried the Impact SE/SI setup and IRIX
complained about too old HUBs...

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Hi there,

like the OP I tried to compile Dillo3 almost a year ago, but with the same result: Build was OK, but problems with loading pages... I used gcc3 back then.

@vishnu: I tried it, and this is what I got:

Code: Select all

thoweh@species8472 $>uname -a
IRIX64 species8472 6.5 07202013 IP27
thoweh@species8472 $>c99 -version
MIPSpro Compilers: Version 7.4.4m
thoweh@species8472 $>ls
dillo-3.0.2      dillo-3.0.2.tar
thoweh@species8472 $>cd dillo-3.0.2
thoweh@species8472 $>ls
aclocal.m4         config.h.in        doc                d_size.h           Makefile.in
AUTHORS            config.sub         Doxyfile           INSTALL            missing
ChangeLog          COPYING            dpi                install-dpi-local  NEWS
configure          depcomp            dpid               install-sh         README
configure.in       dillorc            dpip               lout               src
config.guess       dlib               dw                 Makefile.am        test
thoweh@species8472 $>cd dw
thoweh@species8472 $>c99 -c -w findtext.cc -o findtext.o
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 14
An identifier is expected.

#define _MSG(...)
^

cc-1040 c99: ERROR File = ../lout/msg.h, Line = 15
An identifier is expected.

#define _MSG_WARN(...)
^

cc-1040 c99: ERROR File = ../lout/msg.h, Line = 16
An identifier is expected.

#define _MSG_ERR(...)
^

cc-1040 c99: ERROR File = ../lout/msg.h, Line = 19
An identifier is expected.

#define MSG(...)                                   \
^

cc-1040 c99: ERROR File = ../lout/msg.h, Line = 27
An identifier is expected.

#define MSG_WARN(...)                              \
^

cc-1040 c99: ERROR File = ../lout/msg.h, Line = 33
An identifier is expected.

#define MSG_ERR(...)                               \
^

cc-1055 c99: ERROR File = findtext.cc, Line = 231
A macro invocation has too many arguments.

_MSG("Having to do.");
^

7 errors detected in the compilation of "findtext.cc".
thoweh@species8472 $>


Not better what you got, I suppose :(

The compiler installation is OK I think, it was done by jan-jaap before I got the machine (O2k)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
First: A great, big T H A N K S ! for porting this to IRIX. :D
I waited a really long time for it.

I installed it on both Octanes, and it feels a lot faster than FF2.
Especially scrolling don'r locks up anymore while loading heavy pages,
an Javascript seems to be a lot more responsive...

However, I'm experiencing a strange problem: I can't reach some sites
from FF3, which load fine in FF2. If I type in an address in the address field
and press return, following happens with these addresses:

- FF seems to resolve the hostname successfully
- Begins loading the page from the server:
- Throbber begins to rotate
- Progress bar shows up
- Loading action stops after less than one seconds, status says: Done.
- Result: empty, white page.

Hitting reload button changes nothing. It's the same when trying to access the page from bookmarks,
passing URL as a command line argument and everything else.

These are the pages are affected by this:

http://www.google.com (also other TLDs)
http://www.bing.com
http://www.mozilla.org

and probably others.

But most pages load as intended. So no problems with

http://www.sgi.com
http://www.apple.com
http://www.microsoft.com
http://www.ebay.de
http://www.airliners.net

and lots of others (the one mentioned above are the ones I tried...)

Installation is on 6.5.22 systems, with old nekoware installs on it (originally installed back
in 2008), only updated packes when required, never updated the nekoware install as a
whole. So maybe its a problem with old libraries...
Of course I installed the required dependencies when installing FF3, so these should be up-to-date.

Its maybe interesting that all my traffic is forced to pass a proxy server of the provider (UMTS connection),
which seems to modify some HTTP traffic in sometime unpredictable ways. I've no means to shut this off
currently, but it seems not affecting any other browsers (in case it's the source of the problems with FF3 on
IRIX).

Any ideas about this? So far, I was not to recognize a pattern behind this...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
archaic wrote:
And no, the DM6 doesn't work. The mlquery program shows that it is there but the video daemon refuses to start.


This is most likely what is expected... The DM6 is, as with other video devices from the DM series, an OpenML only device.
So it has no way to speak to the "classic" IRIX video infrastructure like the video daemon.
The DM2/DM3 is mostly used with the discreet software; you will need something similar for the DM6, I think...

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
View source: This is what I get:

Code: Select all

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title></title></head><body></body></html>


which is the source of "about:blank". It's also what the window caption of the source viewer says:
"Source of: about:blank".

Seems that nothing gets downloaded...
So time to install wireshark and dig a little bit deeper.
I wonder where the difference is between the working and non-working sites..?

If I remember correctly the 3.0.X MacOS X versions suffered from the same problem,
but maybe my mind is fooling me on this... But I could swear that I've encountered this
strange phenomena earlier with FF...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
diegel wrote: You can switch this off using about:config by setting network.dns.disableIPv6 to true.


That works. Many thanks! :)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
So, I finally got the time to begin setting these things up...
Since there seems not much about this kind of hardware
neither in the forums nor in the wiki I thought it might be
a good idea to write up the steps to get a working connection
between two machines.

OK, we have: O200 with Gigachannel and O2100, both running
IRIX 6.5.30,

these HIPPI cards, which I got from maxsleg (thanks again :) ):
[see pics]
These are two different versions of the cards, which have the
following obvious differences:

The first is the older version, it has LINC ASICs with yellow traces
on the chip carrier, "ORION" named "Integrated Circuits" chips,
single cooler on the chips below the optical transceiver.
Attachment:
DSC00656.JPG
DSC00656.JPG [ 877.62 KiB | Viewed 108 times ]


The newer version has: LINC2 ASICs with nearly invisible green traces,
no "ORION" print on the "Integrated Circuits" chips, split coolers on the
chips below the transceivers.
Attachment:
DSC00655.JPG
DSC00655.JPG [ 859.82 KiB | Viewed 108 times ]


Before installing the cards I updated the O200 to 6.5.30 and installed
the HIPPI drivers and software package on both machines. The manual of
the HIPPI software package explicitly states that you should do the software install
before installing the hardware, thats why I set in bold...

The software is not part of the regular distribution CDs, you have to download it from
Supportfolio. The file is named "6.5_hippi_4.0.1.tar".
Put the file into a separate directory, untar it and you have the usual IRIX SW dist files.

After installing the packages I shut down the machines and installed the hardware. Should be
straight forward, installing in an Octane requires the locking hardware to be exchanged.
After powering up and starting the OS it should autoreconfigure.

On the O200, which got the old rev card, I got the following:
Code:
The system is coming up.

Automatically reconfiguring the operating system.

Reboot to start using the reconfigured kernel.
Firmware is downrev, downloading new firmware...
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/1: erasing flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/1: programming flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/1: programming flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/1: erasing flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/1: programming flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/0: erasing flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/0: programming flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/0: programming flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/0: erasing flash EEPROM.
NOTICE: hippi0: /hw/module/1/slot/io3/hippi_serial/pci/0: programming flash EEPROM.
Firmware download complete, restarting adapter.


So firmware is automagically updated if the driver detects it being too old.

So this are the first impressions, more to come as I continue...

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Hi,

using the B-type USB port as a serial device will most likely not work, as they are intended to
connect a L2 controller. Besides that there is no support for USB-serial devices in IRIX.
The ttyus* devices are for raw byte access without system calls (see serial(7) ) to generic
RS232/422 ports.

As I see it you have two options:
1.) solder a DB9 connecter to the empty pads on the mainboard, or, probably easier,
2.) use the USB-B connector with an L2 controller (or the L2/L3 software) to access the L1
on the Fuel...

_________________
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Hi,

there is no need to decompress the tardist files. Think of it as a package
format (like *.deb files on debian).
So they can be installed directly by the software manager.
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Maybe I'm defective myself, but the following strange thing happens
(tried with OpenDOS 7.01, DR-DOS 7.03 and MSDOS 6.22 command.com)

Code: Select all

C:\>set foo=bar
C:\>set
[...]
FOO=bar
C:\>echo %foo%
%foo%
C:\>


What the :evil:

Shouldn't I get "bar" on echo %foo% ?
Tried that on two different machines, even with plain DOS boot disk.

[edit: corrected typo]
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
On "echo %foo%" the value should be printed in the
next line and not the variable designator...

I tried the aforementioned example on WinNT's cmd.exe
and I get correctly "bar" as the output on "echo %foo%"...
But not on any DOS system running on two absolutely
different machines!

Maybe I'm overlooking something astonishing simple or
it's just the wrong pressure in the water pipes today... who knows?!

[edit: DOS is not case sensitive]
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
It's right, works only in batch files.
Have been working with WinNT's too long I think...
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Anybody has a copy of this?
(Download location is mentioned here : http://forums.nekochan.net/viewtopic.php?f=7&t=7332
but the original download server does not response anymore. And google doesn't turn up a mirrored
version (at least on a working site)...

Greetings,
Voralyan
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
After some years it happened again... - New hardware.
I moved twice in the last years and at some point in time I swore
(while lifting the whole stuff up to the 5th floor (no elevator!), to
be exact) to never get more.
Well... I got an Origin 2400 rack. :lol:

Getting things ready for transport...

Image

Partly assembled after getting it up to the 4th floor this time
(No elevator again, next flat will definitively be at ground level or have an elevator)

Image

Bits and pieces waiting to be installed again

Image

Had to free up some space, my O2100 deskside sits in another corner of the room now.
The cabling needs to be changed, not a nice job as everything is wrapped in these spiral
PE sleeves. But surely it helps to get everything well organized...

Image


First tests, 3 nodeboards in the lower module showed bad RAM, one has occasional CPU
errors. I moved these boards in the deskside for the time being, needs to be examined later.
The four 400 MHz R12k boards from the O2100 are now in the upper module, the lower one has
three 250Mhz and one 300Mhz now.

Image

The MSC board in the upper module had a broken key switch. It was easily fixed with a drip
plastic glue...

Image

Current picture, I haven't decided if I install the "door" thingy again. I think about connecting
it to the deskside to get a 24 CPU system, but I have to find two NUMAlink >= 2 meters first

Image

I installed a SI Impact graphics card I had lying around, making the machine an Onyx2 SI/MXI

Image

hinv follows soon...

(Sorry for the crappy pictures)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Current config:

Boot output:

Code: Select all

$ CONSOLES/Origin2400_MMSC
Trying 192.168.1.27...
Connected to 192.168.1.27.
Escape character is '^]'.
MMSC> pwr u
R1U:ok
R1L:ok


IP27 PROM SGI Version 6.156  built 11:27:56 AM Nov 18, 2003
*** Diag level set to None (2)
Testing/Initializing memory ...............      DONE
Copying PROM code to memory ...............      DONE
Discovering local IO ......................      DONE
Discovering NUMAlink connectivity .........      DONE
Found 12 objects (8 hubs, 4 routers) in 15362 usec
Waiting for peers to complete discovery....      DONE
Recognized 390 MHz midplane
Global master is /hw/module/1/slot/n1
Testing/Initializing all memory ...........      DONE
waiting for node with nic 4d5d39 at module 3 slot 2 at global barrier.....
Checking partitioning information .........      DONE
Loading BASEIO prom .......................      DONE

BASEIO PROM Monitor SGI Version 6.156  built 11:26:28 AM Nov 18, 2003 (BE64)
16 CPUs on 8 nodes found.
Installing PROM Device drivers ............
Base I/O Ethernet set to /dev/ethernet/ef0

Walking SCSI Adapter 0 (/hw/module/1/slot/io1), (pci id 0)
1+ 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- = 1 device(s)


Walking SCSI Adapter 1 (/hw/module/1/slot/io1), (pci id 1)
1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- = 0 device(s)

Initializing PROM Device drivers ..........             DONE
Checking hardware inventory ...............              DONE

**** System Configuration and Diagnostics Summary ****
CONFIG:
No. of NODEs enabled    = 8
No. of NODEs disabled   = 0
No. of CPUs enabled     = 16
No. of CPUs disabled    = 0
Mem enabled             = 23040 MB
Mem disabled            = 0 MB
No. of RTRs enabled     = 4
No. of RTRs disabled    = 0

DIAG RESULTS:
NO DIAGS WERE RUN!
**** End System Configuration and Diagnostics Summary ****


System Maintenance Menu

1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor

Option? 1


Starting up the system...

IRIX Release 6.5 IP27 Version 07202013 System V - 64 Bit
Copyright 1987-2006 Silicon Graphics, Inc.
All Rights Reserved.

[...]


Code: Select all

hinv -mv
Location: /hw/module/1/slot/n1/node
MODULEID Board: barcode K0015528   part              rev
IP31 Board: barcode GCD995     part 030-1255-003 rev  B
IP31PIMM Board: barcode HJS680     part 030-1313-002 rev  A
8P12_MPLN Board: barcode GBY494     part 030-0762-006 rev  K
Location: /hw/module/1/slot/n2/node
IP31PIMM Board: barcode DLE906     part 030-1313-002 rev  A
IP31 Board: barcode GFD231     part 030-1255-003 rev  B
Location: /hw/module/1/slot/n3/node
IP31 Board: barcode JHH671     part 030-1255-004 rev  A
IP31PIMM8MB Board: barcode JGV418     part 030-1401-003 rev  A
Location: /hw/module/1/slot/n4/node
IP31 Board: barcode JGY884     part 030-1255-003 rev  D
IP31PIMM Board: barcode GFC040     part 030-1313-002 rev  A
Location: /hw/module/1/slot/r1/router
ROUTER_IR1 Board: barcode HMA614     part 030-0841-003 rev  B
Location: /hw/module/1/slot/r2/router
ROUTER_IR1 Board: barcode HMA650     part 030-0841-003 rev  B
Location: /hw/module/1/slot/io2/pci_xio
PCI_XIO Board: barcode GFS776     part 030-1062-002 rev  D
Location: /hw/module/1/slot/io2/pci_xio/pci/2
PCI_ENET Board: barcode JHX727     part 030-1155-002 rev  D
Location: /hw/module/1/slot/io7/hippi_serial
HIPPI_SERIAL Board: barcode JHV649     part 030-0968-004 rev  F
Location: /hw/module/1/slot/io1/baseio
BASEIO Board: barcode HJZ626     part 030-1124-002 rev  M
Location: /hw/module/3/slot/n1/node
MODULEID Board: barcode K0018076   part              rev
8P12_MPLN Board: barcode DFC471     part 030-0762-006 rev  K
IP31PIMMR12KS Board: barcode KRH959     part 030-1423-002 rev  G
IP31 Board: barcode KSB420     part 030-1523-001 rev  C
Location: /hw/module/3/slot/n2/node
IP31 Board: barcode KSB458     part 030-1523-001 rev  C
IP31PIMMR12KS Board: barcode KRH935     part 030-1423-002 rev  G
Location: /hw/module/3/slot/n3/node
IP31 Board: barcode KSB421     part 030-1523-001 rev  C
IP31PIMMR12KS Board: barcode KRH853     part 030-1423-002 rev  G
Location: /hw/module/3/slot/n4/node
IP31 Board: barcode KSB362     part 030-1523-001 rev  C
IP31PIMMR12KS Board: barcode KRH933     part 030-1423-002 rev  G
Location: /hw/module/3/slot/r1/router
ROUTER_IR1 Board: barcode HMA748     part 030-0841-003 rev  B
Location: /hw/module/3/slot/r2/router
ROUTER_IR1 Board: barcode HAM262     part 030-0841-003 rev  B
Location: /hw/module/3/slot/io7/mgras
GM10 Board: barcode FSK904     part 030-0938-003 rev  T
Location: /hw/module/3/slot/io1/baseio
BASEIO Board: barcode GND369     part 030-1124-002 rev  M
Processor 0: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 1: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 2: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 3: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 4: 300 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 2.5
FPU: MIPS R12010 Floating Point Chip Revision: 2.5
Processor 5: 300 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 2.5
FPU: MIPS R12010 Floating Point Chip Revision: 2.5
Processor 6: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 7: 250 MHZ IP27
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 3.4
Processor 8: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 9: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 10: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 11: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 12: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 13: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 14: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
Processor 15: 400 MHZ IP27
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 3.5
CPU 0 at Module 1/Slot 1/Slice A: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 1 at Module 1/Slot 1/Slice B: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 2 at Module 1/Slot 2/Slice A: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 3 at Module 1/Slot 2/Slice B: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 4 at Module 1/Slot 3/Slice A: 300 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 2.5. Scache: Size 8 MB Speed 200 Mhz  Tap 0xa
CPU 5 at Module 1/Slot 3/Slice B: 300 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 2.5. Scache: Size 8 MB Speed 200 Mhz  Tap 0xa
CPU 6 at Module 1/Slot 4/Slice A: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 7 at Module 1/Slot 4/Slice B: 250 Mhz MIPS R10000 Processor Chip (enabled)
Processor revision: 3.4. Scache: Size 4 MB Speed 250 Mhz  Tap 0x9
CPU 8 at Module 3/Slot 1/Slice A: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 9 at Module 3/Slot 1/Slice B: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 10 at Module 3/Slot 2/Slice A: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 11 at Module 3/Slot 2/Slice B: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 12 at Module 3/Slot 3/Slice A: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 13 at Module 3/Slot 3/Slice B: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 14 at Module 3/Slot 4/Slice A: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
CPU 15 at Module 3/Slot 4/Slice B: 400 Mhz MIPS R12000 Processor Chip (enabled)
Processor revision: 3.5. Scache: Size 8 MB Speed 266 Mhz  Tap 0xa
Main memory size: 23040 Mbytes
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 4 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Secondary unified instruction/data cache size: 8 Mbytes
Memory at Module 1/Slot 1: 2048 MB (enabled)
Bank 0 contains 256 MB (Standard) DIMMS (enabled)
Bank 1 contains 256 MB (Standard) DIMMS (enabled)
Bank 2 contains 256 MB (Standard) DIMMS (enabled)
Bank 3 contains 256 MB (Standard) DIMMS (enabled)
Bank 4 contains 256 MB (Standard) DIMMS (enabled)
Bank 5 contains 256 MB (Standard) DIMMS (enabled)
Bank 6 contains 256 MB (Standard) DIMMS (enabled)
Bank 7 contains 256 MB (Standard) DIMMS (enabled)
Memory at Module 1/Slot 2: 2048 MB (enabled)
Bank 0 contains 256 MB (Standard) DIMMS (enabled)
Bank 1 contains 256 MB (Standard) DIMMS (enabled)
Bank 2 contains 256 MB (Standard) DIMMS (enabled)
Bank 3 contains 256 MB (Standard) DIMMS (enabled)
Bank 4 contains 256 MB (Standard) DIMMS (enabled)
Bank 5 contains 256 MB (Standard) DIMMS (enabled)
Bank 6 contains 256 MB (Standard) DIMMS (enabled)
Bank 7 contains 256 MB (Standard) DIMMS (enabled)
Memory at Module 1/Slot 3: 2048 MB (enabled)
Bank 0 contains 256 MB (Standard) DIMMS (enabled)
Bank 1 contains 256 MB (Standard) DIMMS (enabled)
Bank 2 contains 256 MB (Standard) DIMMS (enabled)
Bank 3 contains 256 MB (Standard) DIMMS (enabled)
Bank 4 contains 256 MB (Standard) DIMMS (enabled)
Bank 5 contains 256 MB (Standard) DIMMS (enabled)
Bank 6 contains 256 MB (Standard) DIMMS (enabled)
Bank 7 contains 256 MB (Standard) DIMMS (enabled)
Memory at Module 1/Slot 4: 1024 MB (enabled)
Bank 0 contains 128 MB (Standard) DIMMS (enabled)
Bank 1 contains 128 MB (Standard) DIMMS (enabled)
Bank 2 contains 128 MB (Standard) DIMMS (enabled)
Bank 3 contains 128 MB (Standard) DIMMS (enabled)
Bank 4 contains 128 MB (Standard) DIMMS (enabled)
Bank 5 contains 128 MB (Standard) DIMMS (enabled)
Bank 6 contains 128 MB (Standard) DIMMS (enabled)
Bank 7 contains 128 MB (Standard) DIMMS (enabled)
Memory at Module 3/Slot 1: 3584 MB (enabled)
Bank 0 contains 512 MB (Standard) DIMMS (enabled)
Bank 1 contains 512 MB (Standard) DIMMS (enabled)
Bank 2 contains 256 MB (Standard) DIMMS (enabled)
Bank 3 contains 256 MB (Standard) DIMMS (enabled)
Bank 4 contains 512 MB (Standard) DIMMS (enabled)
Bank 5 contains 512 MB (Standard) DIMMS (enabled)
Bank 6 contains 512 MB (Standard) DIMMS (enabled)
Bank 7 contains 512 MB (Standard) DIMMS (enabled)
Memory at Module 3/Slot 2: 4096 MB (enabled)
Bank 0 contains 512 MB (Standard) DIMMS (enabled)
Bank 1 contains 512 MB (Standard) DIMMS (enabled)
Bank 2 contains 512 MB (Standard) DIMMS (enabled)
Bank 3 contains 512 MB (Standard) DIMMS (enabled)
Bank 4 contains 512 MB (Standard) DIMMS (enabled)
Bank 5 contains 512 MB (Standard) DIMMS (enabled)
Bank 6 contains 512 MB (Standard) DIMMS (enabled)
Bank 7 contains 512 MB (Standard) DIMMS (enabled)
Memory at Module 3/Slot 3: 4096 MB (enabled)
Bank 0 contains 512 MB (Standard) DIMMS (enabled)
Bank 1 contains 512 MB (Standard) DIMMS (enabled)
Bank 2 contains 512 MB (Standard) DIMMS (enabled)
Bank 3 contains 512 MB (Standard) DIMMS (enabled)
Bank 4 contains 512 MB (Standard) DIMMS (enabled)
Bank 5 contains 512 MB (Standard) DIMMS (enabled)
Bank 6 contains 512 MB (Standard) DIMMS (enabled)
Bank 7 contains 512 MB (Standard) DIMMS (enabled)
Memory at Module 3/Slot 4: 4096 MB (enabled)
Bank 0 contains 512 MB (Standard) DIMMS (enabled)
Bank 1 contains 512 MB (Standard) DIMMS (enabled)
Bank 2 contains 512 MB (Standard) DIMMS (enabled)
Bank 3 contains 512 MB (Standard) DIMMS (enabled)
Bank 4 contains 512 MB (Standard) DIMMS (enabled)
Bank 5 contains 512 MB (Standard) DIMMS (enabled)
Bank 6 contains 512 MB (Standard) DIMMS (enabled)
Bank 7 contains 512 MB (Standard) DIMMS (enabled)
ROUTER in Module 1/Slot 2: Revision 2: Active Ports [1,2,4,5,6] (enabled)
ROUTER in Module 1/Slot 4: Revision 2: Active Ports [1,2,4,5,6] (enabled)
ROUTER in Module 3/Slot 2: Revision 2: Active Ports [1,2,4,5,6] (enabled)
ROUTER in Module 3/Slot 4: Revision 2: Active Ports [1,2,4,5,6] (enabled)
Integral SCSI controller 4: Version Fibre Channel QL2200A, 33 MHz PCI
Integral SCSI controller 2: Version QL1040B (rev. 2), single ended
Integral SCSI controller 3: Version QL1040B (rev. 2), single ended
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
IOC3/IOC4 serial port: tty3
IOC3/IOC4 serial port: tty4
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
Graphics board: SI
Gigabit Ethernet: tg1, module 1, PCI bus 0 slot 0 port 0
Gigabit Ethernet: tg2, module 1, PCI bus 0 slot 0 port 1
HIPPI-Serial adapter: unit 0, in module 1 I/O slot 7
Fast Ethernet: ef2, version 1, module 3, slot io1, pci 2
Integral Fast Ethernet: ef0, version 1, module 1, slot io1, pci 2
Fast Ethernet: ef1, version 1, module 1, slot io2, pci 2
Origin PCI XIO board, module 1 slot 2: Revision 3
PCI Adapter ID (vendor 0x14e4, device 0x1648) PCI slot 0
PCI Adapter ID (vendor 0x14e4, device 0x1648) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x2200) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
Origin BASEIO board, module 3 slot 1: Revision 4
Origin BASEIO board, module 1 slot 1: Revision 4
PCI Adapter ID (vendor 0x10a9, device 0x0002) PCI slot 0
PCI Adapter ID (vendor 0x10a9, device 0x0002) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
IOC3/IOC4 external interrupts: 2
IOC3/IOC4 external interrupts: 1
HUB in Module 1/Slot 1: Revision 5 Speed 100.00 Mhz (enabled)
HUB in Module 1/Slot 2: Revision 5 Speed 100.00 Mhz (enabled)
HUB in Module 1/Slot 3: Revision 5 Speed 100.00 Mhz (enabled)
HUB in Module 1/Slot 4: Revision 5 Speed 100.00 Mhz (enabled)
HUB in Module 3/Slot 1: Revision 6 Speed 100.00 Mhz (enabled)
HUB in Module 3/Slot 2: Revision 6 Speed 100.00 Mhz (enabled)
HUB in Module 3/Slot 3: Revision 6 Speed 100.00 Mhz (enabled)
HUB in Module 3/Slot 4: Revision 6 Speed 100.00 Mhz (enabled)
IP27prom in Module 1/Slot n1: Revision 6.156
IP27prom in Module 1/Slot n2: Revision 6.156
IP27prom in Module 1/Slot n3: Revision 6.156
IP27prom in Module 1/Slot n4: Revision 6.156
IO6prom on Global Master Baseio in Module 1/Slot io1: Revision 6.156
IP27prom in Module 3/Slot n1: Revision 6.156
IP27prom in Module 3/Slot n2: Revision 6.156
IP27prom in Module 3/Slot n3: Revision 6.156
IP27prom in Module 3/Slot n4: Revision 6.156


Code: Select all

$ /usr/gfx/gfxinfo -v
Graphics board 0 is "IMPACTSR" graphics.
Managed (":0.0") 1280x1024
Product ID 0x2, 1 GE, 1 RE, 0 TRAMs
MGRAS revision 1, RA revision 0
HQ rev B, GE11 rev B, RE4 rev C, PP1 rev A,
VC3 rev A, CMAP rev E
unknown, assuming 19" monitor (id 0xd)
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)
Power consumption:

Image
:A3502L: :O2000: :O200: = :O200: - :O200: :O200: :Octane: :Octane: :320: :O2: :Indigo2IMP: :Indy:
+ | d | i | g | i | t | a | l | +apple +[...] ;)