[sane-devel] Epkowa failed to find all required interpreter API
Scott Barnham s...@manx.net writes: Hi. I'm struggling to get an Epson Perfection 4180 Photo scanner to work with the Epkowa back-end. I'm running Ubuntu Dapper. I get message: Failed to find all required interpreter API. I can't find any reference to this, so I'm a bit stuck. Any idea what it means? That there is something seriously wrong with the interpreter module (libesint43.so) you installed or the backend you are using. scanimage finds the USB device and attaches. libesint43.so is installed and it appears the back-end is finding it (scanimage used to error loading the library before I installed it from the rpm). I can see the firmware file at /usr/share/iscan/esfw43.bin. iscan fails to load, complaining it can't find libesmod.so.1 (which is there in /usr/local/lib), but I understand this isn't required by sane. libesmod.so is only used by iscan. If you use scanimage, xsane or any other SANE backend, it is neither necessary nor used. This is the relevant output from: SANE_DEBUG_EPKOWA=255 scanimage -L [epkowa] attach_one_usb() [epkowa] SANE EPKOWA Backend 1.16.0-3 - 2005-06-29 Eh, this is way old ... and does not work with the current plugin modules. Do yourself a favour and get iscan-2.x, make sure you use the packages for gcc-3.4 or later for both the iscan and plugin package and try again. Ideally, you'd be using (as per download page[1]): iscan-2.4.0-0.c2.i386.rpm iscan-plugin-gt-f600-1.0.0-1.c2.i386.rpm and install both with: $ sudo alien --install --scripts RPM_FILE after you removed all traces of iscan from your system. [epkowa] attach(, 3) [epkowa] attach: opening [epkowa] attach_one_usb(libusb:005:006) [epkowa] SANE EPKOWA Backend 1.16.0-3 - 2005-06-29 [epkowa] attach(libusb:005:006, 3) [epkowa] attach: opening libusb:005:006 [epkowa] Found valid EPSON scanner: 0x4b8/0x118 (vendorID/productID) [epkowa] failed to find all required interpreter API [epkowa] close_scanner(fd = 0) Thanks for your help. References: [1] http://www.avasys.jp/english/linux_e/dl_scan.html Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] coolscan V
Hi Francesco, Il giorno sab, 16/12/2006 alle 14.50 -0800, Francesco Pietra ha scritto: [..-] QUESTION: In order to check if my coolscan is operated (minimum) by sane-coolscan2.5, can this library be added to my system as it is, or should sane replace xsane. Also, is a deb package somewhere available for sane-coolscan2.5? Not found on debian etc/unstable. support for coolscanV is really minimum and it is actually under development and test. I think you'll have to wait some months in order to get a working sane backend. Moreover, what is sane-coolscan2.5? If you are referring to the manual page ?sane-coolscan2.5? then please note that ?5? stands for the manual section, while the backend name is just coolscan2. Bye, Giuseppe
[sane-devel] SANE2 commitment
Hi Martin, Il giorno dom, 17/12/2006 alle 19.52 +, Martin Owens ha scritto: [...] For device detection and management use HAL, update hal dbus code with all existing detection and status code which will keep these devices happy, enable the modification of the hal xml as a simple way of keeping track of which scanners work with which backends too, removing this from the backend code is a must. You can then change your clients to use hal and simply call dbus commands to scan etc. [...] That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? Bye, Giuseppe
[sane-devel] SANE2 commitment
You can then change your clients to use hal and simply call dbus commands to scan etc. [...] That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? I don't know about solaris, I know hal is being used in a number of linux distributions but not even all of them. windows has it's own hal and less is known about it. It might end up being a separate project for integrating sane with hal in order to repackage sane for certain linux distributions that can take advantage of newer device systems. Bye, Giuseppe Best Regards, Martin
[sane-devel] SANE2 commitment
hi all, I'm working on Gnome Scan and intend to be very active in this realm in the next year. This may hurt some people here. I want to bring scan support to hal. I intended to talk with sane people in january. I want in Gnome to use sane for access, not probe/detection. That's bad to probe each time you launch the app. I wonder if we need a kind of cups for scanner that use sane to access, receive job request and return stream of pictures. I wonder how to handle local and networked detection. I want to add avahi feature to scanner share. Likely, SANE 2 offer a new sane_open () prototype that allow to get device description without doing the probe. But how can hal know the sane device name ? I would like to add a scanner.sane.name field or similar into hal scanner device in order to allow app to use directly SANE (basically, a scaner cups will do that). Is this possible with SANE 1 ? If not, how does SANE 2 help for that ? Some of you may be attached to the double work of sane : device support, device probe. But i really think SANE must add a way for developer to handle device detection according to the target system standard (e.g. hal, windows, Solaris, etc.). I do not want sane to drop sane_get_devices (). Would be nice to get sane device name from vid/pid or some other info an OS/hal can give. That's easy to implement a simple hal addon that handle the filling of scanner.sane.name field. I wish you will understand that need. Kind regards, ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061217/d5528193/attachment.pgp From bersac...@laposte.net Sun Dec 17 22:36:23 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 19:42:50 2006 Subject: [sane-devel] SANE2 commitment In-Reply-To: 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com References: 20061215175700.4c974c89@inspiron 45854deb.9010...@penguin-breeder.org 20061217172351.70067897@inspiron 45858d8f.6080...@zago.net 20061217201545.2a7c85c3@inspiron 4585998d.7030...@zago.net 20061217203458.10327e0e@inspiron 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com Message-ID: 1166391382.5549.17.camel@thilivren Skipped content of type multipart/mixed-- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061217/a9772311/attachment.pgp From bersac...@laposte.net Tue Dec 19 15:55:10 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 20:19:59 2006 Subject: [sane-devel] SANE2 commitment In-Reply-To: 1166539654.30598.31.camel@casa References: 20061215175700.4c974c89@inspiron 45854deb.9010...@penguin-breeder.org 20061217172351.70067897@inspiron 45858d8f.6080...@zago.net 20061217201545.2a7c85c3@inspiron 4585998d.7030...@zago.net 20061217203458.10327e0e@inspiron 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com 1166539654.30598.31.camel@casa Message-ID: 1166540109.5681.35.camel@thilivren Hi, That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? I think that SANE must implement a modular OS - SANE API that allow OS to ask SANE to load a driver for one device and the monitor buttons, ? SANE should then also implement a legacy probe mecanism for other OSes or other purpose (distro not shiping HAL, etc.). ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061219/36fc8090/attachment.pgp From bersac...@laposte.net Tue Dec 19 20:57:38 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 22:58:39 2006 Subject: [sane-devel] Frontends : Gnome Scan 0.4 ! Message-ID: 1166558258.5681.99.camel@thilivren Hi all ! Gnome Scan 0.4 has been released with nice gui improvments and new features like x/y resolutions, computed area rotation, ? http://gnome-scan.blogspot.com/2006/12/releasing-04-is-your-app-people-ready.html ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859
[sane-devel] anyone dealt with any chips from Jeilin Technologies?
Hi, Greetings from gphoto. We just got someone with an Argus DC-1512e write in to us. The camera reports itself as 0x0979:0x0227 and from mfgr. Jeilin. I went to the website of Jeilin, and they also claim to make scanner chips. Thus, just in case I end up getting involved in supporting this camera, I thought I might check up whether the scanner chips are known, whether any of them are using funny compression algorithms, that kind of thing. Theodore Kilgore
