[DeChief]

Hey all,

I'm trying to install Irix 6.5.22 on my Indy R5000 using irixboot in Ubuntu (this fork: https://github.com/unxmaal/irixboot), and I'm running into the following error:

PANIC: KERNEL FAULT
PC: 0x8801ad40 ep: 0xffffc7a8
EXC code: 128, 'Software detected SEGV'
Bad addr: 0x4000, cause: 0x8<CE=-2009769480

[Press reset to restart the machine.]

Despite this, I can successfully run bootp():/disc1/stand/fx.ARCS from Command Monitor and launch fx to go through that part of the process. 

Indy specs:
256MB memory
2GB IBM HDD
SEAGATE HDD (don't know what size, but it's the first drive)
R5000 CPU

What's going on? Is this a hardware error? I've tried taking out half the ram but that only changed part of the error (what you see above is 128MB, 256MB replaces  the top line with "PC: 0x880c2708 ep: 0xffffc6b8").

I'm seriously stumped... after struggling for days to get irixboot/vagrant working correctly on a Windows 10 laptop, I finally dug out an older machine and installed Ubuntu, and successfully used fx.ARCS to partition the hard drive. I really thought everything was going to work this time  :(  For reference, my setup is: Laptop -> network switch -> Indy.

Also I'm extremely new to all of this, so before you respond, think to yourself: "how would I explain this to a 5 year old?". Any and all help is greatly appreciated, thank you.

- Chief

[Raion]

So I did some research into this. This makes me think there's a memory slot in the bottom (primary) memory slots that's either corroded, making poor contact or has a cracked solder joint. Either way the kernel appears to be checking the memory for integrity and not liking it.

Make sure it's all fast page mode, parity 70/60ns SIMMs (PS/2 SIMMs should work okay)

[indy99]

There was a known bug with some variants of the Indy R5 processor (Revision 1.0?) that could cause SEGV faults during IRIX 6.5 installs.

It's been quite some time, but as I (vaguely) recall the fix for that issue was to set "_R5000_CVT_WAR" as a PROM variable.

[Raion]

That sounds about right.

[DeChief]

Thanks for the suggestions, I reflowed all of the ram solder joints and that didn't change anything. Then I tried setting that variable and it didn't change either... Is it possible there's something wrong with the CPU module? Should I look around for a replacement? It doesn't even have to be an R5000, at this point I'll take any CPU if it's going to actually let me install Irix.

[Raion]

If you can find one cheap, sure. buy a new CPU module - any module should work.

[dexter1]

You might want to try indy99's suggestion before you buy a new CPU:

There was a known bug with some variants of the Indy R5 processor (Revision 1.0?) that could cause SEGV faults during IRIX 6.5 installs.

It's been quite some time, but as I (vaguely) recall the fix for that issue was to set "_R5000_CVT_WAR" as a PROM variable.

Correct, For some R5000 machines, notably Indy's, this environment variable setting was needed to install 6.5.22m. Internet thread with the info is: http://unix.derkeiler.com/Newsgroups/com...00016.html

And for reference you have to set the variable in the PROM of the machine via:

setenv -p _R5000_CVT_WAR 0

The -p preserves the variable setting in the prom IIRC.

[DeChief]

You might want to try indy99's suggestion before you buy a new CPU:

There was a known bug with some variants of the Indy R5 processor (Revision 1.0?) that could cause SEGV faults during IRIX 6.5 installs.  

It's been quite some time, but as I (vaguely) recall the fix for that issue was to set "_R5000_CVT_WAR" as a PROM variable.

Correct, For some R5000 machines, notably Indy's, this environment variable setting was needed to install 6.5.22m. Internet thread with the info is: http://unix.derkeiler.com/Newsgroups/com...00016.html

And for reference you have to set the variable in the PROM of the machine via:

setenv -p _R5000_CVT_WAR 0

The -p preserves the variable setting in the prom IIRC.

Yeah I found the command in an old nekochan thread, it didn't work as stated above. The kernel fault I'm getting is different to what you would see with that error anyway.

[DeChief]

Okay, after somehow convincing myself not to smash the Indy R5000 with a sledgehammer and throw it out of a moving vehicle, I took a break for 2 months and am now coming back to it.

But as I worked on it for a few hours today, I was already beginning to regain those same feelings of frustration...

I've been trying to use my SCSI2SD as a CD-ROM drive emulator to install Irix 5.3 (downloaded from http://fr.irisware.net/irix-os/legacy-ir...y%20R5000/), and am having very little luck. When I try to install from the maintenance menu's second option "Install System Software", it will get through the "Copying Installation Tools" progress bar and then drop to this error:

Show Content

Spoiler

I've also tried booting into sashARCS and fx.ARCS from Command Monitor, and I can boot into sashARCS just fine but can't get into fx.ARCS from there. Despite the fact that I can use "ls" to see the file inside the "stand" folder, it gives me an error after I try "boot -f dksc(0,5,7)stand/fx.ARCS". I didn't take a photo of the error but will if somebody thinks it's relevant.

Does anybody have a single clue as to what is going on?

If not, I have an idea: would anybody possibly be willing to use their SGI machine and SCSI2SD to install an Indy R5000 compatible version of Irix onto a MicroSD card, and then send it to me? I'm completely happy to pay for the card and for shipping of course. If that doesn't work, then I'll pretty much know for sure that my Indy has some sort of hardware issue that needs to be repaired.

[DeChief]

Okay, update time:

I managed to make the SCSI2SD act as both a hard drive and CD drive, and I successfully got into fx.ARCS from the Irix 5.3 image! I formatted the drive and then backed out to the maintenance menu, clicked "Install System Software", aaaaaaand... was greeted with the exact same error from my last post.  :( :huh: :dodgy: