CyberstormPPC SCSI settings

[x56h34]

I currently have only one SCSI device in my CSPPC SCSI chain. It's a hard drive (unit 0).

The card produces a considerable delay before the hard drive starts to boot, as I have no IDE devices connected to the motherboard controller, and I need to wait for the scsi.device to stop seeking for a drive before it would switch to CSPPC SCSI scanning.

Anyways, I suspect that the unusual long delay is also a bit due to settings of the CSPPC SCSI early boot menu. Here's what I did:

Unit 0 has a setting of LUN-1. I can tweak this for anything from LUN-1 to LUN-8.
Everything else is switched off (NO LUNs), except unit 7, which is the controller itself.

My question is, can these settings be manipulated in any better way in order for me to decrease some of the boot delay which is happening due to possible long scanning of the SCSI bus? The major culprit is the 3.1 Roms' IDE seek delay, but I have a suspition that CSPPC SCSI has its share of delays too, since it could potentialy not be optimized to quickly scan what's in the chain, and boot.

Any tips? What settings should I use in the CSPPC early boot menu in the SCSI portion?

Thanks.

[Piru]

The major culprit is the 3.1 Roms' IDE seek delay

Well, it's IDE scan delay, which can be upto 30 secs with 3.1 IIRC. Anyway, here's the fix:

no4000ide.lha
IDE_Killer.lha (with a pic)

[x56h34]

Hi Piru.

Yes, I have that hack too. :-)
It has increased the speed of my boot time noticeably, however there's still a largeish delay. I guess CSPPC simply must take its time, and that's it. :-?

[Piru]

Yes, I have that hack too.
It has increased the speed of my boot time noticeably, however there's still a largeish delay. I guess CSPPC simply must take its time, and that's it.

Probably. The settings you use (1 LUN for the used unit, NO LUNs for other units) seems optimal. At least that is what was the fastest with my BPPC SCSI.

However, at least with BPPC SCSI you could also tune the SCSI reset delay, I had it set to 1 second IIRC.

[Framiga]

. . .  .enable SCSIPatch in the Early Boot Menu as reported in the docs, could help :-)

[x56h34]

@Framiga:

I am afraid that is not an option because in order to do that I need to enable MapRom as well (otherwise SCSIPatch is ghosted) and if you enable MapRom with CSPPC, then BlizKick doesn't work. :-(

[Piru]

@x56h34
bk_noide.lha BlizKick module disables scsi.device

Maybe this will do?

[billchase]

I apologize for the unintelligent question, but
what are you using blizkick for?  If this is what
I think it is, it is not necessary for a Cyberstorm.

As far as boot delay, check the jumpers on your
drive, many have a setting for initialization
delays.

C Snyder

[zipper]

If you enable SCSIPatch before disabling MapRom, does it work? At least that way it seems possible to set them.

[Piru]

If this is what I think it is, it is not necessary for a Cyberstorm.

BlizKick does a lot more than just maprom, it can patch the ROM before mapping (fix some bugs for example). Also you can get rid of some extra reboots with AOS 3.5/3.9 + some other patch.