This means, that the controller isn't found during bootup. Make sure
that you
- choosed the right driver (aic7xxx)
- hardwired the support for SCSI in the kernel (do not compile the
driver as a
module).
But you wouldn't see any SCSI-partiton until the controller is found....
hm...?
Try "PCI bridge optimization" - it solved a network card problem in my
case (card was found but no network was reachable; message was "too much
work on interrupt").
Greetings, Dietmar
Charles Galpin wrote:
>
> Ok, here is the latest
>
> Dropped to 13.4 - Still get the timeouts
>
> Dropped to 10 (lowest) - get this error again (same error when disabled
> disconnects)
>
> <4> scsi0: (-1:-1:-1) Referenced SCB 255 not valid during SELTO
> <4> SCSISEQ=0x5a SEQADDR=0x7 SSTAT0=0x10 SSTAT1=0x88
> <6> scsi0: (-1:-1:-1) Invalid WAITING_SCBH value 128, improvising
>
> I want to run something by you guys. When I first boot up, I get
>
> <4>scsi : 0 hosts.
> <4>scsi : detected total.
>
> initially (right before the partition check), and only when it installs the
> modules does it recognize the card.
>
> Is this normal?
>
> Any other ideas?
>
> Can someone tell me what the driver is even doing in that initial probe?
>
> tia
> charles
>
> ===== Original Message from Zygmunt Wiercioch <[EMAIL PROTECTED]> at
> 4/20/99 1:26 pm
> >I had the same problems with a 2940UW and Western Digital drives (WDE9100
> >SCSI 3, but 50 pin). I did manage to get them going, but only at 10Mb
> >synchronous. Anything higher an I'd get corruptions/timeouts/resets. This
> >was with 2.0.35 and 2.2.1. I have not tried to change the settings on 2.2.6
> >or put in Doug's latest driver, since I don't have the time to save my data
> >and try to see if I can get it to go at 40 without problems.
> >
> >Looks like you may have to drop down to 10Mb. Waste of expensive drives and
> >expensive card !
> >
> >Zygmunt Wiercioch
> >
> >-----Original Message-----
> >From: Charles Galpin [mailto:[EMAIL PROTECTED]]
> >Sent: April 20, 1999 12:52
> >To: Dr. Robert J. Meier; Linux-Scsi
> >Subject: RE: adaptec 2940U2W/ibm ultrastar 9ES problem
> >
> >
> >Hi Bob
> >
> >Yes, this is what adaptec suggested. I took it down to 40, and then 20
> >Mbytes/s, but got the same timeout errors.
> >
> >The funny thing (well not really) is that with adaptec's drivers under NT it
> >
> >seems fine, although I have no way of determining if it is performing as
> >expected - seems pretty fast.
> >
> >At this point I'm sorely dissapointed. I spent more on the controller/drive
> >than I did on my last linux system (the entire thing) a year ago which
> >intsalled effortlessly and performs like a champ. I can't even run linux on
> >this hardware.
> >
> >Bob. Did you install from scratch with the 2940U2W? If so, what kernel and
> >scsi driver version were you running when you installed?
> >
> >Can ayone suggest a different drive if I choose to return this?
> >
> >Does anyone suspect the contoller over the drive?
> >
> >thanks
> >charles
> >
> >===== Original Message from "Dr. Robert J. Meier"
> ><[EMAIL PROTECTED]> at 4/20/99 11:34 am
> >>Charles,
> >>
> >> I recently purchased a Seagate 9G SCSI LVD/ultra 2 wide)
> >>Hard Drive (Baracuda) and Adaptec 2940 U2W controller. I suspect
> >>that the IBM 9G Hard drive may also be a Baracuda. I ran into
> >>unreliability problems that appear to represent an overrating of
> >>speed for the hard disk read amplifiers. The workaround that
> >>I am using is a reduced bus speed. I intend to contact Seagate
> >>to see if they will help, though the problem was not discovered
> >>within the 30d warranty period.
> >>
> >> To use the Adaptec Bios setup
> >> 1. Turn on computer power.
> >> 2. Type \C-a when indicated during power-up.
> >> (Be ready. The time window is ~2s.)
> >> 3. Select SCSI configuration.
> >> 4. Move to column logical unit 0 (or as appropriate).
> >> 5. Select speed (default is 80.0 Mbytes/s).
> >> 6. Reduce speed to 53.4 Mbytes/s.
> >> 7. Exit (\E)
> >> 8. Confirm save of settings.
> >> 9. Exit (\E)
> >> 10. Confirm exit of setup program.
> >>
> >> I have similarly tried different cables, termination, and
> >>mount options without affecting behavior.
> >>
> >>Please let me know what you find.
> >>
> >>Bob
> >>
> >>
> >>-
> >>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> >>the body of a message to [EMAIL PROTECTED]
> >
> >-- Charles Galpin <[EMAIL PROTECTED]>
> >
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> >the body of a message to [EMAIL PROTECTED]
>
> -- Charles Galpin <[EMAIL PROTECTED]>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
--
"Don't fear the Gates" (a little like Blue Oyster Cult)
Dietmar Stein, Systemadministrator UNIX/Linux
[EMAIL PROTECTED], [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
