Lines Matching +full:operating +full:- +full:points +full:- +full:v2
2 -=< The IBM Microchannel SCSI-Subsystem >=-
6 Low Level Software-Driver for Linux
17 ----------------
28 ----------------------
29 - Chris Beauregard (improvement of the SCSI-device mapping by the driver)
30 - Martin Kolinek (origin, first release of this driver)
31 - Klaus Kudielka (multiple SCSI-host management/detection, adaption to
33 - Michael Lang (assigning original pun/lun mapping, dynamical ldn
39 -----------------
42 2.1 IBM SCSI-Subsystem Detection
44 2.3 SCSI-Device Recognition and dynamical ldn Assignment
45 2.4 SCSI-Device Order
46 2.5 Regular SCSI-Command-Processing
52 2.11 /proc/scsi-Filesystem Information
53 2.12 /proc/mca-Filesystem Information
54 2.13 Supported IBM SCSI-Subsystems
62 5.4 Support WWW-page
73 ----------
74 This README-file describes the IBM SCSI-subsystem low level driver for
84 --------------------
85 2.1 IBM SCSI-Subsystem Detection
86 --------------------------------
88 Microchannel-bus support is enabled, as the IBM SCSI-subsystem needs the
90 interrupt handler is connected to it to handle answers of the SCSI-
91 subsystem(s). If the F/W SCSI-adapter is forced by the BIOS to use IRQ11
92 instead of IRQ14, IRQ11 is used for the IBM SCSI-2 F/W adapter. In a
94 the kernel commandline, where the I/O port and the SCSI-subsystem id can
95 be specified. The next step checks if there is an integrated SCSI-subsystem
96 installed. This register area is fixed through all IBM PS/2 MCA-machines
97 and appears as something like a virtual slot 10 of the MCA-bus. On most
99 integrated SCSI-controller is available. But on certain PS/2s, like model
101 stage confused the driver and resulted in the detection of some ghost-SCSI.
102 If POS-register 2 and 3 are not 0x00 and not 0xff, but all other POS
103 registers are either 0xff or 0x00, there must be an integrated SCSI-
104 subsystem present and it will be registered as IBM Integrated SCSI-
105 Subsystem. The next step checks, if there is a slot-adapter installed on
106 the MCA-bus. To get this, the first two POS-registers, that represent the
108 adapter list, a SCSI-subsystem is assumed to be found in a slot and will be
109 registered. This check is done through all possible MCA-bus slots to allow
110 more than one SCSI-adapter to be present in the PS/2-system and this is
115 I/O-address at 0x3540 - 0x3547, further installed IBM SCSI-adapters must
116 use a different I/O-address. This is expressed by bit 1 to 3 of POS2
121 The POS2-register of all PS/2 models' integrated SCSI-subsystems has the
123 Bit 7 - 4 : Chip Revision ID (Release)
124 Bit 3 - 2 : Reserved
126 Bit 0 : Chip Enable (EN-Signal)
127 The POS3-register is interpreted as follows (for most IBM SCSI-subsys.):
128 Bit 7 - 5 : SCSI ID
129 Bit 4 - 0 : Reserved = 0
130 The slot-adapters have different interpretation of these bits. The IBM SCSI
131 adapter (w/Cache) and the IBM SCSI-2 F/W adapter use the following
133 Bit 7 - 4 : ROM Segment Address Select
134 Bit 3 - 1 : Adapter I/O Address Select (*8+0x3540)
135 Bit 0 : Adapter Enable (EN-Signal)
137 Bit 7 - 5 : SCSI ID
139 Bit 3 - 0 : Arbitration Level
140 The most modern product of the series is the IBM SCSI-2 F/W adapter, it
141 allows dual-bus SCSI and SCSI-wide addressing, which means, PUNs may be
142 between 0 and 15. Here, Bit 4 is the high-order bit of the 4-bit wide
145 slot-adapters get ports assigned by the automatic configuration tool.
147 One day I found a patch in ibmmca_detect(), forcing the I/O-address to be
148 0x3540 for integrated SCSI-subsystems, there was a remark placed, that on
149 integrated IBM SCSI-subsystems of model 56, the POS2 register was showing 5.
156 Every time, a SCSI-subsystem is discovered, the ibmmca_register() function
157 is called. This function checks first, if the requested area for the I/O-
158 address of this SCSI-subsystem is still available and assigns this I/O-
159 area to the SCSI-subsystem. There are always 8 sequential I/O-addresses
160 taken for each individual SCSI-subsystem found, which are:
172 After the I/O-address range is assigned, the host-adapter is assigned
174 driver itself and the mid- and higher-level SCSI-drivers. The SCSI pun/lun
180 ------------------------------------------------------
186 between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two
188 in wide-addressing mode you can have 16 puns with 32 luns on each device.
189 This section describes the handling of devices on non-F/W adapters.
194 are between 0 and 6(15). On a wide-adapter a pun higher than 7 is
196 one logical unit, with lun=0. A CD-ROM jukebox would be an example of a
199 The embedded microprocessor of the IBM SCSI-subsystem hides the complex
200 two-dimensional (pun,lun) organization from the operating system.
201 When the machine is powered-up (or rebooted), the embedded microprocessor
203 15 devices found are assigned into a one-dimensional array of so-called
208 2.3 SCSI-Device Recognition and Dynamical ldn Assignment
209 --------------------------------------------------------
212 are to offer fake pun/lun combinations to the operating system or to
214 the immediate assign command of the SCSI-subsystem for probing through
216 which is used by IBM SCSI-subsystems to access some valid SCSI-device.
232 fewer than the 15 that it could use, then it just mapped ldn ->
238 The physical SCSI-devices on the SCSI-bus are probed via immediate_assign-
239 and device_inquiry-commands, that is all implemented in a completely new
241 SCSI-world that is now stored in the get_scsi[][]-array. This means,
243 It no longer believes in default-settings of the subsystem and maps all
246 there are more SCSI-devices installed than ldns available (n>15). The
249 SCSI-installations have optimum access-speed and are not touched by
251 lun>0 or to non-existing devices, in order to satisfy the subsystem, if
252 there are less than 15 SCSI-devices connected. In the case of more than 15
256 dynamical reassignments on the SCSI-devices until a certain device
258 during intense I/O between up to 15 SCSI-devices (means pun,lun
264 2.4 SCSI-Device Order
265 ---------------------
267 their report to mid-level- and higher-level-drivers, the new reported puns
271 You have to reboot (CTRL-D) with an old kernel and set the /etc/fstab-file
273 If your boot-partition is not coming up, also edit the /etc/lilo.conf-file
277 the assignment order of the SCSI-devices by flipping the PUN-assignment.
280 The problem for this is, that Linux does not assign the SCSI-devices in the
281 way as described in the ANSI-SCSI-standard. Linux assigns /dev/sda to
285 where the BIOS assigns drives belonging to the ANSI-SCSI-standard. Most
286 other producers' BIOS does not (I think even Adaptec-BIOS). The
288 kernel enables to choose the preferred way of SCSI-device-assignment.
290 same order as DOS and OS/2 does on your MCA-machine. This is also standard
291 on most industrial computers and OSes, like e.g. OS-9. Leaving this flag
296 2.5 Regular SCSI-Command-Processing
297 -----------------------------------
310 --------------------------
314 to be a problem with other low-level SCSI drivers too, however
318 -----------------
326 ----------------------
331 -------------------------
336 ---------------------------------
337 This driver supports up to eight interfaces of type IBM-SCSI-Subsystem.
338 Integrated-, and MCA-adapters are automatically recognized. Unrecognizable
339 IBM-SCSI-Subsystem interfaces can be specified as kernel-parameters.
341 2.11 /proc/scsi-Filesystem Information
342 --------------------------------------
348 (software) or integrated (hardware) SCSI-command set (see below). The
350 in order to help debugging problems with CD-ROMs or tapedrives.
353 used by the SCSI-subsystem. The load on each ldn is shown in the table,
356 15 pun/lun combinations available on the SCSI-bus.
363 2.12 /proc/mca-Filesystem Information
364 -------------------------------------
365 The slot-file contains all default entries and in addition chip and I/O-
366 address information of the SCSI-subsystem. This information is provided
369 2.13 Supported IBM SCSI-Subsystems
370 ----------------------------------
371 The following IBM SCSI-subsystems are supported by this driver:
373 - IBM Fast/Wide SCSI-2 Adapter
374 - IBM 7568 Industrial Computer SCSI Adapter w/Cache
375 - IBM Expansion Unit SCSI Controller
376 - IBM SCSI Adapter w/Cache
377 - IBM SCSI Adapter
378 - IBM Integrated SCSI Controller
379 - All clones, 100% compatible with the chipset and subsystem command
380 system of IBM SCSI-adapters (forced detection)
383 --------------------------
384 The IBM SCSI-subsystem low level driver is prepared to be used with
396 --------------
398 - Martin Kolinek
402 when the machine is powered-up or rebooted) is used.
408 - Martin Kolinek
410 I think that the CD-ROM is now detected only if a CD is
413 - Martin Kolinek
415 Feb 7 1996: Modified biosparam function. Fixed the CD-ROM detection.
419 - Martin Kolinek
428 - Martin Kolinek
431 insufficient for those of us with CD-ROM changers.
432 - Chris Beauregard
440 - Chris Beauregard
442 Mar 8-16 1997: Modified driver to run as a module and to support
445 available for one single adapter. The find_subsystem-routine has vanished.
447 This routine checks for presence of MCA-bus, checks the interrupt
449 Certain PS/2-models do not recognize a SCSI-subsystem automatically.
450 Hence, the setup defined by command-line-parameters is checked first.
451 Thereafter, the routine probes for an integrated SCSI-subsystem.
453 possible combinations of multiple SCSI-subsystems on one MCA-board. Up to
454 eight SCSI-subsystems can be recognized and announced to the upper-level
457 - Klaus Kudielka
460 1) SCSI-command capability enlarged by the recognition of MODE_SELECT.
461 This needs the RD-Bit to be disabled on IM_OTHER_SCSI_CMD_CMD which
463 necessary step to be allowed to set blocksize of SCSI-tape-drives and
464 the tape-speed, without confusing the SCSI-Subsystem.
467 the kernel-scsi-environment. The markup of a tape is done in the
470 3) The ldn_is_tape[] array is necessary to distinguish between tape- and
472 with the SCB-command for read and write in the ibmmca_queuecommand
474 the tape-devices, as recommended by IBM in this Technical Reference,
477 the subsystem and this causes kernel-panic.)
481 The tape-support has been tested with a SONY SDT-5200 and a HP DDS-2
482 (I do not know yet the type). Optimization and CD-ROM audio-support,
484 - Michael Lang
487 1) Submitting the extra-array ldn_is_tape[] -> to the local ld[]
488 device-array.
489 2) CD-ROM Audio-Play seems to work now.
490 3) When using DDS-2 (120M) DAT-Tapes, mtst shows still density-code
491 0x13 for ordinary DDS (61000 BPM) instead 0x24 for DDS-2. This appears
492 also on Adaptec 2940 adaptor in a PCI-System. Therefore, I assume that
493 the problem is independent of the low-level-driver/bus-architecture.
494 4) Hexadecimal ldn on PS/2-95 LED-display.
495 5) Fixing of the PS/2-LED on/off that it works right with tapedrives and
497 - Michael Lang
501 outer-world about operational load statistics on the different ldns,
502 seen by the driver. Everybody that has more than one IBM-SCSI should
504 than one IBM-SCSI hosts.
505 2) Definition of a driver version-number to have a better recognition of
507 the user, when reading about release-specific problems. Up to know,
508 I calculated the version-number to be 1.7. Because we are in BETA-test
511 CD-ROM did not work any more! The C7-command was a fake impression
512 I got while programming. Now, the READ and WRITE commands for CD-ROM are
514 IM_OTHER_SCSI_CMD_CMD. On my observations (PS/2-95), now CD-ROM mounts
515 much faster(!) and hopefully all fancy multimedia-functions, like direct
516 digital recording from audio-CDs also work. (I tried it with cdda2wav
517 from the cdwtools-package and it filled up the harddisk immediately :-).)
518 To easify boolean logics, a further local device-type in ld[], called
520 4) If one uses a SCSI-device of unsupported type/commands, one
521 immediately runs into a kernel-panic caused by Command Error. To better
522 understand which SCSI-command caused the problem, I extended this
523 specific panic-message slightly.
524 - Michael Lang
527 1) Some cosmetic changes for the handling of SCSI-device-types.
528 Now, also CD-Burners / WORMs and SCSI-scanners should work. For
529 MO-drives I have no experience, therefore not yet supported.
530 In logical_devices I changed from different type-variables to one
532 of a SCSI-device are stored.
533 2) There existed a small bug, that maps a device, coming after a SCSI-tape
534 wrong. Therefore, e.g. a CD-ROM changer would have been mapped wrong
535 -> problem removed.
537 vendor and revision-level of a SCSI-device for internal usage.
538 - Michael Lang
540 June 26-29 1997: (v2.0b)
542 recognition and handling of SCSI-devices with the adapter. As I got
544 I remembered this immediate_assign-command, I found once in the handbook.
546 on the SCSI-subsystem. After that, it probes on all puns and luns for
550 by the assignment of all ldns to existing SCSI-devices. If more ldns
557 3) The LED-display shows on PS/2-95 no longer the ldn, but the SCSI-ID
558 (pun) of the accessed SCSI-device. This is now senseful, because the
562 hit-statistics of ldns is shown and a second part, where the maps of
563 physical and logical SCSI-devices are displayed. This could be very
564 interesting, when one is using more than 15 SCSI-devices in order to
566 - Michael Lang
568 June 26-29 1997: (v2.0b-1)
572 - Michael Lang
574 July 1-13 1997: (v3.0b,c)
575 1) Merging of the driver-developments of Klaus Kudielka and Michael Lang
576 in order to get a optimum and unified driver-release for the
577 IBM-SCSI-Subsystem-Adapter(s).
578 For people, using the Kernel-release >=2.1.0, module-support should
579 be no problem. For users, running under <2.1.0, module-support may not
581 2) Added some more effective statistics for /proc-output.
582 3) Change typecasting at necessary points from (unsigned long) to
584 4) Included #if... at special points to have specific adaption of the
587 5) Magneto-Optical drives and medium-changers are also recognized, now.
588 Therefore, we have a completely gapfree recognition of all SCSI-
589 device-types, that are known by Linux up to kernel 2.1.31.
591 the configuration, each connected SCSI-device will get a reset command
592 during boottime. This can be necessary for some special SCSI-devices.
596 - Michael Lang
600 - Michael Lang
603 - chrisb@truespectra.com
604 - made the front panel display thingy optional, specified from the
605 command-line via ibmmcascsi=display. Along the lines of the /LED
607 - fixed small bug in the LED display that would hang some machines.
608 - reversed ordering of the drives (using the
611 - users who've already installed Linux won't be screwed. Keep
613 - be consistent with the BIOS ordering of the drives. In the
617 This whole problem arises because IBM is actually non-standard with
622 - Since this is technically a branch of my own, I changed the
623 version number to 3.0e-cpb.
627 2) Taking care of the SCSI-assignment problem, dealed by Chris at Dec 15
628 1997. In fact, IBM is right, concerning the assignment of SCSI-devices
629 to driveletters. It is conform to the ANSI-definition of the SCSI-
630 standard to assign drive C: to SCSI-id 6, because it is the highest
632 default everywhere id 7). Also realtime-operating systems that I use,
633 like LynxOS and OS9, which are quite industrial systems use top-down
637 the IBM- and ANSI-SCSI-standard and keeps this driver downward
640 SCSI-BIOS do so. Therefore, I moved the IBMMCA_SCSI_ORDER_STANDARD
649 5) Added more in-source-comments and extended the driver description by
650 some explanation about the SCSI-device-assignment problem.
651 - Michael Lang
656 IBMMCA_SCSI_DEV_RESET -> CONFIG_IBMMCA_SCSI_DEV_RESET
657 IBMMCA_SCSI_ORDER_STANDARD -> CONFIG_IBMMCA_SCSI_ORDER_STANDARD
658 - Michael Lang
660 Jan 18, 1999: (v3.1 MCA-team internal)
666 2) The SCSI-subsystem detection was not complete and quite hugely buggy up
670 The pos-registers of integrated SCSI-subsystems do not contain any
671 information concerning the IO-port offset, really. Instead, they contain
672 some info about the adapter, the chip, the NVRAM .... The I/O-port is
673 fixed to 0x3540 - 0x3547. There can be more than one adapters in the
675 I/O-address area. See chapter 2 for detailed description. At least, the
681 of reserved bits - hopefully no trouble here anymore.
684 not like sending commands to non-existing SCSI-devices and will react
690 how often the command errors have been forgiven to the SCSI-subsystem.
696 pass the right name of the SCSI-adapter to Linux.
697 - Michael Lang
700 1) Finally, after some 3.1Beta-releases, the 3.1 release. Sorry, for
703 - Michael Lang
707 every integrated subsystem SCSI-command consequently in case of
713 decisive hint to move the code-part out and declare it global. Now
716 3) By the way, only Sony DAT-drives seem to show density code 0x13. A
717 test with a HP drive gave right results, so the problem is vendor-
719 - Michael Lang
727 is now declared as global variable, even the return-buffer in the
731 avoid memory-pointers for the areas higher than 16MByte in order to
732 be sure, it also works on 16-Bit Microchannel bus systems.
735 - Michael Lang
739 checked the cmd->result return value to the done-function very carefully.
743 cmd->result won't screw up Linux higher level drivers.
744 2) The reset-function has slightly improved. This is still planned for
746 allowed. This is however quite hard to cope with, so the INT-status
751 worse for Linux :-(, so tests will continue.
758 5) Taken into account ZP Gus' proposals to reverse the SCSI-device
762 - Michael Lang
766 various people, trying really quite different things on their SCSI-
769 - Driver crashes during boottime by no obvious reason.
770 - Driver panics while the midlevel-SCSI-driver is trying to inquire
771 the SCSI-device properties, even though hardware is in perfect state.
772 - Displayed info for the various slot-cards is interpreted wrong.
777 1024 bytes of space for the answer, but the IBM-SCSI-adapters do
778 not accept this, as they stick quite near to ANSI-SCSI and report
785 2) On unsuccessful TEST_UNIT_READY, the mid-level driver has to send
787 REQUEST_SENSE may have various length in its answer-buffer. IBM
788 SCSI-subsystems report a command failure if the returned buffersize
791 2) Code adaption to all kernel-releases. Now, the 3.2 code compiles on
792 2.0.x, 2.1.x, 2.2.x and 2.3.x kernel releases without any code-changes.
793 3) Commandline-parameters are recognized again, even under Kernel 2.3.x or
795 - Michael Lang
799 This increases SCSI-performance.
801 SCSI and 10 MHz on internal F/W SCSI-adapter.
804 - Michael Lang
808 flashing in addition to the LED-alphanumeric display-panel on
811 2) Added the READ_CONTROL bit for test_unit_ready SCSI-command.
818 contribution to all kernel-parts by Philipp Hahn.
819 - Michael Lang
824 1) SCSI-2 F/W support crashed with a COMMAND ERROR. The reason for this
825 was that it is possible to disable Fast-SCSI for the external bus.
826 The feature-control command, where this crash appeared regularly, tried
828 reports a COMMAND ERROR if external bus Fast-SCSI is disabled. Now,
829 the feature-command probes down from maximum speed until the adapter
832 5 MHz (slow-) or 10 MHz (fast-SCSI). During feature probing, the
835 SCSI-devices, attached to the F/W-controller. If dual bus is selected,
836 only the internal SCSI-devices get accessed by Linux. For most
838 3) Wide-SCSI-addressing (16-Bit) is now possible for the internal F/W
840 automatically uses the extended PUN/LUN <-> LDN mapping tables, which
846 the integrated SCSI-area are set to 0x00 or 0xff. Now, the mechanism
849 - Michael Lang
854 1) The adapter PUN for F/W adapters has 4-bits, while all other adapters
855 have 3-bits. This is now taken into account for F/W.
857 normally get the inverse probing order of your devices on the SCSI-bus.
859 and tested algorithm inverts the device-order on the SCSI-bus and
861 is set and works with SCSI- and Wide-SCSI-addressing.
862 - Michael Lang
865 1) LED panel display supports wide-addressing in ibmmca=display mode.
866 2) Adapter-information and autoadaption to address-space is done.
867 3) Auto-probing for maximum synchronous SCSI transfer rate is working.
869 5) Added some comment for the user to wait for SCSI-devices being probed.
871 - Michael Lang
879 that the kernel was compiled for i386 and the 9595 has a 486DX-2.
889 harddrive activity LED, existent on all PS/2, except models 8595-XXX.
891 fine together with the linuxinfo utility for the LED-panel.
892 - Michael Lang
895 1) Submission of this driver for kernel 2.4test-XX and 2.2.17.
896 - Michael Lang
915 based on non-command related reasons up to now, so bypassing commands
930 - Michael Lang
933 1) A lot of complains after the 2.4.0-prerelease kernel came in about
941 in internal SCSI-command handlers.
942 - Michael Lang
945 -------
946 - IBM SCSI-2 F/W external SCSI bus support in separate mode!
947 - It seems that the handling of bad disks is really bad -
948 non-existent, in fact. However, a low-level driver cannot help
952 ---------------
954 --------------------------
955 There exist several features for the IBM SCSI-subsystem driver.
966 ------DA
968 where '-' stays dark, 'D' shows the SCSI-device id
974 on the LED-panel, where the * represents a rotator,
976 driver which can take up to two minutes per SCSI-adapter.
978 of the activities on the SCSI-bus. The display will have
984 when the SCSI-device is accessed. 'A' shows again the SCSI
986 PS/2 harddisk LED is used for media-activities. So, if
987 you really do not have a system with a LED-display, you
991 wide-addressed devices e.g. at the SCSI-2 F/W adapter in
993 other tasks in parallel, like the linuxinfo-utility makes
1002 alphanumeric LED display if you want to monitor SCSI-
1010 SCSI-subsystems' integrated SCSI-command set. Except of
1012 every IBM SCSI-subsystem to set its ldns right. Instead,
1013 the ordinary ANSI-SCSI-commands are used and passed by the
1014 controller to the SCSI-devices, therefore 'bypass'. The
1017 could maybe solve troubles with old or integrated SCSI-
1019 this flag will slow-down SCSI-accesses slightly, as the
1021 hardware. Non-harddisk devices always get read/write-
1023 the Linux IBM-SCSI-driver, the bypass command should be
1025 SCSI-hardware!
1027 rail by ZP Gu. This parameter defines the SCSI-device
1029 the first SCSI-device is the one with the lowest pun.
1033 ansi The ANSI-standard for the right scan order, as done by
1034 IBM, Microware and Microsoft, scans SCSI-devices starting
1037 like to have the same SCSI-device order, as in DOS, OS-9
1039 fast SCSI-I/O in synchronous mode is done at 5 MHz for IBM-
1040 SCSI-devices. SCSI-2 Fast/Wide Adapter/A external bus
1041 should then run at 10 MHz if Fast-SCSI is enabled,
1042 and at 5 MHz if Fast-SCSI is disabled on the external
1046 2.5 MHz for IBM SCSI-adapters and 5.0 MHz for F/W ext.
1047 SCSI-bus (when Fast-SCSI speed enabled on external bus).
1049 This means 1.82 MHz for IBM SCSI-adapters and 2.0 MHz
1050 for F/W external bus at Fast-SCSI speed on the external
1053 A further option is that you can force the SCSI-driver to accept a SCSI-
1054 subsystem at a certain I/O-address with a predefined adapter PUN. This
1057 commandN = I/O-base
1060 e.g. ibmmcascsi=0x3540,7 will force the driver to detect a SCSI-subsystem
1061 at I/O-address 0x3540 with adapter PUN 7. Please only use this method, if
1062 the driver does really not recognize your SCSI-adapter! With driver version
1066 different types of IBM SCSI-adapters should be recognized correctly, too.
1079 and will force the driver to accept a SCSI-subsystem at I/O-base 0x3558
1083 -------------------
1087 Q: "Reset SCSI-devices at boottime" halts the system at boottime, why?
1092 kernel configuration, as all post 1989 SCSI-devices should accept
1093 the reset-signal, when the computer is switched on. The SCSI-
1095 is really reserved for users with very old, very strange or self-made
1096 SCSI-devices.
1097 Q: Why is the SCSI-order of my drives mirrored to the device-order
1099 A: It depends on the operating system, if it looks at the devices in
1100 ANSI-SCSI-standard (starting from pun 6 and going down to pun 0) or
1110 A: See the file MAINTAINERS for the current WWW-address, which offers
1112 was: http://www.staff.uni-mainz.de/mlang/linux.html
1113 Q: My SCSI-adapter is not recognized by the driver, what can I do?
1115 If this really happens, do also send e-mail to the maintainer, as
1119 Q: The driver screws up, if it starts to probe SCSI-devices, is there
1121 A: Yes, that was some recognition problem of the correct SCSI-adapter
1139 A: Sorry, the bad-block handling is still a feeble point of this driver,
1141 Q: Linux panics while dynamically assigning SCSI-ids or ldns.
1142 A: If you disconnect a SCSI-device from the machine, while Linux is up
1146 Q: The system does not recover after an abort-command has been generated.
1148 SCSI-adapter does really NOT generate any interrupt at the end of
1149 the abort-command. As no interrupt is generated, the abort command
1154 Q: The system gets in bad shape after a SCSI-reset, is this known?
1157 the reset functions with all other low level SCSI-drivers.
1160 Q: Why does my XXX w/Cache adapter not use read-prefetch?
1164 some major overhead of SCSI-commands that risks the performance to
1166 Q: I have a IBM SCSI-2 Fast/Wide adapter, it boots in some way and hangs.
1167 A: Yes, that is understood, as for sure, your SCSI-2 Fast/Wide adapter
1168 was in such a case recognized as integrated SCSI-adapter or something
1169 else, but not as the correct adapter. As the I/O-ports get assigned
1171 should upgrade to the latest release of the SCSI-driver. The
1173 a stable and reliable condition. Wide-addressing is in addition
1176 A: The reason for this is that the IBM SCSI-subsystem only sends a
1180 Q: I have a F/W adapter and the driver sees my internal SCSI-devices,
1182 A: Select combined busmode in the IBM config-program and check for that
1183 no SCSI-id on the external devices appears on internal devices.
1186 SCSI-ids. If combined bus-mode is activated, on some adapters,
1187 the wide-addressing is not possible, so devices with ids between 8
1192 A: Check the processor type of your 9595. If you have an 80486 or 486DX-2
1217 --------------
1220 best for this is to follow the instructions on the WWW-page for this
1221 driver. Fill out the bug-report form, placed on the WWW-page and ship it,
1224 Zubkoff, as Linus is buried in E-Mail and Leonard is supervising all
1225 SCSI-drivers and won't have the time left to look inside every single
1228 quite buried in E-mail (as me, sometimes, too) and one should first check
1231 a look inside some Linux-distribution showed me quite often some modified
1237 When you get a SCSI-error message that panics your system, a list of
1238 register-entries of the SCSI-subsystem is shown (from Version 3.1d). With
1244 Use the bug-report form (see 5.4 for its address) to send all the bug-
1245 stuff to the maintainer or write e-mail with the values from the table.
1247 5.4 Support WWW-page
1248 --------------------
1249 The address of the IBM SCSI-subsystem supporting WWW-page is:
1251 http://www.staff.uni-mainz.de/mlang/linux.html
1255 WWW-page regularly for latest hints. If ever this URL changes, please
1259 WWW-page. Read the dedicated instructions and write as much as you
1261 some e-mail directly, but at least with the same information as required by
1265 screen-shots, please feel free to send it directly to the address
1268 Michael Lang <langa2@kph.uni-mainz.de>
1271 ------------
1274 (available in the U.S. for $21.75 at 1-800-IBM-PCTB or in Germany for
1275 around 40,-DM at "Hallo IBM").
1283 IBM Corp., "SCSI-2 Fast/Wide Adapter/A Technical Reference - Dual Bus",
1286 Friedhelm Schmidt, "SCSI-Bus und IDE-Schnittstelle - Moderne Peripherie-
1291 Hill - North Carolina, 1995
1297 Programme * Begriffe, IWT-Verlag GmbH - Muenchen, 1988
1300 ------------
1302 ----------
1305 SCSI-driver in order to get it running for some old machine
1308 who wrote the first release of the IBM SCSI-subsystem driver.
1310 who for a long time maintained MCA-Linux and the SCSI-driver
1315 it running with multiple SCSI-adapters.
1317 for his excellent maintenance of the MCA-stuff and the quite
1319 patience ;-)).
1321 for his bug reports and his bold activities in cross-checking
1322 the driver-code with his teststand.
1325 -------------------------
1327 IBM-Deutschland GmbH
1328 the service of IBM-Deutschland for customers. Their E-Mail
1331 Karl-Otto Reimers,
1332 IBM Klub - Sparte IBM Geschichte, Sindelfingen
1334 IBM-Deutschland archives.
1342 for support by shipping me an IBM SCSI-2 Fast/Wide manual.
1351 second-hand computer market. In addition, I would like
1352 to thank him for his exhaustive SCSI-driver testing on his
1359 for his support by memory and an IBM SCSI-adapter. Collecting
1366 drive working and how to connect it to an IBM-diskette port.
1367 Johannes Gutenberg-Universitaet, Mainz &
1372 me to answer all your e-mail.
1375 ------------
1379 MS-DOS is a registered trademark of Microsoft Corporation
1381 Microware, OS-9 are registered trademarks of Microware Systems
1384 ------------
1386 concerning the Linux-kernel in special, this SCSI-driver comes without any
1393 injuries by hardware defects, that could be caused by this SCSI-driver are
1400 ------
1402 (langa2@kph.uni-mainz.de)