I recently purchased a 250MB parallel port zip drive. Unfortunately, it doesn't
seem to work when I set the parallel port to EPP mode. I get hundreds of SCSI
error messages when trying to access it. The drive works fine if the parallel
port is set to Normal or ECP, but it's pretty slow that way. I'd like to know if
my hardware is at fault or if I can do something in software. Relevant info
follows.
System is a generic PC, Intel 440VX chipset, P100, EDO RAM
jf@HAL:~$ uname -a
Linux HAL 2.2.16 #1 Sun Jul 9 13:03:03 EDT 2000 i586 unknown
This is a custom compiled kernel, 2.2.16 stock + Reiserfs 3.5.23
jf@HAL:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 250 Rev: K.47
Type: Direct-Access ANSI SCSI revision: 02
This is using either Normal or ECP modes:
jf@HAL:~$ cat /proc/scsi/imm/0
Version : 2.03 (for Linux 2.0.0)
Parport : parport0
Mode : PS/2
And here are some logs when set to EPP (EPP 1.7 and EPP 1.9 give the same
results)
HAL kernel: parport0: PC-style at 0x378, irq 7 [SPP,PS2,EPP]
HAL kernel: parport_probe: failed
HAL kernel: parport0: no IEEE-1284 device present.
HAL kernel: imm: Version 2.03 (for Linux 2.0.0)
HAL kernel: imm: Found device at ID 6, Attempting to use EPP 32 bit
HAL kernel: imm: Communication established with ID 6 using EPP 32 bit
HAL kernel: scsi0 : Iomega VPI2 (imm) interface
HAL kernel: scsi : 1 host.
HAL kernel: Vendor: IOMEGA Model: ZIP 250 Rev: K.47
HAL kernel: Type: Direct-Access ANSI SCSI revision: 02
--SNIP--
Jul 16 16:51:22 HAL kernel: parport0: PC-style at 0x378, irq 7 [SPP,PS2,EPP]
Jul 16 16:51:22 HAL kernel: parport_probe: failed
Jul 16 16:51:22 HAL kernel: parport0: no IEEE-1284 device present.
Jul 16 16:51:22 HAL kernel: imm: Version 2.03 (for Linux 2.0.0)
Jul 16 16:51:22 HAL kernel: imm: Found device at ID 6, Attempting to use EPP 32 bit
Jul 16 16:51:22 HAL kernel: imm: Communication established with ID 6 using EPP 32 bit
Jul 16 16:51:22 HAL kernel: scsi0 : Iomega VPI2 (imm) interface
Jul 16 16:51:22 HAL kernel: scsi : 1 host.
Jul 16 16:51:22 HAL kernel: Vendor: IOMEGA Model: ZIP 250 Rev: K.47
Jul 16 16:51:22 HAL kernel: Type: Direct-Access ANSI SCSI revision: 02
Jul 16 16:52:52 HAL kernel: Detected scsi removable disk sda at scsi0, channel 0, id 6, lun 0
Jul 16 16:52:53 HAL kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 489532 [239 MB] [0.2 GB]
Jul 16 16:52:53 HAL kernel: sda: Write Protect is off
Jul 16 16:52:54 HAL kernel: sda: sda4
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 225
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 226
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 464
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 465
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 479
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
Jul 16 16:53:29 HAL kernel: scsidisk I/O error: dev 08:04, sector 461175
Jul 16 16:53:29 HAL kernel: SCSI disk error : host 0 channel 0 id 6 lun 0 return code = 27010000
And so on. Any suggestions?
Thanks for any help,
Jean-Francois Landry
-- "MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development." --- dmeggins@aix1.uottawa.ca --- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:10 EST