plustek: sane-find-scanner does not find my UT12
Subject:
Re: sane-find-scanner does not find my UT12
From:
John Mellor ####@####.####
Date:
7 Jan 2002 12:09:22 -0000
Message-Id: <1010405191.2024.20.camel@family.kungfu-tse.net>
On Mon, 2002-01-07 at 02:22, Gene Heskett wrote:
> On Sunday 06 January 2002 07:22 pm, you wrote:
> >Not quite sure what I have done (apart from obey Michael Hackel
> > and fiddle about a bit) but sane-find-scanner now "found USB
> > scanner (vendor = 0x07b3, product = 0x0017) at device
> > /dev/usb/scanner". Hooray. However, scanimage is still unable
> > to connect to it. My configuration file at
> > /usr/local/etc/sane.d/plustek.conf reads:
> >
> >parport
> >
> >/dev/pt_drv
> >
> >I cannot see how this connects with /dev/usb/scanner. Can
> > someone tell me what is now wrong please?
>
> It doesn't. The conf file s/b in /etc/sane.d/ as plustek.conf and
> should look like this:
> -----------------------------
> # Plustek-SANE Backend configuration file
> # For use with Plustek parallel-port scanners and
> # LM9831/2 based USB scanners
> #
> # for multiple devices use
> # /dev/pt_drv0
> # /dev/pt_drv1
> # /dev/pt_drv2
> #
> # For parport devices enable the parport section
> # by uncommenting the lines below
> #
> # parport
> # /dev/pt_drv
> #
> # The USB section
> # each device needs at least two lines:
> # - usb vendor-ID and product-ID
> # - devicename
> # i.e. for Plustek (0x07B3) UT12 (0x0017)
> # usb 0x07B3 0x0017
> # /dev/usbscanner
> # Change the usb device numbers below to match yours
> # as these are for an epson 1250u
>
> usb 0x04b8 0x010f
> /dev/usbscanner
> ---------eof-------------
> sane-find-scanner should then report something along these lines
> [root@gene usb]# sane-find-scanner
> # Note that sane-find-scanner will find any scanner that is
> connected
> # to a SCSI bus and some scanners that are connected to the
> Universal
> # Serial Bus (USB) depending on your OS. It will even find
> scanners
> # that are not supported at all by SANE. It won't find a scanner
> that
> # is connected to a parallel or proprietary port.
>
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x010f) at device /dev/usb/scanner
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x010f) at device /dev/usb/scanner0
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x010f) at device /dev/usbscanner
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x010f) at device /dev/usbscanner0
> [root@gene usb]#
>
> As you can see, there are several devices that lead to the
> correct /dev/name, use the most convienient one.
>
> A side note to those who build their own kernels.
> in /usr/src/linux/drivers/usb, edit the file scanner.h and check
> to see if your device vendor and product codes are there. If
> they are not, add them in the same format as for others shareing
> the same vendor number. Then rebuild the kernel and reboot.
> When the usb bus is scanned, you'll get a hit, and the scanner
> module will automaticly be loaded as can be seen with an "lsmod".
>
Thanks, Gene. I have changed my conf file exactly as you say, but still
scanimage does not find any SANE devices. Sane-find-scanner only finds
the scanner at /dev/usb/scanner, not at any of your other options, if
that is any clue. Any ideas?
