Re: Troubles with NCR controller (was: Unidentified subject!)

Michal Jaegermann (michal@ellpspace.math.ualberta.ca)
Sat, 9 Nov 1996 11:29:46 -0700 (MST)

>
> I'm having a little trouble with the NCR53c8xxx driver on two
> EB164's (running RHL 3.0.3). Here are my settings:
>
> CONFIG_SCSI_NCR53C8XX=y
> # CONFIG_SCSI_NCR53C8XX_TAGGED_QUEUE is not set
> CONFIG_SCSI_NCR53C8XX_IOMAPPED=y
> CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT=y
> CONFIG_SCSI_NCR53C8XX_FORCE_ASYNCHRONOUS=y
> # CONFIG_SCSI_NCR53C8XX_FORCE_SYNC_NEGO is not set
>
>
> The problem only seems to manifest itself when the system crashes
> and fscks on reboot. It will sometimes completely hang the system.

I used this driver, with very good results, for various kernels from
2.0.x series and on Cabriolet and EB164 machines; but with the following
settings:

CONFIG_SCSI_NCR53C8XX=y
CONFIG_SCSI_NCR53C8XX_TAGGED_QUEUE=y
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT is not set
# CONFIG_SCSI_NCR53C8XX_FORCE_ASYNCHRONOUS is not set
CONFIG_SCSI_NCR53C8XX_FORCE_SYNC_NEGO=y
# CONFIG_SCSI_NCR53C8XX_DISABLE_MPARITY_CHECK is not set
# CONFIG_SCSI_NCR53C8XX_DISABLE_PARITY_CHECK is not set

Double-negatives in configuration options require a careful parsing
when the first time. :-)

> The
> strange thing is that if I reboot to the origional 1.3.90 RedHat kernel,
> it will not hang.

1.3.90 does not support the driver in question. It uses an alternative
one.

Michal

--
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com



Feedback | Store | News | Support | Product Errata | About Us | Linux Info | Search | JumpWords
No Frames | Show Frames

Copyright © 1995-1997 Red Hat Software. Legal notices