The collected works of miod - Page 1

polytrope wrote:
Any more current comments on the status of OpenBSD/sgi?

The OpenBSD port page says things are working fine (including X11), while FAQ page on X configuration mentions for sgi "no X servers, only X clients." (Apr 09 version).

That's clearly an error in the FAQ. Framebuffer support is currently still limited to the O2 machines. However there is promising work behind the scene to support VPro boards on Octane and Fuel systems, which will be commited soon.

As for non-framebuffer hardware support, Origin 350 are now working since a few hours :!: , and there is ongoing SMP work targeting the Octane and Origin 200 systems.

_________________
: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...
bri3d wrote:
O350 "working" meaning what?

Meaning that an Origin 350 is now used to build the OpenBSD/sgi snapshots.

bri3d wrote:
Is PCI probing supported?

Yes. Which also means the on-board SCSI and gigabit Ethernet controllers are recognized and working.

bri3d wrote:
Does NUMA work?

Multiple-o350 configurations could not be tested for lack of hardware (the only multiple-node system which has been tested, to the best of my knowledge, is a dual Origin 200 system).

_________________
: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...
bri3d wrote:
I'll pull some snapshots later on and test, as I happen to own two dual-R16k O350s NUMAlinked.

That would be terrific!
bri3d wrote:
Let me know if there's an IRC somewhere I should join to collaborate with you...

I'm afraid I am seldom seen on IRC those years, but I try to answer all my mail without too much delay...

_________________
: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...
It indeed looks like SRM console is configured to use a serial console, but will accept input from glass console if asked nicely (i.e. with the reset button).

If you get a >>> SRM prompt, the command to switch console back to glass console is ``set console graphics'', and you'll need to power-cycle afterwards.

I'd suggest doing ``show console'' first to see what the current settings are - the SRM could be configured for glass console but not like your keyboard and fail to initialize it the first time.

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
wonko wrote:
To answer my own question:

The installer blows up if the machine has more than 1GB ram.

Actually, on Octane, you can use up to 1.5GB without hitting the bug.

The good thing is that I have narrowed it down and I'll fix it shortly. :)

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
neozeed wrote: It'll load on a regular PC.... it just has to really be compatible... if it'll run OS/2 1.3 (and more importantly install it) it'll run AIX... or that's been my experience...


But OS/2 1.x could run on a machine without an ABIOS - at least the version distributed by Microsoft. I am not sure IBM intended AIX 1 to be used on non-PS/2 machines.
: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 am surprised noone mentioned ES40 ( http://www.es40.org/ ) yet.

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
foetz wrote:
jan-jaap wrote:
Which makes you wonder what happened between IP35 (Fuel) and IP53 (Tezro).


could be just a joke. 35 <-> 53


Maybe. But then it got lost when the 1GHz R16000 Tezro were introduced, as these are IP59...

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
ajerimez wrote:
I might be able to get my hands on a DECstation 5000/260 - just the system unit, no keyboard, mouse, monitor, or drives. Aside from the basics that can be gleaned from Wikipedia and a few fan pages, I know next to nothing about these systems.

Any practical advice? What are some of the more interesting apps that can be run on these machines? And where would be the best place to find parts & accessories - eBay doesn't seem to have much? Any input is very much appreciated.


You're a lucky man, the 260 being the high end model. 10+ years ago I would have sold my family to get one... the best I could snatch was a 240. Of course by today's standards the 40MHz 260 will fell as slow as the 33MHz 240 :cry:

This machine uses a combined DB15 keyboard/mouse port, which was also used on several VAXstation models (35x0, 38x0, 4000/60 and 4000/9x) ; the keyboard itself is the regular LK-201 or LK-401, and the mouse is the regular VS-XXX , which are both quite easy to find on eBay or elsewhere; the important part being the DB15 cable, which will be more difficult to find.

Of course, with no keyboard connected, the machine will default to a 9600 8N1 serial console on the first DB25 serial port.

One thing to look for, after all these years, is the quality of the memory sticks. Since quite a few years now, I've seen more and more 16MB sticks becoming more sensitive to dust, and eventually dying. Be sure to clean the memory sticks and connector as best as you can.

You will not find precompiled modern software for MIPS Ultrix. And since Ultrix lacks support for shared libraries, many modern ``desktop'' software will not build on Ultrix (assuming the code is portable enough in the first place).

I am not sure there are Linux distributions available for pmax systems. Your best choice of operating system for this machine is probably NetBSD/pmax, although not all choices of frame buffers are supported (which will only matter if you manage to get a keyboard and mouse for that system, anyway).

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
canavan wrote:
I'd suspect some of the DECLARE_ALIGNED_... statements to be the source of the problem, but they should just be hints for performance optimization, and not actually required for correct operation.

ffmpeg wants proper alignment of its data so that it does not have to perform unaligned load and stores, which are slower (and the assembly parts rely upon this).

So if you have enabled the use of the `ps2' assembler code in libavcodec, you definitely want to make sure your alignment hints are correct as the assembler code will perform aligned loads and stores (ld/sd) instead of possibly-misaligned loads and stores (ldlo ldhi/sdlo sdhi).

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
bhtooefr wrote: Custom connector for *ETHERNET*? Ouch.


Yes, it's a micro-AUI connector (the same found on SS5, but at least on SS5 there is an RJ45 connector so you don't really need the adaptor cable).

This is kinda like the Apple AAUI connector found on 68k macs... except AAUI adaptors are easier to find.
: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...
D-EJ915 wrote:
kshuff wrote:
And I just picked up a 735 Apollo and a 735/125. Haven't had a chance to poke around and see what's in them yet.

Those look pretty cool, I found a site with nice pictures, looks like it has HIL which kind of sucks haha.


Yes, 735 and 755 (same machine in tower case) can only use HP-HIL input devices. And of course serial console if you don't have any.

You also need to check the power supply as many of those found in the old desktop models (720, 730, 735) tend to die of old age and too much dust.

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
If we are talking about zombies, Crimson is the only good choice! Blood'n'guts SGI Crimson, limited edition. With a special offer : order two, get a salesman corpse for free!

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
nuts wrote:
I'm trying to install OpenBSD 4.7 (beta) on octane, it boots with the framebuffer and the keyboard works, but I have a panic, it can't "mount root", then I don't understand the error

edit: woops, I think I use the bad image, I'll try again


You need to boot bsd.rd.IP30 to start the installation procedure, not bsd.IP30 which is the regular kernel.

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
nuts wrote:

It's no use, yet. The kernel interfaces needed by this driver are not there yet in OpenBSD (the OpenBSD Impact driver was written in a rush to meet the release deadline, and still needs some love, for example vertical scrolling is not as fast as it could be). This will be fixed by the next release (time permitting).

So you'll need to stick to "textmode" console (or use a different operating system on the machine) for now.

nuts wrote:

What music is playing in the background? At first I thought this was Ministry, but it also sounds like Laibach to me...

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
porter wrote:
IBM did have SOMobjects running on AIX and OS/400, and they originally had the intention to be able to sit PresentationManager on the top of X11.

Don't forget the REXX interpreter. They even had a Linux/i386 version at some point, under the name `Object REXX'. I wonder how much REXX code is still in use those days...

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
Rhys wrote:
Not gonna happen, OS/2 is 10+ years old. That would be like HP bringing back Tru64.

Not Tru64, Ultrix! :mrgreen:

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
Simply removing the keyboard ought to be enough to get a serial console, unless the ``nogfxkbd'' variable is set in the PROM environment. Could you check whether this variable is defined on your system?

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
bviking wrote:
Yes, nogfxkbd is set.

So it seems this is the expected behaviour?

I would have thought that logically a system which has nogfxkbd set shoul default to console on serial as the administrator clearly intends to remotely administer the system. Must just be one of those quirks we all love, I suppose!


That's the other way around. nogfxkbd means ``don't mind if no keyboard is plugged, and use the video console anyway'', and by default it is not set. I agree the name of this variable is misleading :mrgreen:

_________________
:Indigo: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :O2: :O2: :Octane: :Octane: :O200: - :O200: :Fuel: among ~160 machines...
Looking for IP26 and IP28...
SAQ wrote:
DECstations are interesting - they're MIPS-based little-endian UNIX workstations (the VAXen will run either UNIX or VMS). Get the highest numbered model you can find (the /240 was R4k based, others were R2k/R3k).


Sorry to nitpick, but the R4k based DECstation was model 5000/260. Model 240 still uses a R3k.

_________________
: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...
leaknoil wrote:
The AXP 3000 wont even get through post without a keyboard. No way around that as I remember but, i doesnt matter.


I beg to differ; models 3000/300 have a jumper (W2) on the motherboard, and all the other models (from 3000/400 to 3000/900) use a ``server'' SRM environment variable to let them POST without a keyboard connected.

_________________
: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...
leaknoil wrote:
miod wrote:
leaknoil wrote:
The AXP 3000 wont even get through post without a keyboard. No way around that as I remember but, i doesnt matter.


I beg to differ; models 3000/300 have a jumper (W2) on the motherboard, and all the other models (from 3000/400 to 3000/900) use a ``server'' SRM environment variable to let them POST without a keyboard connected.


Right but, isnt there a problem if you don't have a graphics console first to set the SRM variable ? How do you work around that ?


My words were poorly choosen. The jumper or variable allows the system to autoboot . If there is no keyboard connected, it will POST but wait for user intervention... on the serial console. (However, the DECstation 5000/1xx models will indeed fail to autoboot and won't switch to serial console if there is a frame buffer installed regardless of whether a keyboard is connected, but these aren't AXP systems).

_________________
: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...
nuts wrote:
what's new in the current snapshot for IP30 (x11...?)
Nothing special. There hasn't been any Octane-specific development recently.
nuts wrote:
where can we read news for mips status?
I irregularily post status reports or new hardware support to the [email protected] mailinglist.

_________________
: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...
Stoo wrote:
Kinda ugly compared to most of the other machines..


Only when looking at the front or the back of the machine! The Origin 200 side and top curves definitely have style, and make me think of a Pininfarina design.

_________________
: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...
Valery wrote:
Any plans for porting drivers for X11 from NetBSD for O2? + Maximum that is now in the X11 on OpenBSD is an 8-bit color ... = (

Eventually, yes. But probably not soon, since both Joel Sing and I are busy with other stuff.

_________________
: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...
mattst88 wrote:
Is 'porting' really involved? They can't just be compiled on OpenBSD?

There are probably a few lines of code to add to the kernel driver to allow the X11 userland driver to mmap the various control registers it needs to play with. Nothing particularly difficult.

_________________
: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...
Valery wrote:
We can get it in OpenBSD 4.9? Or no chance?

I'm afraid I don't know the future. 4.9 is months ahead...

_________________
: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...
emachine wrote: Does anyone know how to do instruction by instruction tracing under IRIX? I.e. I want to run an application on my Tezro and generate an execution trace of every instruction executed including program counter, the raw instruction, and if a load or store the memory reference.

On my PowerPC box I would set the single step bit in MSR which causes a SIGTRAP on every instruction, so I just catch the handler, look at the context, save what I want, and then return. I have been mining the web for someone doing something equivalent on SGI but haven't been able to find anything.


This is what logic analyzers are for... Some of the modern MIPS cores have tracing facilities, but the `` original '' MIPS chips used by SGI do not have anything comparable to the hardware single-stepping found on e.g. x86 or powerpc (R10k family has watchpoints, though).
: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...
Tabalabs wrote: - Is it possible to use the 1-Wire bus of the NIC?

Only if you want to achieve unprecedented slowness. Not only will you need a separate power source for your storage device, but all the 1-Wire bitbanging will shrink your bandwidth down to zilch.
: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...
Well, just write down your password in this thread, and we'll tell you if they are strong enough, for free! Aren't we kind hearts?
: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...
Oskar45 wrote:
miod wrote: Well, just write down your password in this thread, and we'll tell you if they are strong enough, for free! Aren't we kind hearts?
pi=4,25?

Definitely too weak.

Try using ``pi=14.3'' instead.
: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...
The PROM ping function does not use icmp, but tcp echo service (port 7). If you want to confirm the PROM network configuration is correct, use tcpdump, and don't try to ping the SGI from another machine.
: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...
BetXen wrote: Voted for singles, but in fact I have 4 uniprocessors and 1 four-processors...
Processors-count, nobody wins, 50:50 (very swiss indeed, compromise culture :) )


But your sig lists five single-processor machines! :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...
skywriter wrote:
Well, as long as everyone is doing it. Here I am, chest shaved, hard at work:


Ah, I knew I had a picture of me at work somewhere. Here it is, about two years old.

_________________
: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...
Pontus wrote: Today I'm sorry to learn that DMR passed away this weekend. It's hard to overestimate his contributions.


Yet you can expect that, unlike Steve Jobs, he won't get an obituary in the media. :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...
Nice cat.

_________________
: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...
kjaer wrote: I have no idea what happens when you put a 735 CPU board with the older I/O, but since from a chassis point of view they're fully interchangeable, I have to ask.

Been there, tried that, the I/O board needs to match the CPU board or the machine won't POST.

Actually it's not *that* surprising, since part of the machine identification information used (and displayed) by the PDC resides on the I/O board (as well as the PDC itself) - in other words, it's the 735 I/O board which makes it a 735, as opposed to a 720...

Another fun thing to do on a rainy day, is to mix 735 (or 720) boards from systems of different speeds: mixing e.g. a 66MHz 720 CPU board with a 50MHz 720 I/O board will create a system where the OS believes (as told by the I/O board) that it runs at 50MHz, while the CPU runs at 66MHz because the clocks are separate. And then ntpd goes nuts trying to adjust your clock :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...
Nihilus wrote:
When I spoke to Art Grabowski years ago, picking up my Indy from him, he told me someone in .se had code for the Indy it in his attic... They are kinda lazy with pushing the code to the trunk the OBSD'ers ;-) .

For what it's worth, recent OpenBSD/sgi snapshots (attempt to) run on the Indy (as well as R4k Indigo and R4k Indigo2), so the IP22 work happened eventually :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...
PM sent.
: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...
PymbleSoftware wrote:
/me smacks 586.

With a large trout?

_________________
: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...