The collected works of recondas - Page 2

fu - as far as I known the Adaptec 7880 stuff is O2 only.

QLogic PCI SCSI does work in an Octane. Those Avid rS's are striped across both ports of a QLogic QLA12160:


I used them along with an Octane Compression as video capture drives. Here's a copy of the results I got with a diskperf test:

fu wrote: i mean i can use a vhdci-hd68 cable to hook the rS drives to the o2, can't i?

The Avid rS drives I have are hd68 <and *low voltage* differential, so the *high voltage* differential 2944 won't work> - The external SCSI connection on the O2 is SE SCSI, so that will work with the Avids. If you add an Adaptec 2940UW in the PCI slot you could stripe the drives across both SCSI busses for a performance increase. I did pretty much the same thing for video capture on the 400MHz O2 I used to have.

Congratulations Regan - that's a *very* nice Onyx2. Lot's of video I/O there - in addition to the DIVO, it looks like you've got a DG5-2 with the GVO option.

If you get a chance, consider adding "gfxinfo -v" and "configmon -h"

Or you could sell or trade the fibre cables to get enough cat 5. Not to mention it'd save you the cost of the cards, switch and transceivers <you could probably buy the cat 5 for just the cost of shipping on those items>.

Have you seen Ian Mapleson's install guide?
http://www.futuretech.blinkenlights.nl/6.5inst.html

pan1k wrote: The monitors at work are: ViewSonic, Mitsubishi and NEC.. none work...

Before you buy a new 13W3 adapter or VPro board, you might check the specs and see if any of the monitors you're trying are sync-on-green friendly <you didn't mention SOG, so stop here if you've already checked>. If manufacturer's specs aren't forthcoming, there is an on-line listing of monitors that reportedly support SOG - some of the posting are obviously contradictory, but it's a reasonable starting place.
http://playstation2-linux.com/sog.php

There are also specific resolution/refresh rate limitations for the V6 <but you probably already know that since you picked a supported resolution >.

pan1k wrote: One of them displays the login screen for a sec then goes to standby mode...

That brings the 'not completely compatible' 13W3 adapter issue to mind. Some here have had to resort to the breaking off some or all the small pins on the 13W3 side of the adapter to get around the issue <disregard if the 13W3 adapter previously worked with your Octane>.
search.php?keywords=sync+on+green+adapter+pins&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search

The DVD on my Octane is on SCSI bus 1, device 5. I just tried it, and got:

It worked. I haven't used IRIXDiVX is a couple of years <hence version 0.94>, and there wasn't a DVD <or anything else> attached to the SCSI address it used.

For those of you out of date like I am, it looks like 0.96 is still the latest version.
http://www.blackboxcentral.com/sgimonkey/downloads.html

vishnu wrote: I am running 6.5.21m currently; do I need to install patch 5086 before I try upgrading to 6.5.30?

According to the IRIX 6.5.30 Release Announcement , no:

Updated Inst program:
New installation features were used starting with IRIX 6.5.21 that necessitate an updated version of the Inst program. If you plan to install using the miniroot, then you may do so by the usual method. However, if you plan to upgrade by 'live' install and are running IRIX 6.5.19 or earlier, you must first install patch 5086.

Why not get an external SCSI CDRW? I've got several Yamahas of varying speeds that work as boot devices <a few needed a firmware update>, and I seem to recall some Plextors are also known to work:
http://www.vigyan.com/~blbates/sgi/hard ... Mpoll.html
http://futuretech.blinkenlights.nl/cdtips.html
BTW, if you leave a CDRW disk in the drive while IRIX is booting, it will briefly complain, but continue to boot. If the messages bother you, empty the drive before rebooting.

radrob wrote: the sgi one has external pwersupply and makes no noise -except the spinning cd-

If anybody ends up with an external SGI drive that needs a power supply, drop me a line. I bought an entire case of new ones a while back to get two.

You've already tried to reseat the RAM and/or have tried it in another location to see if the problem followed the RAM?

aristides wrote: went through ENABLEALL, UPDATE, RESET....

Code: Select all

Command Monitor.  Type "exit" to return to the menu.
>> enableall
>> update
>> reset
Resetting the system...

You might try going into POD mode to clear and flush the diagnostic logs:

Enter POD mode from the PROM command line by entering "pod", then:
"go cac"
"clearalllogs"
"initalllogs"
"flush"
"reset" <the system will reset>

When it restarts, go back into the PROM monitor and try "enableall", "update". and "reset" again.

If that doesn't work, I have one other possiblity you can try <though I'll warn you ahead of time that it's
a long shot *and* I haven't tried it with disabled RAM>. I was able re-enable processors
on a 250MHz nodeboard that appeared in the PROM as "permanently disabled" by skipping the power on diagnostics
check. Various incantations of the normal POD mode log reset method had already failed several times
when I happened to re-try the process after a warm reboot from IRIX and was surprised to see the processors
re-enabled. I ran the board thru several cold reboots without problem and returned it to the owner
<he'd asked my help in reviving it> over a year ago and last I heard it was still working.

You can force the system to skip diagnostics by setting specific hardware or software switches on the MSC,
but the simplest way is to warm reboot the system <with IRIX running>. So:

If the system is able, boot into IRIX.
Warm reboot the system, it should skip power on diagnostics when it restarts.
Stop in the PROM monitor, enter POD mode and repeat the process to clear and re initialize the logs.
If you're *real lucky*, when the system restarts from the POD reset it won't disable the memory.
Since we <tried to> trick the system, closely monitor the running system for memory errors.

If not, then more than likely that means you need to replace or remove some RAM.

BTW - I moved your post to the "Hardware" forum where you're more likely to get the "help" portion of your post the attention it needs. You can repost the hinv in the Hinv forum if you'd like

aristides wrote: Is my hardware such as the IO6G correctly defined?

The IO6G seems to appear ok in you hinv:

Though you do have a PROM revision mismatch between the IO6G and the nodeboards:

See "man flash" after IRIX loads to correct the issue.

You've got an IO6G and graphics installed. Have you tried cold booting with a keyboard, mouse and monitor attached?

regan_russell wrote: the MountainGate RSP-2150 SCSI-VHS Tape....

Interesting piece of equipment - looks like it was a back up device that used VHS tapes as the medium <18GB on an ST-160 tape>. There wasn't a lot in Google, but this article does mention the RSP-2150 was originally marketed by Metrum:
http://www.faqs.org/faqs/arch-storage/p ... on-27.html

With that bit of information I got quite a few Google hits on "Metrum RSP 2150":
http://www.google.com/search?q=Metrum+R ... =firefox-a

aristides wrote: So any further advise from the Nekochan community would be very welcomed

<if you haven't already done so, visit SGI's Technical Pubication Library and check out copies of the Origin 2000 stuff>

Try stripping the O2k until you get a minimum configuration that boots without error.

Remove:
Directory RAM
All standard RAM except the pair in Bank 0 on each node <your hinv indicates all Bank 0s were working>
The Graphics module
The IO6G <if you still have the IO6 to replace it with>
The MENET and FC boards
The HD that contains the failed IRIX install
The external CD
If necessary, all but one nodeboard
<from this point make and test each change/reconfiguration *one* step at a time - it'll take more time, but it will also enable you to make more sense of any errors>

Connect a serial terminal <enable a *large* scroll back buffer on the terminal program and save each session>.

1) Boot to the PROM monitor and issue "resetenv"
2) Enter POD mode from the PROM command line by entering "pod", then:

"go cac"
"clearalllogs"
"initalllogs"
"flush"
"reset" <the system will reset>

3) When it restarts, stop in the PROM and:

run "enableall",followed by "update" at the PROM command line

<NOTE: repeat this 3 step process after *every* hardware error>

Reboot - are there any error messages?

If so - what are they? <stop and report back>

If not, install the IO6G and graphics board <but *nothing* else yet and do not connect kb, m, or monitor>
Boot to the PROM monitor, and "update" the PROM hardware invertory
Boot again - if errors appear report back

If no errors appear during the boot to PROM
Pwer down, re-install the boot drive,
restart the system,
clear/prep the drive and install IRIX <what revision is your install set, btw?>

If there are install errors <stop and report back>

If not, connect a kb, mouse and monitor, <leave the serial terminal connected for now> and attempt to boot IRIX

If booting IRIX is unsuccessful what errors appeared?

If the IRIX boot was successful, test each RAM set in Bank 0 of a nodeboard <*no* Directory RAM yet>.
If any set gives errors, record the error message, init the POD log, update the PROm inventory, and test the remaining sets.

Once you have eliminated any problem RAM
Try the RAM that passed in the other memory banks
If there are any errors during this process, try another known good set in the problem bank
if the problem persists <and cleaning the slot(s) didn't help>, skip the bank or replace the nodeboard

Once the RAM is tested and running w/o error, reinstall the MENET and FC boards
You can also reinstall the Directory RAM, but in an 8 processor system it does little beyond using electricity and producing heat.

BTW - when you remove nodeboards the compression connectors <labeled "Connector Actuation 7/64 Hex> should be released first, then the phillips headed machine screws at the top and bottom of each board.

When you install nodeboard, reverse the process. Tighten the machine screws first, then the compression bolts <I alternate turning each bolt in a pair a few turns at a time so the connector is seated evenly, but *do not* over tighten>. Following this procedure prevents the compression connector having to support the weight of the nodeboard during removal/installation.

aristides wrote: This seemed to work well.

Good - I'm glad you found it useful.

aristides wrote:

Code: Select all


**** System Configuration and Diagnostics Summary ****
CONFIG:
No. of NODEs enabled    = 4
No. of NODEs disabled   = 0
No. of CPUs enabled     = 8
No. of CPUs disabled    = 0
Mem enabled             = 4096 MB
Mem disabled            = 0 MB
No. of RTRs enabled     = 2
No. of RTRs disabled    = 0

DIAG RESULTS:
ALL DIAGS PASSED.
**** End System Configuration and Diagnostics Summary ****

That looks good

aristides wrote: Reinstalled IO6G. I did though shutdown the system prior to removing original IO6. Hope this was correct.

Yes, you did the right thing. I should have offer a little more clarification. **No hardware** gets installed when the system is powered on <well, at least not from our current perspective>.

Looks like IRIX knows the graphics option board and the IO6G are installed <though I haven't referenced them in order, they do appear in your hinv>:

<and>



BTW, your nodeboards and IO6G still have different PROM revisions <6.129 and 6.156>. When you get a chance read through "man flash".

aristides wrote: Now seems that IRIX did properly install.... but here's the rub.... I seem to rely on the serial connection to initiate the xserver [./gfxstop then ./gfxstart]. Then I see the monitor light up and startup screen showing - without console, I can't seem to get the monitor to work. When the monitor is showing, it has a terrible flicker. Can't seem to shake it off (excuse the pun). While flickering, managed to log in (via the gui) as root and go over to system/display attributes to change size/hz to no avail.

If the graphics board and IO6G were installed when you loaded IRIX all of the necessary software sub-systems should have been included in your IRIX installation. You'll need to stop in the PROM and reconfigure it to use a graphics <rather than serial> console <I suspect that's also the reason you're having issues with the graphics>.

"man prom" has all the info you need, but there is a multi-page nekochan topic on adding <and configuring> graphics and a keyboard/mouse to an O2k - you might want to take a look at that. BTW, once you get it set up and start booting to the "graphics console" <KB&M and monitor> you won't have any graphics output until IRIX loads <be patient, the O2k power-on diagnostics can take a while>. On a similar note, once graphics are up and running, if you need to access the PROM menus, you'll need to shut down, disconnect the KB&M, reconnect the serial terminal and reboot - the PROM should sense the missing KB&M and re-directed the console to the serial terminal.

"man prom" can be found here <take a look at the 'console' setting and compare it to the console in your current PROM environment>:
http://techpubs.sgi.com/library/tpl/cgi ... e=1%20prom
and the nekochan topic "Origin 2000 Deskside + SI-Tram Graphics. how its going" is here:
viewtopic.php?f=3&t=5749&
Some of the configuration steps used to get the O2k and IRIX to use the CADDuo KB&M ports *won't* apply to you <the IO6G should be transparent to the system>.. IO6Gs became a little more common towards the end of the topic, so even though it is seven pages long, I'd recommend reading the entire topic. You might find this particular post useful:
viewtopic.php?p=60658#p60658

aristides wrote: So nearly there and not yet. Once I get this out of the way, I still have to test the RAM and reinstall the MENET and FC boards.

Let us know how it goes.

Nice work Ian!

O2 Hardware Aggregator is absolutely a good idea.

Ian, you might also consider asking Jirka Tolvårige if he'd allow you to post the specifics on how adp78.o was modified. It might prove helpful to someone trying a similar mod on yet another piece of hardware.

EDIT: No longer available - thanks.
I have an Amiga 4000 Video Toaster that I picked a while back with the intention of getting it going. I never have, and thought I'd see if there was any interest in it before I eBay it.

It powers on, but I don't have the necessary monitor, keyboard or mouse, so I'm not certain if it boots, or if there's anything to boot to. For those reasons, I'd consider it a repair job or parts box.

I'm far from the Amiga expert. so I'll post a few photos so you can look and judge for yourself. If you need to see anything else or have questions - post 'em or PM me.

tjsgifan wrote: The frustrating thing was also that some of the very early bricks shipped with this Security feature disabled, but this was automatically enabled if you updated the firmware on the L1 (which most people did when firmware updates were released by SGI ie with IRIX updates), only to find they had nobbled the machine unexpectedly.
.......(l1 revision less than 1.3 something I think)

I ran across an indirect mention of this in the Origin 3000 Series L3 Controller 1.4 Update Guide :

L1 Firmware
Note: This version of L1 firmware (version 1.6.0) enables the Router
Port security and System Serial Number security features (if not already
enabled by previously installing a 1.4.x version of L1 firmware). If your
system is not configured properly, these features can cause your R-bricks
not to power up or boot.

sybrfreq wrote: the whole global search thing would be interesting for craigslist...

You can do a quasi-global Craig's List search with Google: will get all the "sgi" listing on the domestic Craig's List. To keep things current I usually do an advanced search and limit the results to the last week.

If you want global results you could probably tweak the search to include the .uk list <or other country specific sites>.

There's a current discussion concerning issues with neko_xmms over in the IRIX and Software forum:
viewtopic.php?f=7&t=16328&st=0&sk=t&sd=a&start=30

@nekonoko - when your schedule allows would you consider adding your system to the Tezro Hardware Gallery?

Some interior shots would be a nice addition

nekonoko wrote: I can add the shots I already took (and are posted earlier in this thread) - there isn't much more to show than that. Two side panels - two views of the interior

Thanks - I know for one I'd be appreciative of their inclusion in the Gallery. Other than your shots most of the photos I've seen are low-res exterior shots with only the occasional oblique glimpse of the internals.

http://techpubs.sgi.com/library/tpl/cgi ... 408-PARENT

modology wrote: gonna stick with 24'' then.

You can still pick up a little more screen real estate. A V12 with a DCD can run two 24" LCDs, each at 1920x1200. And the difference in cost between a 30" and two 24s might be enough to pay for a DCD.

schleusel wrote: Nice - didn't know there was a 30" that could be driven by two single-link channels.

That would be a very nice use for a DCD equipped V12 - if the 13W3-to-DVI connection issue could be resolved, it'd be extra slick on a dual-pipe InfiniteReality system <and setting up the 1200x1920 display modes with ircombine would be relatively simple when compared to the VFC process required by the V12>.

schleusel wrote: So it appears to be possible to produce such complex modes for the V12 - if you find somebody with the vfc skills to do so. I was even too stupid to build regular DCD modes when I tried it..

That means there probably isn't much hope for the rest of us.

Ryan Fox wrote: Hmm Octane 2 + PCI card cage + Voodoo 3 PCI...

Sounds like a challenging project. But once the sense of accomplishment wears off you'd be left with what, a 600MHz <or slower> system with PCI-based graphics and a commodity operating system?

The mechanism is a Pioneer DVD-304S slot-loader; 10x DVD, 40x CD. This one has HP firmware version 2.00, and was apparently intended for use with HP-UX based systems.

The drive has a jumper to allow selection of a 512 or 2048 block size. It successfully booted IRIX while connected to an Octane2 and an Onyx 300. As a bonus, audio-over-SCSI also worked <on either platform>.

The HP part number for this one is C4315-63001. That part number is for the drive in an external case that * was not * intended for stand-alone use, the SCSI connector is an SCA variant meant for use in a modular rack frame via a SCSI backplane. These can be found on a fairly regular basis on eBay <this one went for the opening bid - 99 cents>.

The HP case is a fairly nice tool-less design. To use the HP case the SCA-style connector would need to be replaced <some light-duty modification or fabrication would be involved>. The drive could also be removed from the case for use, but be aware a faceplate is not attached to the drive, it's part of the case. I have also seen the drive in a similar HP case that *was* intended for external use.

Here's how the dive <with HP firmware> identifies itself to IRIX:


Pioneer still lists some info on their version of the drive: http://www.pioneerelectronics.com/PUSA/ ... SI.Support

I'll put up a few photos later.

jan-jaap wrote: Need to try this myself

It'd be nice to find out that the Pioneer firmware works as well with IRIX - let us know what you find out.