Skip to contentSkip to conversation

Proliant hangs with 2.4 but works with 2.2.

DISCUSSION Arturas V 3 participants 3 messages Dec 26, 2001

lore
Share & tools
lore

Arturas V

author
#0 lore raw
Quoted 7 lines · lafanga lafanga

I have a Compaq Proliant 1600 server which can be hung on demand with >all the 2.4 series kernels I have tried (2.4, 2.4.1 & 2.4.2-pre3). >Kernel 2.2.16 runs perfectly (from a default RH7.0).

I have ensured that the server meets the necessary requirements for >the 2.4 kernels (modutils etc) and I have tried kgcc and various gcc versions.

Quoted 1 line

When compiling I have tried default configs and also minimalist configs

(with only cpqarray and tlan). I have also ensured that I have the latest

Quoted 1 line

current SmartStart CD (4.9) and have setup the firmware for installing

Linux.

I had similar problem with 2.4.5 Kernel. I managed to solve the problem by configuring a working verion of kernel with NCR53C8XX SCSI support as well as SYM53C8XX. As far as I understood
SYM53C8xx support covers 53C8xx chips better than NCR53C8xx and that makes all the difference. Anyone understands why?
---
Arturas Vaitaitis.
---
Please CC to [email protected]
P.S. Intelligence has yet to prove its survival value

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

#1 lore raw

Hello Arturus , Fyi , The SYM2 version of the 53c8xx driver (imo) has better support for both the older & newer chips . The first 2.4 kernel with the SYM2 included is 2.4.16 (iirc) .
Hth , JimL

Quoted 23 lines · Arturas V
Quoted 10 lines · lafanga lafanga

I have a Compaq Proliant 1600 server which can be hung on demand with >all the 2.4 series kernels I have tried (2.4, 2.4.1 & 2.4.2-pre3). >Kernel 2.2.16 runs perfectly (from a default RH7.0).

I have ensured that the server meets the necessary requirements for >the 2.4 kernels (modutils etc) and I have tried kgcc and various gcc versions.

Quoted 1 line

When compiling I have tried default configs and also minimalist configs

(with only cpqarray and tlan). I have also ensured that I have the latest

Quoted 1 line

current SmartStart CD (4.9) and have setup the firmware for installing

Linux.

I had similar problem with 2.4.5 Kernel. I managed to solve the problem by configuring a working verion of kernel with
NCR53C8XX SCSI support as well as SYM53C8XX. As far as I understood SYM53C8xx support covers 53C8xx chips better than NCR53C8xx and that makes all the difference. Anyone understands why?
---
Arturas Vaitaitis.
---
Please CC to [email protected]
P.S. Intelligence has yet to prove its survival value

Quoted 9 lines

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | [email protected] | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+
#2 lore raw
In reply to Arturas V
Quoted 9 lines · Arturas V
Quoted 8 lines · lafanga lafanga

I have a Compaq Proliant 1600 server which can be hung on demand with >all the 2.4 series kernels I have tried (2.4, 2.4.1 & 2.4.2-pre3). >Kernel 2.2.16 runs perfectly (from a default RH7.0).

I have ensured that the server meets the necessary requirements for >the 2.4 kernels (modutils etc) and I have tried kgcc and various gcc versions.

Quoted 1 line

When compiling I have tried default configs and also minimalist configs

(with only cpqarray and tlan). I have also ensured that I have the latest

Quoted 8 lines
Quoted 2 lines
Quoted 1 line

current SmartStart CD (4.9) and have setup the firmware for installing

Linux.

I had similar problem with 2.4.5 Kernel. I managed to solve the problem by configuring a working verion of kernel with
NCR53C8XX SCSI support as well as SYM53C8XX. As far as I understood SYM53C8xx support covers 53C8xx chips better than NCR53C8xx and that makes all the difference. Anyone understands why?

- NCR53C8XX supports all chips except the 53C1010 (33MHz and 66MHz PCI) Ultra-160 controllers.

- SYM53C8XX supports chips that implement LOAD/STORE scripts instructions. As a result the 53C1010 Ultra-160 controllers are supported (+810A,860,875,895,895A,896).

- SYM53C8XX_2 (aka sym-2) supports all chips from earliest 810 rev.1 to latest 53C1010-66. Hopefully will replace SYM53C8XX/NCR53C8XX bundle.

(In fact, NCR53C8XX was only useful for 810 and 815 controllers)

For chips that support LOAD/STORE, the SYM53C8XX and SYM53C8XX_2 drivers care about the chips not mastering themselves over the PCI, as required by PCI 2.2 specifications.

NCR53C8XX and SYM53C8XX interface with scsi layer using the scsi-obsolete interface. SYM53C8XX_2 uses the EH interface.

You are encouraged to use SYM53C8XX_2 (aka sym-2, aka SYM53C8XX version 2). The driver is available in latest 2.4 and 2.5 kernels and can also be used on 2.2 kernel.

Gérard.