The collected works of miod - Page 3

For some reason, I always had dismissed the Intergraph workstations as ``not worth looking at''.

But then, a friend of mine salvaged one and insisted demonstrating it to me. And then I realized (with the help of the manuals on bitsavers) how awesome the Clipper architecture was. Ahead of its time, basically bringing 1990 performance and standards back in 1986 and avoiding most of the pitfalls of the early RISC cpus. Yes, really: although it was designed to compete against VAX, and did not pay attention to the Berkeley RISC designs, the Clipper architecture is a many-registers fast context switch, load/store without interlocks or delay slots, but variable yet predictable instruction length, architecture. As a die-hard 88000 person, it rings many bells and looks to me like what 88000 w/could have been, 3-4 years earlier. And all of this as 33MHz, while Digital as well as Motorola was having a hard time moving from 20MHz to 25MHz...

And now that I have been enlightened, I would like to get my hands on a Clipper-based system, and at least be able to compile and run some code to really feel how good the hardware is.

If you know of such a system in working condition, lacking a good home, preferrably in Europe, please let me know.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
mia wrote:
I do have a Leo/ZX, I used it for several years, but the performances were not there. I remember that the ZX gets REALLY hot.

"hot" is quite an understatement. Sun even sold a special fan assembly to use with the ZX in multiprocessor SS20 to prevent them from melting...

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Ryan Fox wrote:
They might have some of these earlier systems in storage here.. I recall back in 1993 local universities using them.. have to check, but its a long way from France

I'd definitely prefer to find a system in Europe, although I think I'm at least 10 years old too late in my scavenging effort. If that fails, I might be insane enough to consider getting one shipped from another continent (and praying for the monitor not to get damaged during shipping, as these systems are apparently not designed to run with a serial console) ;)

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
SAQ wrote:
OS/2 2.0 provided full 32-bit environment.

<nitpicking>
To be honest, the graphics engine (PMGPI) of 2.0 was still a 16-bit DLL, as the 32-bit rewrite could not be completed in time for the april '92 release. The 32-bit PMGPI shipped from 2.1 onwards.
</ntipicking>

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
SAQ wrote:
Never seen Indigo feet before - were they some sort of marketing thing, or did they serve a purpose (increased stability?)

I think he is referring to purple Indigo2 feets.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
hamei wrote:
I'm not entirely happy with this :
Code:
static XtActionsRec actions [] =
{
#ifdef HAVE_LIBGUILE
{"guile", execute_guile_action},
#endif

#ifdef HAVE_LIBTCL
{"tcl", execute_tcl_action}
#endif

#if 0
{"execute", execute_siod_action},
#endif

{"unspeakable_profanity", NULL}
};


Well, what about something ugly like
Code:
static XtActionsRec actions [0
#ifdef HAVE_LIBGUILE
+ 1
#endif
#if 0
+ 1
#endif
#ifdef HAVE_LIBTCL
+ 1
#endif
] =
{
#ifdef HAVE_LIBGUILE
{"guile", execute_guile_action},
#endif

#if 0
{"execute", execute_siod_action},
#endif

#ifdef HAVE_LIBTCL
{"tcl", execute_tcl_action}
#endif
};

It might work if MIPSPro supports zero-sized arrays. I don't remember if it does.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
duck wrote:
You'd need to add backslashes after the 0 and +1:s to make this trick work

No.

duck wrote:
and you introduce another problem with the exact same cause, if neither of the defines are set, the array is initialized with zero length which is not allowed

I said I did not remember whether MIPSPro did support zero-length arrays...

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Alver wrote:
Colour coding makes life easier by making trivial coding errors (forgot a ", forgot a }) immediately visible. It just saves time.

This is a highly subjective matter which also depends a lot upon the quality of your eyesight.

I am confused by colours in my editor. On the other hand, to help notice missing punctuation quickly, I like using highlighting for matching (or non-matching) delimiters. This catches the eye attention, without confusing the brain with all these random colours.

If you are using vim (preferrably an old version from before it became as bloated as emacs), putting
Code:
set t_Co=0

in your .vimrc (telling vim that your terminal has no colours, but not disabling blink, underline, highlight, mother-in-law-repellent and other "minor" terminal attributes) is all it takes to achieve this.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
crystalfire wrote:
I have wanted one of these systems for years and finally broke down and bought a couple.... now I want more.

That's the expected outcome of being exposed to fine hardware, and nothing to be ashamed or afraid of. :mrgreen:

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
crystalfire wrote:
What I kept seeing was something like;

tftprecv: pkt from server port 65528, not -22

For the record, what does ``version'' show? I am (slowly) trying to find the minimal prom versions which have the tftp port bug fixed, which would likely be 5.2 or 5.3.
I know that
Code:
PROM Monitor SGI Version 5.1 Rev B3 IP24 Sep 17, 1993 (BE)

is affected, while
Code:
PROM Monitor SGI Version 5.3 Rev B10 R4X00/R5000 IP24 Feb 12, 1996 (BE)

and
Code:
PROM Monitor SGI Version 5.3 Rev C IP22 Oct 20, 1994 (BE)

are safe.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
smj wrote: There's an OpenBSD/luna88k port , but it doesn't support the framebuffer as far as I can tell...

It does, except for the ultra-rare 24-bit frame buffer (which is not well supported in Mach either).
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ibara wrote:
It was an easy choice, since I'm the maintainer of the Dillo port for OpenBSD ;)
Keep quiet, or they'll realize we're slowly invading the place! :lol:

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
smj wrote: I would clone the system disk so that my Omron Luna 88k has something to boot from.
<off-topic>
I could give you a raw (dd) image of the 230MB disk my Luna was fitted with when I received it. It's a 3.6ish OpenBSD install; enough to get a newer bsd.rd from the network and install from scratch on a larger disk. I'm afraid I don't have any UniOS material.
</off-topic>
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Mine is fitted with 8x Samsung M312L6423ETS-CB3 - PC2700R-25331-Z (PC2700, DDR1, CL2.5 ECC). Funny enough, on the identification sticker, some of them sport `0410' on the top right corner, while the others sport `0411', but there are no other visible differences.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
jan-jaap wrote: If the scrap value of an Onyx2 is > $300 then there must be more gold in my computer systems than in my wife's jewelry box :mrgreen:

It's never too late to swap'em :mrgreen:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ramq wrote: Wouldn't SS1000(E) be classified as a regular SparcServer (SS) and the SC2000(E) as SparcCenter (SC)?

Yes, that's how Sun used to name them.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
cesss wrote: What (64 bit) single processor board do you think would need less modifications (mainly in number of chips and ASICs) in order to support a larger number of RAM GBs? Possible candidates I think would be the Crimson and the Indigo2, but I don't know how complex is their respective memory logic. The O2 cannot run a 64bit OS, so it doesn't count, just like the Indy.


This can't be achieved on R8K/R10K Indigo2. The memory controller chip could theoretically allow for a huge amount of memory in the last bank, but then physical memory would overlap the fast mode/slow mode cache logic, which addresses are also decoded by the memory controller.

The O2 which you dismiss so quickly, could, with minor changes to the CRIME chip to either support more than 8 banks, or (probably easier to do) more than 128MB per bank. With a modified CRIME, an O2 could use up to 3GB of memory; with even more changes to CRIME, it could allow for more than 32 address lines and thus even more physical memory.

cess wrote: And now... do you think IRIX would be able to use 8GB RAM on a Crimson or Indigo2 if you had such a modified board?

It will likely require changes to be aware of the chip changes as well.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
cesss wrote: I don't think XBow and HEART are documented (although there's an experimental version of Linux for Octane which I believe accesses XBow/HEART, but I don't think this hardware is known in detail enough to be emulated).

The only source of information about these widgets are the IRIX system header files. This gives enough knowledge to be able to eventually emulate Linux or OpenBSD running or Octane or Origin, but definitely not enough to be able to run IRIX.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
SAQ wrote: The only big issue was the heat.

That's what I thought... until the power button mechanism broke on mine. It turns out that the power supply is a bit too small for the case power button to activate the power supply switch, so they put an asbestos plastic guide to connect the case power button to the power supply switch.

That plastic part suffers from the heat like the rest of the machine, and becomes dry and fragile, and eventually breaks after too many power cycles... :x
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ClassicHasClass wrote:
Although when you call it a "classic Indigo" it makes me affraid you're going to try to claim it as your own!


In a totally unrelated line of conversation, does your house have a burglar alarm? Asking for a friend.

In another totally unrelated line of conversation, are you aware of the new regulations requiring a spare key to be conveniently placed under your doormat? :mrgreen:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Awesome! Now all you need is to paint it silver! :-D
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
pruten wrote: One thought is that, if there's a platform-independant integer-based (preferably BSD-licensed) IEEE 754 math library somewhere, I could integrate that into Shoebill and have it be the basis of the FPU on non-Intel platforms.

Have you had a look at John Hauser's SoftFloat library? http://www.jhauser.us/arithmetic/SoftFloat.html
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ClassicHasClass wrote: Having not experienced ElectroPaint in the flesh (I should go put it on the Fuel now), how close is StonerView, since that has both Mac PPC and Classic versions?

You should ask the question the other way around: how close is Stonerview to ElectroPaint.

Having been running both for a long time, I consider the `look and feel' of Stonerview very close to EP. There has been really hard work trying to mimic the behaviour of EP, especially when the tiles switch from a single "ribbon" to 4 or 5 "columns". The colour transitions in Stonerview are slightly off, though. They lack a certain je ne sais quoi only EP has.

Of course this is 100% subjective opinion...
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
dreadbit wrote: Hi,
I have B160L & 715/80 HP 9000 workstations and wondering what kind of memory it wants (currenly both have 128M installed). Sure, it's 72pin parity FPM memory which must be installed in pairs, but everything I tried to plug there led to computers not even get started (ie they power off immidiatly).

Not parity... these systems require ECC simms. Also, the 715/80 will not accept simms larger than 32MB.

dreadbit wrote: UPD: And one more thing I'd like to found out. Those workstations have EISA (and even PCI on B160L). Is it theoretically possible to make HP/UX (I'm running it) to see PC style IDE ISA controller (and drives) plugged there? More, isn't it possible to boot from that?

HP/UX could theoretically use it if you could find a driver for your particular board (preferrably PCI), but don't expect to be able to boot from it.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
dreadbit wrote:
miod wrote: Not parity... these systems require ECC simms. Also, the 715/80 will not accept simms larger than 32MB.

But is it normal behavior for system not even to start? (immediate poweroff)

If the onboard electronics "consider" the situation very bad, yes - at least on the 715.

miod wrote: Why PCI is preferable?

A PCI "Super I/O" card based around a Natsemi PC87560 probably would have the best chance to get recognized and have an HP/UX driver, since this is what was put onboard the later generation (B1000, B2000).
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
smj wrote: technologist/strategist for messaging, collaboration tools, social platforms at a global financial services firm.

That's almost good enough to fill a business loto grid. I hope you made big bucks there!
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
As you might have noticed, there is no obvious response to your question, and the response you'll get will change over time (or, more correctly, would have varied over time, back when SGI was alive and kicking).

My first exposure to SGI hardware was the Indy, but back then my boss had an Indigo2 he was running FrameMaker on, and I was in awe. Then we bought an Octane which was put in the empty office just in front of mine, and everyone dropping by was in awe too (to be fair, most of us were doing remote login work on it), and from then on, I was craving for an Octane.

Yet I got a bunch of Indigo, Indy and Indigo2 systems years before I got my first Octane, and despite the Octanes being much faster, I prefer tinkering with my R10000 Indigo2 and R5000 Indy systems (got some O2 and a Fuel, but they lack some je-ne-sais-quoi).
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
duck wrote: Indeed, Adaptec 2940/3940/3950 are not supported by SRM

*some* are. These are the `U' and `W' cards (e.g. my 164LX boots with SRM off a 2940U). On the other hands, the `U2' cards are not recognized by SRM.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
commodorejohn wrote: OpenBSD has been, in my experience, the free Unix that least makes me want to kill myself.
This is simply because we have become quite good at making our users want to kill our own targets rather than themselves :lol:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Ryan Fox wrote: I tried running OpenBSD on sun blade 2K dual 1200 with xvr1200 graphics and 2GB ram and it sucked worse than running it with OpenSXCE.

The XVR-1200 being a completely undocumented beast, the X server for it is unaccelerated. It's no surprise display is slow, especially when using a wide resolution (such as 1920x1080).
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
commodorejohn wrote: Question, though: is there a way to force the Turbo GX framebuffer to display at a particular resolution/refresh rate?

If it is the primary display, yes; see the cgsix(4) manpage for details. If it is not the primary display, this might be possible with a hairy nvramrc, refer to the Sun frame buffer FAQ for hints.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
dreadbit wrote:
You'll run into trouble with the PCI card being initialised differently (irq/dma/ports) on the systems compared to a PC.


As I understand, some initial PCI initialization (assigning irq/dma/ports) should be done with ROM/Firmware/BIOS/Bootloader (or what's the name of it in case of HPPA computers?) (even if they are unsupporded by bootloader). Nothing strange that the card will behave different from PC. And the kernel should read that "PCI resource tree" (or what's the name of it) provided by Bootloader.

Do I understand it correctly or this knowledge is unusable in the world of HPPA computers?

The PA-RISC proms do not have a real PCI BIOS, and will only initialize known devices from a fixed list, i.e. all the onboard devices but nothing more. Even the official HP dual-port NICs boards featuring two PCI Ethernet controllers behind an HP-designed PCI bridge aren't initialized by the PROM, and require specific setup from HP-UX.

The chances of getting a random PCI card correctly set up by the PROM are zero, unless the card and its placement confuse the PROM into thinking this is one of the on-board devices it knows about.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
uridium wrote: I had a B&W '030 Slab for many years. The king gecko I have is noticably faster processing wise.

Nothing to be surprised of. Integer performance of the early PA-RISC processors was uncanny - too bad the worse than average I/O made it useless in most cases. While Sun systems were the opposite. And the 68030's lack of any real cache will always make it lose against a 040 or any RISC processor of that era.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
vishnu wrote: Yes, I'm chomping on a celebratory cigar. No, I did not make the putt...

The first rule of the celebratory cigar, is that you should always set up the grounds for a future achievement which will obviously need to be celebrated with a cigar. Don't kill too many birds at once with your stone!
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ClassicHasClass wrote: I can't get my damn cat OUT of my computer room.

You really ought to heat the other rooms, then :lol:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
robespierre wrote: Indeed, it is a rare CPU that has "idle instructions".

Actually, the vax doesn't have an idle instruction. But Ultrix and VMS' idle loop perform an ``unnatural'' and easy to identify sequence of instructions, which is easy to detect in an emulator to know that it is harmless to suspend emulation until an interrupt occurs.
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Trippynet wrote: An overheating Fuel perhaps? :)

A Fuel without working environment sensors! :mrgreen:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
I got my hands on an Origin 350 today. The real thing, not an Altix 350 with Onyx4 skins this time...

The original configuration was 2x600MHz. The machine had not been used in the last 6.5 years until I asked for an hinv to confirm the configuration:

Code: Select all

001c01-L1>log
04/17/08 11:40:39 L1 booting 1.38.4
04/17/08 11:40:39 ChiServ IP53
04/17/08 11:40:39 Checking for Type
04/17/08 11:40:39  -- ChiServ Type set
04/17/08 11:40:41 USB0: waiting on open
04/17/08 11:40:41 auto power up countdown initiated
04/17/08 11:42:06 auto power up initiated
04/17/08 11:42:06 power up (COMMAND)
04/17/08 11:42:11 PIC cfg: 0x04
04/17/08 11:42:11 Node 0 XTalk clock 88
04/17/08 11:42:12 reset again MIPS
04/17/08 11:42:17 PIC cfg: 0x04
04/17/08 11:42:17 Node 0 XTalk clock 88
04/18/08 07:37:53 power down (PANEL)
11/18/14 06:10:41 L1 booting 1.38.4
11/18/14 06:10:41 ChiServ IP53
11/18/14 06:10:41 Checking for Type
11/18/14 06:10:41  -- ChiServ Type set
11/18/14 06:10:43 USB0: waiting on open
11/18/14 06:10:43 auto power up countdown initiated
11/18/14 06:12:08 auto power up initiated
11/18/14 06:12:08 power up (COMMAND)
11/18/14 06:12:12 PIC cfg: 0x04
11/18/14 06:12:13 Node 0 XTalk clock 88
11/18/14 06:12:14 reset again MIPS
11/18/14 06:12:18 PIC cfg: 0x04
11/18/14 06:12:19 Node 0 XTalk clock 88
11/18/14 06:57:42 power down (PANEL)
11/24/14 03:09:56 L1 booting 1.38.4
11/24/14 03:09:56 ChiServ IP53
11/24/14 03:09:56 Checking for Type
11/24/14 03:09:56  -- ChiServ Type set
11/24/14 03:09:58 USB0: waiting on open
11/24/14 03:09:58 auto power up countdown initiated
11/24/14 03:10:03 power up (PANEL)
11/24/14 03:10:08 PIC cfg: 0x04
11/24/14 03:10:08 Node 0 XTalk clock 88
11/24/14 03:10:09 reset again MIPS
11/24/14 03:10:14 PIC cfg: 0x04
11/24/14 03:10:14 Node 0 XTalk clock 88
11/24/14 03:11:47 power down (PANEL)


And was thus fitted this way (the two 18GB disks had been removed for zeroing already):

Code: Select all

>> hinv -v
IP35 Node Board, Module 001c01
ASIC BEDROCK Rev 2, 200 MHz, (nasid 0)
Processor A: 600 MHz R16000 Rev 2.1
Secondary Cache 4MB 300MHz Tap 0xc , (cpu 0)
R16010FPC Rev 2.1
Processor C: 600 MHz R16000 Rev 2.1
Secondary Cache 4MB 300MHz Tap 0xc , (cpu 1)
R16010FPC Rev 2.1
Memory on board, 2048 MBytes (Standard)
Bank 0, 512 MBytes (Premium)  <-- (Software Bank 0)
Bank 1, 512 MBytes (Premium)
Bank 4, 512 MBytes (Premium)
Bank 5, 512 MBytes (Premium)
IXBRICK Bridge, Module 001c01
ASIC BRIDGE Rev 3, (widget 15)
adapter IOC4 Rev 53
(pci id 1)
adapter IOC4-ATA Rev 53
(pci id 1)
peripheral CDROM, BUS 0, ID 0, MATSHITA DVD-ROM SR-8177
adapter PCI (SCSI interface) Rev 5
(pci id 2)
adapter PCI (SCSI interface) Rev 6
(pci id 3)
adapter GigE Rev 15
(pci id 4)
IXBRICK Bridge, Module 001c01
ASIC BRIDGE Rev 3, (widget 15)
ASIC XBOW Rev 3, on CBrick, Module 001c01


So I replaced the PIMM with a 4x700MHz PIMM I got from dhjj:

Code: Select all

>> hinv -v
IP35 Node Board, Module 001c01
ASIC BEDROCK Rev 2, 200 MHz, (nasid 0)
Processor A: 700 MHz R16000 Rev 2.1
Secondary Cache 8MB 350MHz Tap 0xa , (cpu 0)
R16010FPC Rev 2.1
Processor B: 700 MHz R16000 Rev 2.1
Secondary Cache 8MB 350MHz Tap 0xa , (cpu 1)
R16010FPC Rev 2.1
Processor C: 700 MHz R16000 Rev 2.1
Secondary Cache 8MB 350MHz Tap 0xa , (cpu 2)
R16010FPC Rev 2.1
Processor D: 700 MHz R16000 Rev 2.1
Secondary Cache 8MB 350MHz Tap 0xa , (cpu 3)
R16010FPC Rev 2.1
Memory on board, 2048 MBytes (Standard)
Bank 0, 512 MBytes (Premium)  <-- (Software Bank 0)
Bank 1, 512 MBytes (Premium)
Bank 4, 512 MBytes (Premium)
Bank 5, 512 MBytes (Premium)
IXBRICK Bridge, Module 001c01
ASIC BRIDGE Rev 3, (widget 15)
adapter IOC4 Rev 53
(pci id 1)
adapter IOC4-ATA Rev 53
(pci id 1)
peripheral CDROM, BUS 0, ID 0, MATSHITA DVD-ROM SR-8177
adapter PCI (SCSI interface) Rev 5
(pci id 2)
adapter PCI (SCSI interface) Rev 6
(pci id 3)
adapter GigE Rev 15
(pci id 4)
IXBRICK Bridge, Module 001c01
ASIC BRIDGE Rev 3, (widget 15)
ASIC XBOW Rev 3, on CBrick, Module 001c01

... and I am a happy Origin 350 owner now!
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
vishnu wrote: Um, are you going to give it to me? :lol:

Don't you already have a Tezro? :mrgreen:
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
ClassicHasClass wrote: He's going to port BSD to it, of course.

Nah, I already did about 5 years ago. But I can tackle a few unfinished projects now (IP35 SMP...)
:Indigo: R4000 :Indigo: R4000 :Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4600 :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...