plustek: Thread: USB scanner troubles

Fellow plustek users/developers,

I am trying to install a HP ScanJet 2100C USB which is listed as "mostly
working".  I REALLY am desperate to get this working!

The problem:  scanimage -L lists nothing and either does
sane-find-scanner. :-(

I am using Mandrake 9.0 with the rpm's for libsane and sane-backends
versions 1.0.8 installed.  Additionally, I've installed the latest
plustek-module-0_42_9.tar.gz module.  I downloaded the sane backend and
ran make all;make install from within the plustek directory.  Everything
seemed to install flawlessly.  When I do a cat /proc/usb/devices, it
shows the vender and product ID identical to what is shown on the chart
as "mostly working" so I believe this should work.

After installing, I added the exact vender and product ID to my
/etc/modules.conf and did modprobe scanner. /var/log/messages says: 

Nov 17 22:54:29 fuzzymonkey kernel: usb.c: registered new driver
usbscanner
Nov 17 22:54:29 fuzzymonkey kernel: scanner.c: 0.4.6:USB Scanner Driver

and lsmod says:
scanner                 9140   0  (unused)

Does anyone know what I can do from here?  I don't know how to
troubleshoot further :-(

Thanks,
Michael

Hi, 

the problem is the Mandrake stuff, they have removed all backends
from the SANE configuration file dll.conf.
Search for this file, it should be loacted at:
/etc/sane.d
or
/usr/local/etc/sane.d
(Try: locate dll.conf)
Once found, check at least for the plustek entry, if there's a leading #
remove it...)

This should do the trick
  Gerhard

On Montag, 18. November 2002 05:04, Michael D. Spiceland wrote:
> Fellow plustek users/developers,
>
> I am trying to install a HP ScanJet 2100C USB which is listed as "mostly
> working".  I REALLY am desperate to get this working!
>
> The problem:  scanimage -L lists nothing and either does
> sane-find-scanner. :-(
>
> I am using Mandrake 9.0 with the rpm's for libsane and sane-backends
> versions 1.0.8 installed.  Additionally, I've installed the latest
> plustek-module-0_42_9.tar.gz module.  I downloaded the sane backend and
> ran make all;make install from within the plustek directory.  Everything
> seemed to install flawlessly.  When I do a cat /proc/usb/devices, it
> shows the vender and product ID identical to what is shown on the chart
> as "mostly working" so I believe this should work.
>
> After installing, I added the exact vender and product ID to my
> /etc/modules.conf and did modprobe scanner. /var/log/messages says:
>
> Nov 17 22:54:29 fuzzymonkey kernel: usb.c: registered new driver
> usbscanner
> Nov 17 22:54:29 fuzzymonkey kernel: scanner.c: 0.4.6:USB Scanner Driver
>
> and lsmod says:
> scanner                 9140   0  (unused)
>
> Does anyone know what I can do from here?  I don't know how to
> troubleshoot further :-(
>
> Thanks,
> Michael

Hi Michael, here is my paper on USB scanners. Hope it helps.



		Recipe for Setting Up a Scanner using USB
				Karl Larsen
			     November 17, 2002

	If the scanner you have has a USB cable that plugs into the
computer, and if your computer has a plug for it to plug into, this paper
will tell you how to make certain that the software called Sane on your
Linux operating system can find and use your scanner.

	First your Linux. It should have at least a 2.4.8 kernel and among
other things should have the scanner module compiled and ready for use. 

	Next your Sane. You should have a recent version of this software.
To find out what you have, run this simple test. In an Xterm window type
scanimage --version. This will print out the backend version and it needs
to be 1.0.7 or higher to work well with a USB scanner. If your version is
older you need to install the latest version from

	In terms of the Red Hat Linux, version 7.3 or higher will fully
support running a USB scanner. An earlier version might require both a
kernel and Sane upgrade.

	Plug your scanner into the computer and turn it on. Notice the Name
of your scanner and it's model number. Now in an Xterm window at the command
line do this:

		cat /proc/bus/usb/devices <Enter>

This lists all the data about your USB ports. Here is a copy of my
computer's setup:

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=6400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs=  1
P:  Vendor=04b8 ProdID=010f Rev= 1.00
S:  Manufacturer=EPSON
S:  Product=EPSON Scanner 010F
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=16ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

	I have an Epson model Perfection 1250 scanner and you can see that
this printout is correct for an Epson. Notice at the second P: is listed a
number called Vender=04b8 which means Epson. ProdID=010f which means
model Perfection 1250 are the 2 numbers we need to set up Sane so it can
find the scanner.

	The numbers need to be changed to exact Hex numbers so instead of
04b8 it is written 0x04b8 and 010f is written 0x010f. We will use these
numbers with the scanner module to set up a working scanner. It's assumed
you have scanner as a module on your Linux. 

	To load the module with the scanner numbers in place we use modprobe
and we must be in an xterm window as root. To do this type su - and when it
asks for your password type that in. You will see the prompt turn to # and
you will be in the /root directory. Now type in the following:

	modprobe scanner vendor=0x04b8 product=0x010f

but instead of my numbers put in your scanners numbers. It should take a
second to do it's job and then stop without any error messages. If you get
an error message you didn't type it in right.

	Now to see if Sane can find the scanner. For this we use the tool
that comes with Sane called "sane-find-scanner". In an xterm window type in:

		sane-find-scanner

	My Linux came back with this:  	

# 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/scanner0

Notice the last 2 lines that begin "sane-find-scanner:". It says Sane has
found our scanner because it gives the proper vendor and product numbers for
my scanner. 

	At this point your scanner will probably not work yet but your sure
that Sane can find your scanner. Your more than 1/2 toward a working
scanner in Linux.

	To use the scanner you will want to load the module scanner each
time you turn on your Linux. There are several ways to do this but the most
straight forward way is to load scanner from the file /etc/rc.d/rc.local.
This file on my computer looks like this:

#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

# This turns on the scanner module with the Epson scanner

insmod scanner >/dev/null

It's the insmod scanner that loads the module. Now we want to load the
vendor and product numbers. This is done in the file /etc/modules.conf. Mine
looks like this:

alias parport_lowlevel parport_pc
alias eth0 8139too
alias sound-slot-0 es1371
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null
2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null
2>&1 || :
alias usb-controller usb-uhci
options scanner vendor=0x4b8 product=0x010f

Notice the last line which is what I added. To make that line active as root
you need to use a tool that reads the file and does what it says to do. This
tool is called "depmod" and you use it this way:

		#depmod -a

It will take several seconds and then just stop.

	Testing the setup is easy and takes little time. Remove the scanner
module from the kernel with rmmod scanner. Then run sane-find-scanner and
see it can't find it. Then use modprobe scanner to re-load it and again run
sane-find-scanner and observe it again finds it.

	At this point your ready to approach which back end to use with your
scanner. 





On 17 Nov 2002, Michael D. Spiceland wrote:

> Fellow plustek users/developers,
> 
> I am trying to install a HP ScanJet 2100C USB which is listed as "mostly
> working".  I REALLY am desperate to get this working!
> 
> The problem:  scanimage -L lists nothing and either does
> sane-find-scanner. :-(
> 
> I am using Mandrake 9.0 with the rpm's for libsane and sane-backends
> versions 1.0.8 installed.  Additionally, I've installed the latest
> plustek-module-0_42_9.tar.gz module.  I downloaded the sane backend and
> ran make all;make install from within the plustek directory.  Everything
> seemed to install flawlessly.  When I do a cat /proc/usb/devices, it
> shows the vender and product ID identical to what is shown on the chart
> as "mostly working" so I believe this should work.
> 
> After installing, I added the exact vender and product ID to my
> /etc/modules.conf and did modprobe scanner. /var/log/messages says: 
> 
> Nov 17 22:54:29 fuzzymonkey kernel: usb.c: registered new driver
> usbscanner
> Nov 17 22:54:29 fuzzymonkey kernel: scanner.c: 0.4.6:USB Scanner Driver
> 
> and lsmod says:
> scanner                 9140   0  (unused)
> 
> Does anyone know what I can do from here?  I don't know how to
> troubleshoot further :-(
> 
> Thanks,
> Michael
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 
> 

-- 
                      
               - Karl Larsen k5di Las Cruces,NM Az ScQRPions -

Karl,

may I put this description onto the Plustek backend site?

Gerhard

Hi Gerhard you sure can. I wrote this to help others trying to get their 
scanner working. I'm fixing some small so far errors and will send you 
the finished copy when it's finished...:-)


On Mon, 18 Nov 2002, Gerhard Jaeger wrote:

> Karl,
> 
> may I put this description onto the Plustek backend site?
> 
> Gerhard
> 
> 

-- 
                      
               - Karl Larsen k5di Las Cruces,NM Az ScQRPions -

On Mon, 2002-11-18 at 03:38, Gerhard Jaeger wrote:
> Once found, check at least for the plustek entry, if there's a leading #
> remove it...)
> 
> This should do the trick
>   Gerhard

I edited the dll.conf with a line that said plustek.  Before I edited
it, it just had net and umax_pp.  Now it has those three entries one per
line.

I think the issue may be at the driver/usb level.  I do not have a
/dev/usbcanner or a /dev/usb/scanner :-(  /proc/bus/usb/devices says
lists my scanner with vender and product ID. I issue these to modprobe
and it doesn't give any warnings and /var/log/messages doesn't complain.
I've done this with and without the scanner plugged in.  No matter what
I do, when I plug in my scanner /var/log/messages shows:

Nov 18 12:29:15 fuzzymonkey kernel: hub.c: USB new device connect on
bus1/1, assigned device number 11
Nov 18 12:29:15 fuzzymonkey kernel: scanner.c: probe_scanner: User
specified USB scanner -- Vendor:Product - 3f0:10f
Nov 18 12:29:15 fuzzymonkey kernel: usb.c: USB device 11 (vend/prod
0x3f0/0x505) is not claimed by any active driver.
Nov 18 12:29:19 fuzzymonkey /etc/hotplug/usb.agent: ... no modules for
USB product 3f0/505/100

This makes me believe that even though I am loading the driver with the
exact vendor and product ID, that it still isn't associating it with it.

[root@fuzzymonkey mike]# lsmod | grep scanner
scanner                 9140   0  (unused)
usbcore                58304   1  [scanner hid usbmouse usb-uhci]

Where can I go from here?  What can I do to further troubleshoot it?

Is adding the plustek line to dll.conf sufficient for configuring sane? 
I assume that I need to get the usb stuff to register that driver with
my scanner first before I need to worry about sane working.

Thank you in advance,
Michael

sane-find-scanner now works, but still problems!  The only thing I
changed was passing it the vender and product  using modules.conf
instead of on command line, but sane-find-scanner now works!

sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0505)
at device /dev/usb/scanner0

The problem is that scanimage -L doesn't find it:

[root@fuzzymonkey mike]# scanimage -L
[umax_pp_low] TestVersion(0) (umax_pp_low.c:4412) failed ...

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

Is this due to an incorrectly setup dll.conf as you said?  I put plustek
on that file ... is there somethign else I should do?

Thanks,
Michael

Hi Michael,

remove the umax_pp entry, and edit plustek.conf that way, that
device points to /dev/usb/scanner0. Also make sure to have
read/write access to this device from your user account...

Gerhard

BTW: no need to send the mails twice, the mailing list is enough ;-)


On Monday, 18. November 2002 18:37, Michael D. Spiceland wrote:
> sane-find-scanner now works, but still problems!  The only thing I
> changed was passing it the vender and product  using modules.conf
> instead of on command line, but sane-find-scanner now works!
>
> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0505)
> at device /dev/usb/scanner0
>
> The problem is that scanimage -L doesn't find it:
>
> [root@fuzzymonkey mike]# scanimage -L
> [umax_pp_low] TestVersion(0) (umax_pp_low.c:4412) failed ...
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
>
> Is this due to an incorrectly setup dll.conf as you said?  I put plustek
> on that file ... is there somethign else I should do?
>
> Thanks,
> Michael
>

Hello, 
I think i have  followed  all the instructions but it's always the same 
problem: No scanners were identified! 
In dll.conf, i've just let the plustek  and the net entries.
These are the logs:


[root@localhost fab]# cat /proc/bus/usb/devices
...
P:  Vendor=03f0 ProdID=0605 Rev= 1.00
S:  Manufacturer=Hewlett-Packard
S:  Product=HP ScanJet 2200C
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner"



"[root@localhost fab]# modprobe -v scanner vendor=0x03F0 product=0x0605
/sbin/insmod /lib/modules/2.4.19-16mdk/kernel/drivers/usb/scanner.o.gz 
vendor=0x03F0 product=0x0605"



"[root@localhost fab]# /usr/local/bin/sane-find-scanner
  # No SCSI scanners found. If you expected something different, make sure 
that
  # you have loaded a SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x03f0, product=0x0605) at /dev/usb/scanner0
found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0605 [HP ScanJet 
2200C]) at libusb:001:002
  # A USB device was detected. This program can't be sure if it's really
  # a scanner. If it is your scanner, it may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.
  # Scanners connected to the parallel port or other proprietary ports can't 
be
  # detected by this program."



"[root@localhost fab]# /usr/local/bin/scanimage -L
No scanners were identified. If you w...."


"sanei_debug] Setting debug level of dll to 12.
[dll] sane_init: SANE dll backend version 1.0.6 from sane-backends-1.0.9
[dll] add_backend: adding backend `net'
[dll] add_backend: adding backend `plustek'
[dll] load: searching backend `plustek' in `/usr/local/lib/sane'
[dll] load: trying to load `/usr/local/lib/sane/libsane-plustek.so.1'
[dll] load: dlopen()ing `/usr/local/lib/sane/libsane-plustek.so.1'
[dll] init: initializing backend `plustek'
[sanei_debug] Setting debug level of plustek to 12.
[plustek] Plustek backend V0.44-10, part of sane-backends 1.0.9
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with Plustek parallel-port scanners and<
[plustek] ># LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ># For parport devices use the parport section<
[plustek] >#<
[plustek] ># [parport]<
[plustek] ># device /dev/pt_drv<
[plustek] ><
[plustek] >#<
[plustek] ># leave the default values as specified in /etc/modules.conf<
[plustek] >#<
[plustek] >#option warmup    -1<
[plustek] >#option lOffOnEnd -1<
[plustek] >#option lampOff   -1<
[plustek] ><
[plustek] ><
[plustek] >#<
[plustek] ># The USB section:<
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] >[usb] 0x03f0 0x0605<
[plustek] next device is a USB device (0x03F0-0x0605)
[plustek] next device is an USB device
[plustek] >device /dev/usb/scanner0<
[plustek] Decoding device name >/dev/usb/scanner0<
[pl....
[plustek] drvopen()
[plustek] usbDev_open(/dev/usb/scanner0,0x03F0-0x0605)
[plustek] Vendor ID=0x03F0, Product ID=0x0605
[plustek] usbio_DetectLM983x
[plustek] UIO error
[plustek] This is not a LM9831 or LM9832 chip based scanner.
[plustek] open failed: -1
[dll] init: backend `plustek' is version 1.0.0
[plustek] sane_get_devices (0xbffff068, 0)

No scanners were identified. If you w..."

On Mandrake 9. 
Thanks if you could help me

Hi,

on certain kernels we ave this problem. It helps to replug the scanner
after boot-up sequence...
You might also either use libusb or scanner-module, not both.
To use lubusb with the backend, update to SANE-1.0.11 and then change your
plustek.conf that way, that it contains at least
[usb]
device auto

Gerhard

On Dienstag, 11. März 2003 02:23, Morel Fabrice wrote:
> Hello,
> I think i have  followed  all the instructions but it's always the same
> problem: No scanners were identified!
> In dll.conf, i've just let the plustek  and the net entries.
> These are the logs:
>
>
> [root@localhost fab]# cat /proc/bus/usb/devices
> ...
> P:  Vendor=03f0 ProdID=0605 Rev= 1.00
> S:  Manufacturer=Hewlett-Packard
> S:  Product=HP ScanJet 2200C
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner"
>
>
>
> "[root@localhost fab]# modprobe -v scanner vendor=0x03F0 product=0x0605
> /sbin/insmod /lib/modules/2.4.19-16mdk/kernel/drivers/usb/scanner.o.gz
> vendor=0x03F0 product=0x0605"
>
>
>
> "[root@localhost fab]# /usr/local/bin/sane-find-scanner
>   # No SCSI scanners found. If you expected something different, make sure
> that
>   # you have loaded a SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x03f0, product=0x0605) at /dev/usb/scanner0
> found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0605 [HP
> ScanJet 2200C]) at libusb:001:002
>   # A USB device was detected. This program can't be sure if it's really
>   # a scanner. If it is your scanner, it may or may not be supported by
>   # SANE. Try scanimage -L and read the backend's manpage.
>   # Scanners connected to the parallel port or other proprietary ports
> can't be
>   # detected by this program."
>
>
>
> "[root@localhost fab]# /usr/local/bin/scanimage -L
> No scanners were identified. If you w...."
>
>
> "sanei_debug] Setting debug level of dll to 12.
> [dll] sane_init: SANE dll backend version 1.0.6 from sane-backends-1.0.9
> [dll] add_backend: adding backend `net'
> [dll] add_backend: adding backend `plustek'
> [dll] load: searching backend `plustek' in `/usr/local/lib/sane'
> [dll] load: trying to load `/usr/local/lib/sane/libsane-plustek.so.1'
> [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-plustek.so.1'
> [dll] init: initializing backend `plustek'
> [sanei_debug] Setting debug level of plustek to 12.
> [plustek] Plustek backend V0.44-10, part of sane-backends 1.0.9
> [plustek] ># Plustek-SANE Backend configuration file<
> [plustek] ># For use with Plustek parallel-port scanners and<
> [plustek] ># LM9831/2/3 based USB scanners<
> [plustek] >#<
> [plustek] ># For parport devices use the parport section<
> [plustek] >#<
> [plustek] ># [parport]<
> [plustek] ># device /dev/pt_drv<
> [plustek] ><
> [plustek] >#<
> [plustek] ># leave the default values as specified in /etc/modules.conf<
> [plustek] >#<
> [plustek] >#option warmup    -1<
> [plustek] >#option lOffOnEnd -1<
> [plustek] >#option lampOff   -1<
> [plustek] ><
> [plustek] ><
> [plustek] >#<
> [plustek] ># The USB section:<
> [plustek] ># each device needs at least two lines:<
> [plustek] ># - [usb] vendor-ID and product-ID<
> [plustek] ># - device devicename<
> [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
> [plustek] ># [usb] 0x07B3 0x0017<
> [plustek] ># device /dev/usbscanner<
> [plustek] >#<
> [plustek] ># additionally you can specify some options<
> [plustek] ># warmup, lOffOnEnd, lampOff<
> [plustek] >#<
> [plustek] ># For autodetection use<
> [plustek] >[usb] 0x03f0 0x0605<
> [plustek] next device is a USB device (0x03F0-0x0605)
> [plustek] next device is an USB device
> [plustek] >device /dev/usb/scanner0<
> [plustek] Decoding device name >/dev/usb/scanner0<
> [pl....
> [plustek] drvopen()
> [plustek] usbDev_open(/dev/usb/scanner0,0x03F0-0x0605)
> [plustek] Vendor ID=0x03F0, Product ID=0x0605
> [plustek] usbio_DetectLM983x
> [plustek] UIO error
> [plustek] This is not a LM9831 or LM9832 chip based scanner.
> [plustek] open failed: -1
> [dll] init: backend `plustek' is version 1.0.0
> [plustek] sane_get_devices (0xbffff068, 0)
>
> No scanners were identified. If you w..."
>
> On Mandrake 9.
> Thanks if you could help me
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####