[Avante3000]

I received an Indy R5K for basically nothing, it works though it came without a hard drive. So I bought a 18.2GB Ultra320 SCSI drive, along with a SCA to 50 pin SCSI adapter, and a Raspberry PI 4. Though the problems came when I tried to install IRIX 6.5.22. I am using Reanimator on my PI 4. FX works just fine and partitions the drive, though I cannot get into the installer, when I try to install from the network it loads the miniroot up to 100%, the IRIX text shows up in the bottom right corner of the screen, not long after it just kernel panics.
   
My first thought was "there is probably a memory issue", though after swapping around and reseating all the memory as well as the CPU card, same issue. And after running the IDE all the tests passed just fine. also did resetenv and tried the "_R5000_CVT_WAR" variable, all of which had no effect. 

This is my first SGI machine, and now I am pretty much stuck, as I cant really find anyone online with my same issue, I have seen similar, but nobody with the same "Illegal instruction" error. 

(Extra info in attachments)

[weblacky]

Well usually the best is just to start checking the basics.

Can you tell us which files you grabbed and how you organized them in reanimator.

And go ahead and tell us the commands you typed into the Indy terminal to get things going?

I'd like the specific recall attention to the exact version of sash you booted, and whether you organize the overlay and base files correctly.

[Avante3000]

I just downloaded the preloaded image for Reanimator, using the files and folder structure that it comes with. and to launch the installer, I just used the maintenance menu and used the "Install system software" menu, and typed in "IRIX/6.5.22/ovl1/dist"

[weblacky]

Sorry for the delay, I was away and couldn't properly post a formatted response. My thinking here is that it's actually downloading the wrong executable for the platform and then just bailing out. To make sure that it's doing the right thing I would go ahead and go to the GitHub or repository here: https://github.com/Linux-RISC/Reanimator...l_guide.md

Go to the troubleshooting section, number 3, and manually launch it "the hard way". This will make sure that you forcibly pick the right installer executable for your CPU.

I've never used this tool, so I find it suspicious that you dont' use sashARCs for 6.5.22 deployment on an Indy... but you might wanna try it both ways.

[Avante3000]

Sorry for my massive delay as well, I kind of took a break from working on my indy, but when I run miniroot manually, it does the same kernel fault. and when I try to install from sashARCS, it just does nothing. It doesnt hang but it just seems like its not loading the files from reanimator

[weblacky]

I've never used the network installs and so I've only really had experience with the CDROM based installations. A part of me would say is there a way to try another installation type to prove it's a hardware issue versus simply a problem with the installation process using this method?

Do you happen to have access to a SCSI CDROM or any of the SCSI to SD emulation hardware?

When it comes to the network based set up my bigger concern is that perhaps there happens to be a problem with the files provided?

Just for giggles, using what you have, could you try one of the other OS installations using your current reanimator set up?

While this may not conclusively prove anything, if the rest of them happen to work then you might be able to indicate which files are damaged or otherwise incorrect in the 6.5.22 install. Can you try just base 6.5? Can you also try just 5.3 if 6.5 fails?


Do either of these return exactly the same problem?

[Avante3000]

Sadly I dont have access to any SCSI CD drives or anything, but I did try 6.2 and 5.3. 5.3 seems to just hang, though I feel like its because the version included with reanimator is not the version with R5K support. But 6.2 is interesting, as installing normally just results in a kernel fault, though if I wipe and repartition and relabel the drive and run miniroot directly, it will actually get past where it usually crashes, but with the error "Kernname environment variable not set by sash" and "initial mount of root device 0x2000011 failed with errno 22"

[weblacky]

Can you please go into the PROM terminal and type: version

Report what comes out. Maybe you have an old PROM that's incorrect for your processor version (a incorrectly done upgrade?).

[Avante3000]

Version 5.3 B10 Feb 12 1996

[weblacky]

Version 5.3 B10 Feb 12 1996

That is the correct ROM for your processor:

070-9101-011
SGI Version 5.3 Rev B10 R4X00/R5000 IP24 Feb 12, 1996 (BE) R5000

So that's not the problem.