From owner-freebsd-scsi Sat Sep 25 16: 3:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 25E5A14C1F for ; Sat, 25 Sep 1999 16:03:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA24089; Sat, 25 Sep 1999 17:03:17 -0600 (MDT) (envelope-from ken) Message-Id: <199909252303.RAA24089@panzer.kdm.org> Subject: Re: scanner and scsi In-Reply-To: <19990925083746.A310@rknebel.uplink.net> from Rick Knebel at "Sep 25, 1999 08:37:46 am" To: rknebel@uplink.net (Rick Knebel) Date: Sat, 25 Sep 1999 17:03:17 -0600 (MDT) Cc: jedgar@fxp.org (Chris D. Faulhaber), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rick Knebel wrote... > On Sat, Sep 25, 1999 at 08:11:16AM -0400, Chris D. Faulhaber wrote: > > On Sat, 25 Sep 1999, Rick Knebel wrote: > > > > > Hi, > > > I seem to be having trouble with my scsi scanner. > > > > > *snip* > > > > > > My problem is the scanner on bootup is listed as pass 4 but there is no > > > pass4 in the /dev directory. I have tried to make it but if I do ./MAKEDEV > > > pass4 only pass 0-3 are made. > > > > > > > ./MAKEDEV pass4 means that 4 pass devs are created (0-3). Try ./MAKEDEV > > pass5 to create 0-4. > > Hey thanks that worked. > > I do not know how much you know about scanners but now whenever I go to > start up my scanner with xscanimage I get this message in my dmesg > > xptioctl: pass driver is not in the kernel > xptioctl: put "device pass0" in your kernel config file > > > This is strange because i have device pass0 in my kernal config. Hmm, that is odd, since it does show up in your dmesg as pass4. I'll have to look at the diagnostic code and see if there's a bug somewhere. Does camcontrol work properly? I know you can do a devlist, but that doesn't use the pass device. Try this: camcontrol tur da0 -v Are you sure that xscanimage is looking for a pass device? Is xscanimage in the ports tree at all? A quick grep through the INDEX file doesn't reveal anything obvious. Some scanner utilities want a processor target (pt) device. You might try putting 'device pt0' in your kernel config file (and make sure you have /dev/pt0 as well). Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message