The collected works of recondas - Page 21

You do realize you're saying that to a resident of the largest socialist country in the world... don'tcha?

Along with the V12 that came in the first one you've done pretty well with the you-never-know-what-you're-gonna-get-box-of-chocolates surplus Fuels. Congrats! PROM might be the same, but how about the hardware revisions? Might be interesting to compare an L1 serial all run against either system. If you spot anything different, be sure to let us know - don't recall seeing any info on the subject.

BTW, If you also want to compare an IRIX hinv -vm you could always clone the drive from Big Red - if you haven't already been-there-cloned-that, BetXen's commented clone script is my preferred method. viewtopic.php?f=10&t=11322

viewtopic.php?f=3&t=17194&p=134279&#p134279

I mentioned it once before , but the differences in function might also be related to the underlying hardware the L1 and PROM interact with. Changes to the Fuel's environmental monitoring hardware is the obvious example, and it's likely there are other less obvious examples like those you're experiencing.

You can easily compare the hardware revision levels run running "serial all" at an L1 command prompt. The information included in serial all can be very helpful when trying to diagnose problems or just to provide documentary references for various Fuel hardware levels. The information we share here on nekochan is pretty much our last stand - now that SGI washed their hands (of MIPS/IRIX) and sealed our fate.

@andarm16 - for those very reasons, you might take a look at some of the suggestions in this post and consider adding to your initial hinv post.

Always got the impression that the original was aimed more at stoners than the stars.... though this one added at least a little more lyrical plausibility .

Recently did a Final Cut Studio install on my Mac Pro that weighs in at 17.4GB - though to be fair I did select *every* install option.

Had the V12 out of the Tezro during dustbunny hunting season and this thread came to mind. While it was out I took a few photos the Tezro V12 to illustrate what's different in the Tezro and Fuel mounting hardware.

Second generation V12's like those used in the Fuel, Tezro and Onyx350 IP have a attachment point located on the 'bottom' side of the heatsink boss. The one used in the Tezro Tower has a button head standoff that slides into a clip on the bottom of the Tezro chassis: V12s used in the Fuel have a hex-shaped standoff that is internally threaded to receive a machine screw that's inserted through the bottom of the Fuel chassis. The Fuel VPro shown in the photo is actually a V10 installed in an Origin350, but Fuel V10 and V12s use the same standoff, the one shown is the original Fuel part (the Origin350 has a matching hole in the chassis lid to allow for placement of the attachment screw): The standoffs used in either version of the V12 can be unscrewed from the heatsink boss and be easily interchanged. The Tezro standoff is slotted to allow removal with a flat-tip screwdriver, the hexagonal shape of the Fuel standoff allows for removal with a wrench. The end of either standoff (that goes against the chassis) is threaded to accept an attachment screw:

I don't currently have a VPro with the Fuel/hexagonal standoff, or I would have included measurements for both (you're welcome to add the info).

As long as the secured Tezro standoff doesn't flex the PCB of the V12 when it's installed in the Fuel I'd think you're fine.

If you haven't already tried it, diegel created a tar of FF3.0.19 that includes all the necessary dependencies: viewtopic.php?f=15&t=16727403&start=120#p7360377

Very nicely done - Thanks!

Wrong toolset/software. You'll need to install the DIVO/DVC package - Ian has kindly provided a copy in his Resources Depot: http://www.sgidepot.co.uk/depot/6.5.11_ ... 2.4.tar.gz


PAL as in analog? If so the short answer is you don't.

If you haven't already seen them, the DIVO Release Notes and DIVO Option and DIVO-DVC Option Owner's Guide might be helpful:
http://techpubs.sgi.com/library/tpl/cgi ... notes/divo
http://techpubs.sgi.com/library/tpl/cgi ... /ch01.html

You may have to tell Software Manager to include some of the optional subsystems, but the DIVO/DVC package has an app called Orion that allows control of some decks (and the capture process). Right.

As jan-jaap rightly points out, you'll need the original DIVO/DVC package from Ian's Depot *and* the DIVO/DVC software "upgrade" from your 6.5.30 CD set. The linked file is the actual DIVO/DVC software package; if your Onyx2 was still running IRIX 6.5.11 it would provide a complete self-contained installation. Since your Onyx2 is running an 'upgraded' version of IRIX 6.5, you'll have to upgrade the DIVO/DVC software package to match.

There's a basic run-through on the DIVO/DVC installation process in this post . BTW, the topic there was installing/running an Onyx2 DIVO in an Octane, but the software install process will be the same.

FWIW, I'd recommend you fore go the default install process and instead use the 'Custom' install option in Software Manager . That will allow you the opportunity to see exactly what is or isn't selected for installation (like Orion). Many of the software packages (for hardware options) will have 'extras' that aren't included in a default install.

Looks like a voltage regulator module, or VRM. If the 275 in this googled up photo is the same as yours, what looks like the VRM is located in the lower right corner of the photo - just behind the lower memory slots:

If you haven't already BTDT, you might start with the "Virtual Debug Switch Settings: section of man prom . Here's the cut to the chase part:

If you're interested, from there you could work your way into the "POD Commands" and "Undocumented (POD Commands)" articles in the nekowiki.

If that piques your interest (and you haven't already been inside the POD), the pod command "help" isn't a bad place to start. To ensure the system will still boot the power on diagnostics routine sometimes disables hardware with otherwise non-fatal errors. Clearing stale error entries from the POD log can be another useful way of getting past problems.

If you stay away from the lowend-who-knows-who-made-it stuff, a compressor designed for airbrush work would probably be pretty safe. High-end air brush compressors are designed (and filtered) to prevent the output of oil, water or other contaminants (if you've just spent a couple of days applying detailed custom graphics to someone else's motorcycle you're gonna have zero tolerance for compressor-supplied paint additives).

Probably directly related to the redneck re-engineering it underwent .

If you're happy where you're at, nobody's twistin' yer arm. But on the odd chance you're somebody who ain't got (or can't find) a Tezro, you could do a lot worse than an O350/VPro.

As far as nekochan is concerned the answer is yes.

I've successfully used irsaudit with a G-brick attached to either an O300 or O350, what error(s) did you run into with the O3k?

viewtopic.php?f=4&t=16726496

irsaudit is normally located in /usr/diags/IR/bin/ - but if there wasn't an IR pipe present when IRIX was installed it isn't included in the default selections .

As long as you've got a display that'll work with the resolutions supported by the V8 , $79 ain't a bad deal if you consider that's probably less than half of the going rate for the 128MB V12 alternative. The one currently on eBay is actually being offered by a forum member , so you could always PM him to discuss the issue.

SGI systems run a power on diagnostics routine when powered up that might provide you with a little more detail concerning the problem.

As is, your only indication of the results of those tests are limited to the color/status of the LED display (and the boot chime).

You may be able to capture additional detail from the power on diagnostic routine by connecting a PC/Mac a terminal emulator program to the first serial port.

But for no longer than it'll take I'd probably give the O2 Jump Start Procedure a shot first - there have been more than a few mentions of a jumpstart reviving comatose O2s.

You might also find fu's O2 Diagnostics Aggregator useful.

A zx6000 would be a good way to finally try out the HP-UX 11i CD set HP sent me back in '06 , but by the time coast-to-coast shipping adds the weight of it's thumb to the desirability scale I'll probably end up waiting (another seven years) for one to show up locally.

Congrats - that's a very nice Octane2! For what it's worth, if you put issues of relative rarity aside I tend to think of Octane2's with video hardware/the DM2 as a better example of maxed out than one with a dual V12.



Looks like you got the issues you experienced with your DCD and VBoB sorted out. Any potential words of wisdom or closure for those threads (for others who might find themselves in similar situations)?

Since the DM5 converts your graphics signal to SD or HD video, I'd be at least a little surprised if the DDC info supplied by your monitor got passed back through the VBoB/DM5 to the V12/DCD in your Octane. Do you also get 'unknown monitor' if you connect the monitor directly to either the 13W3 on the V12 or one of the DVI ports on the DCD? I can appreciate wanting to operate your Octane in the maxed out configuration, but if it works with your monitor(s) directly connected to the DCD, you might want to reserve the VBoB/DM5 connection for video editing sessions.

If you still get 'unknown monitor' when connected directly to the DCD (ditto for the 13W3, but you'll want to make sure the analog cable or adapter you're using is wired to provide DDC info), then you might consider adding your specific monitor to the moninfo file. See the man page for moninfo for additional detail; here's the intro (don't be put off by the mention of "CRT monitors", the moninfo file that came with IRIX 6.5.30 includes a number of LCD monitors): I suggested the same thing to someone else who was apparently had incomplete DDC info - xsetmon wouldn't offer *any* 2@ formats for his DCD-equipped V12 until he added his monitors to monifo.

Doesn't seem like it'd be real eye-friendly, but that seems to be exactly what SGI/Discreet intended for the V12/DCD/VBoB/DM5.

Got that part, which is why I asked if you tried connecting the monitor directly to the V12 or DCD.

You didn't mention what your expectations were for your megabuck DCD/DM2/DM5 hardware, but *if* those expectations include the ability to use a 2@ format to display IRIX (your desktop) on a monitor connected through the DM5, you'll probably gonna be disappointed. The DM5 was added to the VBob to give the V12 a Graphics-to-Video (GVO) option, similar in function/intent to the DG5-GVO option for IR graphics. Both were primarily intended to provide a mechanism to preview effects or other edits applied to the video stream, not as a method to display/access/control a multi-screen Desktop. The Silicon Graphics DMediaPro DM5 Graphics-to-Video-Out User's Guide mentions:


Don't think that diagram is in error - the same set up is listed in the several Discreet manuals, here's another quote from Discreet, this one is from "Setting Up Video (Chapter 7) of the Smoke 6.5 Manual , : ...and pretty much the same thing from a completely different Discreet manual ( "Effects Editing 2007: Hardware Setup Guide for SGI Tezro and Octane2" ), That same manual goes on to mention that in systems with (HD) output routed through a DM5, the monitor must be set at 1920x1154 The very same issue you're experiencing with your DCD and DM5 have come up before, and as it turns out, the Discreet method of connecting the monitor directly to the 13W3 and setting the resolution to 1920x1154 worked - though it's worth noting that the Dell monitor originally used by the OP in that thread *wouldn't* support 1920x1154 - he had to switch monitors. BTW - his Dell monitor *did* work without issue(at 1920x1200) if he skipped the DM5 and connected directly to one of the DVI ports on the DCD, which is why I mentioned: In any case, here's a link to that thread - start here and read down a few posts: viewtopic.php?f=3&t=17253&p=7286590&#p7286590

I think what you might have misunderstood is the Discreet set up for the DCD-DM5 doesn't use a 2@ display format . The 13W3 will only undergo a left-to-right smackdown *if* you load one of the 2@ DCD formats, and the Discreet setups don't use 2@ formats. Take a close look at the setmon command Discreet recommends (it's quoted a few posts back) and you'll notice the format recommended for an Octane2 with a DM5 *isn't prefaced with 2@ ( /usr/gfx/setmon -x 1920x1154_60 was the command Discreet recommended to correctly configure an Octane2 equipped with a DCD and DM5.

To recap; In the Discreet set up there's a single connection between the DM5 and the *right* DCD port; the graphics monitor is connected to the 13W3; and both are fed a not-intended-for-a-DCD 1920x1154_60 (unsplit) display format. So the half-field display flickers the 13W3 port would normally get with 2@ formats *isn't* an issue.

What I was trying to point out was the OP in that post, Bodao, followed up to say that setting the resolution to 1920x1154 (and connecting a monitor that could live with that res) resolved his issues with the DCD/DM5, and that the connection method/resolution used by Badao sounds to be pretty much the same as what Discreet recommended.

BTW, the other read-between-the-lines bit of potential enlightenment in Bodao's post was his mention that the DM5 was connected to his Octane2 using *only* the right side port on the DCD . Using just the right port on the DCD to connect the DM5 is the method shown in the 'questioned' connection diagram from the Discreet manual - the very diagram that shows the graphics monitor connected to the planar graphics out port on the V12 (instead of one of the ports on the DCD).

All of the Discreet manuals (for SGI gear using the DM5) mention *not* to connect the DM5 in the method shown by the DMediaPro DM5 Graphics-to-Video-Out User's Guide on TechPubs. Since the connect-both-DCD-ports-and-graphics-monitor-to-the-DM5 method in the TechPubs manual doesn't seem to be working for vishnu, it might be worth the effort to explore the Discreet graphics-monitor-connected-to-the13w3-port method.

Here's the TechPubs DCD-DM5-monitor connection diagram: and the one provided by Discreet: Outside of TechPubs I couldn't find a single application or reference to using the DCD-DM5-monitor connections shown in the SGI diagram. In contrast, I wouldn't be surprised to find that a large percentage of the DM5-equipped systems sold by SGI were probably purchased to run one of the Discreet applications.

If you'd like to try the Discreet method, I've quoted it here (from page 29 of the Discreet Effects Editing 2007; Hardware Setup Guide for the SGI Octane2 and Tezro -the setmon command is on page 11):

Welcome to nekochan crystalfire!

I won't go as far as to say the TechPubs connection diagram can't be made to work...... but I think you'd have to do some custom coding to get there.

All of the OpenML-based SGI video gear I've experienced doesn't seem to have been intended as a turn-key hardware-software solution. Instead it would appear SGI's philosophy was to provide the hardware, necessary hooks for the IRIX kernel, and the basic info/tools for the purchaser to program their own custom OpenML application (or alternatively use a third-party app like the Discreet stuff).

So AFAIC, the reason you (and everyone else who's posted about it on nekochan) can't get the DM5 connection scheme on TechPubs to work is you probably don't have all the necessary software to enable a fully-end-user-functional video editing set up. Which is pretty much the same boat the DM6, DM10 and HD-GVO/TVO are in.

If you have the optional DM2/DM3 Development Environment installed, you can take a look at/play with some of the example code snippets SGI provided with the xtdigvid (DM2/DM3) software package.... ...but I'd guess there was a reason why Discreet choose to fore go the the TechPubs example and go another direction.

On the other hand you could install one of the Discreet apps and take advantage of the proven coding they've provided.

Even without the addition of Discreet software, if you connect your gear using their method, you should be able to get your *graphics* monitor working without having to backdoor yourself via ssh. You might be able to get a display on a *video* monitor too - but you'll probably have to play around with dmconf to see if you can find a combined graphics/video format that works - though your graphics monitor will have to be willing to will play nice with 1920x1154_60.

If were me (it ain't, and I realize I don't get a vote), I'd disconnect DM5 and connect the monitor to one of the DVI ports. Then any time you've got the hankerin' to go skywalker ranch with your Octane2 all you'd have to do is swap a couple of cables.

I've probably misunderstood that reply (and if so, most of this thread)...... have you been trying to feed a 2@ display format through the DM5?

For that to work the DM5 would have to include the necessary logic to reassemble a split dual-channel-display format back into a single display image (there's only *one* DVI-out port on the DM5).

While both frequently mention the DCD, neither the Discreet and SGI manuals ever mention using a 2@ display format. I think it's likely the only role the DCD plays is to provide a digital signal for the DM5 (which why with the IP35 systems that have planar DVI ports Discreet says you can use a Gefen DVI splitter instead of a DCD).

Since you were using the connection diagram from SGI's version of the DM5 manual, I figured you'd long ago tried the matching software configuration (for graphics and video) listed in Chapter 3 and found it didn't work. If you have, my apologies for yet again beating that dead horse.

On the very remote chance you missed it: That'd still require a monitor able sync to a 1920x1154@30Hz signal.

If it produces a display through the DVI-out port on the DM5, you'd still have to do some custom coding to use that mega-buck DM2-VBoB-DM5 combo for something other than a glorified DVI pass through (which is why I suggested the more-mega-bucks-needed Discreet route *and* the no-additional-bucks-needed monitor-connected-directly-to-DCD alternative).

The DCD works just fine without the presence of a 2@ format - you're presented with a practical example every time you boot a DCD-equipped Octane.

With IRIX running, if you connect three monitors (to the 13W3 and both DVI ports) and load a standard non-DCD format, all three monitors will display the same image. If you take into account the inherent differences between the 13W3's analog signal and the digital signal on the DVI ports, the quality of the images will be the same. bitcpy posted a photo of three monitors connected to his DCD-equipped VPro. He wasn't using a 2@ format; all three monitors display an identical image: viewtopic.php?f=3&t=16727561&start=15#p7358665
While I was working out the details of how I wanted to configure OpenGL MultiPipe on a dual V12/DCD O350 (it took a while), I had monitors attached to the DVI ports of both the DCDs and wasn't using 2@ formats. Never experienced any display issues, anomalies, or Magilla Gorilla rabbits .
It would have been nice of them to have included at least a little more detail in the dmconf man page.

Just to further complicate the issue, sample combination files for the VPro Graphics Compositor are also stored in /usr/gfx/ucode/STINGRAY/cmb directory (you can see that same path structure in this illustration from the Compositor Manual ). Here's the contents of /usr/gfx/ucode/STINGRAY/cmb on my DCD/DM2-equipped Octane2: The Compositor combines the output of multiple VPros as "tiles" in a smaller single display. Unless your version of the directory looks different, any combination files that include the word "tiles" were very likely intended for use with the Compositor. If you did inadvertently use a combination file intended for a Compositor it might explain the 'error reading VPro format' messages you saw.

Sounds like it can't 'read' the VPro format because it doesn't know where it is (or because it's broken - /usr/gfx/ucode/STINGRAY/cmb/1280x1024_96s.cmb appears in fm as a text file instead of a binary). Have you tried including the full path?

In any case I wouldn't use the the 1280x1024_96s in the Stingray cmb directory; not only because it's broken/not a binary, but it appears to have been prepared to produce a stereo display for use with a crystal eyes stereo emitter/glasses (the trailing "s" in the file name is typically used to designate a stereo format), and stereo or not, 1280x1024 probably isn't going to work when you're calling for a 1080i video format.

It isn't really discussed in the dmconf man page, but if if they were intended for the DM5 (instead of the Compositor), any files that have a .cmb extension have already been "combined" into a DM5-compatible format, so trying to re-use them as the VPro format in dmconf likely wouldn't work. I suspect the read-between-the lines is that you'd have to call a not-previously-combined VPro format (with a ".vfo" file extension), then read-between-the-lines again and load saved .cmb combination files with setmon.

Even if it means you have to call ssh to the rescue (allegedly dmconf configurations can also be cleared with a reboot), I'd try the syntax in the 1920x1154 example in the DM5 manual (with the addition of a full path for the graphics format). There's a 1920x1154_30f in the VPro format directory (/usr/gfx/ucode/ODSY/vof/1920x1154_30f.vfo). If it turns out dmconf is picky about file paths, you may have to try it with and without the .vfo extension:

@Nedry - Welcome to nekochan, and thanks for retooling your initial post into compliance with forum rules.

I'd recommend cloning your current hard drive so you have a plug-n-play recovery mechanism should your current disk bite the dust (or as a new user you inadvertently fubar it beyond redemption). There are a couple of good tutorials that'll walk you through cloning your IRIX system disk; there's one in the neko-wiki , I've successfully used the one on Ian Mapleson's site numerous times - but my currently my preferred method is BetXen's commented cloning script - the as-you-progress comments in the script pretty much walk you through the cloning process.

As far as SCSI CD drives go, there's several listed in the Octane Hardware Aggregator . You'll also find a few SCSI CDRW and DVD-ROM drives. I use a Pioneer DVD-305s slot-loader, which works fine as an IRIX install drive, and supports audio playback via the SCSI bus.

BTW, if you contact SGI to inquire about an IRIX 6.5.x CD set, it's worth noting that not all IRIX install sets were created equally. There are full install-from-scratch CD libraries (usually 10 or more disks), and Overlay install sets that are intended to upgrade an existing install, but can't be used as is to create a working install (or add stuff like NFS if it isn't already installed on your system). Overlay sets typically have less than 5 CDs.

Maybe....... got any pictures?

Before you spend large amounts of cash it might be a good time to double check your hardware inventory and the version of IRIX currently installed.

Could you run the following commands and post the output here?
BTW, on the odd chance you don't already know, enclosing the output of those commands in "code blocks" will preserve the original formatting. As an example the commands posted above are in code blocks - hovering your cursor over the "Code" button at the top of the 'Post a Reply' page will give a fully visible example of the necessary formatting.

Lots of farmer's markets in this part of the US, most have been around for longer than my memory span. The biggest difference is the USofA is still a more mobile society than china, so farmers don't need to stop in the middle of the street to sell stuff. Around here most are set up along the roadside at the farm - and most everybody round here knows when and where stuff is available.
Don't judge the US by NYC - it shares the impersonal charm of overcrowded metro areas across the globe.
Not quite the same as a farmer's market. Most flea markets are privately run enterprises - you have to pay the landowner for the privilege of arguing with strangers over the price of your broken junk. Locally farmer's markets are typically run by farmers on their own land (sometimes cooperatively), or more recently, by a city or some other local government. The run-by-a-municipality markets I'm familiar with charge the farmer a reasonable fee to cover the cost of whatever facilities were provided and for refuse disposal/clean up.