v2025 firmware causes timeouts on SGI Indigo2, but v2024 works

[thejpster]

I have a 25-pin BlueSCSI v2 and I use it for CD-ROM emulation on my various machines.

I used it with my SGI Power Indigo2 a lot back in November and it was excellent. No problems. It had whatever firmware was the latest at the time.

I recently upgraded it the v2025.07.11 firmware and then used it with my HP 9000 Model 712. Again, it worked great - I installed NeXSTEP 3.3 for PA-RISC without issues.

However, now I connected it back to the Indigo 2, it has stopped working. On boot, the SGI ROM throws timeout errors after sending various SCSI commands. The SGI ROM then declares the SCSI bus broken and won't boot.

I reflashed the BlueSCSI back to v2024.12.08 and it now works fine on the Indigo2 - no errors on start-up.

What can I do to usefully debug this for you? Very familiar with programming the RP2040 so I'm happy to compile test builds or whatever.

[alexthecat123]

The exact same thing just happened to me with my Amiga 3000. I've got a BlueSCSI v2 Desktop installed in there, and it stopped working with a bunch of timeout errors when I upgraded to v2025.07.11. Reverting back to v2024.12.08 fixed it!

[erichelgeson]

Could be due to the tighter timings with the new clock speed. Could either of you try this?

[SCSI]
SpeedGrade="Default"

[alexthecat123]

Thanks for the suggestion! Unfortunately no luck on the Amiga; there isn't any difference at all when I add that line to the config.

[erichelgeson]

Sorry lets take a step back. Can each of you share the logs of the timeouts your getting? Are you seeing this on the host or log.txt?

[alexthecat123]

For me, I see the timeout error in log.txt. The timeout message doesn't appear in the logs when I just try to boot off the disk, but it does appear when I boot from a floppy and try to communicate with the disk from the Amiga's hard disk utility. Booting from the BlueSCSI just results in the activity light coming on for about a second, and then the computer giving up and going to the Kickstart "insert a floppy" screen.

I've attached my logfile. Everything up to 5133ms is the boot attempt, and then everything after that is the disk utility trying to access the drive.

Let me know if you need anything else!

log.txt

[erichelgeson]

It looks like the SpeedGrade setting was not picked up, can you paste your entire ini file? Also lets remove variables - just have one drive for the test (after we get to the bottom of the SpeedGrade not being picked up)

[alexthecat123]

Oh sorry, I removed the SpeedGrade line from the ini file after it didn't fix the problem! But I just added it back and I've attached the new log file. And I also removed the drive that was on ID 5, so we've only got the one on ID 6 now.

Here's the contents of my ini file:

[SCSI]
Debug=1
SpeedGrade="Default"
EnableSCSI2=0

As with the previous log file, everything up through 5411ms is the boot attempt, and everything after that is me trying to access the drive in a disk utility.

log.txt

[thejpster]

Sorry lets take a step back. Can each of you share the logs of the timeouts your getting? Are you seeing this on the host or log.txt?

I see the error on the SGI firmware console on the host on startup, and it causes it to refuse to boot.

When I get back to the machine I'll try and grab a debug log.

[SonnyJim]

Just tried it on my Indigo 2 Maximum Impact and it causes SCSI errors:

https://i.imgur.com/7aGiXgW.png

It was previously working on v2024, ini file looks like this:

[SCSI] Quirks=0 ; Standard EnableParity=0 ; Off EnableSCSI2=1 ; Off

Will have a little playaround to see what's going on. Maybe the Fast20 changes?

[thejpster]

Yes that looks very familiar.

[mynameistroy]

You could try setting MaxSyncSpeed=0 and see if it has anything to do with that first. Otherwise perhaps some timing thing got messed up. I have and Indy, O2 and Fuel I can try it on. I know it worked fine with my O2 in the beta stages but I haven't tested it yet with the released firmware.

[SonnyJim]

Ok so annoyingly, the device works in Indigo 2 when debug=1, if I turn it off debug it fails with bus errors. So maybe turning on debugging slows it down enough or something, I'm not sure.

Tried with MaxSyncSpeed=0 (no debug) and it fails.

[thejpster]

If only we had https://www.artisantg.com/TestMeasurement/57586-7/Teledyne-LeCroy-Ancot-DSC-216-FD-SCSI-Logic-Analyzer

[SonnyJim]

Tried with:

[SDIO] AddClockDelay=2

As per a suggestion in discord, still fails.

[erichelgeson]

Someone on an O2 please try this and provide a log

[SCSI]
SpeedGrade="Default"

Currently have no idea if the o2 and amiga issues are related, o2 we dont have a log from yet and is a timeout on the host, the amiga is a scsiread timeout on the bluescsi. these should probably be worked on separately till we can determine if they are.

Also since @mynameistroy had it working in the beta and now not we can bisect it from the working to broken release and determine the issue.