From c61a85bc64df51812d1de5839a20c4e5e4e0c7fa Mon Sep 17 00:00:00 2001 From: "Jordan K. Hubbard" Date: Sat, 25 Nov 1995 20:00:49 +0000 Subject: [PATCH] My reorganization of chapter 9. Reviewed by: jfieber --- handbook/esdi.sgml | 46 +++++++++--------- handbook/handbook.sgml | 11 +---- handbook/hw.sgml | 106 +++++++++++++++++++++++++++++++++++++---- handbook/scsi.sgml | 36 +++++++------- 4 files changed, 141 insertions(+), 58 deletions(-) diff --git a/handbook/esdi.sgml b/handbook/esdi.sgml index 5d79f44fd3..1705280aa8 100644 --- a/handbook/esdi.sgml +++ b/handbook/esdi.sgml @@ -1,4 +1,4 @@ - + - ESDI hard disks and FreeBSD + Using ESDI hard disks

Copyright © 1995, &a.wilko;.24 September 1995. @@ -46,9 +46,9 @@ the availability of free or cheap surplus drives makes them ideal for low (or now) budget systems. - Concepts of ESDI + Concepts of ESDI

- Physical connections + Physical connections

The ESDI interface uses two cables connected to each drive. One cable is a 34 pin flatcable edge connector that carries @@ -67,7 +67,7 @@ compatibility feature(?) left over from the WD1003 standard that reserves only a single bit for device addressing. - Device addressing + Device addressing

On each command cable a maximum of 7 devices and 1 controller can be present. To enable the controller to uniquely @@ -80,7 +80,7 @@ two drives/controller maximum the first drive is drive 0, the second is drive 1. - Termination + Termination

The daisy chained command cable (the 34 pin cable remember?) needs to be terminated at the last drive on the chain. @@ -95,7 +95,7 @@ Please note that this implies that the controller must be at one end of the cable and not in the middle. - Using ESDI disks with FreeBSD + Using ESDI disks with FreeBSD

Why is ESDI such a pain to get working in the first place? @@ -109,7 +109,7 @@ The following sections try to list all the pitfalls and solutions. - ESDI speed variants + ESDI speed variants

As briefly mentioned before, ESDI comes in two speed flavours. The older drives and controllers use a 10 Mbits/second @@ -120,7 +120,7 @@ As always, consult your controller and drive documentation to see if things match. - Stay on track + Stay on track

Mainstream ESDI drives use 34 to 36 sectors per track. Most (older) controllers cannot handle more than this @@ -139,7 +139,7 @@ or might not work. Give it a try or get another more capable controller. - Hard or soft sectoring + Hard or soft sectoring

Most ESDI drives allow hard or soft sectoring to be selected using a jumper. Hard sectoring means that the @@ -167,7 +167,7 @@ FreeBSD because you need to re-run the low-level format after each change. - Low level formatting + Low level formatting

ESDI drives need to be low level formatted before they are usable. A reformat is needed whenever you figgle @@ -191,7 +191,7 @@ and more importantly causes you grief with bad144 (see the section on bad144). - Translations + Translations

Translations, although not exclusively a ESDI-only problem, might give you real trouble. @@ -240,7 +240,7 @@ read the info and presented itself to the system based on the info from the disk. - Spare sectoring + Spare sectoring

Most ESDI controllers offer the possibility to remap bad sectors. During/after the low-level format of the disk bad sectors are @@ -265,7 +265,7 @@ whatever it may be called by the controller manufacturer when you want to use the disk for FreeBSD. - Bad block handling + Bad block handling

The preceding section leaves us with a problem. The controller's bad block handling is not usable and still FreeBSD's filesystems @@ -303,7 +303,7 @@ rather the entire slice that contains the root filesystem. - Kernel configuration + Kernel configuration

ESDI disks are handled by the same wddriver as IDE and ST412 MFM disks. The wd driver should work @@ -332,13 +332,13 @@ disk wd3 at wdc1 drive 1 - Particulars on ESDI hardware + Particulars on ESDI hardware

- Adaptec 2320 controllers + Adaptec 2320 controllers

I succesfully installed FreeBSD onto a ESDI disk controlled by a ACB-2320. No other operating system was present on the disk. @@ -370,7 +370,7 @@ disk wd3 at wdc1 drive 1 All variations should be capable of using 1:1 interleaving. Use 1:1, FreeBSD is fast enough to handle it. - Western Digital WD1007 controllers + Western Digital WD1007 controllers

I succesfully installed FreeBSD onto a ESDI disk controlled by a WD1007 controller. To be precise, it was a WD1007-WA2. Other @@ -382,7 +382,7 @@ disk wd3 at wdc1 drive 1 WDFMT.EXE from www.wdc.com Running this formatted my drive just fine. - Ultrastor U14F controllers + Ultrastor U14F controllers

According to multiple reports from the net, Ultrastor ESDI boards work OK with FreeBSD. I lack any further info on @@ -390,11 +390,11 @@ disk wd3 at wdc1 drive 1 - Further reading

If you intend to do some serious ESDI hacking, you might want to have the official standard at hand: @@ -414,7 +414,7 @@ disk wd3 at wdc1 drive 1 For info on Western Digital controllers see . - Thanks to... + Thanks to...

Andrew Gordon for sending me an Adaptec 2320 controller and ESDI disk for testing. diff --git a/handbook/handbook.sgml b/handbook/handbook.sgml index 2eabf37912..d8e63081da 100644 --- a/handbook/handbook.sgml +++ b/handbook/handbook.sgml @@ -1,4 +1,4 @@ - + . documentation supplied by the . - Managing hardware - * Adding and reconfiguring disks - &scsi; - &esdi; - * Tapes and backups - * Serial ports - * Sound cards + &hw; @@ -140,7 +134,6 @@ Web server">. &mirrors; &bibliography; &eresources; - &hw; Assorted technical topics &booting; &memoryuse; diff --git a/handbook/hw.sgml b/handbook/hw.sgml index 87f82c2f91..d4566a9994 100644 --- a/handbook/hw.sgml +++ b/handbook/hw.sgml @@ -1,4 +1,4 @@ - + + - SCSI + What is SCSI?

Copyright © 1995, &a.wilko;.3 September 1995. @@ -87,9 +87,9 @@ pre-SCSI-1 disk, a SCSI-2 QIC tape unit, a SCSI-1 helical scan tape unit and 2 SCSI-1 disks work together quite happily. - Components of SCSI + Components of SCSI

- As said before, SCSI devices are smart. The idea is to put the knowledge about intimate hardware details onto the SCSI device @@ -104,7 +104,7 @@ there is no longer a need to change (and qualify!) drivers for every odd new device that is introduced. - For cabling and connectors there is a golden rule: get good stuff. With bus speeds going up all the time you will save @@ -217,7 +217,7 @@ AH1740 as a single ended board, whereas the AH1744 was differential. The software interface to the host is identical for both. - Terminators + Terminators

Terminators in SCSI terminology are resistor networks that are used to get a correct impedance matching. Impedance matching @@ -278,7 +278,7 @@ for the internal flat cable connectors. This makes reconfiguration much easier. - Terminator power + Terminator power

The terminators discussed in the previous chapter need power to operate properly. On the SCSI bus, a line is dedicated to this @@ -318,7 +318,7 @@ configurable, using some sort of setup tool. Consult you documentation! - Device addressing + Device addressing

Because the SCSI bus is, ehh, a bus there must be a way to distinguish or address the different devices connected to it. @@ -350,7 +350,7 @@ tape changer. In this way, the host system can address each of the parts of the tape unit as desired. - Bus layout + Bus layout

SCSI buses are linear. So, not shaped like Y-junctions, star topologies, cobwebs or whatever else people might want to @@ -365,9 +365,9 @@ Stick to the linear bus rule! - Using SCSI with FreeBSD + Using SCSI with FreeBSD

- About translations, BIOSes and magic... + About translations, BIOSes and magic...

As stated before, you should first make sure that you have a electrically sound bus. @@ -458,7 +458,7 @@ about this disk, (e.g. it is not a booting disk) to supply a ficticious geometry that is convenient. - SCSI subsystem design + SCSI subsystem design

FreeBSD uses a layered SCSI subsystem. For each different controller card a device driver is written. This driver @@ -478,7 +478,7 @@ banging and more high level stuff. Adding support for another piece of hardware is a much more managable problem. - Kernel configuration + Kernel configuration

Dependent on your hardware, the kernel configuration file must contain one or more lines describing your host adapter(s). @@ -604,7 +604,7 @@ device cd0 #Only need one of these, the code dynamically grows &lsq subsystem. For more detailed info on host adapter drivers use eg man 4 aha for info on the Adaptec 154x driver. - Tuning your SCSI kernel setup + Tuning your SCSI kernel setup

Experience has shown that some devices are slow to respond to INQUIRY commands after a SCSI bus reset (which happens at Boot time). @@ -626,7 +626,7 @@ options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device with device recognition. If this helps, tune it back until it just stays working. - Rogue SCSI devices + Rogue SCSI devices

Although the SCSI standard tries to be complete and concise, it is a complex standard and implementing things correctly is no easy task. @@ -662,7 +662,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue to connect your bogus Mumbletech SCSI cdrom you might be the one that has to define which workaround is needed. - Busmaster host adapters + Busmaster host adapters

Most, but not all, SCSI host adapters are bus mastering controllers. This means that they can do I/O on their own without putting load onto @@ -693,7 +693,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Check the man pages for the host adapter that you use. Or better still, use the ultimate documentation (read: driver source). - Tracking down problems + Tracking down problems

The following list is an attempt to give a guideline for the most common SCSI problems and their solutions. It is by no means @@ -731,7 +731,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Also look at man 8 scsi. - Further reading + Further reading

If you intend to do some serious SCSI hacking, you might want to have the official standard at hand: