[mrthinlysliced]

(I have necessary XBow 1.4 + cherokee PWR, fwiw)

Edit: Forgot to mention also, PROM seems recent enough:

Code:

<i>
</i>bash-4.4# flash -V
PROM header information (presently loaded)
  Magic:      0x50524f4d
  Version:    4.17
  Programmed: 6/22/2004 17:47:19 GMT
  Length:     682448 bytes
  Reloads:    10
Recovery PROM header information (presently loaded)
  Magic:      0x50524f4d
  Version:    4.9
  Programmed: 5/25/2004 08:26:11 GMT
  Length:     147134 bytes
  Reloads:    7

Any magic incantations I need to do to get an already installed OS to see the VPro (V12)?

It shows up in the hinv in the PROM as ODYSSEY and happily lets me type things at the diagnostics screen, but stays with a frozen PROM style output when booting into 6.5.30.

The OS is still running, and via ssh I see the /usr/gfx/gfxinfo returns "no graphics devices".

I tried installing the available patches from ftp.irix.cc - still no go.

This machine previously had an EMXI installed, if that helps.

Thanks for any pointers, if no luck I guess I'm re-installing 6.5.30 this afternoon....

Mr TS

[dexter1]

Swapping a MXE (MardiGras) with a VPro V12 (Odyssey) also requires you to reinstall the graphic subsystem.
You don't have to reinstall IRIX from scratch, but you need to boot into a miniroot install and perform the procedure as described by Ian

Code:

Btw, for those who don't want to do a full reinstall, here's how to reinstall just the gfx/X libraries to switch from one card to another:

Copy the relevant files to disk from the 6.5 base CD and from the relevant 6.5.x CD, in this example using 6.5.26...

mkdir /usr/local/gfx

From Foundation 1:

cd /CDROM/dist
cp eoe* x_eoe* /usr/local/gfx
cd
eject

From 6.5.26 Installation Tools and Overlays 1 of 3:

cd /CDROM/dist
cp eoe_6526m* x_eoe_6526m* /usr/local/gfx

Then restart and boot into miniroot from the relevant 6.5.x boot CD. At the
inst prompt:

1
/root/usr/local/gfx
keep *
i eoe.sw.gfx
i eoe.sw64.gfx
i x_eoe.sw.Server
i x_eoe.sw.eoe
i x_eoe.sw64.eoe
go
quit
y


Cheers!

Ian.

Since you already have swapped the GFX card, just boot straight into miniroot and open only the overlay 1 from 6.530m and foundation 1. If you do it like that, there is no need to copy the packages on the root file system first.

[mrthinlysliced]

Aha! Perhaps all is not lost on this install!

My google foo was too weak to pull that up - thank you Dexter! I've got all the 6.5.30 bits on a second disk so I'll give that a go.

[mrthinlysliced]

Soooo, I'm having trouble working out how to "just boot straight to miniroot". I've been reading the installation + admin guides from SGI, but most assume you are either coming from CDROM or a network server.

I can get sash running from the PROM command tool ("sash"), but any attempt to "sash -m" or other boot seems to start looking for a tape drive (setenv notape 1, no difference).

If I choose "install software" from the initial PROM menu it wants me to use local CDROM (I have none) or network install.

It seems that whatever upgrade happened during my 6.5.30 install means the PROM can't talk to the rest of my network any more. (this worked great with same cables + addresses before) - I've tried setenv netmask 255.255.255.0 along with appropriate IP but no go.

I can see that the Octane is responding to ARP "who has" - but no packets in or out - wireshark:

Code:

1729    2018-06-09 17:43:30.038234112    192.168.0.74    192.168.0.101    ICMP    98    Echo (ping) request  id=0x2bf5, seq=447/48897, ttl=64 (no response found!)

and

Code:

<i>
</i>1726    2018-06-09 17:43:28.064828027    Apple_7b:d7:6f    SGI_13:45:cd    ARP    42    Who has 192.168.0.101? Tell 192.168.0.74
1727    2018-06-09 17:43:28.067427960    SGI_13:45:cd    Apple_7b:d7:6f    ARP    60    192.168.0.101 is at 08:00:69:13:45:cd

So the network connection is there, just not responding to ICMP or TCP (on the Octane I have left a ping 192.168.0.100 running, doesn't even show up in wireshark...).

To add to the annoyance of the above, booting into the OS (without GFX) means I can still ssh into the host and things are up and running.

The network shouldn't matter though to be honest, I was just hoping as alternative to miniroot via network to get things started, but even re-installing fresh is now blocked.

Any tips are gratefully received -> all issues are mine alone .-)

Maybe (Dexter, thanks for help so far .-) someone can help with miniroot boot from an existing install disk?

[mrthinlysliced]

After much faffing around I discovered that a VMWare upgrade caused the ethernet device to be renamed inside my DINA installer - which explains the networking issues I was having.

I still couldn't get the PROM to ping anything on my network (does that work for anyone?), but after fixing the DINA networking the netboot installation worked fine -> I now have a new 6.5.30 installed with the card recognised and working - off on the merry "reconfigure things" we go :-)

1920x1200 feels much nicer than the 1280x1024 I originally had it on - smells like a proper workstation!

Stealth Octane2 achieved:

Code:

bash-4.2# hinv -vm
Location: /hw/node
      PM20300MHZ Board: barcode HKH112     part 030-1356-001 rev  J
Location: /hw/node/xtalk/15
            IP30 Board: barcode HXY417     part 030-1467-001 rev  B
Location: /hw/node/xtalk/15/pci/2
             FP1 Board: barcode KVH126     part 030-0891-003 rev  G
    PWR.SPPLY.ER Board: barcode AAE9160390 part 060-0035-001 rev  C
Location: /hw/node/xtalk/11
      ODY128B1_2 Board: barcode NEH896     part 030-1945-002 rev  A
2 300 MHZ IP30 Processors
Heart ASIC: Revision F
CPU: MIPS R12000 Processor Chip Revision: 2.3
FPU: MIPS R12010 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)
  Disk drive: unit 2 on SCSI controller 0 (unit 2)
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

[Vanne]

Thanks for that heads up, I have an Octane 2 that id like to revive, I only have the V6 though, currently has stock bog graphics installed. If I pull the stock graphics , and replace the graphics card with the V6, will there be any output on the vpro card? currently don't have any vga/soc monitors so would be nice if this can DVI-D/A out via a hdmi cable to one of my monitors, even just to log into maintenance.

any luck with that or am I pushing shit uphill?

[mrthinlysliced]

I'm not an expert but I'd check that you have needed PROM version before swapping them out.

When the PROM is new enough after swapping the cards I see output from the vpro during the boot - enough to be able to click on maintenance and kick off a fresh install that way. Care with the V6/V8s, from what I've heard they have pixel clock issues that may mean the card will output a signal but your monitor won't be able to handle it.

I wasn't able to fix my existing install to find the new card, so if that data is worth anything, time for a backup :-)

See here:

<URL url="http://irix7.com/techpubs/007-4210-002.pdf">http://irix7.com/techpubs/007-4210-002.pdf

V6/V8 seems to need PROM v4.0 or newer, V10/V12 need PROM 4.5 -> find out with flash -V.

FYI in my testing, swapping _back_ to the EMXI meant existing install came back without issue if you just want to check and see if your monitor can handle the default of the V6.

[dexter1]

If by stock card you mean a Impact/MardiGras currently in your system then no. You need to exchange the graphic subsystem x_eoe.sw.* as per Ian's instructions.

First make sure as MrthinlySliced explained that your system is ready for the VPro6, e.g. IRIX 6.5.10, and a recent PROM.
You can probably perform said action on a live system, then shutdown/poweroff, unplug powercord, exchange carriers, plug powercord and boot.
Having console access makes things much easier, but i don't know if you have that.

[indy99]

<QUOTE author="Vanne" post_id="921" time="1528734233" user_id="175">

I have an Octane 2 that id like to revive, I only have the V6 though, currently has stock bog graphics installed. If I pull the stock graphics , and replace the graphics card with the V6, will there be any output on the vpro card? currently don't have any vga/soc monitors so would be nice if this can DVI-D/A out via a hdmi cable to one of my monitors, even just to log into maintenance.

The out of the box monitor connection on the V6 is 13W3, which is analog. The planar monitor port on all the Octane VPro boards; V6, V8, V10 and V12, are 13W3. Adding the Dual Channel Display Option board, or DCD, would give you two DVI-<U>I</U> ports.

[Vanne]

Wow, didn't even think that as the Vpro that was in my fuel was Dvi.. Grrrr.. not sure what I can use as a vga monitor...

Sigh back to square one