christ,
Yes, the ctrl-A command during a re-boot does detect the adaptec host.
I don't know enough about the settings to feel confident in changing them,
so I have let them alone. There is no explicit place that sets the irq for
this card in that bios, however, only the host's id #(its set to 7 by
default). I'd be happy to relay any other settings to you that you think
may be of use.
Is that superdebug mode you mentioned in the readme for the aic7xxx
driver and run by the driver? If so, I can just follow the instructions for
that...
Thanks,
april
-----Original Message-----
From: christ <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, May 26, 1999 10:46 AM
Subject: Re: Weird SCSI behavior
>
>>Hey all,
>>
>> has anyone encountered this with a scsi behavior before? During a
lilo
>>boot, the scsi host is detected, then goes into what may be an infinite
loop
>>with the following statements:
>>
>> SCSI host 0 abort (pid 2) timed out -- resetting
>> SCSI buss is being reset for host 0 channel 0
>> SCSI host 0 abort (pid 2) timed out -- trying harder
>>
>> These three lines repeat over and over... I have not changed any IRQ
>>settings on the machines manually, but I have changed the posistions of
the
>>PCI cards in the system. I have not changed any BIOS settings manually
>>either. Anyone seen this before?
>
>welp, guess i need to ask what someone else already asked to be sure...
>can you see the device from the bios of the adaptec card? (control-A
during
>card init, before boot)
>
>most scsi probs i see are cabling-related, but those usually mean that in
no
>way does the card work (at least, detect all devices) during boot.,
>
>and, working in other OS'es isnt always a good indicator that stuff is
setup
>right.. linux is often less forgiving than NT or sunos, for instance.
>
>if it seems ok from the bios, tell me and ill track down the list
>of options to the driver to give you more info about the prob--
>i had to use superdebugmode once to fix a 2940 that was "stuck" on boot--
>it needed a wacky boot option to skip initial reset because something
>was horked, but that avoided the brokenness enough for it to boot, and
>it has worked fine since, amazingly enough (unexpected, since this is one
of
>16 in identical setups that spontaneously displayed a problem a year into
>usage...i assumed it was on its way totally south)
>
>
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
