Indy and Monitor issues

Tulac

New member
Sep 29, 2019
1
0
1
Germany
Hi all,

I'm new to this group (first post, hope I'm right here?) and not deep enough into the SGI world. But I own an Indy with some peripherials like the original SGI/Sony Trinitron monitor, cam, keyboard and mouse.

First of all, be kind with me, because last time I worked with this machine was around 2006 - and even then, it was less working, more experimenting and trying to learn something. But sometimes life changes, so I boxed all that SGI stuff and put it away. Until now. And now I'm trying to get this Indy running again... but some help is needed.

First - the monitor (Model GDM-20D11)

On first power up, the monitor showed up a screen, but it was squeezed on the bottom - like a "sand clock" shape. The "hin" part seemed to move for me, very slowly from bottom to top. Then, after a while running, the screen starts to flicker and disorted. After I powered it off and on again (more then one time, taking a break), the picture got a bit better and the extreme "sand clock" shape dissapeared, but screen was still squeezed on the bottom. Then the flicker and disortion came back after a while.

Then the unit itself.

The Indy unit power ups good and shows the boot screen (IRIX 6.2 is installed), goes to the diagnostic screen and looks up ethernet - but it's not connected yet.
It starts checking the root file system (fsck: checking /dev/dsk/dks0d1s0) and goes through the phases good, till phase 4.
On phase 4, there are following issues:

"FREE INODE COUNT WRONG IN SUPERBLK" -> FIX? yes

On phase 5, theres the following:

"FREE BLK COUNT WRONG IN SUPERBLK" -> FIX? yes

"BAD FREE LIST" -> SALVAGE? yes

On phase 6 then:

"20860 files 1699733 blocksd 218225 free"
REMOUNT ROOT? yes

It's remounting then, screen changes to "The System is coming up." and telling me again, that network is not set up properly. Then a messge appears, when the system went down last time (yes, it was really 2006 :D ) and a savecore-message appears.

After a while, i'm getting a PANIC message, telling me

"in_pcbsetaddr primary is loopback"

and then dumping. After the dump is complete, system is halted with "press reset to restart".
But when I restart the machine, everything repeats like before. Every time.


Do someone have some clues and hints for me? I hope, my text is readable enough for you, because I'm not a native speaker ;)
I've attached some pictures from monitor issues and the system output.

Help would be very appreciated. Many thanks and kind regards!

160161162163164
 

Elf

Storybook
Feb 4, 2019
66
12
8
Regarding the monitor, my first thought is old capacitors that could benefit from being replaced as they are often used in the scan circuits. The behavior changing as it warms up sounds like the capacitors starting to reform? I have other electronics that will behave similarly, and malfunctions if not used for a while. However, I am far from being an expert on CRT electronics. They are often discussed on the Retro Computer Discord ( https://discord.gg/XDnjdSf ) though, and someone there may have some ideas?

Regarding the IRIX boot sequence, the easiest thing may just be a fresh reinstall. @Unxmaal 's booterizer ( https://github.com/unxmaal/booterizer ) project can assist with a network install if you don't have any optical drives or media. It could also be that a fresh hard drive would benefit if it is starting to fail, causing the bad blocks?

Welcome to the User Group :)
 

jupo

New member
Jul 9, 2019
1
0
1
40
Tucson, AZ
It looks like the PRAM battery is dead and it has lost the MAC address. From what I learned playing with the Indy emulation, having no MAC address can cause it to panic at boot. You can configure the MAC in the boot rom command monitor, though obviously will have to do this every time you power it off until you replace the Dallas chip.

I agree with bad caps in the monitor, I have one of the 17" that has similar symptoms that I'm procrastinating on working on (because I have a Sun labeled one that still works for now).