The collected works of Jack Luminous - Page 1

Looking for a DCD for my V12 octane2 ! PM me...
I'm interested too. PM me if one deal falls through...
You are not alone. And for some people (me included), it is not only SGI stuff but also old cinema projectors, old industrial coffee machines, old pinball games, old swiss reel-to-reel machines, old tube amps, old Altec horn speakers etc. I wouldn't call it insanity but more of a slight mental disorder bordering on fetichism. There's an undeniable pleasure in getting out of scraps an old useless, very pricy, well-engineered, complicated and arguably beautiful mechanical/electronic thing and getting it to work as intended by researching documentation, gathering spare parts, tinkering with it endlessly etc. 8-)
:Octane2: :Octane: :Octane: :O2:
jan-jaap wrote:
Jack Luminous wrote: old swiss reel-to-reel machines

Studer/Revox? Kewl. I swear, one day I'll buy a Mk II B77 8-)


Yes Revox. One C278 eight track to record and one C270 two track to mix. Great machines ! I spoke to the local Revox dealer about spare parts availability and he told me : "Yes, we have a huge spare parts stock for all models from way back to the 50s". Then I asked : "What if some special part is not in stock anymore, especially the record/play/erase heads ?" and he replied : "Don't worry, we still have all the original molds, we'll just make new ones".... 8-)
:Octane2: :Octane: :Octane: :O2:
So I bought this saturday a nice 1600SW+Multi Link Adapter from Nekochan member bplaa.yai (thanks a lot for the delivery at home !). I then fiddled the whole WE to make the combo work with V12/DCD equipped Octane. Not very straightforward but it kinda worked in the end, thanks to the invaluable infos shared in here. Curiously, the various 1600x1024 vfos found in my install didn't work at all. I finally used the 1600x1024_60-1704TPPL-1056TLPF.vfo file (to be found here : http://forums.nekochan.net/viewtopic.php?f=3&t=16725775 ).

Still, there remains a minor annoyance that I couldn't solve. When the Octane boots up with the 1600SW+MLA plugged in one of the DVI slot, the above mentionned 1600x1024 vfo disappears from the list in xsetmon and some default 1280x1024 is automatically selected. At this point, there is no way to get back to 1600x1024. When I boot up the machine without any monitor connected until the graphic login screen, and then hotplug the DVI, the vfo is back in the list and I can select it properly and make it the default choice. That means : every time I reboot or start up, I need to unplug first the DVI (so that IRIX can't detect the 1600SW+MLA contraption) and plug it later to get the native 1600x1024 or else I'm back at 1280x1024.

It is workable as it is but kinda annoying. Is there's a way to avoid that ?
:Octane2: :Octane: :Octane: :O2:
Geoman wrote: This is really cool!! Strange though, that Octane2+DCD+1600 SW isn't working right out of the box, since this was once upon a time a possible configuration from SGI(?)
octane2_2.jpg


I'm running 6.5.22 at the moment. Maybe I'm missing some needed patch to make the whole thing smoother ?
:Octane2: :Octane: :Octane: :O2:
I use the digital input of the MLA so Sync-On-Green is not the problem...
:Octane2: :Octane: :Octane: :O2:
I confirm it does work with the aforementioned vfo. I was still tinkering with the setup (looks exactly like the pic above) this morning before going to work. But I'd really like to make it work without unplugging the the DVI each and every time... ;)
:Octane2: :Octane: :Octane: :O2:
recondas wrote: In the mean time you might try connecting the DVI port of the 1600SW/MLA to another system to see if you can capture the EDID info and try for a 1600SW/MLA tailored VFO using the EDID template .


I don't have a DVI equipped computer at home apart from the Octane. Though I googled some EDID info about 1600SW+MLA and found this :

<00ffffff ffffff00 4ce90016 55a1aec6 04030103 00100a00 0e000000 00000000 00000021 0800a900 81400101 01010101 01010101 0101302a 40686000 20401030 1300a820 64000000 302a0068 50002040 c8701300 a8206400 00000000 00fc0053 4749204d 756c7469 6c696e6b 000000fd 003c463c 4619000a 20202020 202000b9>

Which translate to :

Code: Select all


Time: 15:43:00
Date: lundi 3 mars 2014
EDID Manager Version: 1.0.0.14
___________________________________________________________________

Block 0 (EDID Base Block), Bytes 0 - 127,  128  BYTES OF EDID CODE:

0   1   2   3   4   5   6   7   8   9
000  |  00  FF  FF  FF  FF  FF  FF  00  4C  E9
010  |  00  16  55  A1  AE  C6  04  03  01  03
020  |  00  10  0A  00  0E  00  00  00  00  00
030  |  00  00  00  00  00  21  08  00  A9  00
040  |  81  40  01  01  01  01  01  01  01  01
050  |  01  01  01  01  30  2A  40  68  60  00
060  |  20  40  10  30  13  00  A8  20  64  00
070  |  00  00  30  2A  00  68  50  00  20  40
080  |  C8  70  13  00  A8  20  64  00  00  00
090  |  00  00  00  FC  00  53  47  49  20  4D
100  |  75  6C  74  69  6C  69  6E  6B  00  00
110  |  00  FD  00  3C  46  3C  46  19  00  0A
120  |  20  20  20  20  20  20  00  B9

(8-9)       ID Manufacture Name : SGI
(10-11)     ID Product Code     : 1600
(12-15)     ID Serial Number    : ???U
(16)        Week of Manufacture : 4
(17)        Year of Manufacture : 1993

(18)        EDID Version Number : 1
(19)        EDID Revision Number: 3

(20)        Video Input Definition: Analog
0.700, 0.300 (1.000 V p-p)

(21)        Maximum Horizontal Image Size: 16 cm
(22)        Maximum Vertical Image Size  : 10 cm
(23)        Display Gamma                : 1,00
(24)        Power Management and Supported Feature(s):
RGB Color, sRGB, Preferred Timing Mode

(25-34)     Color Characteristics
Red Chromaticity   :  Rx = 0,000  Ry = 0,000
Green Chromaticity :  Gx = 0,000  Gy = 0,000
Blue Chromaticity  :  Bx = 0,000  By = 0,000
Default White Point:  Wx = 0,000  Wy = 0,000

(35)        Established Timings I

640 x 480 @ 60Hz (IBM, VGA)
800 x 600 @ 60Hz (VESA)

(36)        Established Timings II

1024 x 768 @ 60Hz (VESA)

(37)        Manufacturer's Timings (Not Used)

(38-53)     Standard Timings

1600x1000 @ 60 Hz (16:10 Aspect Ratio)
1280x960 @ 60 Hz (4:3 Aspect Ratio)

(54-71)     Detailed Descriptor #1: Preferred Detailed Timing (1600x1024 @ 60Hz)

Pixel Clock            : 108 MHz
Horizontal Image Size  : 1704 mm
Vertical Image Size    : 1056 mm
Refresh Mode           : Non-interlaced
Normal Display, No Stereo

Horizontal:
Active Time     : 1600 Pixels
Blanking Time   : 104 Pixels
Sync Offset     : 16 Pixels
Sync Pulse Width: 48 Pixels
Border          : 0 Pixels
Frequency       : 63 kHz

Vertical:
Active Time     : 1024 Lines
Blanking Time   : 32 Lines
Sync Offset     : 1 Lines
Sync Pulse Width: 3 Lines
Border          : 0 Lines

Analog Composite, Horizontal Polarity (-), Vertical Polarity (-)

Modeline: "1600x1024" 108,000 1600 1616 1664 1704 1024 1025 1028 1056 -hsync -vsync

(72-89)     Detailed Descriptor #2: Detailed Timing (1280x1024 @ 74Hz)

Pixel Clock            : 108 MHz
Horizontal Image Size  : 1704 mm
Vertical Image Size    : 1056 mm
Refresh Mode           : Non-interlaced
Normal Display, No Stereo

Horizontal:
Active Time     : 1280 Pixels
Blanking Time   : 104 Pixels
Sync Offset     : 200 Pixels
Sync Pulse Width: 112 Pixels
Border          : 0 Pixels
Frequency       : 78 kHz

Vertical:
Active Time     : 1024 Lines
Blanking Time   : 32 Lines
Sync Offset     : 1 Lines
Sync Pulse Width: 3 Lines
Border          : 0 Lines

Analog Composite, Horizontal Polarity (-), Vertical Polarity (-)

Modeline: "1280x1024" 108,000 1280 1480 1592 1384 1024 1025 1028 1056 -hsync -vsync

(90-107)    Detailed Descriptor #3: Monitor Name

Monitor Name: SGI Multilink

(108-125)   Detailed Descriptor #4: Monitor Range Limits

Horizontal Scan Range: 60kHz-70kHz
Vertical Scan Range  : 60Hz-70Hz
Supported Pixel Clock: 250 MHz
Secondary GTF        : Not Supported

(126-127)   Extension Flag and Checksum

Extension Block(s)  : 0
Checksum Value      : 185

___________________________________________________________________


It looks like it's the same values you used for the previous vfo : Horizontal Image Size : 1704 mm Vertical Image Size : 1056 mm. But I'm not sure.


recondas wrote: Probably not the elegant workaround you were hoping for, but instead of hot-plugging the DVI cable have you tried disconnecting the MLA power supply before booting (to see if that stops the exchange of DDC/EDID info)?


I tried and apparently the EDID is read as long as the DVI cable is plugged, even when the MLA is not powered. I haven't tried to disconnect the 1600SW itself. I'll try tonight.
:Octane2: :Octane: :Octane: :O2:
bplaa.yai wrote: I'm glad it found a good SGI enthusiast home, and that it's living on the edge of unsupported SGI configuration :D


LOL Thanks a lot for your saturday delivery !

So I had 10 minutes this morning before going to work for further testing. here are the results :

- the DVI must be physically disconnected to avoid the EDID reading. Even if both the MLA+1600SW are both shut off, the VPRO card still detects everything and reverts back to "authorized" vfos list.

- I tried with the VPro_1600x1024_60-Analog_MLA.vfo posted above and it gives the same result as the other one : it disappears from the list if the DVI is connected at startup. But it works fine with the hot-plugging scenario.

To be continued... :D
:Octane2: :Octane: :Octane: :O2:
First post from Octane2 freshly configured with Firefox3 installed this morning ! YEAH ! Thanks to everyone who contributed to make this work ! I'm gonna post some hinv next ! 8-)
:Octane2: :Octane: :Octane: :O2:
Sorry, no pics yet, I was too busy making the damn thing work.... Will add later !

Code: Select all

# hinv -vm
Location: /hw/node
PM20600MHZ Board: barcode MME908     part 030-1778-001 rev  C
Location: /hw/node/xtalk/15
IP30 Board: barcode LKD174     part 030-1467-001 rev  D
Location: /hw/node/xtalk/15/pci/2
PWR.SPPLY.ER Board: barcode AAE1330738 part 060-0035-003 rev  A
FP1 Board: barcode MKE459     part 030-0891-003 rev  J
Location: /hw/node/xtalk/11
ODY128VERSIONB Board: barcode MDF684     part 030-1611-001 rev  C
2 600 MHZ IP30 Processors
Heart ASIC: Revision F
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 0.0
Main memory size: 2048 Mbytes
Xbow ASIC: Revision 1.4
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: V12
Integral Fast Ethernet: ef0, version 1, pci 2
Iris Audio Processor: version RAD revision 12.0, number 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 3
Dual Channel Display


Code: Select all

# /usr/gfx/gfxinfo -vv
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 1600x1024
BUZZ version B.1
PB&J version 1
128MB memory
Banks: 4, CAS latency: 3
Monitor 0 type: Unknown
Dual Channel Display option
Monitor 1 type: Unknown         Monitor 2 type: Unknown
Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
Channel 0:
Origin = (0,0)
Video Output: 1600 pixels, 1024 lines, 60.00Hz (VPro_1600x1024_60-Analog_MLA)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  unknown
Gain (all color components) - 0.000000 ; range [1,10]
:Octane2: :Octane: :Octane: :O2:
vishnu wrote: Very nice machine! Quite like mine. I've always thought it odd that gfxinfo doesn't post the graphics board number for the V series. Presumably your DCD works? Mine doesn't work for crap, may I ask what monitors you're using?


Yes the DCD works with a single monitor. I'm using a 1600SW+Multilink Adapter. Not easy to make it work but it worked in the end. See viewtopic.php?f=3&t=16728430&start=15 for the gory details involving butchering a poor DVI-D cable.

mia wrote: now that's a nice machine, doesn't get much better than this.


I want to put 8 gigs in it. But it' too costly for now. Anyway FF3 is working much better than I expected. Quite fast and no crash yet.
:Octane2: :Octane: :Octane: :O2:
Updated with dual channel SGI fibre XIO card + Discreet D9 Stone

Code: Select all

# hinv -vm
Location: /hw/node
PM20600MHZ Board: barcode MME908     part 030-1778-001 rev  C
Location: /hw/node/xtalk/15
IP30 Board: barcode LKD174     part 030-1467-001 rev  D
Location: /hw/node/xtalk/15/pci/2
PWR.SPPLY.ER Board: barcode AAE1330738 part 060-0035-003 rev  A
FP1 Board: barcode MKE459     part 030-0891-003 rev  J
Location: /hw/node/xtalk/11
ODY128VERSIONB Board: barcode MDF684     part 030-1611-001 rev  C
Location: /hw/node/xtalk/10
FIBRE_CHANNEL Board: barcode KXA033     part 030-0927-003 rev  E
2 600 MHZ IP30 Processors
Heart ASIC: Revision F
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 0.0
Main memory size: 2048 Mbytes
Xbow ASIC: Revision 1.4
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
Integral SCSI controller 4: Version Fibre Channel AIC-1160, revision 4
Disk drive: unit 0 on SCSI controller 4 (unit 0)
Disk drive: unit 1 on SCSI controller 4 (unit 1)
Disk drive: unit 2 on SCSI controller 4 (unit 2)
Disk drive: unit 3 on SCSI controller 4 (unit 3)
Disk drive: unit 4 on SCSI controller 4 (unit 4)
Disk drive: unit 5 on SCSI controller 4 (unit 5)
Disk drive: unit 6 on SCSI controller 4 (unit 6)
Integral SCSI controller 3: Version Fibre Channel AIC-1160, revision 4
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: V12
Integral Fast Ethernet: ef0, version 1, pci 2
Iris Audio Processor: version RAD revision 12.0, number 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 3
PCI Adapter ID (vendor 0x9004, device 0x1160) PCI slot 0
PCI Adapter ID (vendor 0x9004, device 0x1160) PCI slot 1
Dual Channel Display
:Octane2: :Octane: :Octane: :O2:
Thanks ! Luckily, it has been pretty painless to set up until now. One of my goals with it is to buy some used bigger FC hdds from ebay and create a big and fast file server with the thing. I still need to buy a cheap PCI gigabit ethernet card to put in the PCI cage (already have the cage but it is not plugged in yet).

The only drawback of the whole system is the noise of the D9 Stone... Crazy !!! I didn't fire it up in 3 years or so and totally forgot the madness. When I pushed the on button this morning after set up, it felt like an airplane taking off in my basement. Can't even hear the Octane next to it ! :D

I don't understand why it needs so much cooling... I'm gonna try to replace the fans with modern ones and slow them down with resistors... Pics coming in the next few days... 8-)
:Octane2: :Octane: :Octane: :O2:
recondas wrote: If you don't mind pin-plucking another DVI cable (and just happen to have a second 1600SW/MLA) you can always try for a [email protected] monitor set up.


I wouldn't mind pin-plucking another DVI cable and would love to try a [email protected] monitor set-up. It also happens that I have a second 1600SW to go with my O2 but I only have one MLA so it will have to wait for some more SGI play-money availability. I already got past the intended budget in the last month to get everything up and running as I wanted.

jan-jaap wrote: The D9 stone is the cube shaped metal box, right? Those go back to the 1st generations of 10K disks etc, and they ran *hot*. Put a dozen together in a shoebox and you need a lot of airflow.

Modern disks run much cooler, so you can reduce cooling as well. I have one of these which was modded with an ATX PSU -- probably because the original PSU died. Then the ATX PSU died as well :(


Yes it's the cube shaped industrial metal looking thing. What hdd would you advise to use ? I see a lot of cheap used 300gb FC hdd on the bay or even 600gb sometimes...
:Octane2: :Octane: :Octane: :O2:
Yes, it's in a basement, under metallic stairs. And I'm not much of a photographer LOL


Image
:Octane2: :Octane: :Octane: :O2:
So, has someone successfully run Premiere on a VPro equipped Octane ? Is there some known trick or should I let it go already ? :?:
:Octane2: :Octane: :Octane: :O2:
LOL thanks for your straight-to-the-point reply. :D
:Octane2: :Octane: :Octane: :O2:
Grandmaster Flash - The Message

https://www.youtube.com/watch?v=O4o8TeqKhgY

Afrika Bambaataa - Looking For The Perfect Beat

https://www.youtube.com/watch?v=2RJlYzBhLg4

Kurtis Blow - The Breaks

https://www.youtube.com/watch?v=5ZDUEilS5M4
:Octane2: :Octane: :Octane: :O2:
Either a maxed out O2 with R12K 400 and 1 gig ram. It's a really small, nice and comfy little workstation. You can already do a lot of things with it. I really like mine. Or if you want more power, a bigger Octane with dual cpu is really faster and more responsive. I have one with dual 600mHz, V12+DCD and 2 gigs ram. It's my go-to machine.
:Octane2: :Octane: :Octane: :O2:
Here's my own collection :

Code: Select all

812-0119-006 : IRIX 5.3 : Nov 94
812-0128-005 : Network File System 5.3 : Nov 94
812-0129-005 : IRIS Development Option 5.3 : Nov 94
812-0400-010 : MIPSpro C++ Compiler 7.4 requires IRIX 6.5 or later (no support for IRIX 6.2, 6.3 or 6.4) : Nov 02
812-0402-010 : MIPSpro Fortran 90 Compiler 7.4 requires IRIX 6.5 or later (no support for IRIX 6.2, 6.3 or 6.4) : Nov 02
812-0403-010 : MIPSpro Fortran 77 Compiler 7.4 requires IRIX 6.5 or later (no support for IRIX 6.2, 6.3 or 6.4) : Nov 02
812-0653-003 : SCSL Scientific Library 1.3 : July_2000
812-0688-024 : IRIX 6.3 Recommended Required Patches 1 of 2 : Mar 1999
812-0688-027 : IRIX 6.3 Recommended Required Patches 1 of 2 : Jun 1999
812-0688-030 : IRIX 6.3 Recommended Required Patches 1 of 2 : Sep 1999
812-0690-002 : SoftWindows 95 5.0 : June 1998
812-0706-004 : MIPSpro Auto Parallelizing Option 7.4
812-0707-004 : MIPSpro C Compiler 7.4 requires IRIX 6.5 or later (no support for IRIX 6.2, 6.3 or 6.4) : Nov 02
812-0739-004 : EnlightenDSM 3.1 : May 1999
812-0757-002 : IRIX 6.5 Development Foundation : Jun 1998
812-0757-004 : IRIX Development Foundation 1.3 requires IRIX 6.5 or later (no support for IRIX 6.2, 6.3 or 6.4) : Nov 02
812-0758-002 : IRIX 6.5 Installation Tools : Jun 1998
812-0759-002 : IRIX 6.5 Foundation 1 : Jun 98
812-0760-002 : IRIX 6.5 Foundation 2 : Jun 98
812-0761-002 : IRIX 6.5 Applications : Jun 1998
812-0766-002 : IRIX 6.5 Development Libraries : Jun 1998
812-0766-003 : IRIX 6.5 Development Libraries : Feb 02
812-0768-006 : ProDev WorkShop 2.9.2
812-0773-001 : Freeware : Jun 1998
812-0773-004 : Freeware : May 1999
812-0773-013 : Freeware Part 1 of 3 : Aug 2001
812-0773-017 : Freeware 1 of 4 : Aug 2002
812-0774-002 : ONC3/NFS Version 3 for IRIX 6.2, 6.2, 6.4 and 6.5 : May 99
812-0776-001 : Database Accelerator 3.0 : Jul 1998
812-0779-001 : IRIX 6.5 Base Documentation : Jun 1998
812-0779-004 : IRIX 6.5.4 Base Documentation : May 1999
812-0779-013 : IRIX 6.5.15 Base Documentation : Aug 2001
812-0779-015 : IRIX 6.5.15 Base Documentation : Feb 02
812-0779-017 : IRIX 6.5.17 Base Documentation : Aug 2002
812-0780-001 : O2 Demos 1.2 : Jun 1998
812-0783-001 : SNMP Access to HP-UX MIB 1.1.2 : Jun 1998
812-0783-002 : SNMP Access to HP-UX MIB 1.1.3 for IRIX 6.5 and later : Dec 99
812-0787-001 : OCTANE IMPACT Video : Jun 1998
812-0817-013 : IRIX 6.5.13 Overlays (3 of 3) : Aug 01
812-0817-017 : IRIX 6.5.17 Overlays (3 of 4) : Aug 2002
812-0817-021 : IRIX 6.5.21 Overlays (3 of 4) : Aug 03
812-0817-022 : IRIX 6.5.22 Overlays (3 of 3) : Nov 03
812-0817-023 : IRIX 6.5.23 Overlays (3 of 3) : Feb 2004
812-0817-029 : IRIX 6.5.29 Overlays (3 of 3) : Feb 2006
812-0817-030 : IRIX 6.5.30 Overlays (3 of 3) : Aug 2006
812-0818-004 : IRIX 6.5.4 Installation Tools and Overlays (1 of 2) : May 1999
812-0818-013 : IRIX 6.5.13 Installation Tools and Overlays (1 of 3) : Aug 2001
812-0818-017 : IRIX 6.5.17 Installation Tools and Overlays (1 of 4) : Aug 2002
812-0818-021 : IRIX 6.5.21 Installation Tools and Overlays (1 of 3) : Aug 2003
812-0818-022 : IRIX 6.5.22 Installation Tools and Overlays (1 of 3)
812-0818-023 : IRIX 6.5.23 Installation Tools and Overlays (1 of 3) : Feb 2004
812-0818-029 : IRIX 6.5.29 Installation Tools and Overlays (1 of 3) : Feb 2006
812-0818-030 : IRIX 6.5.30 Installation Tools and Overlays (1 of 3)
812-0819-003 : IRIX 6.5.3 Overlays (2 of 2) : Feb 1999
812-0819-004 : IRIX 6.5.4 Installation Tools and Overlays (1 of 2) : May 1999
812-0819-013 : IRIX 6.5.13 Overlays (2 of 3) Aug 2001 : Aug 01
812-0819-017 : IRIX 6.5.17 Overlays (2 of 4) : Aug 2002
812-0819-021 : IRIX 6.5.21 Overlays (2 of 4) : Aug 2003
812-0819-022 : IRIX 6.5.22 Overlays (2 of 3) : Nov 2003
812-0819-023 : IRIX 6.5.23 Overlays (2 of 3) : Feb 2004
812-0819-029 : IRIX 6.5.29 Overlays (2 of 3) : Feb 2006
812-0819-030 : IRIX 6.5.30 Overlays (2 of 3) : Aug 2006
812-0877-003 : IRIX 6.5 Applications : May 1999
812-0877-012 : IRIX 6.5 Applications : Aug 2001
812-0877-017 : IRIX 6.5 Applications : Aug 2002
812-0877-019 : IRIX 6.5 Applications : Feb 2003
812-0877-021 : IRIX 6.5 Applications : Aug 2003
812-0877-023 : IRIX 6.5 Applications : Feb 2004
812-0877-030 : IRIX 6.5 Applications : Aug 2006
812-0881-001 : TELEFFECT 1.0
812-0892-001 : 1600SW Flat Panel Patches IRIX 6.3 : Dec1998
812-0918-030 : IRIX 6.3 Recommended Required Patches 2 of 2 : Sep 1999
812-0924-002 : Compiler Execution Environment 7.4
812-0964-013 : Freeware Part 2 of 3 : Aug 2001
812-0964-017 : Freeware Part 2 of 4 :Aug 2002
812-1066-002 : General & Platform Demos 6.5.12 1-of-2
812-1085-013 : Freeware Part 3 of 3 : Aug 2001
812-1086-002 : Silicon Graphics General and Platform Demos 6.5.12 2 of 2 : May 2001
812-1123-017 : IRIX 6.5.17 Overlays 4 of 4 : Aug 2002
812-1123-021 : IRIX 6.5.21 Overlays 4-of-4 08/03 : August 2003
812-1137-017 : Freeware Part 4 of 4 : Aug 2002
812-1180-023 : IRIX_6.5 Complementary Applications : Feb2004
812-1180-030 : IRIX 6.5 Complementary Applications : Aug 2006
812-1197-001 : Artifex Technology Patch 6.5.15 through 6.5.23 : May 2004
:Octane2: :Octane: :Octane: :O2:
No.
:Octane2: :Octane: :Octane: :O2:
Yes the missing gateway ip address is likely the problem. You must fill it with your cable modem ip address for the Octane to reach the net. I think you can set it using the toolchest network tool.
:Octane2: :Octane: :Octane: :O2:
Wow what a relief ! I was scared, alone in the dark with my SGI toys LOL
:Octane2: :Octane: :Octane: :O2:
Can we have it back please ?
:Octane2: :Octane: :Octane: :O2:
Wow thanks ! I'm a total noob concerning phpbb etc. I was really annoyed that something I clicked thousands of times had suddenly disappeared from my life LOL
:Octane2: :Octane: :Octane: :O2:
recondas wrote: Without picking out anyone in particular (I've had my share of WTF moments too), the idea that simple forum interface overwhelmed guys who routinely master obscure operating systems and hardware (in a number of flavors) brought a smile to my face.


LOL I must say I realized I really was a simpleton when I read the first reply to my topic LOL

Doesn't matter. Maybe 25 years of computer coding must have taken its toll on my braincells. Or maybe alzheimer first signs LOL
:Octane2: :Octane: :Octane: :O2:
So I'm using this old D9 Stone with 8 FC-AL 300gb HDDs to store various bits and blobs (family pics, mp3, home recordings etc.). One problem I have is that the HDDs mount in slightly different order every time I reboot. I cannot figure out why. Is there a simple way to get the HDDs to mount the same way every time so it doesn't wreck havoc in my symbolic links ?
:Octane2: :Octane: :Octane: :O2:
No Fiber Channel or IRIX automount expert around here ?? Someone must have encountered this problem before... :(
:Octane2: :Octane: :Octane: :O2:
Thanks for your reply. The disks have no jumper whatsoever. Is there a software way to control disk spin-up ?
:Octane2: :Octane: :Octane: :O2:
I do not use the Stone+Wire Discreet driver as the Stone comes from another system. I only use it with as a standard storage array with the standard Irix driver. I clicked "OK" when Irix proposed me to automount the drives at startup. I haven't seen any option anywhere to delay the spindle of the drives individually or anything else for that matter. Hence the situation...
:Octane2: :Octane: :Octane: :O2:
hamei wrote: Disclaimer : I don't know anything about fiber channel. But I have a couple of sata disks that do something similar to what you describe ..

Does each disk show up individually ? /dev/dksc/dsk3d2s7 etc etc ? If so, I am guessing you have your links interlaced ? Because on my system, there's a mount point for each disk on the boot filesystem. There's no problem with this setup, it doesn't care when each disk comes online. The boot disk comes up first, then the subdisks can mount in any order.


Yes, each disk show up individually. Yes my links are all mixed up. Precisely, I devised a small website for my own usage with data stored on the arrray and symbolic links pointing to paths within the array are all mixed up everytime I reboot the system.

Basically, my question is :

How do you maintain correct and stable symbolic links from the root to the content of the FC array thoughout several reboots of the whole system ??? There must be a simple way as it seems to me a really basic functionality. I'm no Unix specialist, although I used Irix, SunOs and Aix in various dev environment from 1994 to 2002. But I was a software developer, not a sysadmin. I have no idea how such common problem is handled in a standard environment.

hamei wrote: I'm not sure they would ever have done what you are talking about because in a big installation, what if disk #3 with mountpoints for disks 4 and 5 failed ? Then everything dependant on it would also fail ...


What you're describing is an entirely different problem concerning mountpoints. For example, in a SCSI array, each disk has a fixed SCSI id and show up every time in the same device in the filesystem (usually with a naming scheme related to the SCSI id), regardless of spindle time or any other consideration.
:Octane2: :Octane: :Octane: :O2:
uunix wrote: What about using XVM and making a raided drive?


Doesn't XVM require some kind of license ? I do not trust RAID arrangements for my own small tasks anyway. I prefer having the simplest possible scheme (JBOD wthout interleaving of the data across the disks, much too risky).
:Octane2: :Octane: :Octane: :O2:
robespierre wrote: You can use XLV to create stripes and concatenated volumes without a license, it only requires one for plexes (mirroring). Not sure if the situation is the same with XVM, but perusing techpubs it seems to be the same.


I don't want to create stripes or concatenation as it weakens the integrity of the data greatly. I just want to use my disks in the simplest way.

robespierre wrote: From your symptoms it seems like you're using automounting/mediad. If you just turn that off, and add entries to fstab manually, I don't think you will still see things breaking.


I guess this is what I'm using. I'll look into fstab and report the result. Thanks for you help !
:Octane2: :Octane: :Octane: :O2:
Thanks everyone for your insights. I guess the only solution left for me is to write some kind of script that will mount the drives in some temp mountpoints and then identify each of them by checking the existence of a id file in them and then remount them at the right locations based on that. Ugly solution I hoped to avoid !
:Octane2: :Octane: :Octane: :O2:
Yes, the ids are slightly different every time. Not totally jumbled, but the 1 and 2 are swapped etc. Just slightly different every time. The 7th never becomes the first but it might become the 6th, you get the picture. I never tried to let the stone powered on since it burns about 150 watt/h (the octane burns about 250 watt/h) so for the time being I only power them when I feel like toying with old computers. The long term plan is to let them powered up 24h but I still don't have an upload rate worhty enough of it (my street is only DSL, not optical fiber so the rate is really low).
:Octane2: :Octane: :Octane: :O2:
hamei wrote:
jan-jaap wrote: Queue Hamei and the IBM T221 in 5, 4, 3, 2, 1, ... :mrgreen:

hey, there's an Eizo that takes two dvi inputs also !


Which Eizo model would that be ? Can't seem to find it on the Eizo site...
:Octane2: :Octane: :Octane: :O2:
Thanks for the infos, Hamei ! When I got the V12/DCD in my Octane, I looked for a monitor with two DVI inputs to display sided-by-side but couldn't find any at the time (about two years ago).
:Octane2: :Octane: :Octane: :O2:
The Keeper wrote: Knowing that they show up differently in the hinv every time, then it sounds like whichever drive is spinning up first is assigned an FC-AL address first. I think there may have been an "auto" mode in FC-AL where if there isn't a drive position specified, one is assigned automatically, but those details are a bit fuzzy.


They don't show up differently in the hinv, they appear identical every time :

Code: Select all

Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
Integral SCSI controller 4: Version Fibre Channel AIC-1160, revision 4
Disk drive: unit 0 on SCSI controller 4 (unit 0)
Disk drive: unit 1 on SCSI controller 4 (unit 1)
Disk drive: unit 2 on SCSI controller 4 (unit 2)
Disk drive: unit 3 on SCSI controller 4 (unit 3)
Disk drive: unit 4 on SCSI controller 4 (unit 4)
Disk drive: unit 5 on SCSI controller 4 (unit 5)
Disk drive: unit 6 on SCSI controller 4 (unit 6)
Disk drive: unit 7 on SCSI controller 4 (unit 7)
Integral SCSI controller 3: Version Fibre Channel AIC-1160, revision 4


The disks ids are always sequential starting from 0 but they are not assigned to the same physical disk in the enclosure, which seems totally strange and illogical to me.

For example, when I list the content, what was previously mounted on /stor0 at last power-up is now mounted on /stor1 and conversely (I mounted the 8 disks on /stor0 - /stor7 folders). Just as if I swapped the disks in the enclosure.

The Keeper wrote: Does the DS9 have any switches on it anywhere? If so, that might configure the "auto" mode. And also, has the DS9 always misbehave this way, or did it just recently start misbehaving?

Chris


There's no visible switches or jumpers anywhere on the D9 enclosure. I'll have to dismantle it completely and check the innards. Even if I find random jumpers inside, I'd be wary of changing anything beause I have no documentation about the D9 Stone hardware and couldn't find any on the net. I guess it always behaved that way but I just didn't see it before because at first, I didn't use all the disks and also, I hadn't set up a website with symbolic links pointing to data on several disks. Thanks for your help in any case ! 8-)
:Octane2: :Octane: :Octane: :O2: