[sane-devel] Epson 3170 in Kubuntu
Just another reminder that Iscan works on my machine. I have a feeling you understood that it doesn't. Am I wrong? To recap. Yes, as you said I installed the two iscan files from avasys and together with libsane everything went fine. (BTW why don't you also provide deb packages on the Avasys website? As there is no source for the plugin all we have is an RPM.) scanimage command also moves the scanner. The big mystery is why kooka and Gwenview don't work. And a bigger mystery is why they do work in SUSE 9.3 with KDE 3.5.2 and they don't work with the same KDE version on a newer kernel in both suse and Kubuntu. There is another thread on the Kubuntu forum about this issue and other people have also complained that after an upgrade to Dapper the 3170 scanner does not fire-up anymore. It appears I'm not the only one with this issue. I did a verbose debug and attaching the files for iscan and kooka Another curious thing: on SUSE 9.3 I see no libkscan...is this a clue? AJ On Sunday 18 June 2006 20:14, you wrote: Adrian Jadic ja...@dallnet.net writes: On Tuesday 13 June 2006 18:48, you wrote: If you have the plugin installed, it ought to work with other SANE frontends as well. But wait! You run on AMD64, right? It won't work with 64bit. You will need to run all your SANE stuff in 32bit mode. AMD 3000+ 32 bit. That ought to be OK. Other sane frontends like kooka and Gwenviw do not work. This is basically my big mystery. They did work in suse 9.3 but with 10.0 and 10.1 they don't work . only Iscan can fire up this scanner. Now I found the same situation in Kubuntu as well. I had so much trouble with this scanner that I was really thinking to sell it on ebay and get a Canon Lide or smthg since I don't use the film feature anyway nor have I used the high resolution enough to justify this unit. But let me first thank you for trying to help me with this., I have been crying about this issue in all possible forums, reported bugs and so on. I even returned a purchased suse 10.0 on this issue (among others) and nobody gave it any attention. So now kooka displays that small window with choosing device and the Epson 3170 is listed correctly. But when I press preview or scan nothing happens. Hmm, that's weird. If listed in the window to choose a device, the backend did see the device allright. Could you take a look at the debugging output? $ SANE_DEBUG_EPKOWA=50 iscan 2 debug.log I am attaching the output as requested. I also did one with kooka and I see that it is different so I am attaching it as well [epkowa] sane_get_devices() [epkowa] sane_open(libusb:005:004) [epkowa] init_options() [epkowa] open_scanner() [epkowa] setvalue(option = 43, value = 0xbfb7da90) [epkowa] close_scanner(fd = 0) Hmmm, option 43 is the document source. Setting that option does not cause any communication to the device, AFAIK. There are two calls in the sources that could trigger an error at this point: - sanei_constrain_value - search_string_list and there is no way to extract more debugging info without modifying the source code. Looking at the source code of both functions, the only reason I can think of that would trigger a failure to set the document source here, is that your frontend tries to set an invalid or non-existent document source. The list of available sources should be correct based on the log (so there is no chance of duplicate matches that would cause sanei_constrain_value to return a no good status). To summarise, I have no clue :-(. Perhaps that running iscan with a more verbose debug setting sheds some light on this, but I doubt it. $ SANE_DEBUG_EPKOWA=127 iscan perfection-3170.log Are you 100% positive that you are running a 100% 32bit setup when trying to use the scanner? I don't understand what the kooka error messages are about. Maybe something in libkscan itself? But, shouldn't this unit work just by installing libsane and libsane-extras? I see that libsane-extras has epkowa. Bottom line which file does actually contain the driver? The epkowa backend from libsane-extras is not expected to work with this device. It requires a non-free module which is not included in that package (for obvious reasons). You can safely uninstall it if you don't use the other SANE backends it includes. Your EPSON Perfection 3170 should work (out-of-the-box) by installing libsane and a recent version of iscan (= 1.18.0) with the plugin that your device requires (iscan-plugin-gt-9400). # I'm not sure what'll happen if you also have libsane-extras # installed, so suggest you uninstall it. Thank you The output will end up in the debug.log file. Thank you, A Jadic On Tuesday 13 June 2006 00:54, you wrote: Adrian Jadic ja...@dallnet.net writes: I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06 Kooka and scanimage recognise the
[sane-devel] Epson 3170 in Kubuntu
Adrian Jadic ja...@dallnet.net writes: Just another reminder that Iscan works on my machine. I have a feeling you understood that it doesn't. Am I wrong? No, you are right. I was indeed under the impression that iscan did NOT work for you. Sorry about the misunderstanding. To recap. Yes, as you said I installed the two iscan files from avasys and together with libsane everything went fine. (BTW why don't you also provide deb packages on the Avasys website? As there is no source for the plugin all we have is an RPM.) I'd suggest sending a short mail requesting this (with a rationale) to pipsnews at avasys dot jp. In the mean time, alien is your friend. The plugins don't do anything special before/after (un)installing, so there should be no problems. scanimage command also moves the scanner. The big mystery is why kooka and Gwenview don't work. And a bigger mystery is why they do work in SUSE 9.3 with KDE 3.5.2 and they don't work with the same KDE version on a newer kernel in both suse and Kubuntu. There is another thread on the Kubuntu forum about this issue and other people have also complained that after an upgrade to Dapper the 3170 scanner does not fire-up anymore. It appears I'm not the only one with this issue. You might want to post the URL so we can all go take a look ;-) I did a verbose debug and attaching the files for iscan and kooka Thanks for the logs but they don't say anything new. I think the problem is with libkscan (perhaps indirectly because Scim is also bleating). Another curious thing: on SUSE 9.3 I see no libkscan...is this a clue? As a package? I just checked a default 9.3 Professional install and there most certainly is a libkscan.so under /opt/kde3/lib. [snip] Still 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] [patch] epkowa.desc
I know I've sent mail about this to the list (it's in the archives) but I can't seem to find my reply in my mailbox anymore :-( Anyway, here is the patch for epkowa.desc that I promised. The patch is against 1.11 in CVS. It incorporates information from epson.desc 1.26 and unsupported.desc 1.255. I've dropped the silly(?) notion that EPSON AVASYS' QA department decides the support :status of the devices listed and synchronised them with the contents in epson.desc. That leads to quite a lot of change, but I hope it is in the user's best interest. As I noticed an incorrect USB ID in epson.desc, I also attached a patch for that. The ID mentioned is the one for the GT-6600 (aka Perfection 610). Note that the Stylus CX6600 is also reported to have an ID of 0x0813 somewhere in the list archive. I didn't add this because epson_usb.c does not list it either. If some kind SANE developer could commit this, I'd be grateful. 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 -- next part -- --- ../../epkowa-1.11.desc 2006-06-15 16:45:23.0 +0900 +++ doc/epkowa.desc 2006-06-20 10:20:10.0 +0900 @@ -22,35 +22,28 @@ ;;; This list of devices was compiled from the following sources: ;;; -;;; * iscan-1.18.0/NEWS -;;; * iscan-1.18.0/doc/sane-epkowa.man -;;; * iscan-1.18.0/backend/epkowa_usb.c -;;; * sane-backends-1.0.15/backend/epson_usb.c -;;; * sane-backends-1.0.15/doc/descriptions/epson.desc +;;; * iscan-2.1.0/NEWS +;;; * iscan-2.1.0/doc/sane-epkowa.man +;;; * iscan-2.1.0/backend/epkowa_usb.c +;;; * sane-backends/backend/epson_usb.c (CVS 1.18) +;;; * sane-backends/doc/descriptions/epson.desc (CVS 1.26) ;;; * http://www.freecolormanagement.com/sane/supported.html ;;; * http://www.sane-project.org/lists/sane-mfgs-cvs.html#Z-EPSON ;;; * http://www.epsondevelopers.com/ ;;; * http://www.epson.com/ (several representative countries) ;;; * http://www.i-love-epson.co.jp/ +;;; * messages on the sane-devel and LinuxPrinting.org epson-list +;;;mailing lists ;; Backend data. ;; :backend epkowa -:version 1.18.0 -:url http://www.avasys.jp/english/linux_e/dl_scan.html; +:version 2.1.0 +:url http://www.avasys.jp/english/linux_e/index.html; -:comment Based on the epson backend of sane-backends-1.0.15. +;:comment Based on the epson backend of sane-backends-1.0.15. -; AFAIK, all devices listed on the sane-epkowa.man page have been -; tested by EPSON AVASYS Corporation but _only_ for SCSI and USB -; interfaces. The IEEE1394 and parallel interfaces have never been -; tested. These models have all been marked :complete (even though -; some are not really quite :complete). All other devices have, in -; principle, been marked as :unsupported. -; Devices supported by the epson backend (as of version 1.0.15 of -; sane-backends) as well as overseas versions of supported models -; have been marked :untested. ;; Device and manufacturer information. ;; @@ -78,16 +71,22 @@ ;; :model Actionscanner II -:interface parallel -:status:untested ; :good +:interface parallel SCSI +:status:good :comment overseas version of the GT-5000 :model AcuLaser CX11 :interface USB :usbid 0x04b8 0x0815 -:status:complete +:status:good :comment overseas version of the LP-A500 +:model AcuLaser CX11NF +:interface USB +:usbid 0x04b8 0x0815 +:status:good +:comment AcuLaser CX11 with network interface and faxbrnetwork interface not supported + :model CC-500L ; product spec (JP) :interface USB :status:unsupported @@ -101,13 +100,13 @@ :model CC-570L ; product spec (JP) :interface USB :usbid 0x04b8 0x0802 -:status:untested ; :good +:status:good :comment all-in-one :model CC-600PX ; product spec (JP) :interface USB :usbid 0x04b8 0x0801 -:status:complete +:status:good :comment all-in-one :model CC-700; product spec (JP) @@ -117,17 +116,21 @@ :model ES-300C :interface SCSI parallel -:status:untested ; :good +:status:good :comment overseas version of the GT-6000 +:model ES-300GS +:interface SCSI +:status:good + :model ES-600C :interface parallel -:status:untested ; :good +:status:good :comment overseas version of the GT-5400 :model ES-800C :interface SCSI -:status:untested ; :good +:status:good :comment overseas version of the GT-8000 :model ES-1000C @@ -136,7 +139,7 @@ :model ES-1200C :interface parallel -:status:untested ; :good +:status
[sane-devel] [patch] epkowa.desc
Russbucket russbuc...@nwi.net writes: On Monday 19 June 2006 18:29, Olaf Meeuwissen wrote: [snip] As I noticed an incorrect USB ID in epson.desc, I also attached a patch for that. The ID mentioned is the one for the GT-6600 (aka Perfection 610). Note that the Stylus CX6600 is also reported to have an ID of 0x0813 somewhere in the list archive. I didn't add this because epson_usb.c does not list it either. Does this mean the new version of Iscan will not work with a CX6600. I run the CX6600 with Iscan 1.18.0. I had to change the device ID to 0x0813 as that s what comes from the printer/scanner with the lsusb -v command Bus 004 Device 002: ID 04b8:0813 Seiko Epson Corp. and with sane-find-scanner found USB scanner (vendor=0x04b8 [EPSON], product=0x0813 [USB2.0 MFP(Hi-Speed)]) at libusb:004:002 The scanner work fine with Iscan, Kooka and xsane. The epkowa backend (part of iscan) recognises *both* product IDs as of iscan-2.0.0. As a matter of fact, I think it was your messages that prompted that change ;-) I'm on SUSE 10.0. Should I upgrade to the new Iscan?? If your current iscan (and other SANE frontends) work fine now, there is no real need to upgrade. The only thing I can think of that could make it worth your while is the new udev support but I believe that SUSE 10.0 has that part already covered with their sane package for your device. 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] Lexmark X1185 Scanner
Hello, could you give the experimental lexmark backend a try ? Here are quick instructions to build it from cvs, and run it without system-wide install. First we get sane sources and patch them to get experimental version, and compile it. cd /tmp mkdir testing cd testing cvs -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane login (type return when asked for a password). cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co sane-backends cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co experimental/lexmark cd experimental/lexmark sh link.sh ../../sane-backends cd ../../sane-backends ./configure make You have now an experimental version in /tmp/testing/sane-backends. Now to run it without install (assuming you don't change from the /tmp/testing/sane-backends directory): export LD_PRELOAD=backend/.libs/libsane-lexmark.so.1.0.17 You can now run xsane/xscanimage/scanimage from the command line. Regards, Stef
[sane-devel] Genesys Backend and Umax Astra 4700
Le lundi 19 juin 2006 19:24, mfi3 a ?crit?: Hello, I am an unhappy owner of Astra 4700 scanner. I cannot use it for some years (I am using almost only linux), since it isn't supported under my OS. A two or three years ago I had hope that my scanner will be supported by Genesys backend - but now, when backend is released, Umax Astra 4700 still isn't supported (Astra 4500 at least will be added in the future). So I started to think about selling my scanner. So it's question mainly for Genesys backend developers - are You planning to add support for Astra 4700 to Genesys backend, and are there any chances that it will be added in predictable future ? sorry for my english, and thanks in advance for reply :) Michael. Hello, adding support for it involved recording the USB activity of the windows driver, then use them to figure out hiow to operate it. Then the backend can be modified and tested. This process isn't that hard, but involves having such a scanner. Since I don't have one, I can't do it. But I you feel like doing it, I can help you in this process, and share my tools with you. Regards, Stef
[sane-devel] [patch] epkowa.desc
On Monday 19 June 2006 19:23, you wrote: snip Should I upgrade to the new Iscan?? If your current iscan (and other SANE frontends) work fine now, there is no real need to upgrade. The only thing I can think of that could make it worth your while is the new udev support but I believe that SUSE 10.0 has that part already covered with their sane package for your device. Hope this helps, It appears that SUSE works with the udev since thats how it is configured. I'll hold off on upgrading. Thanks again -- Russ
[sane-devel] Epson 3170 in Kubuntu
I sent the request for deb to avasys, Yes you are right I just looked for libkscan as a package. I also have the libkscan.so As for the url: http://kubuntuforums.net/forums/index.php?topic=5751.0 In terms of libkscan and kooka: I have a feeling they are not maintained anymore. The person who was in charge (Klaas Freitag) does not seem to be supporting these products since the newest logs on the website are from 2004. I guess I'll have to switch to another app until someone from KDE takes over this issue seriously. Thank you for your help On Monday 19 June 2006 19:36, you wrote: Adrian Jadic ja...@dallnet.net writes: Just another reminder that Iscan works on my machine. I have a feeling you understood that it doesn't. Am I wrong? No, you are right. I was indeed under the impression that iscan did NOT work for you. Sorry about the misunderstanding. To recap. Yes, as you said I installed the two iscan files from avasys and together with libsane everything went fine. (BTW why don't you also provide deb packages on the Avasys website? As there is no source for the plugin all we have is an RPM.) I'd suggest sending a short mail requesting this (with a rationale) to pipsnews at avasys dot jp. In the mean time, alien is your friend. The plugins don't do anything special before/after (un)installing, so there should be no problems. scanimage command also moves the scanner. The big mystery is why kooka and Gwenview don't work. And a bigger mystery is why they do work in SUSE 9.3 with KDE 3.5.2 and they don't work with the same KDE version on a newer kernel in both suse and Kubuntu. There is another thread on the Kubuntu forum about this issue and other people have also complained that after an upgrade to Dapper the 3170 scanner does not fire-up anymore. It appears I'm not the only one with this issue. You might want to post the URL so we can all go take a look ;-) I did a verbose debug and attaching the files for iscan and kooka Thanks for the logs but they don't say anything new. I think the problem is with libkscan (perhaps indirectly because Scim is also bleating). Another curious thing: on SUSE 9.3 I see no libkscan...is this a clue? As a package? I just checked a default 9.3 Professional install and there most certainly is a libkscan.so under /opt/kde3/lib. [snip] Still hope this helps,
[sane-devel] Epson 3170 in Kubuntu
One more question: I have a little annoyance with Iscan and I wonder if there is a way to fix it so I can satisfy my obsessive compulsive bursts..;) Every time Iscan starts it defaults the units to inches even though the system (KDE) is set to metric. Is there a way to change this so I don't have to modify that dropdown item all the time? BTW 96% of the world's population uses metric and only 4% uses imperial. Why default to imperial? Makes no sense... Thank you.
[sane-devel] Epson usb scanner hangs up
Is the scanner connected via a USB hub? If so, does it make a difference if you connect it directly to the computer? Do you have another USB interface that you could try? A different cable? Karl Heinz On Jun 17, 2006, at 6:15 AM, Ruell Magpayo wrote: Hi I need help in configuring in order for me to use my Epson AL-CX11 scanner in linux. Im not using any UI(X11,KDE,Gnome) since Im using Linux server which is all console based and im trying to setup my print and scanning server anyways I installed sane-backends-1.0.17 and my scanner is already found when issuing sane-find-scanner and scanimage -L . But when I try to issue scanimage command in console the scanner doesnft scan anything, displays the log as Tryin to write 2 bytes Wanted 2 bytes, wrote 2 bytes Tryin to read 4 bytes Read returned EOF scanimage: sane_start: End of file reached and freezes up the device, Thus causing the problem gDevice or resource busyh. I need to turn the device off-on. Ive searched all over the net for this problem and people suggested to modify/update something in ohci.c but when I look at the source for the kernel the file ohci.c doesnft exists but lots of ohci-* files. I need help on the following points; 1) what do I need to fixed this problem? 2) am I on the right track? Is it my usb that is the problem? is my research that points me to modifying usb host drver correct? (ehci,ohci,uhci) 3) where else do I need to look for solutions? Heres my some useful info: Libusb 0.1.12 Sane-backends-1.0.17 Linux kernel 2.6.15 Ubuntu server (but I donft think distro matters) thanks -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
