I have previously sent in the output of:
export SANE_DEBUG_PLUSTEK=19 ; scanimage -L
as advised by Gerhard Jaeger and want to add some observations.
I am able to use the scanner on the same hardware, using a Slax Linux
LiveCD and sane-backends-1.0.17
Back to OpenBSD, what I have also noticed, is that if I disconnect the
scanner, then reconnect it, scanimage -L will show the scanner as being
connected, but only for a limited length of time. It is not long enough
to do anything useful though. If I disconnect it then reconnect it and
try xscanimage, I will get the initial dialogue box and can select
resolution and color depth, but when I attempt scan something, the
scanner has become unavailable again and I get a pure black scan.
I'm only able to get even this far, if I do all this as root, but that
is obviously a permission issue and I can address that after I have got
this working.
Hope the above helps and I have again included the sane debug output below.
--
Best regards,
Craig
http://slashboot.org/
Support OpenBSD
http://www.openbsd.org/orders.html
# export SANE_DEBUG_PLUSTEK=19 ; scanimage -L
[sanei_debug] Setting debug level of plustek to 19.
[plustek] Plustek backend V0.50-7, part of sane-backends 1.0.17
[plustek] Retrieving all supported and conntected devices
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0016
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0007
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x0005
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0012
[plustek] Checking for 0x0400-0x1000
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0458-0x2007
[plustek] Checking for 0x0458-0x2008
[plustek] Checking for 0x0458-0x2009
[plustek] Checking for 0x0458-0x2013
[plustek] Checking for 0x0458-0x2015
[plustek] Checking for 0x0458-0x2016
[plustek] Checking for 0x03f0-0x0505
[plustek] Checking for 0x03f0-0x0605
[plustek] Checking for 0x04b8-0x010f
[plustek] Checking for 0x04b8-0x011d
[plustek] Checking for 0x1606-0x0050
[plustek] Checking for 0x1606-0x0060
[plustek] Checking for 0x1606-0x0160
[plustek] Checking for 0x049f-0x001a
[plustek] Checking for 0x04a9-0x2206
[plustek] Checking for 0x04a9-0x2207
[plustek] Checking for 0x04a9-0x2208
[plustek] Checking for 0x04a9-0x220d
[plustek] Checking for 0x04a9-0x220e
[plustek] Checking for 0x04a9-0x2220
[plustek] Available and supported devices:
[plustek] Device: libusb:/dev/usb1:/dev/ugen0 - 0x04a9x0x220d
[plustek] # Plustek-SANE Backend configuration file
[plustek] # For use with LM9831/2/3 based USB scanners
[plustek] #
[plustek]
[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] # or
[plustek] # device libusb:bbb:ddd
[plustek] # where bbb is the busnumber and ddd the device number
[plustek] # make sure that your user has access to /proc/bus/usb/bbb/ddd
[plustek] #
[plustek] # additionally you can specify some options
[plustek] # warmup, lOffOnEnd, lampOff
[plustek] #
[plustek] # For autodetection use
[plustek] # [usb]
[plustek] # device /dev/usbscanner
[plustek] #
[plustek] # or simply
[plustek] # [usb]
[plustek] #
[plustek] # or if you want a specific device but you have no idea about
the
[plustek] # device node or you use libusb, simply set vendor- and
product-ID
[plustek] # [usb] 0x07B3 0x0017
[plustek] # device auto
[plustek] #
[plustek] # NOTE: autodetection is safe, as it uses the info it got
[plustek] # from the USB subsystem. If you're not using the
[plustek] # autodetection, you MUST have attached that device
[plustek] # at your USB-port, that you have specified...
[plustek] #
[plustek]
[plustek] [usb]
[plustek] next device uses autodetection
[plustek] ... next device
[plustek] #[usb] 0x04A9 0x220D
[plustek] usb 0x04A9 0x220D
[plustek] ignoring usb 0x04A9 0x220D
[plustek]
[plustek] #device /dev/uscanner
[plustek] #device libusb:/dev/usb1:/dev/ugen0
[plustek] device auto
[plustek] Decoding device name auto
[plustek]
[plustek] #
[plustek] # options for the previous USB entry
[plustek] #
[plustek] # switch lamp off after xxx secs, 0 disables the feature
[plustek] # (can also be set via frontend)
[plustek] option lampOff 300
[plustek] Decoding option lampOff
[plustek]
[plustek] # warmup
