Nekonomicon - jan-jaap

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of eBay: Onyx 10000 InfiniteReality... at Sept. 11, 2009, 1:05 a.m...

SAQ wrote: That and there appear to be two or three IO4s, which would again be difficult in a deskside Onyx.

ebay onyx wrote: Includes:
* 030-0683-004 - Raster Manager w/16MB Texture Memory for IR graphics
* 030-0681-003 - Geometry Engine for IR graphics
* 030-0686-004 - PCA DG4-2

* 030-0527-508 - SCIP SCSI Mez board w/cables and connector plates
* 030-0753-005 - PCA SAMZ
* 030-0500-206 - PCA VCAM
* 030-0815-002 - PCA IO4 W/F2 AND F3

* 030-0604-106 - MC3 Board
* 030-0604-106 - MC3 Memory Board (32 SIMM slots - suports 16 & 64MB SIMMs)
* 030-8109-006 - Silicon Graphics - CALL AUDIO BOARD FOR INDIGO2
* 003-0290-003 - Scsi 50pin Controller

(ok, I shuffled the order)

I count one (IR capable) IO4, a VCAM, and two MEZs: a SAMZ (audio/serial) and an SCIP. Seems legit to me?
I always wondered why the audio connector box of Onyx1 ASO sticks out of the bulkhead. Could it be the audio daughtercard of an Indigo2 is hiding in there?

Oh, and there are VFE bulkheads, but if you look closely, it says something about the board being someones property. It appears to be gone.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of eBay: Onyx 10000 InfiniteReality... at Sept. 17, 2009, 8:31 a.m...

bri3d wrote: Best of luck to the seller

Somebody actually placed a bid of (at least) $3K :shock:

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Iris 4D anyone? at Sept. 29, 2009, 8:04 a.m...

wolflord wrote: I assume the VGX didn't have the pinstripe of death issue like my poor G boardset suffers.

It is possible, but much less likely. From the 6 or so VGX RM's I've had only one suffered from it, and only 2 out of 8 RM4's.

OTOH, I haven't seen a GT or GTX in years that didn't suffer from it.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of HOWTO: Restore Fuel L1 firmware after a broken update at Sept. 30, 2009, 4:29 a.m...

ShadeOfBlue wrote: If you try to issue a power up command, you will receive this lovely message:

Code: Select all
001?01-L1>pwr up ERROR: no power supplies available.

Damn, that happened to me too, but in my case the system was a Fuel prototype !
I used the same procedure to recover the system.

ShadeOfBlue wrote: If anyone has the newest 1.48.0 L1 image, I could give it a try to see whether they've fixed this or not

Forget it. That's what I used:

Code: Select all


   Flash image B currently booted
   

   

   Image      Status        Revision    Built
   

   -----   -------------   ----------   -----
   

   A     valid           1.48.1       01/22/2007 11:33:34
   

   B     user default    1.9.15       12/04/2001 16:21:34

To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. ( IRIS 4D/70 Superworkstation Technical Report )

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of HOWTO: Restore Fuel L1 firmware after a broken update at Oct. 1, 2009, 1:09 a.m...

SAQ wrote: Why haven't you re-flashed the first image back so you have a failsafe again?

That would be the rational thing to do. But the damn thing gave me a heart attack when it pulled that stunt on me (it wasn't my system) so I decided not to mess with it anymore :oops:

To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. ( IRIS 4D/70 Superworkstation Technical Report )

jan-jaap
Who joined June 17, 2004, 10:35 a.m.
and authored 3591 notes

Wrote on the subject of PMC RM7000C-600T CPUs on ebay at Oct. 9, 2009, 12:43 a.m...

mapesdhs wrote:

PS. I have a slightly different theory. I don't think they even have the PROM source anymore.

That code is closely related to the IRIX kernel code, and some bits are shared between kernel and PROM. I don't think they lost it, but I understand they have issues releasing it

mapesdhs wrote:

mattst88 wrote:

Beyond that, I doubt the own all the PROM source.

Since it's proprietory code, why not?

Propriety has little to do with it. If part of the PROM code is licensed by SGI from a 3rd party, they don't own the copyrights and they they cannot just release it without permission. In the case of the PROM code one such party is almost certainly MIPS. The first CPU boards in the Professional Series were basically OEMed from MIPS, including the PROM, and later IPxx boards were derived from those.

But unfortunately you're certainly right when you say this isn't happening. They will bury every last bit of it, and the IRIX code, rather than releasing it. Sad but true.

ShadeOfBlue wrote:

How about disassembling the PROM, rewriting the CPU initialization code and then reassembling it?

I did that for some of the early systems like IP7 and IP12 and it is a monumental task. There is little reward because you cannot publish your results. I did it because I wanted to learn about the PowerSeries at the very lowest level.

99% of the PROM was originally written in C, so it's not just a matter of disassembling, you basically have to rewrite the matching C code. For a later, much more sophisticated system like an O2, it's not something I would consider doing.

Oh, and I no longer have a computer with the IDApro license, so while I still have the IDA data files they are now useless

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Original SGI list prices... at Oct. 15, 2009, 8:11 a.m...

dc_v01 wrote:

mapesdhs wrote: Never ceases to amaze me how much extra RAM costs in original pricing.

I hadn't paid attention - over $20,000 a gigabyte!

Pffft. In 1991, the list price for 24MB of RAM for a PowerSeries was 30.200DM, and the exchange rate was 0.61:1 (so $18.422). That's $768.000 per gigabyte.

My 4D/380VGX, 4D/440VGX and Crimson RE each have the maximum 256MB installed ...

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Who joined June 17, 2004, 10:35 a.m.
and authored 3658 notes

Wrote on the subject of Octane / Dual Head at Oct. 15, 2009, 12:20 p.m...

GeneratriX wrote:

And now?

Now you need to go fix the lightbar of your Octane. That, or the photo is tricked

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Piranha HD 3.6 Trial, anyone still has it? at Oct. 21, 2009, 7:02 a.m...

I have that download. Also the video tools.

To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. ( IRIS 4D/70 Superworkstation Technical Report )

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2688 notes

Wrote on the subject of Octane2: 2x600MHz R14000, V12, 8GB of RAM at Oct. 21, 2009, 8:13 a.m...

eMGee wrote:

With a PCI card cage and three internal SCSI disks in the bays installed by the looks of it, you could run that in [software] RAID5 if you wanted to.

IRIX doesn't do software RAID5, and I wouldn't recommend installing Linux on such a nice system :lol:

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Oct. 23, 2009, 1:28 a.m...

zuluchas wrote:

nv ram checksum incorrect, check with printenv and fix with 'setenv ENV_VAR'
where ENV_VAR is a non-volatile environment variable such as bootmode

Wow, I've never seen a PowerSeries with a dead NVRAM battery, but it seems it can happen after all.
The battery is on the the IO2.

But maybe a 'resetenv' and running the beast for a while does the trick.

zuluchas wrote:

I have also connected the same serial adapter to the serial port on one of the GM. It prints out a sequence of POST messages and concludes with:

Code:

GM PROM diags PASSED.

It prints this series of messages twice, actually, on first power-up. Then it presents a prompt-looking "gm>" but doesn't take any input.

I think I managed to get some limited interaction with it once but it's a long time ago. It's not very useful.

zuluchas wrote:

The LED status digit near the front power switch alternates between 1 and 2 continuously. This is normal while in PROM, right?

Correct.

zuluchas wrote:

There's no keyboard attached, so I expect the no keyboard and gfx(0) errors. All the other diagnostics seem to pass, but I'm experiencing two problems:
1) I am unable to enter anything into the terminal -- it doesn't accept or respond to any input over the VT.

You probably missed a wire in the adapter cable. With communication working the other way, I would guess you've got it set for 9600/n/8/1.

zuluchas wrote:

2) When plugging in a monitor using the primary graphics output, I'm presented with a garbled, black and white console screen which echoes the output on the serial port. You can almost make out what's on the screen, but clearly there's some thing wrong with the graphics subsystem.

Looks like a version of the infamous 'pinstripe of death'. Either that, or you need to reseat the boards, and especially the bridge board connecting the RM's and DG at the front. Unfortunately, GTX graphics seem to all suffer from the infamous pinstripe now. I haven't seen a working set in years.

zuluchas wrote:

I have a couple old SGI keyboards from this era, and am planning to make a keyboard adapter as well. But beyond that, I'm not sure where to begin troubleshooting the console and graphics issues. I hope it's salvageable! The lack of SGI documentation is unfortunate -- or can anyone point me to a reference more specific than This Old SGI (which is excellent but doesn't have a lot of detail about this system and the options available)? Are there scans of the original docs somewhere?

I have an "Owners Guide" for a PowerSeries, but it's not very in depth. You weren't supposed to mess with these systems, you were supposed to call SGI. "This old SGI" has more information than the manual. I've got a PDF of the Crimson Field Service Handbook, but once again, not much.

If you install IRIX 5.3 on it, the "Diagnostics 5.3" CD might be able to find the problem. PM me about that one once you're ready. But I'm pretty sure it will tell you there's a problem with one of the RMs

zuluchas wrote:

Also, is http://sgistuff.g-lenerz.de/ down or is it just me? (I just get a "500 Internal Server Error" message.)

Yeah, Gerhard is having some issues with his current hoster and is moving to a new domain.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Noise - Indigo2 vs Octane and Fuel at Oct. 23, 2009, 4:59 a.m...

The user manual of each system should tell you how much noise it makes.

A couple of reasons why people have different opinions:

* Wear and tear. Fans make more noise when they wear out. If you happen to have a system which ran non-stop for several years, especially in a room with smokers, it will be more noisy. Similarly, a dirty fan makes more noise than a clean one.

* Position of the system vs. the user. You will think the Octane sitting on the desk next to the monitor is louder than a Fuel on the floor.

* Vibration. Depends on the floor the system is on.

* Perception. Personally, I find the Fuel the most annoying of the bunch. This is not because the amount of noise it makes, but because the pitch of the noise varies almost continuously as it adjusts the fan speed. It is almost like it is singing a tune. The Fuel also contains a couple of small fans in front of the graphics, where Octane and Indigo2 contain only fairly large fans. These systems 'hum', the Fuel has a higher pitched noise.

Oh: you don't want to be in the same room with an Octane in 'fastfan' mode. It's louder than an Onyx2 (untill the Onyx2 goes into 'fastfan', of course

)

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Oct. 24, 2009, 5:02 a.m...

dexter1 wrote:

Where is the GM2 BTW?

My thought exactly. But since he's gout output on the screen he probably forgot to list it.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Oct. 26, 2009, 2:10 a.m...

FWIW: This system is old enough that it requires a CD-ROM drive with a special firmware which basically mimics a harddisk when first powered up. It is usually marked "P6-CDROM". This one isn't. If you put a generic SCSI CD-ROM in, you won't be able to boot the system from it.

Second: the board in the "stackable" drive module looks like a Y-junction in the SCSI chain. But that's not how SCSI works. SCSI is a chain, terminated at both ends.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Cool (open source) software you would like to see ported... at Oct. 27, 2009, 5:32 a.m...

ramq wrote:

I'd love to see 'fwdl' from this guy:
http://www.tc.umn.edu/~erick205/Projects/index.html

It should compile without too much hassle under IRIX

It seems it wants to talk to a PRISA FC adapter on IRIX:

README wrote:

'fwdl' is a program which will download firmware to a Seagate Fibre Channel disk drive. The program currently only works with drives attached to a Prisa Networks NetFX adapter on Silicon Graphics systems, drives attached to Sun Microsystems workstations, or drives attached to a Linux-based workstation.

And it probably needs some PRISA headers too:

Code:

  $ make prisa
  
  CC -n32 -mips3 -O2 -o fwdl -Dsgi -DDEBUG fwdl.C fwdl-prisa.C \
  
  -lfcp
  
  fwdl.C:
  
  cc-3968 CC: WARNING File = fwdl.C, Line = 424
  
  implicit conversion of a 64-bit integral type to a smaller integral type
  
  (potential portability problem)
  
  fwSize = fwStats.st_size;
  
  ^
  
  fwdl-prisa.C:
  
  cc-1005 CC: ERROR File = fwdl-prisa.C, Line = 44
  
  The source file "nport.h" is unavailable.
  
  #include <nport.h>
  
  ^
  
  1 catastrophic error detected in the compilation of "fwdl-prisa.C".
  
  Compilation terminated.
  
  make: *** [prisa] Error 2

The alternative targets are 'sun' and 'linux' and those give many, many errors.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Personal Iris 4D/35 R3K 36MHz 48Mb at Nov. 2, 2009, 5:01 a.m...

Nice one, with Turbo option even!

Better make sure the main system fan and the little fan in the electronics unit are in good working order, or the thing will cook itself before you know it.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Another IRIS 4D in trouble... at Nov. 2, 2009, 6:39 a.m...

Hi Gerhard,

The system is taking an exception, and the 'cause' register tells you the reason you're in the exception handler:

Code:

Cause register: 0x30001008<CE=3,IP5,EXC=RMISS>

RMISS means a 'read TLB miss', usually this means there's an error reading the memory address.
In other words: time to reseat / remove / swap around the memory sticks

Gerhard.Lenerz wrote:

Code:

exit(-1) called

[...]
Anyone got an idea what is wrong? I believe the machine is still doing POST as the LED shows "D" while the error is showed again and again and again.

If the PROM calls 'exit()' it resets the system. Of course, it will hit the same error and everything will happen all over.

Gerhard.Lenerz wrote:

On a brighter note, good old 'boromir' (4D/420VGX) is doing just fine. Despite the bent chassis and the wrong skins.

Those skins used to be on my 4D/210GTX, no? My own 4D/440VGX has also started to act up. It looks like a glitch in the power resets the system after a couple of minutes. Looks like I'll have to get familiar with the PowerOne PSU's again this winter

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Another IRIS 4D in trouble... at Nov. 3, 2009, 8:22 a.m...

dexter1 wrote:

Could it be a loose contact somewhere? Maybe the main switch? My Crimson suffered from a Main switch that didn't made fully contact and issued a reset every now and then. Replacing it with a new one solved the problem immediately

I can try, I think I have a spare breaker and a front panel with on/off switch for a 4D deskside. It's certainly easier to try than removing the PSU.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of eBay: Iris Crimson at Nov. 4, 2009, 12:51 a.m...

The product code is W6-CRIMEG , which according to my documentation means R4000 CPU, 16MB of low density RAM and Elan graphics.
Whether it's still complete, or maybe even upgraded, is anybody's guess.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Who joined June 17, 2004, 10:35 a.m.
and authored 3657 notes

Wrote on the subject of Show Off Your Home Office Setup & SGI Collection... at Nov. 4, 2009, 1:01 a.m...

indyman007 wrote:

sybrfreq, What kind of keyboard is that?

Looks like a modded C64 :lol:

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Mystery Crimson VME board at Nov. 5, 2009, 1:02 a.m...

R-ten-K wrote: That looks like a serial or FDDI concentrator board.

I've never looked inside an FDDI concentrator, but the VME FDDI board for Iris 4D's (a rebadged Interphase V/FDDI 4211) looks like this:

wolflord wrote: HIPPI board maybe? First spec for that was a 50 wire TP cable according to wikipedia....

I think so too. And Performance Technologies used to make them. That was when HIPPI was still called something else (turbo net?). I had spotted this board on eBay months ago, but the lack of drivers, bulkheads, or a system to connect it to stopped me from buying one of them.

At least you've got yourself a VME 6U-9U adapter

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of FS: Onyx2 IR2E [NL-EU] at Nov. 5, 2009, 1:32 a.m...

Looking at my collection of boards, I realized I might as well assemble and sell a complete Onyx2. I can basically build to order

I'll give you an idea of what I have:
* several dual R10K@195MHz nodeboards.
* one dual R12K@300MHz nodeboard.
* lots or RAM in 256MB and 512MB kits

Infinite Reality 2E graphics, so:
* GE16-4
* One or two RM9-64 raster managers.
* DG5-8 or DG5-2/GVO

* A DIVO board (dual SDI video I/O) if you wish.
* Plus everything else that makes a working system, such as the chassis, fan tray, PSU, IO6G, system controller, harddisk etc.

This is the "rackmounted deskside" version, so it looks like this:

Price depends on configuration, but I'm not unreasonable. Remark: the DG5-8 has funny colors on channel#7 and therefore fails irsaudit. The other channels work just fine.

Location is The Netherlands, but not far from the German border.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Mystery Crimson VME board at Nov. 5, 2009, 6:13 a.m...

pentium wrote: I thought HPPI was just another version of FDDI?

Certainly not.

FDDI is a network technology, like ethernet (or ATM). If you want to know about FDDI, read this: http://www.siliconsamsara.org/OLD/PracFDDI/index.html
I don't know much about HIPPI, but I do know it's not FDDI. I think HIPPI is (was ?) mostly used as a point-to-point interconnect, like infiniband.

HIPPI is a parallel interface using copper wiring, FDDI is a serial interface with a fiber optic transport.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Another IRIS 4D in trouble... at Nov. 5, 2009, 3:15 p.m...

jan-jaap wrote:

dexter1 wrote:

Could it be a loose contact somewhere? Maybe the main switch? My Crimson suffered from a Main switch that didn't made fully contact and issued a reset every now and then. Replacing it with a new one solved the problem immediately

I can try, I think I have a spare breaker and a front panel with on/off switch for a 4D deskside. It's certainly easier to try than removing the PSU.

I'll be damned. I changed both the breaker on the back and the on/off switch panel on the front, and at least for the time being it's working beautifully

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Another IRIS 4D in trouble... at Nov. 6, 2009, 5 a.m...

dexter1 wrote:

Awesome, Jan-Jaap! This is exactly why i really love these old systems: Using soldering iron, steel file and pliers you can repair these machines very quickly.

True, but in this case I just used parts from another PowerSeries I scrapped at some point.

I suspect the problem was caused by the switch on the old front panel and will probably replace that, if only to keep my supply of spares intact. And no, that doesn't even require a soldering iron :mrgreen:

As an extra bonus, it then successfully passed all the VGX diagnostics, so it can celebrate it's 18th birthday in good health.

Next I'm going to make a little adapter for my CrystalEyes 3D glasses. Performer/Inventor grab all 4 CPUs so the 4D/440 does quite well. I love messing with these old systems

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of Another IRIS 4D in trouble... at Nov. 17, 2009, 5:52 a.m...

jan-jaap wrote:

I'll be damned. I changed both the breaker on the back and the on/off switch panel on the front, and at least for the time being it's working beautifully

Bah, the problem returned. :evil:

Must be in the PSU after all...

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2688 notes

Wrote on the subject of Optimum O2 recording settings at Dec. 21, 2009, 9:28 a.m...

http://lurkertech.com/lg/

Uncompressed SD video is ~ 25 MB/s or so.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Dec. 22, 2009, 4:10 a.m...

dexter1 wrote:

I'm sure JanJaap knows this.

Uhhhh

dexter1 wrote:

from the 4dfaq it states that you cannot mix 2mb and 8mb on an MC2.

There was a link to my adventures with a Crimson in this thread. It worked there, but a Crimson doesn't have an MC2.

I already promised the OP to check out my systems. I also have a couple of MC2's in storage. Another possibility is the firmware he has on the IP5, which is not exactly the latest version.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Dec. 23, 2009, 6:31 a.m...

Here's what I have:
* The 4D/380 has an MC2 030-0117-010 rev A, with 32*8MB SIMMs installed.
* The 4D/440 has an MC2 030-0117-034 rev C, with 32*8MB SIMMs installed.

MC2's in storage:
1 * 030-0117-034 rev B (with 32*2MB SIMMs installed).
2 * 030-0117-026 rev A.
1 * 030-0117-009 rev A.

So, my both MC2s with high density RAM are a newer rev. than yours. Unfortunately, this doesn't offer conclusive proof whether the older card is should support high density RAM.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Dec. 24, 2009, 3:15 a.m...

I can do that, but I'm not sure there's a lot to be learned from this exercise:

* If 8MB SIMM support was added to some MC2 rev, it must have been rev -010 or earlier. After all, it works in the Predator (030-0117-010 rev A). So the -034 and -026 boards will support it as well.

* The earliest specimen I have is the -009 board in storage. I could try that one, but if it works, it still does not give conclusive proof whether your problem is due to your even older MC2 rev, or your older IP5/IO2 PROM revision. Only if the -009 board works with 2MB SIMMs but not 8MB SIMMs do we learn anything.

Something else: "This old SGI" says the SIMMs have to be installed in banks of 4 . You did not mix two 2MB and two 8MB SIMMs in one bank, did you? Oh, and unlike what "This old SGI" may suggest, an MC3 belongs in an Onyx, not in a PowerSeries

I have dumps of the IP5 and the IO2 PROMs, but these were created by dumping the relevant address range on the system itself, not by pulling the EPROM chips out and reading them in in an EPROM burner. So, I have one file for the IP5 PROM but in reality it's 4 chips and I wouldn't know how to split the data and create 4 new chips. Same for he IO2 PROM.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Rebirth of my O2...(I'm baaaaaaack, anyone remember me?) at Jan. 6, 2010, 2:24 a.m...

I want a Tezro. Then I'll have both

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Rebirth of my O2...(I'm baaaaaaack, anyone remember me?) at Jan. 7, 2010, 1:58 a.m...

voidfoo wrote: I got a baby girl too. She is about 7 month old so still no time to play with O2/Octanes in near future.

Ga53n wrote: I had to free some space and time before our son arrived, so I got rid of my trusted O2, which is am still kind of sad about.

I can understand space issues, but don't these babies sleep in the evening? Our 14 month old son goes to bed ~ 19:30 which leaves another 3 or 4 hours before I go to bed myself. All you have to do is say 'no' to the TV, but there's rarely something worth watching anyway.

My weekends are reserved for the family.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Jan. 28, 2010, 2:32 a.m...

zuluchas wrote:

I've tried the following configurations which prove that you can mix 8MB and 2MB simms on an IP17 board:

8x 8MB + 8x 2MB, recognized as 80MB, installed in identical sets of eight, one adjacent pair per bank, populated from the LED side of the board.

Yeah, I ran my first Crimson for a couple of years like this.

zuluchas wrote:

This is with PROM revision 4.0.3 IP17,

AFAIK, there is only one PROM revision for IP17, and it's on both the 100 and 150MHz boards

zuluchas wrote:

So here goes: there are four contacts that are easy to get to on the top of the Dallas chip assembly, which I've labeled A, B, C, and D in red. The top diagram is borrowed from the modern DS1216B datasheet and may help illustrate what we're looking at. Here are the measured potential differences across the contacts:
C to A: ~ +58 mV
D to A & B to A: ~ +95mV
everything else zero.

Can we see this diagram? Do I get this right, can we rebuild this battery backup using a suitable coin cell, a socket, some hot glue and maybe some soldering? In that case I like this better than the dremeling required for later Dallas parts. I still have working IO2's and IO3's, if it helps I can remove a battery/socket assembly and measure the voltages.

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2689 notes

Wrote on the subject of 4D/240GTX troubleshooting at Jan. 29, 2010, 3:46 a.m...

rscottdrysdale wrote:

now prepare for the joys of non-Y2K compliant clock chips - you're on your own there!!!

Amazingly, my PowerSeries (4D/380, 4D/440) know about post Y2K years, but the Crimson doesn't.

As long as you run a Y2K patched OS (IRIX 5.3) on them there are no issues with the old 4Ds. On IRIX 4.x and older, the day of the week doesn't match the date post Y2K :lol:

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Old Salt
Who joined June 17, 2004, 11:35 a.m.
and authored 2688 notes

Wrote on the subject of Octane V8 R14K 550MHz 2GB at Feb. 1, 2010, 1:57 a.m...

The processor part# is 'PM10600MHZ'

Does that make the 550MHz module an underclocked 600MHz? An attempt to improve yields by underclocking CPUs that fail at their nominal speed?

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum: almost every MIPS/IRIX system.

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Challenge L, 6*R4x00, 1GB, HIPPI at Feb. 2, 2010, 2:59 p.m...

Picked up last weekend:

Code: Select all


   IRIS 1# hinv
   

   Processor 0: 250 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 6.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   Processor 1: 250 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 6.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   Processor 2: 250 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 6.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   Processor 3: 250 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 6.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   Processor 4: 100 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 4.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   Processor 5: 100 MHZ IP19
   

   CPU: MIPS R4400 Processor Chip Revision: 4.0
   

   FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
   

   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: 1 Mbyte
   

   Secondary unified instruction/data cache size: 1 Mbyte
   

   Data cache size: 16 Kbytes
   

   Instruction cache size: 16 Kbytes
   

   Main memory size: 1024 Mbytes, 2-way interleaved
   

   I/O board, Ebus slot 5: IO4 revision 1
   

   Integral EPC serial ports: 4
   

   Integral Ethernet controller: et0, Ebus slot 5
   

   EPC external interrupts
   

   Integral SCSI controller 4: Version WD33C95A, differential, revision 1
   

   Integral SCSI controller 3: Version WD33C95A, differential, revision 1
   

   Integral SCSI controller 2: Version WD33C95A, differential, revision 1
   

   Integral SCSI controller 1: Version WD33C95A, differential, revision 0
   

   Disk drive: unit 1 on SCSI controller 1
   

   Integral SCSI controller 0: Version WD33C95A, single ended, revision 0
   

   CDROM: unit 4 on SCSI controller 0
   

   HIPPI adapter: hippi0, slot 5 adap 6, firmware version 27161144
   

   Integral EPC parallel port: Ebus slot 5
   

   VME bus: adapter 0 mapped to adapter 21
   

   VME bus: adapter 21
   

   IRIS 2#

I picked up a Challenge DM as well. When I'm done with this box it will have 12*R10000 w. 2MB L2 and 2GB RAM. So this is a work in progress. I rearranged the RAM a bit to improve interleaving, and to get some confidence wanted to run the diagnostics. I get:

Code: Select all


   IRIS login: diag
   

   Password:
   

   IRIX Release 6.2 IP19 IRIS
   

   Copyright 1987-1996 Silicon Graphics, Inc. All Rights Reserved.
   

   Last login: Tue Feb  2 13:28:21 PST 2010 on ttyd1
   

   TERM = (vt100)
   

   CPU: MIPS R4400 Processor Chip Revision: 4.0
   

   CPU: MIPS R4400 Processor Chip Revision: 4.0
   

   *********************************************************************
   

   *** DETECTED DOWNLEVEL 100 Mhz R4400 PROCESSOR CHIP REVISION: 4.0 ***
   

   ***  ON THIS SYSTEM WHICH NEED TO BE UPDATED.                     ***
   

   *** PLEASE LOGIN AS ROOT AND EXECUTE HINV TO SEE WHICH PROCESSORS ***
   

   ***  ARE DOWNLEVEL AND UPDATE THOSE PROCESSORS.                   ***
   

   *********************************************************************

There's a HIPPI board installed, I was wondering why it was in a 'wrong' slot (not VME) until I put it in the right slot -- and now the front doesn't close anymore

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Challenge L, 6*R4x00, 1GB, HIPPI at Feb. 3, 2010, 4:15 a.m...

josehill wrote:

Indyboy wrote: Is it possible to use more than 4 cpus (1 nodeboard) in a Challenge DM?

I think jan-jaap was talking about getting the Challenge L up to 12 cpus. A Challenge DM can only go up to four cpus.

Indeed. My intention is to transform the 'L' into the ultimate build system for old IRIX versions: running IRIX 5.3 with 12 R4400's or IRIX 6.2 with 12 * R10K's (with 2MB L2!). I already had two quad R10K IP25's, one in my Onyx, one as a spare. Now, with the 'DM' I got number three. In the 'L' was a quad 250MHz IP19, and again I had one already plus a quad 200MHz.

I'm currently just taking inventory of what I picked up, what works and what not, board revisions etc. Tonight I'll pull the 'downrev' IP19 and run diagnostics on this system, them I'll move on to the DM.

I'm kind of curious where the built-in limitation (single CPU board) of the DM is hiding -- backplane? system controller?

I have no intention to keep both systems around. If someone wants the Challenge DM, I can probably create a working system from the dual CPU board. Otherwise I'll dismantle it and keep all the power bricks, system controller and boards as spares / donors.

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Challenge L, 6*R4x00, 1GB, HIPPI at Feb. 3, 2010, 12:01 p.m...

zackwatt wrote: Pics Please!

I took off the skins before transporting it, I will clean them before I put them back on. I just put the front door on so my 15 month old son doesn't hurt himself on the sheet metal. Not that he cares about it, there are no buttons to press or beeping noises :mrgreen:

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Challenge L, 6*R4x00, 1GB, HIPPI at Feb. 4, 2010, 2:37 p.m...

The Challenge DM is also back! It has two IO4's; I had to swap them because the NVRAM on the primary has died and this freaks out the system.

Code: Select all


   IRIS 1# hinv -v
   

   CPU Board at Slot 2: (Enabled)
   

   Processor 0 at Slot 2/Slice 0: 194 Mhz R10000 with 2 MB secondary cache (Enabled)
   

   Processor 1 at Slot 2/Slice 1: 194 Mhz R10000 with 2 MB secondary cache (Enabled)
   

   Processor 2 at Slot 2/Slice 2: 194 Mhz R10000 with 2 MB secondary cache (Enabled)
   

   Processor 3 at Slot 2/Slice 3: 194 Mhz R10000 with 2 MB secondary cache (Enabled)
   

   CPU: MIPS R10000 Processor Chip Revision: 2.6
   

   FPU: MIPS R10010 Floating Point Chip Revision: 0.0
   

   Secondary unified instruction/data cache size: 2 Mbytes
   

   Data cache size: 32 Kbytes
   

   Instruction cache size: 32 Kbytes
   

   Main memory size: 1024 Mbytes, 4-way interleaved
   

   MC3 Memory Board at Slot 1: 512 MB of memory (Enabled)
   

   Bank A contains 16 MB SIMMS (Enabled)
   

   Bank B contains 16 MB SIMMS (Enabled)
   

   Bank C contains 16 MB SIMMS (Enabled)
   

   Bank D contains 16 MB SIMMS (Enabled)
   

   Bank E contains 16 MB SIMMS (Enabled)
   

   Bank F contains 16 MB SIMMS (Enabled)
   

   Bank G contains 16 MB SIMMS (Enabled)
   

   Bank H contains 16 MB SIMMS (Enabled)
   

   MC3 Memory Board at Slot 3: 512 MB of memory (Enabled)
   

   Bank A contains 16 MB SIMMS (Enabled)
   

   Bank B contains 16 MB SIMMS (Enabled)
   

   Bank C contains 16 MB SIMMS (Enabled)
   

   Bank D contains 16 MB SIMMS (Enabled)
   

   Bank E contains 16 MB SIMMS (Enabled)
   

   Bank F contains 16 MB SIMMS (Enabled)
   

   Bank G contains 16 MB SIMMS (Enabled)
   

   Bank H contains 16 MB SIMMS (Enabled)
   

   I/O board, Ebus slot 4: IO4 revision 1
   

   I/O board, Ebus slot 5: IO4 revision 1
   

   Integral EPC serial ports: 4
   

   Integral Ethernet controller: et0, Ebus slot 5
   

   EPC external interrupts
   

   Integral SCSI controller 41: Version WD33C95A, differential, revision 0
   

   Integral SCSI controller 40: Version WD33C95A, differential, revision 0
   

   Integral SCSI controller 1: Version WD33C95A, differential, revision 0
   

   Disk drive: unit 1 on SCSI controller 1
   

   Integral SCSI controller 0: Version WD33C95A, single ended, revision 0
   

   CDROM: unit 4 on SCSI controller 0
   

   Integral SCSI controller 44: Version SCIP/WD33C95A, differential
   

   Integral SCSI controller 43: Version SCIP/WD33C95A, differential
   

   Integral SCSI controller 42: Version SCIP/WD33C95A, differential
   

   CC synchronization join counter
   

   Integral EPC parallel port: Ebus slot 4
   

   Integral EPC parallel port: Ebus slot 5
   

   VME bus: adapter 0 mapped to adapter 21
   

   VME bus: adapter 21
   

   IRIS 2#

Next, I'm going to install a second IP25. This should fail on a genuine DM, but I cannot find any difference between the system controllers of the DM and the L The L booted fine with the system controller of the DM, with 8 CPUs installed ...

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

jan-jaap
Donor
From Wijchen, The Netherlands
Who joined June 17, 2004, 11:35 a.m.

Wrote on the subject of Challenge L, 6*R4x00, 1GB, HIPPI at Feb. 5, 2010, 12:28 p.m...

Booted the 'DM' with a second IP25 this evening, and got:

Code: Select all


   >> hinv -b
   

   

   System Bus Information:
   

   Slot 1: MC3 memory board with 512 megabytes of memory (Enabled)
   

   Slot 2: IP25 processor board with 4 cpus (Enabled)
   

   Slot 3: IP25 processor board with 0 cpus (Enabled)
   

   Slot 4: IO4 I/O peripheral controller board (Enabled)
   

   Slot 5: IO4 I/O peripheral controller board (Enabled)

The '0 cpus' raised my blood pressure for a moment (as did the B+++ text on the LCD), but it turns out both IP25's work fine as long as they are in slot 2.

Guess I have to look again at what limits the DM ... but I have many other things to do so this project will be suspended for a short while.

Oh, and I tried again with the system controller of the Challenge L -- same result. Will have to inspect the backplane ...

Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

The collected works of jan-jaap - Page 5