[sane-devel] Visioneer OneTouch 7100 USB
madams9 at gmail.com
Tue Jul 6 06:52:47 UTC 2010
What causes this?
Scanimage can not see the scanner:
# scanimage -L
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).
But sane-find-scanner has no problem seeing it:
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04a7 [Visioneer], product=0x0229 [USB
Scanner], chip=GL646) at libusb:007:006
# Your USB scanner was (probably) detected. It may or may not be
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
This is really frustrating.
Sombody please advise. Thanks.
On 07/06/2010 12:22 AM, Gernot Hassenpflug wrote:
> On Tue, Jul 6, 2010 at 3:13 PM, Mark Adams<madams9 at gmail.com> wrote:
>> Thanks for the assist Gernot. I uninstalled ver 1.0.20 and compiled 1.0.21
>> from source. It tests okay:
>> [root at spike madams]# sane-config --version
>> [root at spike madams]# scanimage -v -T
>> scanimage: scanning image of size 2549x3500 pixels at 8 bits/pixel
>> But I still can't get a frontend to start. If I start xsane as a user, it
>> just aborts:
> Sadly I don't know this scanner. But can you get an image using
> scanimage? If so then at least the backend can work in some
> I would suggest some environment variables for debugging, check the
> backend man page for which ones to set (some at generic, some depend
> on the chipset the scanner uses), as well as the sane man page for
> SANE-related and maybe USB-related debug codes. I don't recall them
> offhand. Then do the scanimage test again (if it works is a good
> baseline) and xsane.
More information about the sane-devel