This USB id is declared in the ImageCLass part of the pixma backend, and
should be thus at least detected by scanimage.
This looks here rather like a permission issue to access the scanner,
from a standard user account, or a library mess up issue.
Did you try the same scanimage command under ro
your xinetd config needs the 'groups = yes' line?
allan
On Thu, Feb 19, 2009 at 7:50 PM, Grant wrote:
> I have local scanning working via USB on an Epson Artisan 700. I'm
> trying to use xinetd and saned to scan over the network from another
> system. From the client, I get:
>
> $ scanimage -L
Hello
I'd like to report an unsupported device. Its name is Canon i-Sensys MF4018.
Bus type: USB
USB id: 04a9/26b4
This multifunctional belongs to 4010 series and must be identical to
MF4010. I tried to use sane-backends-2009-02-19, but 'scanimage -L'
said: "No scanners were identified".
$ sane
> your xinetd config needs the 'groups = yes' line?
>
> allan
Thank you but I already have that in /etc/xinetd.conf. Any other ideas?
- Grant
>> I have local scanning working via USB on an Epson Artisan 700. I'm
>> trying to use xinetd and saned to scan over the network from another
>> system.
* "Simon Matter" :
>> About the same as uncompressed PNM. (Also tried 200 DPI now, with no
>> noticeable difference in speed from 300 DPI.)
>>
>> The computer I'm testing this on is a Core 2 E8500 3.16GHz, by the
>> way.
> I understand that the 6240 is similar to the 6230 but faster and
> with SCS
I have local scanning working via USB on an Epson Artisan 700. I'm
trying to use xinetd and saned to scan over the network from another
system. From the client, I get:
$ scanimage -L
device `net:192.168.100.1:epkowa:usb:004:003' is a Epson (unknown
model) flatbed scanner
$ scanimage
scanimage: o
> * "m. allan noah" :
>>> It's close enough for me. Who knows how they measure these things.
>>> My measurement was "time scanadf", basically. It was done actually
>>> feeding the papers through the scanner before scanadf exited, so
>>> it's not entirely unimaginable that there is a bit of overhe
* "m. allan noah" :
>> It's close enough for me. Who knows how they measure these things.
>> My measurement was "time scanadf", basically. It was done actually
>> feeding the papers through the scanner before scanadf exited, so
>> it's not entirely unimaginable that there is a bit of overhead in
* "m. allan noah" :
>> In case anyone should search for this particular model: We bought a
>> Fujitsu fi-6240, and after (brief) testing it appears to work great
>> with SANE (CVS-version) and is also blazingly fast. It scans color
>> pages at 300 DPI in 2-2.5 seconds per page using the document
>
JKD wrote:
Hi,
> gcc -g -O2 -W -Wall -o sane-find-scanner sane-find-scanner.o check-usb-chip.o
> sane_strstatus.o ../sanei/.libs/libsanei.a /usr/lib/libusb.so
> sane-find-scanner.o: In function `check_libusb_device':
> /home/jkd/hp3900-series-190209-1542/src/sane-backends/tools/sane-find-scann
eturned 1 exit status
I've attached entire log.
Jonathan Bravo Lopez
-- next part --
A non-text attachment was scrubbed...
Name: sanecomp.log
Type: text/x-log
Size: 62677 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090219/5aee1f8a/attachment-0001.bin
* "m. allan noah" :
>>> http://www.fujitsu.com/global/services/computing/peripheral/scanners/product/fi6230/
>>> It performs as advertised- 30ppm color at 300dpi.
>> This one looks very nice, and the SANE compatibility list says
>> "complete" as well. Thanks again.
> sure- just make sure you are r
Hi,
> Modified: ChangeLog configure configure.in include/sane/config.h.in
> sanei/sanei_usb.c tools/check-usb-chip.c
> tools/sane-find-scanner.c
>
> Add support for libusb-1.0.
So, it's in. A few things to know:
- ./configure --enable-libusb_1_0
- it will fall back to libusb
On Thu, Feb 19, 2009 at 10:09 AM, Johannes Groedem wrote:
> * "m. allan noah" :
>>> In case anyone should search for this particular model: We bought a
>>> Fujitsu fi-6240, and after (brief) testing it appears to work great
>>> with SANE (CVS-version) and is also blazingly fast. It scans color
>>
On Thu, Feb 19, 2009 at 9:48 AM, Johannes Groedem wrote:
> * "m. allan noah" :
http://www.fujitsu.com/global/services/computing/peripheral/scanners/product/fi6230/
It performs as advertised- 30ppm color at 300dpi.
>>> This one looks very nice, and the SANE compatibility list says
>>> "co
or they are used, but the resolution is unused?
allan
On Thu, Feb 19, 2009 at 9:03 AM, Chris Bagwell wrote:
> I think this is the interesting part of --help?
>
> Geometry:
> -l 0..200mm (in steps of 1) [0]
> Top-left x position of scan area.
> -t 0..200mm (in steps of 1) [0]
> T
m. allan noah wrote:
> or they are used, but the resolution is unused?
>
> allan
>
OK, my fault again... I failed to notice that when I converted sanei
directory to automake a few days back that it stopped finding config
files. :-(
It will be fixed within the day. Need to add reference to $(
with a couple week old cvs, when i run your command i get this:
> scanimage -d test -T
scanimage: scanning image of size 157x196 pixels at 8 bits/pixel
scanimage: acquiring gray frame, 8 bits/sample
scanimage: reading one scanline, 157 bytes... PASS
scanimage: reading one byte... PASS
s
I think this is the interesting part of --help?
Geometry:
-l 0..200mm (in steps of 1) [0]
Top-left x position of scan area.
-t 0..200mm (in steps of 1) [0]
Top-left y position of scan area.
-x 0..200mm (in steps of 1) [80]
Width of scan-area.
-y 0..200mm (
On 10485 day of my life Lars Ljung wrote:
> But I'm not sure if I'm trying to reinvent the wheel here. What is
> exactly the relationship between the epkowa backend and libesint32? I
> have looked at the epkowa source code but I don't fully understand how
> it works. I suppose libesint32 loads the
ked
>sane-backends
> To: Jacek Ru?yczka
> Cc: sane-devel at lists.alioth.debian.org
> Message-ID:
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>
> Hello,
>
> On Feb 17 20:22 Jacek Ru?yczka wrote (shortened):
> > I didn't compile it myself, I used the following RPMs:
> >
> > jacek at veteran:~> rpm -qa | grep sane
> > sane-backends-32bit-1.0.19-99.1
> > sane-backends-autoconfig-1.0.19-99.1
> > sane-frontends-1.0.14-302.35
> > sane-backends-1.0.19-128.106
>
> See
> https://bugzilla.novell.com/show_bug.cgi?id=475266#c1
>
>
> By the way, only for your information regarding
> our sane-backends-autoconfig package:
>
> user at host$ rpm -qi sane-backends-autoconfig
> ...
> USB scanner autoconfiguration happens via udev.
> The file /etc/udev/rules.d/56-sane-backends-autoconfig.rules
> contains entries for those USB scanners where the USB IDs
> are known, which are supported by a free driver,
> where the support status is "complete" or "good",
> and which do not require firmware upload.
> ...
>
>
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
> AG Nuernberg, HRB 16746, GF: Markus Rex
>
>
>
> --
>
> ___
> sane-devel mailing list
> sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>
> End of sane-devel Digest, Vol 44, Issue 46
> **
>
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090219/ada0c559/attachment-0001.htm
21 matches
Mail list logo
