[DVE]

Hi all,

I have an absolutely similar problem as described by the topic starter, though my config is a bit different - I am using two drives on the same SCSI2SD device.

These are the steps I did:
- I created two partitions on the SD card, 16 GB for HDD and 1 GB for "CDROM", copied the content of the 'IRIX 6.5.22 Overlay 1 of 3.iso' using dd on a second drive.
- My SCSI2SD has an ID=1, two drives having IDs 1 and 2
- I used the same video https://youtu.be/Jy90tmEayjo as a tutorial, I am able to get the boot menu using "boot -f dksc(1,2,8)sashARCS" and "boot -f dksc(1,2,7)...". Then the copy files progress appears, but after the reboot, I only get the message "Boot file not found on device scsi(1)disk(1)rdisk(0)partition(8)/sash"

If I go to the command line and enter "ls dksc(1,1,8)" I just see the empty disk, there is no "sash" folder, it looks like no files were copied.

Maybe should I try another iso image? Another possible issue - I am using the back SCSI port on my Indigo 2, I have no disk sled, so I have no possibility to install a SCSI terminator to the internal port, can it cause the problem? Is it possible to copy files manually via the command line? it may be easier to verify that the copy is correct.

Tnx

[robespierre]

The internal SCSI bus is not the problem.
There are no "files" copied by the install button. There is only the miniroot, which is a single filesystem image. The installation procedure is supposed to reset the "bootfile" and "bootparams" variables to point to the kernel on the software distribution media. sash is not installed this way, it must be copied by a script that runs dvhtool(1M) from the inst(1M) package after booting from the miniroot.
You may have come agutser when you said "reboot" because it is not supposed to reset the machine (that would have cleared the variables that should still point to the kernel on CDROM). It should instead continue by showing the text window with IRIX kernel messages.
Incidentally CDROM is normally set at ID #4. I don't know if there is some bug lurking if you don't use the expected address for it.

[DVE]

Thanks for the answer. I tried to change the CDROM ID to 4, but it did not help. I also have a SCSI(1) instead of SCSI(0) in the system, but I am not sure if it may cause a problem.

These are all the steps, I do:
1) I copied the disk "IRIX 6.5.22 Overlay 1" iso image using dd
2) I check the environment: hinv shows 2 scsi drives 1,1 (HDD) and 1,4 (CDROM)
3) I run the command: boot -f dksc(1,4,8)sashARCS - I can enter the sash shell
4) I run the command: boot -f dksc(1,4,7)stand/fx.ARCS --x, set the SCSI id to 1, disk id to 1, other parameters keep as defaults, enter 'exit'
5) I go to System install, press Install, files are copying 1-2 minutes, then the screen becomes black, it looks like reboot, but I see only black screen, nothing happened. If I press the 'reset' button, I get the message "Boot file not found on device scsi(1)disk(1)rdisk(0)partition(8)/sash".

Do I miss some steps? Maybe scsi(1) is not suitable for system boot? Or for Indigo 2 some command line parameters are maybe different?

[DVE]

A small addition - it looks, that the problem may be more serious. I decided to make another install using a serial port, and when running the installation process, got this:

Code:

Insert the installation CD-ROM, then press <enter>:

Exception: <vector=UTLB Miss>
Status register: 0x30044803<CU1,CU0,CH,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
Cause register: 0x8008<CE=0,IP8,EXC=RMISS>
Exception PC: 0x8bf9c39c, Exception RA: 0x8bf9a234
exception, bad address: 0x1c
Local I/O interrupt register 2: 0xca <EISA,SLOT0,SLOT1>
  Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
  arg: a8740000 43 96 a
  tmp: a8740000 8bfa9c78 8bfb0a08 a874a688 887fe7d4 9fc51cc0 9fc51cc8 31
  sve: a8740000 3 400000 8000000 16 3f80 0 4000000
  t8 a8740000 t9 5a41c700 at 85048a62 v0 ce69440a v1 9abd8093 k1 0
  gp a8740000 fp e027c88a sp 13fe4c23 ra 9c430358

PANIC: Unexpected exception

[Press reset or ENTER to restart.]

No idea what can I do with that, if it is a hardware error, replacing CPU and/or motherboard will be too expensive.

[robespierre]

scsi(0) is the internal bus on Indigo2, scsi(1) is external. The Indy (the machine shown in that video) has only one bus, scsi(0), which is both internal and external.
The problem is at your Step 5. "The screen becomes black" can mean that your monitor does not like the video signal. It's important to know that the firmware ("prom") and the IRIX system use different signal frequencies for graphics output. You could alternatively try running from a serial console to see if the kernel loads successfully.

edit: I see you tried that. Is that error coming when you type "2" to install software and choose the CDROM #4 as the source? I would check to see if you have a hardware fault using the diagnostics. From the prom console, type "dksc(1,4,8)ide.IP22" and see what it reports.
Also, you don't show your machine's configuration. It can be useful for finding problems.

[DVE]

Thanks for the help. It looks like this computer is dead :( The problem is (not only) in SCSI, the last message was a Kernel Panic, now it does not boot at all, even to PROM via serial, with or without SCSI2SD connected. It reacts to the power button press, but I get nothing via serial anymore.

[weblacky]

Yo,
So while this is by no means conclusive, seems like a PSU issue..and that's easy to check. I've rebuilt like 13 Indy Nidec brand PSUs and I've seen one the PSU (on bench with load tester) FULLY START while missing it's 5V rail entirely! So I know the PSU will turn on while it's missing some voltages.

While you likely don't have a current-limiting setup to help protect things, since it's doesn't work anyway I suggest the following (I'm not responsible for anything I say here :-).

Go here: https://wiki.preterhuman.net/Indy_Power_Supplies

Unhook BOTH power and IDC connectors from the Indy main board to the PSU (PSU cables now fully disconnected), get a multimeter with probes that fit into the back-side of the LARGE WHITE PSU connector (so you can touch the crimped wires with a needle probe).

Plug in the PSU and it will automatically start. Voltages WILL BE UNSTABLE (no load) but kind of close, use wire colors in the URL to test for voltage that's close on 5v, 3.3v, and 12v (molex drive connector end). Likely your CPU needs 5v and likely that's like less than 1v or gone!

If you find this is the case then it's a good bet (not a guarantee) that a another, working, Indy PSU will solve your issues as you may be have been underfeeding your CPU this whole time.


I'm not trying to plug my rebuild service, since your in Amsterdam and I'm in the USA it's likely too costly to do business together, but if you can find another PSU near you, get it this after basic testing, and I think things will be different.

[DVE]

Thanks, The PSU looks ok. I reconnected the EISA board, cleaned pins with a contact cleaner and it boots again

But I still cannot install any system on it, I tried local and remote install, and at the beginning of the installation, I get the same "Exception: <vector=UTLB Miss>" error.
It may be a SCSI termination issue, I don't have a disk sled, so the bus is not properly terminated. I have to postpone it while I'll get one.

This thing takes months to run, every component (video cable, SCSI2SD, adapter to DB25, etc) is minimum a month of post waiting :( (I am not in a hurry though)