88 lines · plain
1.. SPDX-License-Identifier: GPL-2.02 3=================================4Qlogic FASXXX Family Driver Notes5=================================6 7This driver supports the Qlogic FASXXX family of chips. This driver8only works with the ISA, VLB, and PCMCIA versions of the Qlogic9FastSCSI! cards as well as any other card based on the FASXX chip10(including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).11 12This driver does NOT support the PCI version. Support for these PCI13Qlogic boards:14 15 * IQ-PCI16 * IQ-PCI-1017 * IQ-PCI-D18 19is provided by the qla1280 driver.20 21Nor does it support the PCI-Basic, which is supported by the22'am53c974' driver.23 24PCMCIA Support25==============26 27This currently only works if the card is enabled first from DOS. This28means you will have to load your socket and card services, and29QL41DOS.SYS and QL40ENBL.SYS. These are a minimum, but loading the30rest of the modules won't interfere with the operation. The next31thing to do is load the kernel without resetting the hardware, which32can be a simple ctrl-alt-delete with a boot floppy, or by using33loadlin with the kernel image accessible from DOS. If you are using34the Linux PCMCIA driver, you will have to adjust it or otherwise stop35it from configuring the card.36 37I am working with the PCMCIA group to make it more flexible, but that38may take a while.39 40All Cards41=========42 43The top of the qlogic.c file has a number of defines that controls44configuration. As shipped, it provides a balance between speed and45function. If there are any problems, try setting SLOW_CABLE to 1, and46then try changing USE_IRQ and TURBO_PDMA to zero. If you are familiar47with SCSI, there are other settings which can tune the bus.48 49It may be a good idea to enable RESET_AT_START, especially if the50devices may not have been just powered up, or if you are restarting51after a crash, since they may be busy trying to complete the last52command or something. It comes up faster if this is set to zero, and53if you have reliable hardware and connections it may be more useful to54not reset things.55 56Some Troubleshooting Tips57=========================58 59Make sure it works properly under DOS. You should also do an initial FDISK60on a new drive if you want partitions.61 62Don't enable all the speedups first. If anything is wrong, they will make63any problem worse.64 65Important66=========67 68The best way to test if your cables, termination, etc. are good is to69copy a very big file (e.g. a doublespace container file, or a very70large executable or archive). It should be at least 5 megabytes, but71you can do multiple tests on smaller files. Then do a COMP to verify72that the file copied properly. (Turn off all caching when doing these73tests, otherwise you will test your RAM and not the files). Then do7410 COMPs, comparing the same file on the SCSI hard drive, i.e. "COMP75realbig.doc realbig.doc". Then do it after the computer gets warm.76 77I noticed my system which seems to work 100% would fail this test if78the computer was left on for a few hours. It was worse with longer79cables, and more devices on the SCSI bus. What seems to happen is80that it gets a false ACK causing an extra byte to be inserted into the81stream (and this is not detected). This can be caused by bad82termination (the ACK can be reflected), or by noise when the chips83work less well because of the heat, or when cables get too long for84the speed.85 86Remember, if it doesn't work under DOS, it probably won't work under87Linux.88