1 =================================== 1 ===================================
2 Linux and parallel port IDE devices 2 Linux and parallel port IDE devices
3 =================================== 3 ===================================
4 4
5 PARIDE v1.03 (c) 1997-8 Grant Guenther <gran 5 PARIDE v1.03 (c) 1997-8 Grant Guenther <grant@torque.net>
6 PATA_PARPORT (c) 2023 Ondrej Zary <<
7 6
8 1. Introduction 7 1. Introduction
9 =============== 8 ===============
10 9
11 Owing to the simplicity and near universality 10 Owing to the simplicity and near universality of the parallel port interface
12 to personal computers, many external devices s 11 to personal computers, many external devices such as portable hard-disk,
13 CD-ROM, LS-120 and tape drives use the paralle 12 CD-ROM, LS-120 and tape drives use the parallel port to connect to their
14 host computer. While some devices (notably sc 13 host computer. While some devices (notably scanners) use ad-hoc methods
15 to pass commands and data through the parallel 14 to pass commands and data through the parallel port interface, most
16 external devices are actually identical to an 15 external devices are actually identical to an internal model, but with
17 a parallel-port adapter chip added in. Some o 16 a parallel-port adapter chip added in. Some of the original parallel port
18 adapters were little more than mechanisms for 17 adapters were little more than mechanisms for multiplexing a SCSI bus.
19 (The Iomega PPA-3 adapter used in the ZIP driv 18 (The Iomega PPA-3 adapter used in the ZIP drives is an example of this
20 approach). Most current designs, however, tak 19 approach). Most current designs, however, take a different approach.
21 The adapter chip reproduces a small ISA or IDE 20 The adapter chip reproduces a small ISA or IDE bus in the external device
22 and the communication protocol provides operat 21 and the communication protocol provides operations for reading and writing
23 device registers, as well as data block transf 22 device registers, as well as data block transfer functions. Sometimes,
24 the device being addressed via the parallel ca 23 the device being addressed via the parallel cable is a standard SCSI
25 controller like an NCR 5380. The "ditto" fami 24 controller like an NCR 5380. The "ditto" family of external tape
26 drives use the ISA replicator to interface a f 25 drives use the ISA replicator to interface a floppy disk controller,
27 which is then connected to a floppy-tape mecha 26 which is then connected to a floppy-tape mechanism. The vast majority
28 of external parallel port devices, however, ar 27 of external parallel port devices, however, are now based on standard
29 IDE type devices, which require no intermediat 28 IDE type devices, which require no intermediate controller. If one
30 were to open up a parallel port CD-ROM drive, 29 were to open up a parallel port CD-ROM drive, for instance, one would
31 find a standard ATAPI CD-ROM drive, a power su 30 find a standard ATAPI CD-ROM drive, a power supply, and a single adapter
32 that interconnected a standard PC parallel por 31 that interconnected a standard PC parallel port cable and a standard
33 IDE cable. It is usually possible to exchange 32 IDE cable. It is usually possible to exchange the CD-ROM device with
34 any other device using the IDE interface. 33 any other device using the IDE interface.
35 34
36 The document describes the support in Linux fo 35 The document describes the support in Linux for parallel port IDE
37 devices. It does not cover parallel port SCSI 36 devices. It does not cover parallel port SCSI devices, "ditto" tape
38 drives or scanners. Many different devices ar 37 drives or scanners. Many different devices are supported by the
39 parallel port IDE subsystem, including: 38 parallel port IDE subsystem, including:
40 39
41 - MicroSolutions backpack CD-ROM 40 - MicroSolutions backpack CD-ROM
42 - MicroSolutions backpack PD/CD 41 - MicroSolutions backpack PD/CD
43 - MicroSolutions backpack hard-drives 42 - MicroSolutions backpack hard-drives
44 - MicroSolutions backpack 8000t tape d 43 - MicroSolutions backpack 8000t tape drive
45 - SyQuest EZ-135, EZ-230 & SparQ drive 44 - SyQuest EZ-135, EZ-230 & SparQ drives
46 - Avatar Shark 45 - Avatar Shark
47 - Imation Superdisk LS-120 46 - Imation Superdisk LS-120
48 - Maxell Superdisk LS-120 47 - Maxell Superdisk LS-120
49 - FreeCom Power CD 48 - FreeCom Power CD
50 - Hewlett-Packard 5GB and 8GB tape dri 49 - Hewlett-Packard 5GB and 8GB tape drives
51 - Hewlett-Packard 7100 and 7200 CD-RW 50 - Hewlett-Packard 7100 and 7200 CD-RW drives
52 51
53 as well as most of the clone and no-name produ 52 as well as most of the clone and no-name products on the market.
54 53
55 To support such a wide range of devices, pata_ !! 54 To support such a wide range of devices, PARIDE, the parallel port IDE
56 in two parts. There is a base pata_parport mod !! 55 subsystem, is actually structured in three parts. There is a base
57 to kernel libata subsystem, registry and some !! 56 paride module which provides a registry and some common methods for
58 the parallel ports. !! 57 accessing the parallel ports. The second component is a set of
59 !! 58 high-level drivers for each of the different types of supported devices:
60 The second component is a set of low-level pro !! 59
61 parallel port IDE adapter chips. Thanks to th !! 60 === =============
62 Linux users from many parts of the world, supp !! 61 pd IDE disk
63 known adapter protocols: !! 62 pcd ATAPI CD-ROM
>> 63 pf ATAPI disk
>> 64 pt ATAPI tape
>> 65 pg ATAPI generic
>> 66 === =============
>> 67
>> 68 (Currently, the pg driver is only used with CD-R drives).
>> 69
>> 70 The high-level drivers function according to the relevant standards.
>> 71 The third component of PARIDE is a set of low-level protocol drivers
>> 72 for each of the parallel port IDE adapter chips. Thanks to the interest
>> 73 and encouragement of Linux users from many parts of the world,
>> 74 support is available for almost all known adapter protocols:
64 75
65 ==== ============================== 76 ==== ====================================== ====
66 aten ATEN EH-100 77 aten ATEN EH-100 (HK)
67 bpck Microsolutions backpack 78 bpck Microsolutions backpack (US)
68 comm DataStor (old-type) "commuter" 79 comm DataStor (old-type) "commuter" adapter (TW)
69 dstr DataStor EP-2000 80 dstr DataStor EP-2000 (TW)
70 epat Shuttle EPAT 81 epat Shuttle EPAT (UK)
71 epia Shuttle EPIA 82 epia Shuttle EPIA (UK)
72 fit2 FIT TD-2000 83 fit2 FIT TD-2000 (US)
73 fit3 FIT TD-3000 84 fit3 FIT TD-3000 (US)
74 friq Freecom IQ cable 85 friq Freecom IQ cable (DE)
75 frpw Freecom Power 86 frpw Freecom Power (DE)
76 kbic KingByte KBIC-951A and KBIC-97 87 kbic KingByte KBIC-951A and KBIC-971A (TW)
77 ktti KT Technology PHd adapter 88 ktti KT Technology PHd adapter (SG)
78 on20 OnSpec 90c20 89 on20 OnSpec 90c20 (US)
79 on26 OnSpec 90c26 90 on26 OnSpec 90c26 (US)
80 ==== ============================== 91 ==== ====================================== ====
81 92
82 93
83 2. Using pata_parport subsystem !! 94 2. Using the PARIDE subsystem
84 =============================== !! 95 =============================
85 96
86 While configuring the Linux kernel, you may ch 97 While configuring the Linux kernel, you may choose either to build
87 the pata_parport drivers into your kernel, or !! 98 the PARIDE drivers into your kernel, or to build them as modules.
88 99
89 In either case, you will need to select "Paral 100 In either case, you will need to select "Parallel port IDE device support"
90 and at least one of the parallel port communic !! 101 as well as at least one of the high-level drivers and at least one
91 If you do not know what kind of parallel port !! 102 of the parallel port communication protocols. If you do not know
92 you could begin by checking the file names and !! 103 what kind of parallel port adapter is used in your drive, you could
>> 104 begin by checking the file names and any text files on your DOS
93 installation floppy. Alternatively, you can l 105 installation floppy. Alternatively, you can look at the markings on
94 the adapter chip itself. That's usually suffi 106 the adapter chip itself. That's usually sufficient to identify the
95 correct device. 107 correct device.
96 108
97 You can actually select all the protocol modul !! 109 You can actually select all the protocol modules, and allow the PARIDE
98 subsystem to try them all for you. 110 subsystem to try them all for you.
99 111
100 For the "brand-name" products listed above, he 112 For the "brand-name" products listed above, here are the protocol
101 and high-level drivers that you would use: 113 and high-level drivers that you would use:
102 114
103 ================ ============ !! 115 ================ ============ ====== ========
104 Manufacturer Model !! 116 Manufacturer Model Driver Protocol
105 ================ ============ !! 117 ================ ============ ====== ========
106 MicroSolutions CD-ROM !! 118 MicroSolutions CD-ROM pcd bpck
107 MicroSolutions PD drive !! 119 MicroSolutions PD drive pf bpck
108 MicroSolutions hard-drive !! 120 MicroSolutions hard-drive pd bpck
109 MicroSolutions 8000t tape !! 121 MicroSolutions 8000t tape pt bpck
110 SyQuest EZ, SparQ !! 122 SyQuest EZ, SparQ pd epat
111 Imation Superdisk !! 123 Imation Superdisk pf epat
112 Maxell Superdisk !! 124 Maxell Superdisk pf friq
113 Avatar Shark !! 125 Avatar Shark pd epat
114 FreeCom CD-ROM !! 126 FreeCom CD-ROM pcd frpw
115 Hewlett-Packard 5GB Tape !! 127 Hewlett-Packard 5GB Tape pt epat
116 Hewlett-Packard 7200e (CD) !! 128 Hewlett-Packard 7200e (CD) pcd epat
117 Hewlett-Packard 7200e (CD-R) !! 129 Hewlett-Packard 7200e (CD-R) pg epat
118 ================ ============ !! 130 ================ ============ ====== ========
119 !! 131
120 All parports and all protocol drivers are prob !! 132 2.1 Configuring built-in drivers
121 parameter is used. So just "modprobe epat" is !! 133 ---------------------------------
122 drive to work. !! 134
123 !! 135 We recommend that you get to know how the drivers work and how to
124 Manual device creation:: !! 136 configure them as loadable modules, before attempting to compile a
125 !! 137 kernel with the drivers built-in.
126 # echo "port protocol mode unit delay" !! 138
127 !! 139 If you built all of your PARIDE support directly into your kernel,
128 where: !! 140 and you have just a single parallel port IDE device, your kernel should
129 !! 141 locate it automatically for you. If you have more than one device,
130 ======== ============================= !! 142 you may need to give some command line options to your bootloader
131 port parport name (or "auto" for a !! 143 (eg: LILO), how to do that is beyond the scope of this document.
132 protocol protocol name (or "auto" for !! 144
133 mode mode number (protocol-specifi !! 145 The high-level drivers accept a number of command line parameters, all
134 unit unit number (for backpack onl !! 146 of which are documented in the source files in linux/drivers/block/paride.
135 delay I/O delay (see troubleshootin !! 147 By default, each driver will automatically try all parallel ports it
136 ======== ============================= !! 148 can find, and all protocol types that have been installed, until it finds
>> 149 a parallel port IDE adapter. Once it finds one, the probe stops. So,
>> 150 if you have more than one device, you will need to tell the drivers
>> 151 how to identify them. This requires specifying the port address, the
>> 152 protocol identification number and, for some devices, the drive's
>> 153 chain ID. While your system is booting, a number of messages are
>> 154 displayed on the console. Like all such messages, they can be
>> 155 reviewed with the 'dmesg' command. Among those messages will be
>> 156 some lines like::
>> 157
>> 158 paride: bpck registered as protocol 0
>> 159 paride: epat registered as protocol 1
>> 160
>> 161 The numbers will always be the same until you build a new kernel with
>> 162 different protocol selections. You should note these numbers as you
>> 163 will need them to identify the devices.
137 164
138 If you happen to be using a MicroSolutions bac 165 If you happen to be using a MicroSolutions backpack device, you will
139 also need to know the unit ID number for each 166 also need to know the unit ID number for each drive. This is usually
140 the last two digits of the drive's serial numb 167 the last two digits of the drive's serial number (but read MicroSolutions'
141 documentation about this). 168 documentation about this).
142 169
143 If you omit the parameters from the end, defau !! 170 As an example, let's assume that you have a MicroSolutions PD/CD drive
144 !! 171 with unit ID number 36 connected to the parallel port at 0x378, a SyQuest
145 Probe all parports with all protocols:: !! 172 EZ-135 connected to the chained port on the PD/CD drive and also an
146 !! 173 Imation Superdisk connected to port 0x278. You could give the following
147 # echo auto >/sys/bus/pata_parport/new !! 174 options on your boot command::
148 !! 175
149 Probe parport0 using protocol epat and mode 4 !! 176 pd.drive0=0x378,1 pf.drive0=0x278,1 pf.drive1=0x378,0,36
150 !! 177
151 # echo "parport0 epat 4" >/sys/bus/pat !! 178 In the last option, pf.drive1 configures device /dev/pf1, the 0x378
152 !! 179 is the parallel port base address, the 0 is the protocol registration
153 Probe parport0 using all protocols:: !! 180 number and 36 is the chain ID.
154 !! 181
155 # echo "parport0 auto" >/sys/bus/pata_ !! 182 Please note: while PARIDE will work both with and without the
156 !! 183 PARPORT parallel port sharing system that is included by the
157 Probe all parports using protoocol epat:: !! 184 "Parallel port support" option, PARPORT must be included and enabled
158 !! 185 if you want to use chains of devices on the same parallel port.
159 # echo "auto epat" >/sys/bus/pata_parp !! 186
160 !! 187 2.2 Loading and configuring PARIDE as modules
161 Deleting devices:: !! 188 ----------------------------------------------
162 !! 189
163 # echo pata_parport.0 >/sys/bus/pata_p !! 190 It is much faster and simpler to get to understand the PARIDE drivers
>> 191 if you use them as loadable kernel modules.
>> 192
>> 193 Note 1:
>> 194 using these drivers with the "kerneld" automatic module loading
>> 195 system is not recommended for beginners, and is not documented here.
>> 196
>> 197 Note 2:
>> 198 if you build PARPORT support as a loadable module, PARIDE must
>> 199 also be built as loadable modules, and PARPORT must be loaded before
>> 200 the PARIDE modules.
>> 201
>> 202 To use PARIDE, you must begin by::
>> 203
>> 204 insmod paride
>> 205
>> 206 this loads a base module which provides a registry for the protocols,
>> 207 among other tasks.
>> 208
>> 209 Then, load as many of the protocol modules as you think you might need.
>> 210 As you load each module, it will register the protocols that it supports,
>> 211 and print a log message to your kernel log file and your console. For
>> 212 example::
>> 213
>> 214 # insmod epat
>> 215 paride: epat registered as protocol 0
>> 216 # insmod kbic
>> 217 paride: k951 registered as protocol 1
>> 218 paride: k971 registered as protocol 2
>> 219
>> 220 Finally, you can load high-level drivers for each kind of device that
>> 221 you have connected. By default, each driver will autoprobe for a single
>> 222 device, but you can support up to four similar devices by giving their
>> 223 individual co-ordinates when you load the driver.
>> 224
>> 225 For example, if you had two no-name CD-ROM drives both using the
>> 226 KingByte KBIC-951A adapter, one on port 0x378 and the other on 0x3bc
>> 227 you could give the following command::
>> 228
>> 229 # insmod pcd drive0=0x378,1 drive1=0x3bc,1
>> 230
>> 231 For most adapters, giving a port address and protocol number is sufficient,
>> 232 but check the source files in linux/drivers/block/paride for more
>> 233 information. (Hopefully someone will write some man pages one day !).
>> 234
>> 235 As another example, here's what happens when PARPORT is installed, and
>> 236 a SyQuest EZ-135 is attached to port 0x378::
>> 237
>> 238 # insmod paride
>> 239 paride: version 1.0 installed
>> 240 # insmod epat
>> 241 paride: epat registered as protocol 0
>> 242 # insmod pd
>> 243 pd: pd version 1.0, major 45, cluster 64, nice 0
>> 244 pda: Sharing parport1 at 0x378
>> 245 pda: epat 1.0, Shuttle EPAT chip c3 at 0x378, mode 5 (EPP-32), delay 1
>> 246 pda: SyQuest EZ135A, 262144 blocks [128M], (512/16/32), removable media
>> 247 pda: pda1
>> 248
>> 249 Note that the last line is the output from the generic partition table
>> 250 scanner - in this case it reports that it has found a disk with one partition.
>> 251
>> 252 2.3 Using a PARIDE device
>> 253 --------------------------
>> 254
>> 255 Once the drivers have been loaded, you can access PARIDE devices in the
>> 256 same way as their traditional counterparts. You will probably need to
>> 257 create the device "special files". Here is a simple script that you can
>> 258 cut to a file and execute::
>> 259
>> 260 #!/bin/bash
>> 261 #
>> 262 # mkd -- a script to create the device special files for the PARIDE subsystem
>> 263 #
>> 264 function mkdev {
>> 265 mknod $1 $2 $3 $4 ; chmod 0660 $1 ; chown root:disk $1
>> 266 }
>> 267 #
>> 268 function pd {
>> 269 D=$( printf \\$( printf "x%03x" $[ $1 + 97 ] ) )
>> 270 mkdev pd$D b 45 $[ $1 * 16 ]
>> 271 for P in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
>> 272 do mkdev pd$D$P b 45 $[ $1 * 16 + $P ]
>> 273 done
>> 274 }
>> 275 #
>> 276 cd /dev
>> 277 #
>> 278 for u in 0 1 2 3 ; do pd $u ; done
>> 279 for u in 0 1 2 3 ; do mkdev pcd$u b 46 $u ; done
>> 280 for u in 0 1 2 3 ; do mkdev pf$u b 47 $u ; done
>> 281 for u in 0 1 2 3 ; do mkdev pt$u c 96 $u ; done
>> 282 for u in 0 1 2 3 ; do mkdev npt$u c 96 $[ $u + 128 ] ; done
>> 283 for u in 0 1 2 3 ; do mkdev pg$u c 97 $u ; done
>> 284 #
>> 285 # end of mkd
>> 286
>> 287 With the device files and drivers in place, you can access PARIDE devices
>> 288 like any other Linux device. For example, to mount a CD-ROM in pcd0, use::
>> 289
>> 290 mount /dev/pcd0 /cdrom
>> 291
>> 292 If you have a fresh Avatar Shark cartridge, and the drive is pda, you
>> 293 might do something like::
>> 294
>> 295 fdisk /dev/pda -- make a new partition table with
>> 296 partition 1 of type 83
>> 297
>> 298 mke2fs /dev/pda1 -- to build the file system
>> 299
>> 300 mkdir /shark -- make a place to mount the disk
>> 301
>> 302 mount /dev/pda1 /shark
>> 303
>> 304 Devices like the Imation superdisk work in the same way, except that
>> 305 they do not have a partition table. For example to make a 120MB
>> 306 floppy that you could share with a DOS system::
>> 307
>> 308 mkdosfs /dev/pf0
>> 309 mount /dev/pf0 /mnt
>> 310
>> 311
>> 312 2.4 The pf driver
>> 313 ------------------
>> 314
>> 315 The pf driver is intended for use with parallel port ATAPI disk
>> 316 devices. The most common devices in this category are PD drives
>> 317 and LS-120 drives. Traditionally, media for these devices are not
>> 318 partitioned. Consequently, the pf driver does not support partitioned
>> 319 media. This may be changed in a future version of the driver.
>> 320
>> 321 2.5 Using the pt driver
>> 322 ------------------------
>> 323
>> 324 The pt driver for parallel port ATAPI tape drives is a minimal driver.
>> 325 It does not yet support many of the standard tape ioctl operations.
>> 326 For best performance, a block size of 32KB should be used. You will
>> 327 probably want to set the parallel port delay to 0, if you can.
>> 328
>> 329 2.6 Using the pg driver
>> 330 ------------------------
>> 331
>> 332 The pg driver can be used in conjunction with the cdrecord program
>> 333 to create CD-ROMs. Please get cdrecord version 1.6.1 or later
>> 334 from ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . To record CD-R media
>> 335 your parallel port should ideally be set to EPP mode, and the "port delay"
>> 336 should be set to 0. With those settings it is possible to record at 2x
>> 337 speed without any buffer underruns. If you cannot get the driver to work
>> 338 in EPP mode, try to use "bidirectional" or "PS/2" mode and 1x speeds only.
164 339
165 340
166 3. Troubleshooting 341 3. Troubleshooting
167 ================== 342 ==================
168 343
169 3.1 Use EPP mode if you can 344 3.1 Use EPP mode if you can
170 ---------------------------- 345 ----------------------------
171 346
172 The most common problems that people report wi !! 347 The most common problems that people report with the PARIDE drivers
173 concern the parallel port CMOS settings. At t 348 concern the parallel port CMOS settings. At this time, none of the
174 protocol modules support ECP mode, or any ECP !! 349 PARIDE protocol modules support ECP mode, or any ECP combination modes.
175 If you are able to do so, please set your para 350 If you are able to do so, please set your parallel port into EPP mode
176 using your CMOS setup procedure. 351 using your CMOS setup procedure.
177 352
178 3.2 Check the port delay 353 3.2 Check the port delay
179 ------------------------- 354 -------------------------
180 355
181 Some parallel ports cannot reliably transfer d 356 Some parallel ports cannot reliably transfer data at full speed. To
182 offset the errors, the protocol modules introd !! 357 offset the errors, the PARIDE protocol modules introduce a "port
183 delay" between each access to the i/o ports. 358 delay" between each access to the i/o ports. Each protocol sets
184 a default value for this delay. In most cases 359 a default value for this delay. In most cases, the user can override
185 the default and set it to 0 - resulting in som 360 the default and set it to 0 - resulting in somewhat higher transfer
186 rates. In some rare cases (especially with ol 361 rates. In some rare cases (especially with older 486 systems) the
187 default delays are not long enough. if you ex 362 default delays are not long enough. if you experience corrupt data
188 transfers, or unexpected failures, you may wis 363 transfers, or unexpected failures, you may wish to increase the
189 port delay. !! 364 port delay. The delay can be programmed using the "driveN" parameters
>> 365 to each of the high-level drivers. Please see the notes above, or
>> 366 read the comments at the beginning of the driver source files in
>> 367 linux/drivers/block/paride.
190 368
191 3.3 Some drives need a printer reset 369 3.3 Some drives need a printer reset
192 ------------------------------------- 370 -------------------------------------
193 371
194 There appear to be a number of "noname" extern 372 There appear to be a number of "noname" external drives on the market
195 that do not always power up correctly. We hav 373 that do not always power up correctly. We have noticed this with some
196 drives based on OnSpec and older Freecom adapt 374 drives based on OnSpec and older Freecom adapters. In these rare cases,
197 the adapter can often be reinitialised by issu 375 the adapter can often be reinitialised by issuing a "printer reset" on
198 the parallel port. As the reset operation is 376 the parallel port. As the reset operation is potentially disruptive in
199 multiple device environments, the pata_parport !! 377 multiple device environments, the PARIDE drivers will not do it
200 automatically. You can however, force a print 378 automatically. You can however, force a printer reset by doing::
201 379
202 insmod lp reset=1 380 insmod lp reset=1
203 rmmod lp 381 rmmod lp
204 382
205 If you have one of these marginal cases, you s 383 If you have one of these marginal cases, you should probably build
206 your pata_parport drivers as modules, and arra !! 384 your paride drivers as modules, and arrange to do the printer reset
207 before loading the pata_parport drivers. !! 385 before loading the PARIDE drivers.
>> 386
>> 387 3.4 Use the verbose option and dmesg if you need help
>> 388 ------------------------------------------------------
>> 389
>> 390 While a lot of testing has gone into these drivers to make them work
>> 391 as smoothly as possible, problems will arise. If you do have problems,
>> 392 please check all the obvious things first: does the drive work in
>> 393 DOS with the manufacturer's drivers ? If that doesn't yield any useful
>> 394 clues, then please make sure that only one drive is hooked to your system,
>> 395 and that either (a) PARPORT is enabled or (b) no other device driver
>> 396 is using your parallel port (check in /proc/ioports). Then, load the
>> 397 appropriate drivers (you can load several protocol modules if you want)
>> 398 as in::
>> 399
>> 400 # insmod paride
>> 401 # insmod epat
>> 402 # insmod bpck
>> 403 # insmod kbic
>> 404 ...
>> 405 # insmod pd verbose=1
>> 406
>> 407 (using the correct driver for the type of device you have, of course).
>> 408 The verbose=1 parameter will cause the drivers to log a trace of their
>> 409 activity as they attempt to locate your drive.
>> 410
>> 411 Use 'dmesg' to capture a log of all the PARIDE messages (any messages
>> 412 beginning with paride:, a protocol module's name or a driver's name) and
>> 413 include that with your bug report. You can submit a bug report in one
>> 414 of two ways. Either send it directly to the author of the PARIDE suite,
>> 415 by e-mail to grant@torque.net, or join the linux-parport mailing list
>> 416 and post your report there.
>> 417
>> 418 3.5 For more information or help
>> 419 ---------------------------------
>> 420
>> 421 You can join the linux-parport mailing list by sending a mail message
>> 422 to:
>> 423
>> 424 linux-parport-request@torque.net
>> 425
>> 426 with the single word::
>> 427
>> 428 subscribe
>> 429
>> 430 in the body of the mail message (not in the subject line). Please be
>> 431 sure that your mail program is correctly set up when you do this, as
>> 432 the list manager is a robot that will subscribe you using the reply
>> 433 address in your mail headers. REMOVE any anti-spam gimmicks you may
>> 434 have in your mail headers, when sending mail to the list server.
>> 435
>> 436 You might also find some useful information on the linux-parport
>> 437 web pages (although they are not always up to date) at
>> 438
>> 439 http://web.archive.org/web/%2E/http://www.torque.net/parport/
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.