The collected works of jpstewart - Page 1

Hello, everyone. I'm a newcomer here. Actually, I'm a long time lurker who has finally decided to come out of the shadows and join into the discussions. I used to be somewhat active in the comp.sys.sgi.* newsgroups 8-10 years ago. My Indigo2 was set aside for a number of years, but I've been playing with it again lately. (Amazingly, after five years in storage it booted up just fine!) I thought I'd introduce my Indigo2 now:

Code: Select all

hinv -vm
CPU: MIPS R4400 Processor Chip Revision: 6.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 250 MHZ IP22 Processor
Main memory size: 64 Mbytes
Secondary unified instruction/data cache size: 2 Mbytes 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: Solid Impact
Integral Ethernet: ec0, version 1
Iris Audio Processor: version A2 revision 1.1.0
EISA bus: adapter 0


Code: Select all

Graphics board 0 is "IMPACT" graphics.
Managed (":0.0") 1280x1024
Product ID 0x1, 1 GE, 1 RE, 0 TRAMs
MGRAS revision 1, RA revision 0
HQ rev A, GE11 rev B, RE4 rev A, PP1 rev A,
VC3 rev A, CMAP rev EMC rev C
unknown, assuming 19" monitor (id 0xf)

Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60)


The EISA bus adapter is an E100 Fast Ethernet card. I actually have Phobos G160 sitting on my desk, but it's still in the original box (even shrink wrapped!) so I'm a little reluctant to install it.

The Indigo2 is connected to a 17 inch Samsung SyncMaster 760V LCD through a cheap 13W3<->VGA adapter.

The box came with IRIX 6.5 pre-installed when I bought it about 8 or 9 years ago. I recently downloaded and installed the 6.5.22 patchset. I should probably do a full re-install (once I get my hands on IRIX media) since I almost certainly messed up the installation in the early days before I knew much about IRIX. (I'm a Linux guy, primarily. But ever since using Solaris 2.x in the early- to mid-1990s, I've had an interest in anything Unix-y.)

I know the system desperately needs more RAM, but it's getting hard to find (and consequently rather expensive). I almost purchased an Octane recently, and have a few Octane accessories already sitting on my desk waiting for a home. So I'm not sure if I'll upgrade the RAM or not. I've heard older versions of IRIX run better with 64MB, so I may downgrade the OS instead.

I'll try to get some pictures to post.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote: There are a couple of empty Octane cases for sale on Ebay these days, if you're looking for a shiny new home for your Octane parts... :mrgreen:


Yeah, I'm quite familiar with all the temptations eBay currently has to offer. Most of the vendors want nearly $100 to ship the $20 empty Octane case, though. I keep hoping an Octane will show up within driving distance to avoid shipping one of those beasts.

vishnu wrote: Southwestern Ontario, anywhere near Atikokan? :?:


Nope. Atikokan is Northwestern Ontario. I'm nowhere near that far north nor even that far west. "Southwestern Ontario" generally refers to the Windsor/London area (and even a little further east). The area southwest of Toronto, basically. I'm actually between Buffalo NY and Detroit MI. Atikokan is roughly 1000 miles (or 1600 km) northwest of me.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Thanks to Mike in this For Sale thread , I've finally been able to upgrade to a reasonable amount of RAM at a reasonable price. I got 2x128MB kits from him and now my Indigo2 totals 320MB. It swaps a lot less (obviously!) and so it now performs surprisingly well as long as you keep in mind that it is a 15 year old computer.

Code: Select all

hinv -vm
CPU: MIPS R4400 Processor Chip Revision: 6.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 250 MHZ IP22 Processor
Main memory size: 320 Mbytes
Secondary unified instruction/data cache size: 2 Mbytes 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: Solid Impact
Integral Ethernet: ec0, version 1
Iris Audio Processor: version A2 revision 1.1.0
EISA bus: adapter 0
IMPACT Compression: unit 0, revision 0:0


Oh, yes: I also scored an IMPACT Compression card off of eBay last month (although I'd be willing to bet that that seller was also a forum member here). I guess I'll have to excavate down to make some desk space near the I2 for some video gear!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Edited the original post to change the thread title to reflect the new configuration.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
ozpass wrote: 1 x Sun Microsystems Sunfire V880z, 3 x UltraSPARC III CPU's

You might want to double check the number of CPUs. AFAIK, the V880 systems used CPU boards with 2 CPUs each so 3 CPUs wouldn't be possible. 3 boards with 2 CPUs each would be a more likely configuration, for a total of 6 CPUs. (Which was the max for 880z, AFAIK. The non-z 880 could handle 8 CPUs on 4 boards.)
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Alver wrote: Are you sure it's an X1? C8000s 'officially' don't support those (or they're missing from the docs), it's usually either T2 or X3.

The FireGL X1 is definitely mentioned in some of HP's docs for the C8000:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=408101&prodTypeId=12454&objectID=c00332698

Alver wrote: Also, the X1 only had 128MB, afaik.

The ATI FireGL X1-256p card (with 256MB) for the C8000 was offered as HP part number A9653A.
http://www.hp.com/workstations/irg/risc/HP_workstations_UNIX_options.pdf

I had a 256MB FireGL X1-256 in one of my PCs for the better part of the last decade, so I'm quite sure that ATI made FireGL X1 cards with 256MB. (They may also have been available with 128MB, too, but that's another matter. And what was supported in the C8000 is yet another question!)

gkl wrote: some docs refer to the "high end" graphics option as X1 and other docs say X3

Probably at the time of introduction, the high end was the X1 and then when ATI released the X3 it superseded the X1 as the high end option. The fine print in those docs show copyrights of 2004 and 2007.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500, T5240
HP C8000
D-EJ915 wrote:
jpanchal wrote: I have a J6750, and the new HP-UX patching policy is a pain (it's as bad as the new Oracle policy for Solaris...) - just to let you know, Debian runs a dream on PA-RISC hardware thanks to the folks at ESIEE, if you ever need a backup OS. :)

It does for now (5.0) but for 6.0 hppa is dropped :(

Just FYI: Debian 6.0 (aka Squeeze) was released a week ago, on Feb. 6, 2011. But Debian 5.0 (aka Lenny) is still available.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500, T5240
HP C8000
PymbleSoftware wrote: Doing a low level block by block read of a deleted file system on one of the machines I got had evidence of a French (Aerospace ?) CAD/CAE system whose name I forget.

Probably CATIA ( http://en.wikipedia.org/wiki/CATIA ), originally from Dassault (a French company). I think it ran on IRIX in version 5.x.

Pro/Engineer (from PTC) ran on IRIX up to and including the version known as "Wildfire 2.0" (circa 2004). See http://en.wikipedia.org/wiki/Pro/Engineer#Release_history for a timeline and http://www.ptc.com/WCMS/files/71140/en/proewf2.pdf for the official support info.

I don't know when IRIX support started for either of those applications. Those are (AFAIK) the versions after which it was dropped.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
PymbleSoftware wrote: I think you may have been right about it be it CATIA, but my memory is too hazy to be sure, but it was running on 6.5.xx hardware so either upwards compatible from IRIX 5.x or there was a newer version, that ran on 6.5.xx.


Sorry, when I said "version 5.x" I meant of CATIA, not IRIX! My previous post was very poorly worded! :oops: Oops!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Do the included disks have IRIX drivers & software or is it Windows only? It's kind of hard to make out in the pictures, but it looks to me like the CDs and floppy disk all mention Windows. Or are drivers included with IRIX anyway?

I've always wanted one of these Spaceballs, but I know absolutely nothing about them!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
PymbleSoftware wrote: I have nothing to do with the seller, but if it is a compatible device, and it looks like the one I have.. Spaceball drivers are built into IRIX...with correct bits installed in swmgr.. read the wiki topic: here

Thanks for the link to the Wiki page! I have a bad habit of forgetting to check the wiki for info. :oops:
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I was interested in this Spaceball, until I saw the size of the credit card bill that came in the mail yesterday. No new tech toys for a while. :( I do hope you can find it a good home, leaknoil . It's an unusually complete setup you've got for sale!

I should also point out that my research found that drivers (for at least some later models of Spaceball) are available from http://www.3dconnexion.com/service/drivers.html . Be sure to check the box next to "Also show archived* software" when searching for IRIX drivers. You also may need to register first (whatever that may entail) before you can actually download anything.

It's nice to see that the current manufacturer still remembers the existence of IRIX. It seems to me like the company has changed names a few times, so the continued support for IRIX is a pleasant surprise after all that.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
ShadeOfBlue wrote: Copy the above into a file (e.g. card.c)


Wow! :!: It's pretty clear that a lot of effort went into that. I'm very impressed. Not only are the sources in pretty patterns, but the output is some mighty nice ASCII art, too. I'm not even going to try to decipher the C source code, so I can't even begin to imagine what it must have taken to write it. Again, wow! :!:
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Apparently I never posted a hinv of my Octane (which I've had for over a year), so here it goes:

hinv -vm:

Code: Select all

Location: /hw/node
PM20250MHZ Board: barcode GLZ858     part 030-1427-001 rev  A
Location: /hw/node/xtalk/15
IP30 Board: barcode LKD648     part 030-1467-001 rev  D
Location: /hw/node/xtalk/15/pci/2
PWR.SPPLY.ER Board: barcode AAE0170215 part 060-0035-002 rev  A
FP1 Board: barcode KSN507     part 030-0891-003 rev  G
Location: /hw/node/xtalk/13
XTALKPCI Board: barcode JKG045     part 030-0952-005 rev  E
Location: /hw/node/xtalk/12
MOT10 Board: barcode KXG042     part 030-1241-002 rev  K
Location: /hw/node/xtalk/11
EVO Board: barcode KWY124     part 030-1156-003 rev  B
Location: /hw/node/xtalk/10
MOT10 Board: barcode KCJ752     part 030-1241-002 rev  J
2 250 MHZ IP30 Processors
Heart ASIC: Revision F
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 0.0
Main memory size: 768 Mbytes
Heart ASIC: Revision F
CPU: MIPS R10000 Processor Chip Revision: 3.4
FPU: MIPS R10010 Floating Point Chip Revision: 0.0
Main memory size: 768 Mbytes
Xbow ASIC: Revision 1.4
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Tape drive: unit 2 on SCSI controller 0: DAT
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
CDROM: unit 1 on SCSI controller 1
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: ESI
Graphics board: ESI
Integral Fast Ethernet: ef0, version 1, pci 2
Gigabit Ethernet: tg1, PCI slot 3
Iris Audio Processor: version RAD revision 12.0, number 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 0x0005) PCI slot 3
PCI Adapter ID (vendor 0x14e4, device 0x1645) PCI slot 3
Personal Video: unit 1, revision 2.0, DigCam version 1.2 connected

gfxinfo -vv:

Code: Select all

Graphics board 0 is "IMPACTSR" graphics.
Managed (":0.0") 1280x1024
Product ID 0x2, 1 GE, 1 RE, 0 TRAMs
MGRAS revision 4, RA revision 0
HQ rev B, GE12 rev A, RE4 rev C, PP1 rev G,
VC3 rev A, CMAP rev F, Heart rev F
unknown, assuming 19" monitor (id 0xf)
Video board present

Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  unknown
Gain (all color components) - 1.000000 (nominal)
Graphics board 1 is "IMPACTSR" graphics.
Managed (":0.1") 1280x1024
Product ID 0x2, 1 GE, 1 RE, 0 TRAMs
MGRAS revision 4, RA revision 0
HQ rev B, GE12 rev A, RE4 rev C, PP1 rev H,
VC3 rev A, CMAP rev F, Heart rev F
unknown, assuming 19" monitor (id 0xf)

Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  unknown
Gain (all color components) - 1.000000 (nominal)

uname -aR:

Code: Select all

IRIX64 gumby 6.5 6.5.22m 10070055 IP30

scsicontrol -i:

Code: Select all

/dev/scsi/sc0d1l0:  Disk          COMPAQ  BD03664553      3B05
ANSI vers 2, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueing
Device is  ready
/dev/scsi/sc0d2l0:  Tape          ARCHIVE Python 01931-XXX5.63
ANSI vers 2, ISO ver: 0, ECMA ver: 0; supports:  synch linkedcmds
Device is  not ready

/dev/scsi/sc1d1l0:  CD-ROM        HP      DVD-ROM 305     1.01
ANSI vers 2, ISO ver: 0, ECMA ver: 0; supports:  synch
Device is  not ready

diskpatch -v:

Code: Select all

sc0d1l0:  Disk         COMPAQ  BD03664553      3B05  Serial: 3FD0B627

The Archive tape drive is an SGI original DDS-2 drive I stumbled upon on eBay which seems to have the audio-over-SCSI firmware. The drive works flawlessly, too. I've used it for a full backup (and restore!) successfully.

I bought that HP DVD-ROM based on the suggestion in another forum thread and stuck it in a Sun 611 case. Works great, too. Thanks to whoever suggested those HP DVD readers!

The machine also has an IBM-branded Spaceball input device hanging off a serial port but that doesn't show up in the hinv. (Between that and the aforementioned HP drive in a Sun case all running off of an SGI computer I sure do seem to be mixing and matching my Unix vendors!)

Alas, all is not well with the machine. Around the time I got the machine, I posted in another thread about some networking problems. I've since added a PCI cage and Gigabit NIC so it's at least on the network now. But it still has some serious gremlins. I think SAQ hit the nail on the head in that other thread when he suggested looking at the frontplane. In addition to no on-board network connectivity, I get XIO errors whenever I run the system fully configured with both SE cards and the PVO installed. Either SE card alone is rock solid stable. Both SEs together, or any one SE + the PVO, or both SEs + PVO are all unstable configurations. Sometimes the screen will just go black. If the screen stays functional I get messages about "Heart: DMA Memory Address Error" to go with my lock-up.

So for the most part, I run it headless and connect via SSH. Which is a shame considering the Octanes were built for graphics. Someday I'll replace the frontplane. But I keep spending my computer budget on other toys instead....
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I recently took a chance on an "As-Is" Origin 300 from eBay. I won the auction for just $36, and the shipping was a lot less than what I've seen from other sellers. (It was halfway across Canada but still north of the border, so no customs hassles...which might explain why shipping was less than half the cost of other Origins I've looked at from US sellers.)

Turns out that in this case "As-Is" meant fully functional! :D I was a little disappointed that it was only 2 CPUs and only 1GB RAM. I had been hoping it would have disk sleds in it, and so I was very pleasantly surprised to find that it had a 73GB system disk (with no root password on what appears to be a fresh install of 6.5.29) and a 300GB Seagate disk in the second slot, along with a QL12160 SCSI card in one of the PCI slots. That made up for having only 2 CPUs. So all in all, it was better than expected! :!: Even more so considering it was still well under $100 even after adding shipping and taxes.

hinv -vm:

Code: Select all

Location: /hw/module/001c24/node
IP45_2CPU Board: barcode MJH014     part 030-1780-001 rev -C
Location: /hw/module/001c24/Ibrick/xtalk/14
IO8 Board: barcode MJL112     part 030-1673-003 rev -F
Location: /hw/module/001c24/Ibrick/xtalk/15
IO8 Board: barcode MJL112     part 030-1673-003 rev -F
2 500 MHZ IP35 Processors
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
CPU 0 at Module 001c24/Slot 0/Slice A: 500 Mhz MIPS R14000 Processor Chip (enab
Processor revision: 2.4. Scache: Size 2 MB Speed 250 Mhz  Tap 0xa
CPU 1 at Module 001c24/Slot 0/Slice C: 500 Mhz MIPS R14000 Processor Chip (enab
Processor revision: 2.4. Scache: Size 2 MB Speed 250 Mhz  Tap 0xa
Main memory size: 1024 Mbytes
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Memory at Module 001c24/Slot 0: 1024 MB (enabled)
Bank 0 contains 512 MB (Premium) DIMMS (enabled)
Bank 1 contains 512 MB (Premium) DIMMS (enabled)
Integral SCSI controller 3: Version QL12160, low voltage differential
Integral SCSI controller 6: Version QL12160, low voltage differential
Integral SCSI controller 0: Version QL12160, low voltage differential
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Disk drive: unit 2 on SCSI controller 0 (unit 2)
Integral SCSI controller 1: Version QL12160, low voltage differential
IOC3/IOC4 serial port: tty3
IOC3/IOC4 serial port: tty4
Integral Fast Ethernet: ef0, version 1, module 001c24, pci 4
PCI Adapter ID (vendor 0x1077, device 0x1216) PCI slot 1
PCI Adapter ID (vendor 0x1077, device 0x1216) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 4
PCI Adapter ID (vendor 0x11c1, device 0x5802) PCI slot 5
IOC3/IOC4 external interrupts: 1
HUB in Module 001c24/Slot 0: Revision 2 Speed 200.00 Mhz (enabled)
IP35prom in Module 001c24/Slot n0: Revision 6.210
USB controller: type OHCI

uname -aR:

Code: Select all

IRIX64 orion 6.5 6.5.29m 01090133 IP35

scsicontrol -i /dev/scsi/*:

Code: Select all

/dev/scsi/sc0d1l0:  Disk          SGI     ST373307LC      2741
ANSI vers 3, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueig
Device is  ready
/dev/scsi/sc0d2l0:  Disk          SEAGATE ST3300007LC     0002
ANSI vers 3, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueig
Device is  ready

diskpatch -v:

Code: Select all

sc0d1l0:  Disk         SGI     ST373307LC      2741  Serial: 3HZ0MW7R
sc0d2l0:  Disk         SEAGATE ST3300007LC     0002  Serial: 3KR0E5B7

l1cmd serial all:

Code: Select all

Data                            Location      Value
------------------------------  ------------  --------
Local System Serial Number      NVRAM         M2001347
Reference System Serial Number  NVRAM         M2001347
Local Brick Serial Number       EEPROM        MJH014
Reference Brick Serial Number   NVRAM         MJH014

EEPROM      Product Name    Serial      Part Number           Rev  T/W
----------  --------------  ----------  --------------------  ---  ------
NODE        IP45_2CPU       MJH014      030_1780_001          C    00
IO8         IO8             MJL112      030_1673_003          F    00

EEPROM      JEDEC Info                Part Number         Rev
----------  ------------------------  ------------------  ---
DIMM 0      CE0000000000000027F43B00  M3 46L6510BT1-CA0   0B
DIMM 2      no hardware detected
DIMM 1      CE00000000000000279F3B00  M3 46L6510BT1-CA0   0B
DIMM 3      no hardware detected

l1cmd flash status:

Code: Select all

Flash image B currently booted

Image      Status        Revision    Built
-----   -------------   ----------   -----
A     valid           1.10.12      02/01/2002 14:40:22
B     default         1.10.12      02/01/2002 14:40:22

l1cmd env:

Code: Select all

Environmental monitoring is enabled and running.

Description    State       Warning Limits     Fault Limits       Current
-------------- ----------  -----------------  -----------------  -------
12V IO    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.12
12V DIG    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.25
5V    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    4.97
3.3V    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.34
5V aux    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    4.99
3.3V aux    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.42
2.5V    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.50
Speedo2 CPU    Enabled  10%   1.44/  1.76  20%   1.28/  1.92    1.59
1.5V    Enabled  10%   1.35/  1.65  20%   1.20/  1.80    1.48

Description    State       Warning RPM  Current RPM
-------------- ----------  -----------  -----------
FAN 0     LEFT    Enabled         2160         3960
FAN 1   CENTER    Enabled         2160         4007
FAN 2    RIGHT    Enabled         2160         4105
FAN 3       PS    Enabled         2160         3175
FAN 4      PS'    Enabled         2160         4371

Advisory  Critical  Fault     Current
Description    State       Temp      Temp      Temp      Temp
-------------- ----------  --------  --------  --------  ---------
NODE 0            Enabled  30C/ 86F  35C/ 95F  40C/104F  19c/ 66F
NODE 1            Enabled  30C/ 86F  35C/ 95F  40C/104F  19c/ 66F

l1cmd pci:

Code: Select all

Slot    Power
----    -----
Slot 1  15.0
Slot 2  0.0

I won't bother with pictures. It's nothing special visually. But I'm still very excited. I'll probably spend next weekend putting it through it's paces to compare it to my 2x250MHz Octane.

And I just love the L1 functionality. I wish all systems had that! I do notice that it's quite an old L1 firmware version and that will have to be updated. (In fact, something in the boot process is complaining about the firmware being too old to support some feature.) I've read up on that in the wiki and the cautionary tales in the forum about trying to jump too many versions at a time. I think I've got a bit more reading to do before I actually understand it well enough to attempt the multi-stage incremental updates to the firmware and the flash utility. But you guys have done the hard parts: figuring out the process and documenting it. Thanks for that! Otherwise I'd be in big trouble. :lol:
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Does anyone know of any good sources of documentation for SunOS 4.1.4? I recently installed it on my SS20 after finding some good installation docs on the web. Unfortunately I can't find any post-installation administration guides anywhere.

I'd really like to play around with SunOS 4.1.4 (and possibly Solaris 2.x) on this machine because that's where I got my introduction to Unix. I can't quite remember what the machines were running back then but it was in the SunOS 4.1.4 to Solaris 2.3 timeframe according to Wikipedia's Solaris version history chart. Back then I was merely a (novice) user on a system run by the professional sysadmins at my university. So at the time I knew very little about using the system and even less about administration. Unfortunately, I still know very little about being sysadmin on SunOS!

So far it boots fine, I can login, and I can launch SunView and OpenWindows. It's almost connected to the rest of my network...it just won't talk to my DNS server. (But pinging by IP address is fine and routing is properly configured.) AFAICT I've got /etc/resolv.conf and /etc/nsswitch.conf setup correctly according to their respective man pages, but DNS queries fail. An admin guide would likely point me in the right direction to fix that and answer future questions, too.

Any suggestions on where to find a book, PDF, or website for sysadmins of such an old operating system? Thanks!

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
miod wrote:
SunOS 4 will not perform DNS lookups by default.

Interesting. I was not aware of that. It certainly explains why I can get anywhere by IP address but not by name.

Since it came with an early version of named and the resolv.conf man page on the box talks about DNS servers, I assumed that meant it would do DNS lookups. (That, and it's the only Unix-y system I've encountered that didn't do DNS....)

I did get named configured and now nslookup works on the machine. Still can't ping by name. But at least it's a step in the right direction.

I'll definitely look into YP as you suggest.

miod wrote:
Also, note that /etc/nsswitch.conf is a Solaris thing, it has no effect on a SunOS 4 system.

I see. I must have been reading the wrong documentation when it told me to verify nsswitch.conf was correctly configured. Oops. :oops: Too many projects on the go, perhaps!

Thanks for pointing me in the right direction!

Still looking for good documentation if anyone knows of good books....

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
SAQ wrote:
Another SunOS reference I use is The System Administrator's Guide to the Sun Workstations and the Unix Admin Red-book, but neither of these are electronic or out-of-copyright.

Aha! That first one sounds like somethng I should look into. Another source also mentioned the "Red" book and now that you've recommended it too, I'll look into it some more. It looks like both books are available cheaply from an on-line used book store here in Canada. Even better!

I've also been able to locate some on-line docs too. In particular, Chapter 30 of this on-line book has a lot of what I was looking for. (The rest of the book should be at least somewhat helpful, too.) And another member here has helpfully reminded me via PM that the Unix Rosetta Stone has a SunOS 4 column.

Thanks all!

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote:
What'cha gonna do with it? :mrgreen:

Make the rest of us jealous and cause a lot of head scratching? :lol:

When I first saw the thread, I was convinced "Onyx 200" was a typo. Apparently not. But it's that modularity of the hardware permitting such odd configurations that makes SGI hardware so much fun to play with, isn't it?

Perhaps this is the start of bjornl's evil plot to take over the world by leaving the rest of sitting here muttering under our breath, "what the heck?". Or maybe that's just me. :D

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
After having a bad day yesterday resurrecting an Indigo, I thought I'd ask you all if you've got any hardware-related "oops" moments to share. I'll kick it off with my own story:

Several months ago, I was able to score a reasonably-priced Indigo R4K off of eBay. It was nearly local and had skins in almost perfect condition. (Missing a latch on the drive door, but otherwise very nice for its age.) But it didn't boot due to the typical TOD clock battery problem. I finally got around to replacing the battery this weekend. (Largely because I'd been waiting to amass enough of a shopping list to make it worthwhile to order supplies from DigiKey. I wasn't going to pay $8 shipping just to get a $6 battery!) De-soldering the old one and soldering in the new battery wasn't too big a deal. Put the motherboard back in, hooked up the serial cable, flipped the power switch. Saw a green light and nothing else. No boot tune. No output in minicom.

Now I'm not exactly skilled at soldering so my first thought was that I had killed the motherboard with too much heat, damaged another nearby component, or otherwise made things worse with my amateurish use of the soldering iron. A quick search led to this thread and in particular the last post there where SAQ suggests cleaning & re-seating the PM1 CPU module. That's when I realized that the PM1 was still sitting on my desk, unconnected to anything.

:oops: Oops! :oops:

My enthusiam to test my soldering job had apparently gotten the best of me, and I'd missed the rather important step of re-attaching the CPU. :!: Funny how computers don't work so well without CPUs. :lol: After fixing that oversight, it boots up to the PROM menu just fine, I can run hinv, etc. All is good.

So, now that I've told my story do any of you have similar tales of silly mistakes you've made while repairing hardware? Something that caused you to initially panic thinking you'd made things worse when in reality it was just a minor problem or skipped step that had a happy ending after all. If you can stop laughing at me long enough to post your stories, I'd sure like to know I'm not alone!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I recently scored a nicely equipeed HP C8000 for my collection. One dual-core 1.1GHz PA-8900 CPU (w/64MB L2 cache), 16GB RAM (8x2GB DIMMs), 146GB HDD, FireGL T2 graphics. Not a bad "starter system" for an introduction to the world of HP-UX, which I'd never used until about 2 weeks ago.

Of course, it's not quite as "vintage" as the rest of my collection. Maybe that'll be my excuse to go searching for some older HP gear....

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
ClassicHasClass wrote:
Picked up a C8000 for a nice price which arrived yesterday. Dual-core 1.1GHz PA-8900, DVD, FireGL-UX graphics and a gig of RAM.

Are you sure it's a FireGL-UX? That seems odd for the C8000. With the 1.1GHz CPU model, I'd expect it to be a FireGL T2 or X3 (according to this link ). The FireGL X1 was also used on earlier C8000s with slower CPUs, so you might have one of those. Those are all AGP (Pro) cards. The FireGL-UX is a generation older (at least) and 64bit/66MHz PCI instead, and would seem unlikely (if it's even supported) in a C8000.

Not that it really matters.... But you might have much newer/better graphics than you think! :D

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
mia wrote:
urbancamo wrote:
A ZX6000 with a single PSU, two 1.3Ghz Madison class processors, three 15k hard drives and 16GB of RAM idles at 380 watts. If you were to remove drives, a processor and some RAM you could probably make quite a dent in this figure.


380W!

I think the Altix 350 is roughly 250W with 2x1.5Ghz I2 and a few disks. Why such discrepancy?


Probably the graphics. The ZX6000 is a workstation whereas the Altix is a server. Moreover, the ZX6000 probably has an AGP Pro graphics slot that can supply up to 110W to the graphics card alone. And since HP was selling the ZX6000s as high-end graphics workstations, it's a safe assumption that there's a power-hungry AGP Pro graphics card in there taking full advantage of the AGP Pro slot, not some wimpy entry-level card.

Newer generation processors and disks could also account for some of the reduced power consumption of the Altix.

Of course, all of this is just speculation on my part, not having either of the machines in my collection.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
bluecode wrote:
Maybe this is a stupid question but since they are listing the header files that are going away, can't you just add them back and compile on your system?

Maybe, maybe not. Depends on what else has changed that interacts with those dropped header files. Unfortunately, it is common (IME) for things to be dropped because they cannot (easily) be made compatible with code changes elsewhere in the application.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
urbancamo wrote:
OK, here are some pictures of the AlphaStation 500 333Mhz

Thanks for the pics! I guess I've never seen an AlphaStation 500 before. It kind of resembles the Indigo2 at first glance. I like it! The Alphas I've seen have been no where near as interesting, visually.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Winnili wrote: What isn't entirely clear yet to me, is what this will mean for operating systems which still bundle CDE (and Motif), like HP-UX and VMS.

Why would it mean anything to them? I can't see any reason why software being re-released under an open source license would have any impact on prior licensees. Was there some particular issue you were worried about?
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
AFAICT (from a quick Google) the AMCC PCI Matchmaker is just a PCI interface chip and doesn't really give any clue as to what this card is. But looking at the top of the card in the photo, I can see the words "Sonic Solutions" on it. That suggests the card has something to do with audio I/O. Again, a quick Google suggests that Sonic Solutions provided audio hardware for Discreet Smoke systems. This thread mentions Sonic Solutions and Discreet. Perhaps that poster might have info and/or be interested in the card you have.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Winnili wrote:
jpstewart wrote: Why would it mean anything to them? I can't see any reason why software being re-released under an open source license would have any impact on prior licensees.

DECwindows PAKs come to mind; although they should nowadays (with VMS I64 and the licensing overhaul since) be integrated with the base OEs.

The re-release of code under an open source license doesn't automatically affect code that was previously released under a different set of licensing terms. So DECwindows will continue to be licensed the same way it always has been AFAIK. The only way that will change is if somebody at HP decides to re-release it under new license terms.

It's actually fairly common for software to be released under multiple licenses simultaneously, and AIUI that's what's happening with CDE. It is now open source in addition to still being available under whatever previous licenses there were.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote:
hamei wrote:
vishnu wrote: I saw an HP 7475a pen plotter sitting in the scrap bin at work today, those things were thousands of dollars when they were new... :shock: :cry:

You should grab it !
Can you even buy pens for them anymore :?: :?: :?:


This on-line store lists pens for the HP 7475A. I would imagine there are other sources, too. I just happen to have that one bookmarked from when I nearly purchased a pen plotter earlier this year. Supplies are out there!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
The Centronics connector is sometimes referred to as a "SCSI-I" connector. The other is sometimes referred to as a HD50 or "SCSI-II" or "SCSI-2" connector. Trying various combinations of those keywords might help your turn up a local one through Google searches.

This online store has what you're looking for in a couple of lengths, but I doubt you'd want to have one shipped from Canada.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
big_mac wrote:
Basically I'm going to use a modern m-atx mobo with a PCI slot where I plan to use the Number Nine Revolution IV-FP card to hook up my 1600sw panel.

I'm going to run debian/win7 on the machine - will the card work with those os's, and if so how much can you push the card in terms of 3D etc?l

I have no idea about Windows (any version), but Debian should work. (And any other Linux distro will have pretty much the same support since it's X.org and DRI that matter.)

http://xorg.freedesktop.org/wiki/i128
http://dri.freedesktop.org/wiki/NumberNine

As for 3D performance, don't expect much. Remember, the card you're using is nearly 15 years old now! Even if Linux does fully support it, its performance won't be great. And I gather that support is only partial, so far.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
It's impossible to find accurate performance comparisons between the 15 year old Number Nine card and modern graphics, but I'd strongly suspect that either of the solutions smj mentioned coupled with even the lowliest of current integrated graphics solutions would far, far outperform the old Number Nine card for 3D stuff while still using (at most) only one PCI slot.

Plus, Windows 7 drivers for modern graphics will likely be easier to find than for a 15 year old card from a now-defunct manufacturer.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
IIRC somebody, somewhere else in these forums mentioned that there's a timeout on the TOD clock error. Something like 2 or 2.5 hours. You might want to let it run for a bit and see if you can get further into the boot process.

(I can't find the post I'm thinking of right now. Anybody else remember that bit of info, or am mis-remembering?)

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei wrote:
But the "hobbyist community" has lost interest ? What do "hobbyists" do, just flit from flower to flower clicking the icons on the desktop ? I'm puzzled.

Since this thread is about Sun hobbyists, I'd suggest that the loss of interest is a reaction to Oracle's acquisition of Sun Microsystem. The Sun-related newsgroups and mailing lists I read have been universally negative in their reaction to the merger/takeover/whatever-it's-called. Sun was moving towards making Solaris open source and had been making it available at little to no cost long prior to that. Then Oracle seemed to slam that door shut. There's a perception (either rightly or wrongly) that Oracle doesn't care about hobbyists. (Compare their policies to the OpenVMS hobbyist program, for example.)

So in this specific case, I suspect the hobbyists lost interest because of the way they were treated by Oracle.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei wrote:
You are reinforcing my opinion of "hobbyists" as ignorant little twats

I'm not trying to argue one way or the other. Just trying to share some of the insight I've picked up in various newsgroups and mailing lists.

hamei wrote:
Open Solaris exists. It doesn't belong to Oracle. Take it. Use it. Run with it.

IBM shit on OS/2 users for fifteen years, but there's still a group of people who use it and develop for it. (More than Irix, in fact.) SGI shit all over the hobbyist group, we're still here

All of that's true. But what mattered (from what I've read) in the Sun situation was the change in attitude from Sun to Oracle (more than the actual end result). OS/2 and IRIX hobbyist users never had a company who cared about them, so they had nothing to lose. But the Sun enthusiasts did. It went from Sun being a company who tolerated (or even supported) hobbyist use to the appearance of hostility from Oracle. That drove away many (but by no means all) of the hobbyist users. There are still plenty of them out there, just not in the numbers they used to be.

(The same happened with a lot of Sun's paying customers, too, AFAIK. Many of them were driven away by the steep increases in licensing fees for Solaris, and the corresponding change in the cost/benefit equation. The change in ownership didn't just affect the hobbyist community.)

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I've had similar trouble with both the motherboard and the XIO carrier in my Octane not wanting to seat properly. It only happens when the machine is its normal, upright position. Lie the machine on its face, so the back is pointing up and slide the motherboard straight down. On my system it seats perfectly every time. Take the front (plastic) skin off the (metal) chassis first though! You don't want to damage the skin. And the metal chassis has two little "feet" on either side of the drive bays that make the system stand up perfectly level and stable!

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
jsloan wrote:
So, dual cpus, but not so fast that they overheat and run the fans all the time, etc. - I think there were some problems with dual ross 200s ?

You might want to read The Rough Guide to MBus Modules , and in particular the SPARCstation-20 page in the Systems section for notes on heat. Aparently the Ross 200s are cooler than some other configurations (such as the Ross 150s and the Sun SM81 modules).

Also note that the SS20 can handle two MBus modules, and each module can have one or two CPUs. So you can put in two dual Ross 200MHz modules for quad CPUs total if you really want to max it out.

jsloan wrote:
TGX+ graphics ?.

If you can find the VSIMM (either 4MB or 8MB), you might like SX graphics instead. But that will reduce the amount of system RAM you can have somewhat. (Although max on the SS20 is 512MB, which is an awful lot for such an old machine. So a reduction might not be too bad a thing.) But the VSIMMs are hard to find and pricey IME. The old Sun Frame Buffer FAQ can tell you more about the differences between TGX and SX than I could.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I like what ShadeOfBlue suggested. That's a well though out proposal, especially his note about inst.README.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
jsloan wrote:
The key with the graphics is that I would like to try to achieve triple-head, somehow... possible ?

Sure should be, in any of (at least) 3 different ways:

1) 3 x TurboGX SBus cards would likely be easiest to find and cheapest

2) 1 x VSIMM (for onboard SX) + 2 x TuboGX SBus cards

3) 2 x VSIMM + auxilliary video board (AVB, Sun part 501-2488, which is rare and expensive) (for 2 SX heads) + 1 TurboGX SBus

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
canavan wrote: While we are discussing changes, I think manpages should always go into /usr/nekoware/man, not share/man

The same logic should probably be applied to texinfo pages. I've noticed some packages put them in /usr/nekoware/info and others in /usr/nekoware/share/info. If manpages should go in man rather than share/man, then info pages should be in /usr/nekoware/info rather than share/info. That would mean that the neko_texinfo package would have to be configured to look there. I think that the info utility looks in share/info by default. (Or rather, I think that GNU standards specify share/man and share/info by default for their stuff.)

Note that the use of man vs. share/man and info vs. share/info is due to differences in the source packages' defaults. Some install into PREFIX/man and PREFIX/info while others install into PREFIX/share/man by default. It will be necessary to pass --mandir=... and --infodir=... (or perhaps just --datarootdir=/usr/nekoware) options to the configure script (after the --prefix option as described in http://www.nekochan.net/wiki/Packaging_Software#Building_the_Software ) to get consistent behaviour across all source packages. If that's what people want.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000