[sotlampr]

Hello there! I’ve been running an indigo2 with HIGH IMPACT graphics and a 13W3-VGA SGI cable fine for a while until the screen went black. Everything works until the login screen (I assume it’s called managed mode) but then my screen gets confused, tries to detect a signal and finally sleeps.

Some pics:
Boots fine:
   
   

I managed to get this by playing around with setmon:
   
   

However after logging in I get the same problem - monitor cannot correctly detect the signal.

Running stopgfx gives me this:
   

And sometimes when shutting down I get the standard screen:
   


Other things I tried was reseating the graphics card, also on a different slots. All of the above on a clean 6.5.22 install.

It seems I need a new graphics board??

Thanks!

[weblacky]

I think we need a little more description...because some of this COULD be explained away by someone screwing around with the monitor resolution for X sessions using the graphical system to change monitor resolution. Changing resolutions is something I normally advise people never to try as you can get behavior just like this, once you login another resolution takes over in your X profile and now, issues. This maybe other things, but normally working graphics under PROM and INTO login and OS reinstall (which does not wipe settings by they way, unless you wipe the drive first) without graphics error normally means you have a settings issue and not a hardware issue. But more info it needed here.

Fixing this in software (assuming the above) is a hassle, we've had a couple instances where people enabled SOME form of serial terminal, telnet, rsh, or ssh, then logged into the station, then telnetted in and as the same user and set the resolution manually to come back...but it's a huge pain.

Example: https://forums.irixnet.org/thread-2835.html

[robespierre]

When you are in the textport (your image #5), type "/usr/gfx/setmon -x 72" and then type "reboot".

[Irinikus]

If the command given by @robespierre doesn't help, then try this one:

"/usr/gfx/setmon -x 1280x1024_60"

(This should bring its output into an acceptable resolution and refresh range for most monitors)

[jan-jaap]

When you are in the textport (your image #5), type  "/usr/gfx/setmon -x 72" and then type "reboot".

Actually, the 72 or 75Hz refresh rate might be the problem. Plenty of LCD screens can't deal with it. I would stick with 60Hz, like Irinikus said.

[Irinikus]

I see that it has a TRAM installed, what are the failure modes of one of these modules? (The OP stated that the machine was working fine until the screen went black, so unless he changed something in the graphics settings, there was a failure of some kind.)

Usually if the set resolution and refresh rate are incompatible with a monitor, you won't even get the login screen!!! (Hence the need to go in via serial) I wonder if it's not experiencing a problem once it attempts to access its TRAM after login?

Try removing the TRAM module from the card and see if it helps. (Caution must be exersised here, as the TRAMS are very delicate modules)

[weblacky]

I’ve personally seen a situation where someone fooled with the resolution on an Indigo2 so you only got the login screen, then blank after successfully login.

It was my understanding the login screen presents at its own low resolution, then changes upon actual X session instantiation from Xdm? I’ve never seen a high-res login screen for Irix.

Also TRAM issues tend to give artifacts or missing elements (missing textures)? It cannot be totally discounted, sure. But a reset of resolution should definitely proceed touching the TRAM module.

[Irinikus]

It’s been a while since I’ve had a resolution or refresh compatibility issue.

If the command line that I suggested doesn’t work, then maybe take a look at the TRAM model on the card.

[jan-jaap]

I see that it has a TRAM installed, what are the failure modes of one of these modules?

Artifacts on screen, X11 server crashes.

Try removing the TRAM module from the card and see if it helps. (Caution must be exersised here, as the TRAMS are very delicate modules)

I would not do that unless the diagnostics fail. These things are very sensitive to mechanical stress and you risk damaging it when removing it and especially when inserting it in the system.

Every Indigo2 has the diagnostics on the system disk. Why not run it? Hook up a serial NULL modem cable to serial #1 of the Indigo2, 9600-n-8-1, detach keyboard and mouse, and when the system comes up and presents a PROM menu, choose #3: "Run Diagnostics".

The reason you need to use the serial console is that display output is gone / used during the diagnostics run and you can't rely on error messages showing up on the monitor.

[Irinikus]

Cool thanks for the info!

Possible future project:

Would it not be possible to get thicker PCB's made up for the TRAMS and transfer the chips over to them, rendering them less susceptible to thermal and mechanical stress?