recondas & others,
Thanks for tip on VBOB version, I come across that one... but it was not possible to tell exactly what I had until I got info on diagnostic port.
That has confirmed that I have vbob firmware: 1.3.22 & dm5.
As next step I uninstalled and reinstalled the "DMediaPro DM2/DM3 ML Execution Environment" & "DMediaPro DM2/DM3 dmSDK Execution Environment" and reran "vbob_flash -vnl" and I now get:
Code:
Select all
./vbob_flash -vnl
Trial run. No images will be upgraded...
vbob_flash: Doing a killall on any dmdaemon or mldaemon.
process <dmdaemon> not found
process <mldaemon> not found
[libvboblvds] I/O ERROR: VBOB possibly disconnected!
vbob_flash: Internal Error! vbobReadData failed.
vbob_flash: Checking for vbob on pipe 0 (:0.0)
vbob_flash: Vbob found on :0.0
vbob_flash: Vbob found on pipe 0
No dcard installed
vbob_flash: Updating operating code
vbob_flash: Vbob xilinx 1 config 1 is up to date
vbob_flash: Vbob xilinx 2 config 1 is up to date
vbob_flash: Vbob xilinx 3 config 1 is up to date
vbob_flash: Vbob xilinx 4 config 1 is up to date
vbob_flash: Vbob xilinx 5 config 1 is up to date
vbob_flash: Vbob xilinx 6 config 1 is up to date
vbob_flash: Vbob xilinx 7 config 1 is up to date
vbob_flash: Vbob xilinx 8 config 1 is up to date
vbob_flash: Vbob xilinx 9 config 1 is up to date
vbob_flash: Vbob xilinx 10 config 1 is up to date
vbob_flash: Vbob xilinx 11 config 1 is up to date
vbob_flash: Vbob xilinx 12 config 1 is up to date
vbob_flash: Vbob xilinx 13 config 1 is up to date
vbob_flash: Vbob xilinx 14 config 1 is up to date
vbob_flash: Vbob xilinx 15 config 1 is up to date
vbob_flash: Vbob bootloader is up to date
Ahh - recondas, I think the line "No dcard installed" refers to the HD-GVO "daughter board" being referred to in the other instructions. I have no idea what such a board looks like or how you would identify it. I am going to open up the vbob that is not working to see if there is any obvious physical damage or such that resulted from shipping to Australia, so will check if there is area for additional daughter board to be installed.
So I now seem to be communicating with vbob, still no lights showing on DM2 and only the far right hand diagnostic light is flashing periodically on vbob, when before vbob lvds leds were blinking.
This is consistent with SGI doco @
http://techpubs.sgi.com/library/tpl/cgi ... /ch03.html
Rear Chassis LEDs
There are eight LEDs on the rear of the VBOB chassis, as shown in Figure 3-2 (see digram below)
The SD, HD, Genlock, and LVDS LEDs indicate the following:
SOLID - Signal present and valid
FLASHING - Signal present but unrecognizable (invalid, such as wrong video format)
OFF - No signal present
The last LED on the right indicates the processor activity. This LED should flash at a rate of about 1 Hz.
From this I would expect that lights will only go solid when there is valid video signal on LVDS lines.
This manual refers to older vbob, without 3 DVI DM5 ports:
I have also been to shop to get 2 extra DVI cables but when I try to get output to monitor via vbob, I get no signal... so I have moved cable back over to monitor directly.
The gfxinfo report with single line into vbob and other to LCD is now:
Code:
Select all
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 1600x1200
BUZZ version B.1
PB&J version 1
128MB memory
Banks: 4, CAS latency: 3
DM5 attached to Dual Channel 1
Monitor 0 type: Unknown
Dual Channel Display option
Monitor 1 type: IBM 16736 Monitor 2 type: Unknown
Channel 0:
Origin = (0,0)
Video Output: 1600 pixels, 1200 lines, 59.83Hz (1600x1200_60)
So at least DM5 connection is being seen via DCD DVI connector.
So it appears that at least one of the vbobs is working at the moment.
On LVDS cable front, I am using 2 black cables, which I have tagged to help make sure they are plugged into the correct ports. I think the white/black colouring was just to help ensure correct ports were being connected.
Cheers,
