23 Apr
2013
23 Apr
'13
3:32 p.m.
On Apr 23, 2013, at 5:52 PM, allison wrote:
Those are fine; this is actually the exact same setup as my
11/23 with the CPU and RAM swapped out (it's an H9276 backplane,
so it should be fine with that arrangement). That machine was
just fine.
For the record, the setup is:
KA655
MS650-BA
DELQA
CQD-220
I used to have a DLV11J in there as well (configured for CSR/INT
1776500/300) in between the DELQA and the CQD-220, but I removed
that for now in case the TU58 driver was interfering (probably
not, since it didn't solve the problem). I also took out the
TSV05, since the tape drive it goes to isn't behaving right now
anyway.
If it were a grant chain continuity problem, I wouldn't expect
the SCSI card to even be able to boot, since it's MSCP-based
(unless the early MSCP boot stuff doesn't require an interrupt,
which would surprise me).
Just in case
it rings a bell with anyone here, though, if I'm
seeing a hang after this, is there anything in particular I
should do? I'm booting a SCSI CD drive off a CQD-220, which
seems to work OK for booting, at least.
Check your bus grant sequence and also the assigned addresses
of the IO cards (all of them). I 'll bet you have more than a few on the same
address or incorrect ones.
There is a specific set that is best to use and also the grant chain will
have the system see devices and hang using them (or try to).
There are definitely no address conflicts unless the KA655 is
adding something I'm not aware of (the DLV11J is NOT set to
provide the console SLU address, if that even matters, but it
is also not currently installed). My guess is that it's just
a matter of the CQD-220 not playing nicely with my CD-ROM drive,
though I'm a bit puzzled as to why it boots the initial part
and barfs at trying to start BACKUP. Some extra verbosity
would be handy there; I suppose if I get really desperate, I
could just try halting and disassembling and see where it's
waiting.
- Dave