From owner-freebsd-hackers Tue Nov 2 12:48:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id DAA5B14CAD for ; Tue, 2 Nov 1999 12:48:28 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 191B59B25; Tue, 2 Nov 1999 15:48:18 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 08B72BA1D; Tue, 2 Nov 1999 15:48:18 -0500 (EST) Date: Tue, 2 Nov 1999 15:48:17 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Gustavo V G C Rios Cc: Gustavo Vieira Goncalves Coelho Rios , hackers@freebsd.org Subject: Re: wfd0: i/o error, status=51 , error=40 In-Reply-To: <381F4C4E.5F4E5545@ddsecurity.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Nov 1999, Gustavo V G C Rios wrote: > "Chris D. Faulhaber" wrote: > > > > On Tue, 2 Nov 1999, Gustavo Vieira Goncalves Coelho Rios wrote: > > > > > That is the message i get at the console when i try to write some thing > > > in my IDE ZIP drive! > > > Have anyone already faced such a problem ? > > > Does any one here know how to fix it ? > > > > > > > Could you provide the relevant part of dmesg WRT to the Zip drive model > > number. This sounds like what happens when the wfd driver does not > > properly recognize the Zip drive inquiry string and does not set maxblks > > to 64 (see PR kern/12095). > > > > ----- > > Chris D. Faulhaber | All the true gurus I've met never > > System/Network Administrator, | claimed they were one, and always > > Reality Check Information, Inc. | pointed to someone better. > > > This is what i get from dmesg output: (only relevant part) > ... > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , > removable, intr, iordis > wfd0: medium type unknown (no disk) > ppc0 at 0x378 irq 7 flags 0x40 on isa > ... > That's the same as my problem drive. Apply the patch in the PR for the driver to limit maxblks properly by using a strncmp vs. strcmp. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message