(06-28-2024, 12:49 AM)weblacky Wrote: OK well sorry to keep everyone in suspense. But it looks like the mystery hole just got a little deeper. It turns out that all the cards are in it are one gigantic stack. There are no independent cards, they're all connected together, including the so-called "bottom SCSI card".
It looks like my second statement of that they may have used the SCSI port but maybe it's not SCSI and they instead used it to connect some video option is likely what this is. The stack contains the following numbers however the bottom card has only two references online and there's zero description about what it actually is.
Top-down:
030-8111-004 Rev D -- Galileo Video board (for Indigo2) FHV (D9-GV-TWO) : http://www.bbsolutions.com/sgi/indigo2.html
030-8105-006 Rev C -- (VB2) EXTREME GRAPHICS Board (3-set) : http://www.bbsolutions.com/sgi/indigo2.html
030-8226-002 Rev B -- (RU1) : http://www.megarat.com/indigo/docs/partnumbers.txt
030-8106-005 Rev G -- (GU1) Odd "SCSI-Like" connector on bottom.
As you can see all the fixed with standoffs making them one solid installable block. So I guess all of them are video options as far as I can tell.
I've uploaded additional pictures with the existing files inside the same folder as before: https://siliconimage.irixnet.org/index.p...-Rare-Card
Thanks.
The bottom three cards together make the Extreme graphics boardset. The top one is the Galileo video option.
You can see the individual cards of the Extreme graphics here:
http://www.sgidepot.co.uk/extremegfx.html and they're easily recognized in your pictures.
The slot bracket of the lowest card in the Extreme set is not original. There's nothing major on that PCB close to the slot bracket, just what looks like some RAM chips. My guess: someone externalized the internal SCSI chain, probably coming from whatever is installed in the 5.25" CD-ROM tray. Just follow that cable and see where it goes.
NB: on the topic of "Can we extract installed drivers back into an installable package": if you look in /var/inst, you'll find the product descriptor files of all installed packages, e.g. eoe1, eoe2, ...
There's a tool, I think it's called genspec, probably from the inst_dev package, that will dump the product descriptor into a text form, e.g (a random one from 5.3):
Code:
product efast
id "EFast (Fast Ethernet Board), 5.3"
# product format 5, created Fri Nov 4 12:09:49 1994
image man # (efast.man)
id "EFast Documentation"
version 1021572033 order 625
# format 2
subsys relnotes # (efast.man.relnotes)
id "EFast Release Notes"
exp "!noship && irix_eoe.man.efast_rn"
replaces patch*.efast_man.relnotes 0 1021572032
replaces maint*.efast_man.relnotes 0 1021572032
replaces efast.man.relnotes 0 1021572032
replaces EtherXPress.man.relnotes 0 1021572032
replaces efast.man.relnotes 0 1021572032
endsubsys
endimage
image sw # (efast.sw)
id "EFast Software"
version 1021572033 order 620
# format 2
subsys fxp # (efast.sw.fxp)
id "EFast Software"
exp "!noship && irix_eoe.sw.efast"
replaces patch*.efast_sw.fxp 0 1021572032
replaces maint*.efast_sw.fxp 0 1021572032
replaces efast.sw.fxp 0 1021572032
replaces EtherXPress.sw.fxp 0 1021572032
replaces efast.sw.fxp 0 1021572032
endsubsys
endimage
endproduct
To generate an installable package, you need the payload (installed files), the spec file
and the idb file. That last one would have to be reconstructed. Lacking that one, you're also a bit in the dark about exactly
what was in the installation package to begin with. And if a package was not fully installed (e.g. online books and other non-default parts), they're gone.