The collected works of snowolf

I finally gave this puppy a proper name. I'm planning to max out the memory but 6.5.22m seems to run decent even on 128MB. If there's any interest, I'll look into taking some pictures of it.

Code:
shodan 1# hinv -mv
CPU: MIPS R4400 Processor Chip Revision: 5.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 150 MHZ IP20 Processor
Main memory size: 128 Mbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Instruction cache size: 16 Kbytes
Data cache size: 16 Kbytes
Integral SCSI controller 0: Version WD33C93B, revision C
Disk drive: unit 1 on SCSI controller 0 (unit 1)
On-board serial ports: 2
On-board bi-directional parallel port
Graphics board: GR2-Elan
Integral Ethernet: ec0, version 1
Iris Audio Processor: revision 10

Code:
shodan 2# /usr/gfx/gfxinfo
Graphics board 0 is "GR2" graphics.
Managed (":0.0") 1280x1024
4 GEs, 1 RE, 24 bitplanes, 4 auxplanes, 4 cidplanes, Z-buffer
GR2 revision 2, VB1.1
HQ2 rev A, GE7 rev B,  RE3 rev D, VC1 rev B, MC rev C
19" monitor

Code:
shodan 3# uname -a
IRIX IRIS 6.5 10070055 IP20
shodan 4# cc -version
MIPSpro Compilers: Version 7.4.4m

_________________
:Indigo: :Octane: :PI:
jan-jaap wrote:
Nice classic :)
snowolf wrote:
I'm planning to max out the memory

Since you ave a rev. "C" MC chip, you can. Otherwise it would start to complain when you install more than 256MB.


Oh cool; I wasn't aware. I really got lucky with this machine. :)

_________________
:Indigo: :Octane: :PI:
I don't have a lot of time, equipment (I only have an Indigo and a really low-end, early Octane) or experience porting software to IRIX. However, the MIPS-3 Nekoware repository seems a little neglected, so I am going to do what I can to contribute and help bring it up to date.

Packages:
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_expat-2.0.1.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_libiconv-1.13.1.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_ncurses-5.7.tardist (Missing .idb file)
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_pkgconfig-0.23.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_sdl-1.2.14.tardist (I was able to compile NeHe's Lesson 5 successfully -- very cool!)
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_aterm-1.0.1.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_autoconf-2.65.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_glib-2.22.5.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_irssi-0.8.15.tardist
http://forked.subprogr.am/snowolf/irix/neko-mips3/neko_m4-1.4.14.tardist
Please let me know if there's any sloppiness and I'll rebuild the package.

These packages are in progress:
screen-4.0.3
bash-4.1
dosbox-0.74 (Having a lot of problems with this one)

I'm certain this question has been asked before, so forgive me but is it possible to have my Octane cross-compile for the MIPS-3 architecture? My guess is: "Yes, but it's painful."

Thanks!

_________________
:Indigo: :Octane: :PI:
vishnu wrote:
IIRC to cross-compile you can use the -TARG: argument but for mips3 I think it's as simple as cc -mips3 (???)


Right; there are compiler options that will need to be set but my concern was more the MIPS-3 flavor libraries I imagine most software will need to compile against and setting that up on the build machine. I would also like to know people's general experience cross compiling between MIPS-3 and MIPS-4.

_________________
:Indigo: :Octane: :PI:
nekonoko wrote:
If you'd like these added to the MIPS3 collection, drop them in /incoming on FTP and I'll move them over to the beta directory. They'll get soaked up on the mirrors that way.


Well, I feel these are at a pre-beta stage. I would prefer at least one other person besides me to test and verify them before they go into the beta directory to make sure there isn't anything obvious I missed. I'm fairly new to Irix and even newer to MIPSPro and packaging software.

How much interest is there in getting the MIPS-3 repository up to date anyway? Have the MIPS-3 equipped SGI machines moved into obsolescence and novelty even for Nekochan?

_________________
:Indigo: :Octane: :PI:
A friend of mine has one sitting in the corner of his office collecting dust for at least the last decade. I haven't spoken to him in a while and I think he's attached to the machine nevertheless but I could at least ask about it.

_________________
:Indigo: :Octane: :PI:
Dragongolfer wrote:
Snowolf could you ask if its not to much trouble?

Will do.

_________________
:Indigo: :Octane: :PI:
SAQ wrote:
For the most part (provided makefiles are done right) there isn't a problem. The libraries are the same as far as the linker goes - it happily links away to whichever version is installed on the target machine (many IRIX 6.5 system libraries are MIPS-3 anyway, so it doesn't matter). I build -mips3 -n32 on a O2k (when it's running, need to get it uncovered but haven't had the time) for my MIPS3 builds and my only problem with arch diffs so far has been one file where -mips4 was hardcoded in the makefile and had to be patched.


Ok, interesting. Guess I'll look into setting up my Octane as a build machine this weekend. This also gives me an excuse to start looking for a nice Octane2 :mrgreen:

_________________
:Indigo: :Octane: :PI:
Just added a bunch of packages to the list. I'll upload them into /incoming some day...

_________________
:Indigo: :Octane: :PI:
Very cool! Is the source code available by any chance? :]

_________________
:Indigo: :Octane: :PI:
Just picked up one of these locally today. There is no hard disk or hard disk caddy so I'm going to have to find both. Nevertheless, here is the hinv (from console) and a few bad pictures I took with my Macbook. You cannot see it, but there's a fair amount of rust and a lot of dirt/dust and dead spiders. I don't know a whole lot about these machines and have yet to take this thing apart so more to come later. It does have a "Property of the University of Arizona" sticker on it.

Code:
>> hinv
Memory size: 72 Mbytes
Instruction cache size: 64 Kbytes
Data cache size: 64 Kbytes
Graphics: GR1.2
Auxiliary Planes Option
Medium Resolution Monitor
Bitplane Expansion Option
Z-Buffer Option
SCSI Tape: QIC-150 tpsc(0,2)
CPU board: IP12 36 MHz, with FPU


Image
Image
Image
Image

_________________
:Indigo: :Octane: :PI:
Ryan Fox wrote:

Oh you're going to have a tough time finding a hard drive for this one. Perhaps someone on here might have some spare

Right, I understand they are the same ones used for Crimsons?
jan-jaap wrote:
Nice find. Hope you've got the side panel missing in the photos.

As for the harddisk: I see you've got a QIC150 drive. I'm sure you can mount a harddisk in that sled, using a 3.5" -> 5.25" bracket.

Yes, I have the side panel but removed it so I could plug things in and investigate the condition of the machine. I had not thought about using the QIC150 sled to mount a hard disk but it is a good idea to get things going. Thanks.

_________________
:Indigo: :Octane: :PI:
The other night, my Indigo's power supply let out magic smoke while I was listening to a few mp3s on it and cleaning my room. Some how it kept running, but I flipped the switch to prevent any more damage. It was very upsetting since I really have come to love the thing; thankfully I had a spare PSU. Anyway, I pulled out the bad one and opened it up to look at the damage. It looks like one of the diodes (?) cracked or split open and shorted, causing the component and leads to melt and char a bit.

I think simply replacing the component would give it new life, at least for a few years, but I do not have an EE background -- I know these questions are difficult to answer but would replacing the component be enough? Or is this an indicator of a much bigger problem? What are common points of failures in Indigo power supplies?

Also, after some searching around on this forum, I came across a few very old threads where people mentioned fitting regular AT or ATX power supplies into the Indigo power supply chassis. I am very interested but the website they were referencing appears to be down. Does anyone have a copy of the guide by any chance? And can anyone vouch for this mod?

Thanks!

_________________
:Indigo: :Octane: :PI:
recondas wrote:
There's a couple of PI/Crimson drives <with sled or bracket> currently on eBay. The seller, dhjj , is a nekochan member if you'd like to contact him directly.

Thanks for the heads up.

_________________
:Indigo: :Octane: :PI:
SAQ wrote:
Do you know about where in the supply "chain" the diode was? Since the computer went on running it (if it was really a diode) was probably in a lesser-used rail such as the -12V.

I have no idea where in the supply "chain" the diode was since I don't know anything about electronics. I don't know how familiar you are with the inside of an Indigo 9430812-A power supply but the component that failed is located on the main board, underneath the daughter board, and just below the "Caution: For continued protection against risk of fire..." warning. It may be component CR108. The component itself is cylindrical, black, with a silver band on one end. It has 5352B NT or 5852B NT printed on it; the B may be a 6.

SAQ wrote:
Check out to see if it might have been a tantalum "blasting cap" or a paper cap - these are often used as small filter/ground shunt caps and can fail spectacularly without much additional damage. The tants are either surface-mount boxes or the sort of capacitor that looks a little like a pillow.

Granted, I had my music playing a little loud but I didn't hear a pop that I would expect with a failed cap. I can't seem to find anything charred except for the component described above which looks more like it fried in-place than exploded.

BTW, is it possible this may have been caused by the fact I have the original PM2 heatsink on my R4400 150MHz? I really ought to take the time to replace it with a PM1 heatsink.

japes wrote:
I think this happened to me the other night too.

Bummer, man :[ Indigos are some seriously cool machines; saddens me to hear of any of these guys failing.

_________________
:Indigo: :Octane: :PI:
SAQ wrote:
Definitely a diode. Diodes tend to fail spectacularly for one of two reasons: excessive reverse voltage and excessive current, and in both cases the overload needs to be significant for there to be anything noticeable.

Look very carefully at the caps in that section of the PSU to see if one has failed. A large cap shorting can drag a diode with it easily before going open-circuit, whereas the small caps generally don't need too much juice to burn out a connector wire.

Most PSUs use the diodes in a bridge configuration, so provided that there is enough filter capacitance available it will still look like it's working, but something went bad. Go over that area with a flashlight and magnifying glass.

A big diode near a fuse rating is probably in the main (~320V) section before the choppers/regulators.

The diode that failed is also in close proximity to a cluster of four fairly large caps. Granted, I haven't ripped apart the PSU yet, but there doesn't seem to be anything obviously wrong with them. Could you please tell me a little more about what things I should be looking for?

I think it's time to dust off my copy of the Art of Electronics book :D

Also, a big thanks for your help so far. I really appreciate it :]

_________________
:Indigo: :Octane: :PI:
pentium wrote:
I recently had to help someone else clean up their collection. You think my collecting is bad? This place was a disaster.
Attachment:
100_0601.jpg


Man, that's pretty bad. Reminds me of a friend I had whose studio apartment was packed from floor to ceiling with stuff he had hoarded. It was a really sad situation :[

pentium wrote:
Anyways, It turns out the Compaq has a bad screen. No worries, there is yet another portable 386 that had been uncovered at the place I work. It would be nice if I could swap out the displays and then possibly sell whatever remains for parts.


Anyway, I have one of those lunchbox Compaqs too -- the orange plasma display is really the coolest thing and takes me back to the Kaypro II and WYSE terminals I sat in front of as a kid. I don't know what to do with mine though -- serial terminal? -- so I've been thinking of selling or giving it away.

_________________
:Indigo: :Octane: :PI:
I too want to take the time to say: Thank you all!

I would be lost without such a fantastic community.

_________________
:Indigo: :Octane: :PI:
sybrfreq wrote:
It might be worthwhile to post a picture of the damage. I wouldn't be too surprised if somebody here could tell you exactly what failed just from that.

Agreed. Unfortunately, I don't have a decent digital camera, but I may be able to borrow one. I'll try and get some pictures up by tonight.

Update: Pics aren't happening this weekend; too many things going on.

_________________
:Indigo: :Octane: :PI: