[Soy]

Hi,

I am doing format of SD card with SDCard formatter software, and FAT32 formatting with Windows 10 (some youtube vide recommend this procedure for a big capacity SD card).

I think that the "boot -f dksc(0,1,8)sashARCS" enters to prompt, and we can do "something ... dksc(0,4,7)stand/fx.ARCS --x", right?
If it is so, then the "boot -f dksc(0,1,8)sashARCS" does not make no valid volume header error, I think.

My SCSI CDROM drive's power supply circuit is gone recently, I attempt to install the CDROM drive through Indy's internal 50pin flat connector.
It detects as multiple CDROM Drives, it seems that is caused by no ID assignment for the drive.
If this is correct, is there any solution in order to use the drive?

--
NaN

[jpstewart]

I attempt to install the CDROM drive through Indy's internal 50pin flat connector.
It detects as multiple CDROM Drives, it seems that is caused by no ID assignment for the drive.
If this is correct, is there any solution in order to use the drive?

Assign the CDROM an unused SCSI ID.  The controller in an SGI is always ID 0 (which is what your CDROM will be with no jumpers set).  Your SCSI2SD appears to be ID 1.  So jumper your CDROM drive to anything else.  You're using dksc(0,4,7) in your sample command, so I'd suggest jumpering the CDROM to ID 4.  Most SCSI drives have a label near the connector describing the jumpers.  If yours doesn't, you'll have to do a Google search for the manual for you specific model to figure out which pins to jumper to set the ID.  (They're usually between the SCSI and power connectors along with pins for other settings.)

It might also be possible to configure your SCSI2SD to emulate both a hard drive and a CDROM.  Check the SCSI2SD documentation for how to do that if your real CDROM doesn't work out.

[Soy]

Hi,

Thank you for your advice.

Currently my Indy does not recognize SCISI2SD, hinv does not show.
1) CDROM Drive is live (I checked LED), so Indy's power supply connector is not issue
2) CDROM Drive is recognized as multiple drives, so SCSI bus is not issue
3) Two SCSI2SD cards are not recognized, so SCSI2SD cards are not issue (up to 25% probability of two cards are failed)
4) SCSI2SD with out SD card, "boot -f dksc..." shows SCSI2SD does not proper disk, so SCSI2SD cards are not isssue

Before doing remove PROM, I see that
"boot -f dksc(0,1,8)sashARCS dksc(0,1,7)stand/fx --x"
has error on dksc(0,1,8) is not live, so I doubt PROM.

I tried to remove PROM and putting other PROM, then I missed that a pin is gone...
I bought home-made PROMs supporting R5000, I just waiting for receiving it (will be arrived in next week).

This is current status.

--
NaN

[Soy]

Today I got PROMs and put on system board. Boot then boot sound is heard, so the new PROM is valid, indeed.

At first boot, parity error on CPU(R5000PC) is occurred, there is no displaying after first boot. I replaced with other graphics board, but no sense of the output.

The boot sound is always ok, so I guess CPU board and PROM are no problem, graphic board also no problem(I have two boards). I think that the problem is on system board or main memory, but no idea.

Issue: No Displaying
1) Both of R5000PC and R4400SC is ok (always makes boot sound at the start) with new PROM supporting R5000.
2) Power LED is green, so there is indeed no system error.
3) SCSI2SD brinks the LED only once at booting.

—
Soy

[dexter1]

As a person who wrote down the Wiki pages for the SCSI2SD v5.1 with the Indy, can you tell me:

- What firmware is on the SCSI2SD board?
- Does the Indy have a SCSI terminator on the SCSI connector on the back?

An old firmware version may prevent the SCSI2SD from working correctly. I noticed on some firmware version that the SCSI2SD doesn't like additional devices on the SCSI chain.

[Soy]

- What firmware is on the SCSI2SD board?
- Does the Indy have a SCSI terminator on the SCSI connector on the back?

Hi,
- I have updated the firmware (forget its version).
- I use physical terminator at end of cable.

Progress:
I replaced with other PROM, and other Graphics 24b XL, then worked (SCSI CDROM internally connected, ID issue was there). Unfortunately, after connecting more properly PROM, then indeed PROM is gone (Red Blinking the Power LED, I removed all SIMM but still blinking, so I doubt memory mapped PROM).

Now I order ROM inserter and remover, pin aligner (I have two backup PROMs).
Home-made EPROM, I bought is here;
https://www.ebay.com/itm/Eprom-Silicon-G...SwUcteNmWK

[Soy]

Ummm...

I replaced EPROM with new one, but still blinking as red on power LED. Manual explains the red blinking is failure of SIMM. I removed all SIMMs, and turn on the power, it still blinking as red. Does someone know red blinking without SIMMs is normal behavior (I also tried to put SIMMs only on Bank0, but same error)?

Error List for Indy
https://techpubs.jurassic.nl/manuals/hdw.../ch07.html

Best,
NaN

[dexter1]

Soy, i've read this topic multiple times, and it left me in a baffled state. At some point you decided to remove the PROM, got a new one and installed that one, and now you don't know what happened, since it is not working. So my question to you is:

Why did you remove and replace the PROM?

That really does not make sense, since you're now in a worse state than before. You had a working system, except for the SCSI2SD which wasn't initialised which we explained. And now you swap parts and doubt everything.

Please put your system in the same state as it was before, with the old PROM. You cannot expect us to fault find a system component (SCSI2SD), while you change that very system in a radical fashion (PROM) and ask us for advice...

[Soy]

Why did you remove and replace the PROM?

Error (red-blinking) indicates a fault around a memory sub-system (ex. SIMM). I tried to replace SIMMs with others, then did not change the red-blinking. So, I had doubt the PROM which is seemed a memory mapped ROM for a memory controller (There is no blinking and boot-sound when I remove CPU, so I think that PROM is read at the booting by CPU).

I replaced the PROM with new one, but still same error is occurred. After all, PROM has not any problem. So, I have changed PROM to old one now (after this same error is of course still occurred). If system without SIMM(s) can boot and make boot-sound then the system board itself have some problem. But if system without SIMM(s) can not boot and red-blinking, then system board is seemed that has no problem. I tried to separate problem to sub-problems, and I checked every sub-problem.

I do not doubt SCSI2SD (I have two units), because the booting does not displaying any message and there is no boot-sound, the error is happen before booting the system I think (SCSI device itself is separated from system, and "hinv" command shows valid SCSI devices after booting, because diagnosis routine works before system boot, and this routine detects the error in my case).

Best,
Soy

[dexter1]

The only way to diagnose the system is to hook up a terminal to the serial port and check the messages appearing there (if any): The easiest way to do that is to connect it to another PC or laptop by means of a nullmodem cable.