Mike Sienicki <mike@cpdist.com> wrote:
>Dear NetBSD/i386,

>My Iomega Zip100 drive worked just fine under NetBSD.  I recently upgraded
>to an Iomega Zip 250 drive and I can't get it to work.  It is recognized
>under NetBSD V1.4.1, but, I can't mount either a 100MB or a 250MB disk.  I
>suspect that this may be a driver problem.  I get the following dmesg output:

I've got the same problem, but with a newer atapi zip 100 (so it's not
just limited to the 250's).  At least now I know I didn't just get a broken
drive, since someone else is having a problem too...

>NetBSD 1.4.1 (MIKE) #0: Wed Oct  6 19:27:34 EST 1999
[...]
>pciide0 at pci0 dev 7 function 1: VIA Technologies VT82C586A IDE Controller
>pciide0: bus-master DMA support present
>pciide0: primary channel configured to compatibility mode
>atapibus0 at pciide0 channel 0
>sd0 at atapibus0 drive 1: <IOMEGA  ZIP 250     ATAPI, , 51.G> type 0 direct
>removable
>sd0: 239MB, 239 cyl, 64 head, 32 sec, 512 bytes/sect x 489532 sectors
>sd0: 32-bits data port
>sd0: drive supports PIO mode 3
>wd0 at pciide0 channel 0 drive 0: <WDC AC14300R>
>wd0: drive supports 16-sector pio transfers, lba addressing
>wd0: 4112MB, 8912 cyl, 15 head, 63 sec, 512 bytes/sect x 8421840 sectors
>wd0: 32-bits data port
>wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4, Ultra-DMA
>mode 3, Ultra-DMA mode 2
>pciide0: primary channel interrupting at irq 14
>pciide0: secondary channel configured to compatibility mode
>atapibus1 at pciide0 channel 1
>cd0 at atapibus1 drive 0: <FX240S, , j01> type 5 cdrom removable
>cd0: 32-bits data port
>cd0: drive supports PIO mode 3, DMA mode 2
>pciide0: secondary channel interrupting at irq 15
>wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
>transfers)
>sd0(pciide0:0:1): using PIO mode 3
>cd0(pciide0:1:0): using PIO mode 3, DMA mode 1 (using DMA data transfers)
[...]
>biomask c840 netmask c840 ttymask d8c2
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>findroot: can't open dev sd0a (5)
>wscons: wskbd0 glued to wsdisplay0 (console)
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>pciide0:0:1: piomode error (0x4)
>sd0(pciide0:0:1): ATA command aborted
>boot device: wd0
>root on wd0a dumps on wd0b
>root file system type: ffs
>
>Any help would be greatly appreciated.  Thanks from --Video Mike--

Here's a diff of dmesgs from the same machine, the -oldzip using an older
zip 100 that I've had running in there for a long time, the +newzip using
the new zip drive, both set up as master on the secondary bus, with a
cdrom slave (which is how the oldzip originally came when I bought the
machine).  I've tried other combinations, unplugging the cdrom, etc.,
still the same errors.

(This was tested with a 1.4Q or so -current...)

--- dmesg.p5.oldzip	Fri Apr 14 08:23:16 2000
+++ dmesg.p5.newzip	Mon Feb 28 17:52:58 2000
@@ -25,14 +25,15 @@
 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
 pciide0: secondary channel wired to compatibility mode
 atapibus0 at pciide0 channel 1
-sd0 at atapibus0 drive 0: <IOMEGA  ZIP 100       ATAPI, , 13.A> type 0 direct removable
+sd0 at atapibus0 drive 0: <IOMEGA  ZIP 100       ATAPI, , 03.H> type 0 direct removable
 sd0: drive offline
 sd0: 32-bits data port
+sd0: drive supports PIO mode 3, DMA mode 1
 cd0 at atapibus0 drive 1: <TOSHIBA CD-ROM XM-5702B, 8100802946, 3476> type 5 cdrom removable
 cd0: 32-bits data port
 cd0: drive supports PIO mode 3, DMA mode 1
 pciide0: secondary channel interrupting at irq 15
-sd0(pciide0:1:0): using PIO mode 3
+sd0(pciide0:1:0): using PIO mode 0, DMA mode 1 (using DMA data transfers)
 cd0(pciide0:1:1): using PIO mode 0, DMA mode 1 (using DMA data transfers)
 uhci0 at pci0 dev 7 function 2: Intel 82371AB USB Host Controller (PIIX4) (rev. 0x01)
 uhci0: interrupting at irq 9
@@ -83,6 +84,27 @@
 apm0: A/C state: on
 apm0: battery charge state: no battery
 biomask ef4d netmask ef4d ttymask ffcf
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+findroot: can't open dev sd0a (5)
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
+pciide0:1:0: piomode error (0x4)
+sd0(pciide0:1:0): ATA command aborted
 boot device: wd0
 root on wd0a dumps on wd0b
 root file system type: ffs

I thought of the possibility of it being the DMA and PIO modes supported,
but never got around to playing with the flags arguments to test.  However,
I notice that your drive is showing just PIO mode 3 (like my working old
drive) and is still giving the problems...

It would be nice to get this fixed, but for now I'll probably just end up
throwing the new drive into the machine that's being forced into windows
2000, and letting the iomega drivers handle it.  However, I'll still be
able to test-boot kernels on that machine, if anyone needs me to...

jdarrow

-- 
John Darrow - Senior Technical Specialist               Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187  Fax:    630/752-5968
Alphapage: 6303160707@alphapage.airtouch.com            Pager:  630/316-0707
Email:     John.P.Darrow@wheaton.edu