Andre,
I'm certainly no zip expert but I did notice that your read operations
weren't going through the file system while your write operations
were. Have you considered testing some reads from the zip device while
going through the file system? (it's a thought anyway)
Also, um.... have you tried playing with your parport settings?
Josh
On Mon, 16 Oct 2000, Adminstrador de aqui.em.casa wrote:
> Hello, I'm experiencing a problem with my Zip drive which I cannot
> solve. I've searched the mailing list to check whether someone had already
> gone through this, but the closest I could get is the mail:
>
> Parallel ZIP-drive is little buggy with kernel 2.4.0-test1
>
> What I have is a very similar problem, but I could find no answer on that or subsequent replies. When I do tests like:
>
> time dd if=/dev/sda of=/dev/null count=81920 # this is 40 Mb!
>
> Everything works fine, nothing strange happens and the timing goes to
> 1m29s approximately. But, when I try to copy large files into the zip disk
> the kernel starts:
>
> Oct 16 20:57:20 aqui kernel: Filesystem panic (dev 08:04).
> Oct 16 20:57:20 aqui kernel: fat_free: deleting beyond EOF
> Oct 16 20:57:20 aqui kernel: File system has been set read-only
>
> After that a bunch of messages start to appear on /var/log/messages:
>
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 109167
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 109168
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 109421
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 109675
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 109929
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 110183
> Oct 16 21:48:17 aqui kernel: I/O error: dev 08:04, sector 110437
> ...
>
> I've counted up to 68 messages like that. After all that, I can't eject the device anylonger and neither mount another disk with the following message appearing:
>
> mount: /dev/sda4 is not a valid block device
>
> No processes seem to be hanging the zip drive since it is unmounted!
>
> Well, I can't use the zip drive them, till I reboot... Other things happen as well: my printer stops receiving printing commands. I've been using kernel 2.3 andeverything seemed to work just fine, but with 2.4.0-test* series nothing works any more.
>
> Here's my linux box config:
>
> AMD K6III 450 / 128 MB RAM
> ZIP DRIVE 100 PARALLEL PORT
> PRINTER: HP DESKJET 560C (_REALLY_ OLD:)
>
> BIOS: AWARD SUPPORTING EPP, SPP AND ECP on a FIC PA2013
> BIOS CONFIG: SPP + EPP (V. 1.9) DMA==3 IRQ==5
> Although I select the DMA and IRQ on bios, I don't use them on linux.
>
> I'll attach my .config from the kernel (2.4.0-test9) so one can see what's been selected. Basically, everything to support the zipdrive and the parellel port. I've compiled that stuff statically, so maybe for tests it would be better to make it a module...
>
> Here's my dmesg ppa/sda lines:
>
> ppa: Version 2.05 (for Linux 2.2.x)
> ppa: Found device at ID 6, Attempting to use EPP 16 bit
> ppa: Communication established with ID 6 using EPP 16 bit
> scsi1 : Iomega VPI0 (ppa) interface
>
> Vendor: IOMEGA Model: ZIP 100 Rev: D.13
> sda : READ CAPACITY failed.
> sda : status = 0, message = 00, host = 0, driver = 08
> sda : extended sense code = 2
> sda : block size assumed to be 512 bytes, disk size 1GB.
> sda: I/O error: dev 08:00, sector 0
>
> parport0: PC-style at 0x278 (0x678) [PCSPP,TRISTATE,COMPAT,EPP,ECP]
> parport0: irq 5 detected
> parport0: cpp_daisy: aa5500ff(08)
> parport0: assign_addrs: aa5500ff(08)
> parport0: cpp_daisy: aa5500ff(08)
> parport0: assign_addrs: aa5500ff(08)
> lp0: using parport0 (polling).
>
> This is _not_ necessarely on order (I've used cat | grep). And, finally, my fstab entry:
>
> /dev/sda4 /mnt/zip vfat noauto,user 0 0
>
> If anyone wants to reproduce the error, I think it would be enough to copy many medium sized files into the zip disk with:
>
> cp [files] /mnt/zip
>
> And there the error will appear, presumably.
>
> If anyone could help, I would really appreciate, I need to use my zip for my thesis and I can't make it work.
>
> Cheers, Andr.
>
>
>
>
>
>
> -- To unsubscribe, send mail to: linux-parport-request@torque.net --
> -- with the single word "unsubscribe" in the body of the message. --
>
>
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Tue Oct 17 2000 - 22:33:13 EDT