CACook at quantum-sci.com writes:
> Anyone have any ideas?
>
> On Tuesday, December 13, 2011 07:03:57 AM CACook at quantum-sci.com wrote:
>> On Sunday, December 11, 2011 03:42:26 PM Olaf Meeuwissen wrote:
>> > > # sane-find-scanner
>> > > ...
>> > > found USB scanner (vendor=0x138a, product=0x0007
Anyone have any ideas?
On Tuesday, December 13, 2011 07:03:57 AM CACook at quantum-sci.com wrote:
> On Sunday, December 11, 2011 03:42:26 PM Olaf Meeuwissen wrote:
> > > # sane-find-scanner
> > > ...
> > > found USB scanner (vendor=0x138a, product=0x0007) at libusb:003:004
> > > # Your USB sca
On Tue, Dec 13, 2011 at 10:03 AM, wrote:
> On Sunday, December 11, 2011 03:42:26 PM Olaf Meeuwissen wrote:
>> > # sane-find-scanner
>> > ...
>> > found USB scanner (vendor=0x138a, product=0x0007) at libusb:003:004
>> > ? # Your USB scanner was (probably) detected. It may or may not be
>> > suppo
On Tuesday, December 13, 2011 07:10:51 AM m. allan noah wrote:
> > # SANE_DEBUG_DLL=15 scanimage -L 2>/home/carl/dl/dll.log
> > No scanners were identified.
> >
>
> And what was in the log?
Attached.
-- next part --
A non-text attachment was scrubbed...
Name: dll.log.tar.
On Sunday, December 11, 2011 03:42:26 PM Olaf Meeuwissen wrote:
> > # sane-find-scanner
> > ...
> > found USB scanner (vendor=0x138a, product=0x0007) at libusb:003:004
> > # Your USB scanner was (probably) detected. It may or may not be
> > supported by
> > # SANE. Try scanimage -L and read th
CACook at quantum-sci.com writes:
> On Thursday, December 08, 2011 11:52:34 AM m. allan noah wrote:
>> skip xsane for a minute. what about scanimage -L
>
> # scanimage -L
> No scanners were identified.
> ...
> # sane-find-scanner
> ...
> found USB scanner (vendor=0x138a, product=0x0007) at libusb:
Try this:
SANE_DEBUG_DLL=15 scanimage -L 2>dll.log
then look in that log file.
allan
On Fri, Dec 9, 2011 at 10:10 AM, wrote:
> On Thursday, December 08, 2011 11:52:34 AM m. allan noah wrote:
>> skip xsane for a minute. what about scanimage -L
>
> # scanimage -L
> No scanners were identified.
"m. allan noah" writes:
> skip xsane for a minute. what about scanimage -L
>
> allan
>
> On Thu, Dec 8, 2011 at 2:26 PM, wrote:
>> On Thursday, December 08, 2011 10:29:16 AM m. allan noah wrote:
>>> Just disable v4l in dll.conf, and see if that helps.
>>
>> Thanks, but disabling only v4l still
On Thursday, December 08, 2011 11:52:34 AM m. allan noah wrote:
> skip xsane for a minute. what about scanimage -L
# scanimage -L
No scanners were identified.
...
# sane-find-scanner
...
found USB scanner (vendor=0x138a, product=0x0007) at libusb:003:004
# Your USB scanner was (probably) detecte
skip xsane for a minute. what about scanimage -L
allan
On Thu, Dec 8, 2011 at 2:26 PM, wrote:
> On Thursday, December 08, 2011 10:29:16 AM m. allan noah wrote:
>> Just disable v4l in dll.conf, and see if that helps.
>
> Thanks, but disabling only v4l still says 'no devices'.
>
> For some reason
Just disable v4l in dll.conf, and see if that helps.
allan
On Thu, Dec 8, 2011 at 1:20 PM, wrote:
>
> Having a problem with XSane -- it always chooses the wrong device. ?It
> chooses the v4l built-in camera in my laptop, rather than the saned daemon's
> scanner, which is a Canon.
>
> There do
On Thursday, December 08, 2011 10:29:16 AM m. allan noah wrote:
> Just disable v4l in dll.conf, and see if that helps.
Thanks, but disabling only v4l still says 'no devices'.
For some reason XSane does not seem to be looking to saned's port 6566.
OK there's more to the story: My saned server
Having a problem with XSane -- it always chooses the wrong device. It chooses
the v4l built-in camera in my laptop, rather than the saned daemon's scanner,
which is a Canon.
There doesn't seem to be any place in XSane to select device, and the
documentation doesn't address this issue at all.
13 matches
Mail list logo
