The collected works of Dr. Dave - Page 3

Hi, finally got around to installing an SAS3041X-R card in my Fuel, after futzing around getting it seated it worked fine as well. Stuffed a 200GB Western Digital IDE drive through an IDE->SATA bridge (picked up a couple for $10 each) and everything worked great, GUI tools found, initialized, and mounted the drive like it was a standard SCSI drive. A+++++++, would try again!

Finally, a use for the odds-and-sods IDE drives I have around here. The card is probably the 'same' as the one's Hamei found, albiet with some cross ocean markup. Still, seemed to work fine though.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Yep, that's the one I got from that eBay vendor. The full-height bracket didn't quite 'fit' properly, but a bit of bending got it to work. Not a show stopper by any means.

Drive is a Western Digital WD200 200 GB IDE disk, not sure offhand if it's the 2MB or the 8MB cache version (would have to pull things apart to check now) and made in 2004 - so one might argue that the latest crop of SATA disks should run much faster. In any regard however, here is the diskperf run on it:

Code: Select all

Dudley 1# diskperf -W -D -c4g /disk3/test
#---------------------------------------------------------
# Disk Performance Test Results Generated By Diskperf V1.2
#
# Test name     : Unspecified
# Test date     : Wed Mar 25 17:53:43 2009
# Test machine  : IRIX64 Dudley 6.5 07202013 IP35
# Test type     : XFS data subvolume
# Test path     : /disk3/test
# Request sizes : min=16384 max=4194304
# Parameters    : direct=1 time=10 scale=1.000 delay=0.000
# XFS file size : 4294967296 bytes
#---------------------------------------------------------
# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   43.75   34.36    7.03    7.50    3.74    1.69
32768   45.96   40.45   11.83    7.99    6.89    3.25
65536   44.76   22.84   18.39    8.32   11.94    5.92
131072   44.74   44.70   18.61   17.41   13.75    9.82
262144   46.63   24.65   25.04   17.79   20.22   14.52
524288   46.13   25.54   28.42   28.32   25.65   21.33
1048576   46.49   34.45   37.03   36.56   32.68   28.76
2097152   47.32   37.19   44.00   44.39   39.70   34.08
4194304   46.32   41.39   44.36   43.40   43.63   33.52
Dudley 2#

Bit inconsistent on the read speeds, but one could probably argue that given the vintage nature of the disk that 45 MB/sec is probably close to the areal transfer rate of the drive, and again a modern zoomy SATA drive would probably double that.

As for the SATA->IDE adapter, it's one of those 'bidirectional' ones. Looks like it uses the SATALink SPIF223A chipset, board is labelled RXD639 Rev 1.2 2008-10, blister pack is labelled " IDE to SATA or SARA to IDE Adpter " (typo's as shown) - but in order to get clearance with the wind turbine housing in the Fuel had to use a right-angle SATA cable and not the one that came with it. I'd guess that probably any of the SATA->IDE bridge-boards would work OK and would have less clearance issues. Camera is on charge, will try to post some pics up later.

As I noted before, once the Fuel booted up and found everything, the disk truly acted just like a standard SCSI disk with all of the GUI disk admin tools. No futzing with crazy mount paths. So far it's been working fine.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Looks like the drive is an 8-meg cache version:

Code: Select all

Dudley 8# configmon -h
SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
0              NA            NA                  NA            NA        NA
1   MODULE_001c01            NA                  NA            NA        NA
2              L1        001c01                  NA            NA        NA
3            IP34        001c01              MDB183  030-1707-003        -F
4       MEMBANK_0        001c01                  NA            NA        NA
5       MEMBANK_1        001c01                  NA            NA        NA
6       MEMBANK_2        001c01                  NA            NA        NA
7       MEMBANK_3        001c01                  NA            NA        NA
8          R14000        001c01                  NA            NA        NA
9              NA        001c01                  NA            NA        NA
10            IP34        001c01              MDB183  030-1707-003        -F
11       ASTODYV10      XTALK_13              MSX293  030-1826-001        -B
12            IP34      XTALK_14              MDB183  030-1707-003        -F
13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
15     SCSI_CTLR_0            NA                  NA            NA        NA
16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
17     SCSI_CTLR_1            NA                  NA            NA        NA
18         CDROM_6            NA                  NA            NA        NA
19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================
Dudley 9#

For the WD2000 J B drive, the ' J ' indicates the larger cache memory.

And credit where credit is due, thanks for the heads up Hamei!
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Stiff wire through one of the panel screw holes...
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
hamei wrote:
ajerimez wrote:
Well, that's that, I guess.

Maybe :) I've known of several cases where they didn't actually give up for years. One just got married to her prey about three months ago. Took her twelve years but she succeeded. :P


Man, I've never had the pleasure of being stalked like that - I usually get the "I should have listened to you" talk about 3 years down the road when they're all tied up in some completely avoidable drama, or married with two kids, those being the baby and the daddy. Well duh... turns out fantasy fades to reality pretty quickly, while reality is a constant.

(And a note of warning: Guys rarely change - unless they've had blunt head trauma. Don't think that you have the power to perform this miracle unless your prepared to wield a frying pan and go for the random outcome. And not one of those tinny french omlette kinds of frying pans either, they don't have enough mass, you gotta go all ode skoo on this one...)

Maybe it's a blessing in disguise... sure hate the speech though.

_________________
:O3000: :O2000: <> :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
heh - I'm like 6-foot-2 as well... they better know how to jump high.

_________________
:O3000: :O2000: <> :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
It's old hardware, but at the time showed up fairly easily on eBay.

This link will probably die pretty quickly, however but there's one up now:

eBay linky
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
The way I figure it, when the original V10/V12 for Fuel was made, the price of RAM was such that there was an advantage to going with two types of RAM as they had done with the Octane V12's. As production continued, RAM prices fell, and it was cost effective to just go with the higher-density stuff, and build out to either a V10 or a V12 - this also meant that in production they only had to stock one set of parts and could build either way depending on demand much later in the manufacturing cycle. The resistor could be added or removed from the BOM at the time the production order went in, and the ID strings were programmable.

As a note, I too was poking around in the kernel files, and note that there is only one set of BUZZ microcode that get's uploaded. With all of the 'types' of V10/V12 part numbers out there, I can't actually imagine that they can actually check by part number, as a V12 is a V12, early or late vintage, and indeed poking through the Odyssey driver binary I didn't see anything obvious. If past history is any indication, I wouldn't be suprised if it was just the 'amount of reported memory' that determines to the system whether it's a V10 or a V12.

I have 2 V10's here, one with the old-style 32MB SGRAM, and one with the Samsungs. Guess I'll have to warm up the soldering iron tonight...

Addendum: Looks like in Hamei's photo's, the PCB part number is the same between both boards. I know the 'old-style' 32MB boards are different (they also have a 'Made in Canada' under the part number) but since the newer boards use the same PCB, it looks really promising...
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Probably a good time to build up the FrankenFuel from parts tonight too, for testing.

Addendum: Just had a quick glance at my 'old-style' V10 (XIO edge connector up), resistors are quite different, basically being:

Code: Select all

top set: x o o o
bottom set: o o o o

where x = resistor, o = open

This may however not mean much. If anyone has a loose Fuel V10/V12 with the larger chips, it would be worth seeing what they are set to and report back here, possibly with ID strings.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Don't piss on the electric fence, though.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Power screwdriver is charged, and got a dozen Timmies donuts... here's the starting point with the 'new-style' V10:

Code: Select all

Dudley 1% hinv
1 600 MHZ IP35 Processor
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Main memory size: 2048 Mbytes
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 4 Mbytes
Integral SCSI controller 3: Version SAS/SATA LS1064
Disk drive: unit 0 on SCSI controller 3
Integral SCSI controller 0: Version QL12160, low voltage differential
Disk drive: unit 1 on SCSI controller 0
Integral SCSI controller 1: Version QL12160, single ended
CDROM: unit 6 on SCSI controller 1
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: V10
Gigabit Ethernet: tg2, module 001c01, PCI bus 2 slot 1
Integral Fast Ethernet: ef0, version 1, module 001c01, pci 4
Iris Audio Processor: version MAD revision 1, number 1
USB controller: type OHCI

Note I'm using an X-session off my laptop to grab this, thus the 'unmanaged' board.

Code: Select all

Dudley 2% /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
Unmanaged 1280x1024
BUZZ version B.1
PB&J version 1
32MB memory
Banks: 2, CAS latency: 3
Monitor 0 type: Unknown
Xvc info not available for unmanaged boards

Code: Select all

Dudley 1# configmon -h
SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
0              NA            NA                  NA            NA        NA
1   MODULE_001c01            NA                  NA            NA        NA
2              L1        001c01                  NA            NA        NA
3            IP34        001c01              MDB183  030-1707-003        -F
4       MEMBANK_0        001c01                  NA            NA        NA
5       MEMBANK_1        001c01                  NA            NA        NA
6       MEMBANK_2        001c01                  NA            NA        NA
7       MEMBANK_3        001c01                  NA            NA        NA
8          R14000        001c01                  NA            NA        NA
9              NA        001c01                  NA            NA        NA
10            IP34        001c01              MDB183  030-1707-003        -F
11       ASTODYV10      XTALK_13              MSX293  030-1826-001        -B
12            IP34      XTALK_14              MDB183  030-1707-003        -F
13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
15     SCSI_CTLR_0            NA                  NA            NA        NA
16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
17     SCSI_CTLR_1            NA                  NA            NA        NA
18         CDROM_6            NA                  NA            NA        NA
19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
After a sprinkle donut...

Code: Select all

Dudley 1# /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 1280x1024
BUZZ version B.1
PB&J version 1
32MB memory
Banks: 2, CAS latency: 3
Monitor 0 type: Unknown
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 72.24Hz (1280x1024_72)
Dudley 2#

Code: Select all

Dudley 2# configmon -h
SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
0              NA            NA                  NA            NA        NA
1   MODULE_001c01            NA                  NA            NA        NA
2              L1        001c01                  NA            NA        NA
3            IP34        001c01              MDB183  030-1707-003        -F
4       MEMBANK_0        001c01                  NA            NA        NA
5       MEMBANK_1        001c01                  NA            NA        NA
6       MEMBANK_2        001c01                  NA            NA        NA
7       MEMBANK_3        001c01                  NA            NA        NA
8          R14000        001c01                  NA            NA        NA
9              NA        001c01                  NA            NA        NA
10            IP34        001c01              MDB183  030-1707-003        -F
11         ASTODYB      XTALK_13              MLB811  030-1725-001        -F
12            IP34      XTALK_14              MDB183  030-1707-003        -F
13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
15     SCSI_CTLR_0            NA                  NA            NA        NA
16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
17     SCSI_CTLR_1            NA                  NA            NA        NA
18         CDROM_6            NA                  NA            NA        NA
19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================

This is the 'old style' V10, with the square SGRAM's. Actually glad it works, this is the first time I've powered it up.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Boston Creme this time...

Code: Select all

Dudley 1# /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 1280x1024
BUZZ version B.1
PB&J version 1
32MB memory
Banks: 2, CAS latency: 3
Monitor 0 type: Unknown
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 72.24Hz (1280x1024_72)
Dudley 2#

Code: Select all

Dudley 2# configmon -h
SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
0              NA            NA                  NA            NA        NA
1   MODULE_001c01            NA                  NA            NA        NA
2              L1        001c01                  NA            NA        NA
3            IP34        001c01              MDB183  030-1707-003        -F
4       MEMBANK_0        001c01                  NA            NA        NA
5       MEMBANK_1        001c01                  NA            NA        NA
6       MEMBANK_2        001c01                  NA            NA        NA
7       MEMBANK_3        001c01                  NA            NA        NA
8          R14000        001c01                  NA            NA        NA
9              NA        001c01                  NA            NA        NA
10            IP34        001c01              MDB183  030-1707-003        -F
11       ASTODYV10      XTALK_13              MSX293  030-1826-001        -B
12            IP34      XTALK_14              MDB183  030-1707-003        -F
13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
15     SCSI_CTLR_0            NA                  NA            NA        NA
16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
17     SCSI_CTLR_1            NA                  NA            NA        NA
18         CDROM_6            NA                  NA            NA        NA
19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================


Resistor removed (note: value was 10k). No dice, didn't seem to make a difference. Ah well, up next...
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
hamei wrote:
Dr. Dave wrote:

Code: Select all

Dudley 1# /usr/gfx/gfxinfo

Is your other Fuel Snidely or Sweet_Nell ? Don't tell me it's Horse :P


LOL - no, it's Snidely...
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
so I was cruising through odyssey.a with hexedit - and I'm starting to get the feeling that the memory size, CAS, banks, etc. are stored in the config EEPROM on the Vpro board, and that everything seems to reference it from there, reading it through the I2C bus on the card. Since it looks like things are statically linked, more than likely the EEPROM would have to be read and reprogrammed to sort this out.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Hi, was thinking about that. Suspiciously, I'd bet that that 8-pin connector nearby is implicated in this process, but at worst case you'd just have to unsolder the EEPROM, read, and decode the data. If I was designing one of these boards, I'd try to make it easy to grab a blank one from inventory, install the correct profile, put on the appropriate V10 or V12 part number, and ship it.

I'll have a look at part numbers tonight and see if I can figure out what's going on.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I'm guessing U13, the Atmel 24c04 I2C serial EEPROM chip is the culprit.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Regarding newer drives, high platter densities mean that the areal transfer rates have gone way up on consumer drives lately - but as your test has noted the access times (and latencies) would still be better on the 15k drives. The 10k SATA drives are likely in the middle.

As for testing gotchas, I'd be concerned that for large contiguous files the SATA drive will post good numbers, but for small file accesses with lots of random seeks, the 15k SCSI drive will likely still win out by a fair margin. As a note, I always try to use a 15k drive as the root drive on any of the later-model SGI's I have - and for the Fuel this combo with a large consumer SATA/IDE drive for bulk storage (ie: homes) seems to be the best of both worlds. The root drive doesn't have to be more than 18GB or so to give you ample room for just about anything you'd want to do if you set it up this way, and 18GB 15k drives are pretty cheap.

So keeping this in mind, probably the two tests I'd try is a huge contiguous file transfer, and maybe a 'find' function across the disk to replicate random seek timing effects, using a SATA drive which has a duplicate filesystem to ensure the tests are equivalent. 'Diskperf' is actually a pretty good tool for easily showing this, though since it uses only the portion of the disk that the temp file is on, the numbers only represent a portion of the transfer curve for the platter.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
hamei wrote: Anyway, I was thinking that before we got really carried away, someone with a late-model V12 and V10 and some Arctic Silver should pop the heat sinks off and check out the markings on the underling chips. Just in case they are different ....


I'd guess not, actually. Gfxinfo always reports the version of the chip the same, and in comparing an Octane V8 and V12, the boards are identical, which leads me to believe that the taxonomy is:

32MB board vs. 128 MB board.
Slow ASIC vs. fast ASIC
EEPROM tells the driver which to configure
Stick on appropriate part number
Bill customer

It just appears in the case of the late-model Fuel V10's that the 32MB vs. 128 MB board distinction went away over the life of the product.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
This worked well for me in a loaded MXE Octane with a Lucent PSU:

Dr. Dave wrote: We have a winner!

The Panaflo FBA12G12M1BX seems to work well - I think it's blowing a bit more air than the regular fan on slow, but nowhere close to the vortex of doom that is a regular fan on full. TRAM temps seem up about 4-5 degrees on the MXI (basically nothing to worry about), and if you don't have anything particularly hot in the bottom right slot (here it's a shoehorn with a Gigabit etherenet card) then this tames the noise to the point of being noticeable, but not deafening. Still blows a lotta heat too. This is in a Lucent PSU.

For comparison:

Panaflo FBA12G12M1BX - 2100 RPM, 86.5 CFM, 35.5 dBa
Original PSU fan - 2750 RPM, 114 CFM, 45.2 dBa


Anything slower caused too much positive delta-T on the TRAM's on the MXE. I'd imagine a Vpro Octane 2 would probably have much the same problem.

Since then I've run it quite a bit (though not lately) and have not seen any problems whatsoever. The Cherokee's run quieter, but in this case I wanted an 'Octane 1' configuration (with MXE/PVO), as I already have 3 newer systems.

As for acoustic dampening, I'd be tempted to try those silicon rubber fan frames you see at the modz store, though they're probably not compatible with the clip mounts due to thickness. I tried one in the PSU and it caused the fan hub to rub on the PSU circuit board, so out it came. The idea is that by acoustically isolating the fan from the box, the vibration noise won't transfer, rather than trying to dampen the vibrations in the box plastic itself. Some PC fans come with rubber 'pull mounts' (rubber 'bolts' that pull through the fan mount holes, I believe Zalman fans come to mind) that might be useful if you drilled the clips out of the fan box and used these rubber pins to mount the fan instead.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Load up your XIO's (the infamous 'bottom right' is usually the culprit), and they still make tons of noise and benefit from the fan swap. As a bonus, if you're finding yourself in a situation where fastfan hasn't yet kicked in, it will be quieter than stock with the peace of mind that there is still adequate airflow if fastfan is required.

I'd agree that on a lightly loaded Octane, the top fan is the loudest. Be curious to see how it turns out. Do you have a sound level meter to generate some numbers?
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Just be careful, sometimes those SilentX fans don't deal well with back pressure.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I'd have to find where I saw that reference. But this is interesting.

I have a 92mm SilenX in my main PC as a front fan, it's not noticeably quieter than a lot of other fans, but I was disappointed at the airflow. I would also say that the small hub motor would likely factor into the backpressure issue as it reduces available torque at the hub to spin the rotor. I've been much more satisfied with the Zalman, Scythe, or Arctic Cooling fans, running examples of each, and consider the Panaflo's to be of better quality than any of them, but likely not in the same acoustic league.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Good question. Probably U11, though I don't have a Fuel video card handy. It's the Philips part, and should be basically an I/O chip with an I2C interface - I tried looking at the pics posted a while back but can't read the part number. Philips calls these parts "I/O Expanders" so no bowdlerization there.

So.... it's looking like in the case where there are issues, the I2C interface to the graphics card is not working, or at least the I2C peripherals on the card are not responding. I'd bet the later revisions of the L1 firmware have issues initializing the I2C controller on the motherboard. and thus (depending on the severity of the problem) may cause *none* of the I2C peripherals to be detected. This of course leads to the inevitable problem...

Hamei, have a look at U11 closely and see if there is anything like a cold solder joint. There is a cluster of I2C chips around there, including the Dallas environment monitor and an Atmel flash chip, as well as the Philips part and whatever else. Check them all. The address is latched internally at reset if I remember correctly, so basically if it's flaky and you reset it enough times it will eventually 'latch' the correct value and everything is then hunky-dory until the next reset/powerup.

I2C is a bidirectional serial protocol, all the peripheral chips are wired in parallel, and a unique 'address' is usually hard-strapped to each device by tying pins high and low. For the flaky board, it could be possible that one of the chips is getting an incorrect address strapped to it (which would interfere with the address decoding mechanism), or again the mainboard I2C (or whatever I2C controller the L1 has access too, probably on-chip) is not being set-up/initialized/run properly by the later L1 firmware.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Worked great on an RM5200/300 O2!
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I have bought one of these in the past, perhaps pricier than some used items, but you get:

- the FPA
- the Colorlock sensor
- Installation guide (can't remember if there was software, but the 1600SW software is on the Irix install CD's anyways)
- Nifty SGI screwdriver
- brand spanking new, get your shrinkwrap ripping skills a twirl.

so not out of line. Basically if you want 'the whole shebang' this is it, after that you can just search out the FPA loose, and still have a Colorlock sensor to do color calibration.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Sure we're talking about the same Ford here? If you think this is just 'nice', hate to see what you think is awesome! LOL!

(Supposedly they are *very* drivable. and keep the malarkey content down pretty low, AND are pretty fuel efficient to boot)

Ford GT from Wikipedia .
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
iKitsune wrote: Ford Crown Victora Police Interceptor. Fun, fast, safe, and affordable by mortals. Besides, it's like driving a land-boat, the last of the great body-on-frame rear-wheel-drive American gashog monsters.

First car was a hand me down '75 Ford LTD Landau...

Some notes:

- Speed bumps? OK, I'll speed up...
- Hood longer than most microcars these days
- Lawn roller fit in the trunk, with the trunk closed.
- Seats wide enough to sleep stretched out in, or other things...
- Record was 7 people at the drive in, 3 in the front, 4 in back, beer in the trunk. Not really cramped at all...

Everything after that was a Ford truck. Currently an '09 Ranger FX4 off-road, manual tranny, Zexel-Torsen 4.10 LSD in the back, 4.0 SOHC motor. Li'l hot rod.

Shameless topic link: Was gonna call it the 'Octane III', but lo-and-behold... :?
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I had to do a symlink to get it to work, as /usr/nekoware/lib doesn't seem to be in the internal library path. I think I linked it to the regular SGI lib directory, that is linked an entry to the Nekoware libglut in the system library directory, as the path to this was in the error message as one of the directories it checks. This can also likely be fixed with an environment path variable, perhaps someone can come up with a cleaner, less hacky way of doing this.,

Code: Select all

ln -s /usr/nekoware/lib/libglut.so /usr/lib32/libglut.so


Think this is what I did, but may have that wrong. If it doesn't work it's close. Someone feel free to correct me if it isn't right.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
hamei wrote: Well, that was interesting .... my O2 runs at 1440 x 900 so I thought I'd give it a shot from home. Found out I didn't have glut installed so got that. Gave the executable a double-click and wham ! computer locked up tighter than a Shanghai Princess' pocketbook. Not the desktop, the entire thing. Vulcan death grip failed, power button failed, I had to pull its life support cord. Sumbitch.

Got it back running again, since Mom is a Republican I guess stupidity is inherited. I gave it another try, this time from a terminal. Wham ! locked up instantly again. I was hoping that just that app would freeze and I could close the terminal window but no such luck. Same thing, nothing did nothin', had to cut off her vital bodily fluids to shut down. Damn commies are everywhere.

This is an r5k-350 O2 running 6.5.22, graphics is 1440 x 900, neko glut (the latest one, forget what rev.)


Worked fine on one of my O2's, only diff from your's is a 300 MHz CPU, even using the same resolution. Something about the code locks up the 350 CPU's maybe?
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
"PCC" = 'Programmable Communications Controller' maybe?

Look up the datasheets on those AMD chips at the bottom, that should give you a good idea.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
nekonoko wrote: Yeah, looking at the auction description again it does say it's missing video (graphics) as well as the drive sleds. The sleds aren't really a problem as Tezro uses generic sleds (one suitable replacement being Sun 330-3696 spuds; there are several of those on eBay).

Finding a cheap Tezro/Fuel V12 for it might not be fun though. But it would make a good parts machine for Dr. Dave :)


frackin' hell!
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I'll find out how much shipping will be tomorrow, and see who else bids on it. One bid in already (not mine).
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
pentium wrote:
porter wrote:
pentium wrote:
Geez, now that I got this and a few cables, what exactly can be done with it? I know I have to find a new rack for it (ugh....) but what use is HP-UX, if that is still on the drive?


HP/UX is an excellent OS. Did you talk the opportunity of the offer....?

http://forums.nekochan.net/viewtopic.php?f=18&t=10771&start=0

Bah, I heard about that but that was just when I was getting into obscure hardware so no I didn't take up on that offer. :<

Edit: oh, and judging from the yelling I am receiving from my dad, it needs to be out of the living room immediately. this is going to eb a fun noght. Now he'' be asking me 20 questions about why I need it (actually, I don't know why I need it but it's too late now).

EDIT: Crap, I can hear him slamming doors and yelling. I think this was a REALLY bad idea.

EDIT: Bad idea it was. I have to get it out of my fathers sight before dawn or else it is off to the scrappers tomorrow weather I like it or not.


I've had days like this... but not in the last 15 years or so...

_________________
:O3000: :O2000: <> :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
pentium wrote:
After I figured out how to pull the enormous battery packs out of their boxes I dragged everything downstairs and I'm safe...for now.
Still, one thing that confuses me is why the UPC charger/inverter inputs and outputs 230v even though all the hardware can run at 110v no problem. I take it this is partly because the higher the voltage, the lower the amperage draw, right?


Yes, but that doesn't impact the watt-hour capacity of the battery. Most switching power supplies have better efficiency at 230v, and this is likely part of the answer.

_________________
:O3000: :O2000: <> :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
I have an IBM 5150 PC back at home in the barn. It has a working Intel Inboard386 co-processor card in it (last time I checked it worked). It's fast for a 5150!
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Just finally got all the bits together, this should be useful for something!

Anyone have any suggestions as to which video tools will work best with this?

_________________
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Two cents worth on the O2 CPU modules.

With the exception of the 400 MHz R12k, I think they were all the removable CPU's. Once when I was messing with a module, I got the machine to start booting at 400 MHz (with a 300 MHz chip) but it didn't get very far. A good R12k-300 chip will usually run at 350 reliably, but not much more as you're running into process limits on the silicon. I've found with the Octane modules that I don't think I've had one that had any cache issues assuming your chip will run at 350, and from what I've seen the O2 modules are similar. 350 is probably the highest safe overclock then for an R12k module. Anything below 250 MHz doesn't have the necessary split-plane power supply and can't really be upgraded, so they're basically called 'test modules' around here.

Of interest is modding an R12k-400 to 450 MHz, but I only have one module and would hate to break it, as they're quite rare these days. Probably be the worlds fastest O2 at that point.

I did a lot of messing around with cache speeds on the Octane. There is a single CPU module - originally a 400 - kicking around out there I did quite some time ago, and think it ran at 470 MHz with the stock cache divider. This is the exception rather than the norm.

Attached is my little cache-speed calculator for Excel, it takes the actual 'resistor divider' number and module crystal frequency, and spits out the final CPU clock and cache speed.

_________________
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
SAQ wrote:
mapesdhs wrote:
I figure one couldn't move a 360 core into a 250 module as the cache would be too different, yes?

I have a couple of 360 modules I can expt with. However, I'd need to know a bit more about the multiplier resistor positions to try it.

Ian.


I think I might have found your problem with the Octane PM20s upgraded from 250.

It appears that SGI used a 1:1 ratio for the cache for 250 and under, while 300 (at least for Origin) uses 5nS SRAMs for a 200MHz cache clock (2:3). Unless you swap out the setup SEPROM with one that changes the cache timing it seems you're running the 250MHz cache at full processor speed when you bump it up to 350, and I don't think the SRAM has enough tolerance. Note I haven't actually opened up my PM20 yet, so this is mostly conjecture based on documentation and hinvs. 250MHz would require 4nS chips, 300 would require 3.3nS, and 350 2.8nS (for a 1:1 divisor), and my guess is there isn't quite enough headroom in the 250s cache chips. If you have a 2MB dualie and 2MB 300 singlies you can pull the SEPROM and swap that as well and you should be good (a 1MB dual 250 would need a reprogram to deal with the different cache size, as would the chips from the Origin PIMMs w/ 8MB SC).

I so need an EPROM programmer :(


For an Octane PM, it's still resistors, Shown is the 1.5 and 2.0 positions, useful for all but the slowest PM's. The duals are similarly configured, though the BGA dual boards have a slightly different layout.

http://www.nekochan.net/wiki/gallery2/v/SGI_ ... d.jpg.html

_________________
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
The problem I believe is the 360's and 400's are soldered to the board and are not removable. The R12k-360 is basically a binned R12k-400, so basically if you're overclocking these you are limited to how far you can push the chips.

I have a dead O2 module that has had the 350 hack which surfaced recently, I will try to take a pic tomorrow and post it up for comparison.

_________________
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day