2025.08.02 firmware issue for Indigo2 where 2024.12.08 works

[mzryz]

I have flashed v2025.08.02 firmware, but my Indigo complains:

Unexpected info phase 20, state 4e, resetting scsi bus
Internal SCSI device/cable *FAILED*
Diagnostics failed

Going back to 2024.12.08 firmware, the machine boots and runs without any problem. I have attempted to flash back and forth a few times to confirm that the only thing changing is the firmware.

I have tried the recommended settings:

[SCSI]
System="Generic"
SpeedGrade="Default"
MaxSyncSpeed=10
Debug=1

But this has not changed the situation at all.

I am running the image on ID1, I have also tried ID2. The system does 'see' the drive in the Prom hardware inventory. But cannot boot off it.

SonnyJim recommended I move this to it's own issue, since it does not appear to be the same problem in the 'timing related' thread.

log.txt

[erichelgeson]

If anyone could give the latest a try - some timings and ram optimizations were pulled in - https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2025.10.27

[mzryz]

If anyone could give the latest a try - some timings and ram optimizations were pulled in - https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2025.10.27

@erichelgeson the new release didn't improve the situation, but I have managed to get it to work by setting EnableSCSI2=0 in the bluescsi.ini. This works on the previous release, and this release. I haven't done any benchmark yet, so I am not sure if it's losing any performance by turning SCSI2 mode off, since the Indigo2 should be a SCSI2 system.

edit: I did a benchmark, it seems to be quite fast, reaching around 9mb/s. Does the scsi2 option actually do anything?

[mzryz]

I also wanted to add, this person tipped me off (he was experiencing the same issue, on the previous firmware, but he got it working) https://forums.sgi.sh/index.php?threads/bluescsiv2-indigo2-problems.1410/post-8426

Oddly though, he was under the impression that it was the 'overclock' which made it work. I first tried the overclock, which made no difference. I then noticed he was disabling scsi 2, so I tried that and voila. Who know why he was randomly turning scsi2 off... but whatever.

[erichelgeson]

I was chatting with Stormy on discord and I think disabling scsi2 having an effect helps narrow down the issue quite a bit (again, sorry I don't have a system that exhibits this behavior so it's difficult for me to test).

I've created a test firmware if someone can help me test to narrow down where the issue is we can implement a fix or work around.

Flash this firmware: https://github.com/BlueSCSI/BlueSCSI-v2/actions/runs/20211510272 ("Artifacts" on the bottom of the page, must be logged into github to see)

Test in isolation each of these 3. Please provide the log, ini, and results of each.

---

Test 1: Phase Change Delay Only (Most Likely Fix)
[SCSI]
EnableSCSI2 = true
PhaseChangeDelay = 100

---

Test 2: Data Phase Delay Only
[SCSI]
EnableSCSI2 = true
DataPhaseDelay = 400

---

Test 3: Both Phase Delays
[SCSI]
EnableSCSI2 = true
PhaseChangeDelay = 100
DataPhaseDelay = 400

[mzryz]

I went through the systematic process of choosing different PhaseChangeDelay settings (Test 1) starting at 100 (which worked!) going 50, 25, 10 and finally 5. The system failed on 5, so 10 is the sweet spot..

So using the settings in Eric's TEST 1 parameters will work, with PhaseChangeDelay = 10

Thank you