[indigofan]

OK thanks for the printenv.... I tired to reimage the drive thinking from a previous post that there was a file missing, now the CDROM won't load the OS Install Tools, but will load fx, so need to figure that out or try a netowrk install from my Fuel. Ugh.

[Raion]

Yeah I'm sorry for not saying much here as I have an Onyx2 but I have never encountered such a thing.

[indigofan]

Well it just seems not to be able to find the graphics pipe..

IP27 PROM SGI Version 6.156 built 11:27:56 AM Nov 18, 2003
Testing/Initializing memory ............... DONE
Copying PROM code to memory ............... DONE
Discovering local IO ...................... WARNING: xbow_base: 0x9200000000000000 link: 12 Widget present, but link not alive!
WARNING: xbow_base: 0x9200000000000000 link: 12 Widget present, but link not alive!

Found an io Board with nic 030-1275-002.
DONE
Discovering NUMAlink connectivity ......... DONE
Found 2 objects (2 hubs, 0 routers) in 10465 usec
Waiting for peers to complete discovery.... DONE
Global master is /hw/module/1/slot/n2
Testing/Initializing all memory ........... DONE
Checking partitioning information ......... DONE
Loading BASEIO prom ....................... DONE

BASEIO PROM Monitor SGI Version 6.156 built 11:26:28 AM Nov 18, 2003 (BE64)
4 CPUs on 2 nodes found.
***WARNING: Console has moved from /hw/module/1/slot/io4/kona to /hw/module/1/slot/io1
Check for LINK errors or setenv ConsolePath to new value.
Installing PROM Device drivers ............
Base I/O Ethernet set to /dev/ethernet/ef0
Installing Graphics Console...
graphics install: searching for pipe 0

Walking SCSI Adapter 0 (/hw/module/1/slot/io1), (pci id 0)
1+ 2- 3- 4- 5- 6+ 7- 8- 9- 10- 11- 12- 13- 14- 15- = 2 device(s)


Walking SCSI Adapter 1 (/hw/module/1/slot/io1), (pci id 1)
1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- = 0 device(s)

Initializing PROM Device drivers .......... DONE
Cannot connect to keyboard -- check the cable.
Cannot open /dev/input/ioc3pckm0 for input
Cannot connect to keyboard -- check the cable.
Cannot open /dev/input/ioc3pckm0 for input
Checking hardware inventory ...............
***Warning: Board in module 1, slot io6 is missing or disabled
It previously contained a New Type board, barcode KAH529 laser 3e315a
DONE

**** System Configuration and Diagnostics Summary ****
CONFIG:
No. of NODEs enabled = 2
No. of NODEs disabled = 0
No. of CPUs enabled = 4
No. of CPUs disabled = 0
Mem enabled = 2048 MB
Mem disabled = 0 MB
No. of RTRs enabled = 0
No. of RTRs disabled = 0

DIAG RESULTS:
/hw/module/1/slot/io6: IO link bad
**** End System Configuration and Diagnostics Summary ****


System Maintenance Menu

1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor

---

From digging in the service manual, when you setenv ConsoleIn and ConsoleOut you have to set the same when set to g so:


>> setenv gConsoleOut /hw/module/1/slot/io4/kona
>> setenv gConsoleIn /dev/input/ioc3pckm0
>> setenv oldConsolePath /hw/module/1/slot/io4/kona
>> setenv ConsolePath /hw/module/1/slot/io4/kona


Will see if this works.

---

Forcing the Graphics Console to an ASCII Terminal
If console control is at the graphics keyboard (console=g) and a problem exists in the graphics hardware that prevents the initialization of the graphics subsystem during the power-on boot process, the microcode attempts to transfer the console to the ttydl port of the BaselOG (I06G) board. This enables a user to retain control of the system even though a problem exists in the graphics subsystem.
A problem in the graphics subsystem prevents access to the system by locking up the graphics console keyboard (the keyboard is inactive) and preventing the microcode from switching console control to the ttydl port.
The following procedure forces console control to the ttydl port when the console variable is set to g (console=g).
1 Power off the system.
2. RemovethegraphicskeyboardcablefromtheI06G. 3. Poweronthesystem.
Late in the power-on boot process, the microcode attempts to initialize the graphics subsystem. Because the microcode does not detect the graphics keyboard, an error message is displayed and console control is automatically switched to the alternate console (the ASCII terminal).
4. FromtheASCIIterminal,startthesystem(bootIRIX).
5. After IRIX is running, you can use the irsaudit diagnostic to attempt to isolate the graphics problem.
Note: Remember to reconnect the graphics keyboard after the problem is fixed.

[jan-jaap]

Discovering local IO ......................            WARNING: xbow_base: 0x9200000000000000 link: 12 Widget present, but link not alive!
WARNING: xbow_base: 0x9200000000000000 link: 12 Widget present, but link not alive!

I've seen this happen and it turned out to be bad / dirty compression connectors.

What you need to do to resolve this depends a bit on what you did before this started happening. There are two sides to a compression connection: the backplane and the compression connector. Both can get dirty and if either one gets dirty or damaged, the connection will be bad and you get this message.

• If you have e.g. an Octane and you find yourself an interesting XIO option to put in an unused slot, and then get this error: after 20+ years a layer of fine dust accumulated on the backplane and you should have cleaned the backplane contact surface before installing the XIO option. Unfortunately this usually means tearing the entire system apart. Clean mating surfaces with pure alcohol and something that doesn't leave lint behind. I've seen this when I added a PCI shoebox to my Octane2
  
• If you tear a system apart, put it back together, and then this happens: you probably damaged the compression connector on the XIO option -- the GE card in this case. Don't worry, there are only two types around, the big one (O2K/Onyx2 nodeboards) and the small one (everything else). Find an el-cheapo known good XIO option card (an unloved SCSI board, SI gfx, ...) and transplant the compression connector to your GE board. Never touch the business end of the XIO connector. I think you need a 2mm hex (inbus) tool to replace an XIO connector.
  

***WARNING: Console has moved from /hw/module/1/slot/io4/kona to /hw/module/1/slot/io1

Having failed to connect to the IR pipe, the system switches consoles to the serial port.

[indigofan]

Lekker.. Will give it a go. Haven't touched the connector but there sure is some dust in the box that hasn't been opened up in a while.

[indigofan]

Swapped a compression connector from a board I'll never use (FIDDI). Still having the same issue. Cleaned the female side of the connector with 99% alcohol. I think that the I/O board might be the root cause of the issue as I haven't pulled out any other cards, but willing to do so a give it a full cleaning. Feels like I am cleaning up an old Mac.. LOL.

[indigofan]

Well all good and up and running. Thanks for the help all.