[sane-devel] Epson Perfection 3490 PHOTO
Oliver Schwartz oliver.schwa...@gmx.de writes: Hi, the code is in CVS now. Please try it and let me know if it works for you. I currently don't have any information on the firmware filename. Usually there is only one supplied with the windows driver. Look for any *.bin file in the twain32 directory. esfw51.bin, IIRC. -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Epson Perfection 3490 PHOTO
Olaf Meeuwissen writes: Oliver Schwartz oliver.schwa...@gmx.de writes: Hi, the code is in CVS now. Please try it and let me know if it works for you. I currently don't have any information on the firmware filename. Usually there is only one supplied with the windows driver. Look for any *.bin file in the twain32 directory. esfw51.bin, IIRC. Does all this mean that I need to load some firmware onto the scanner before I can use it, or should it work out-of-the-box with the snapscan backend? I'll try the CVS code a little later. Bjorn.
[sane-devel] Epson Perfection 3490 PHOTO
Hi, Does all this mean that I need to load some firmware onto the scanner before I can use it, or should it work out-of-the-box with the snapscan backend? Yes and no. The backend will download the firmware to the scanner automatically (as does the windows driver). See http://snapscan.sourceforge.net for more information. The firmware is only loaded into the internal RAM of the scanner. Once you switch off the scanner it is restored to it's original state. /Oliver
[sane-devel] Epson Perfection 2480 Photo: firmware loading
Julien BLACHE j...@jblache.org wrote: I've been thinking about something like this for iscan and discussed it to some extent with Johannes Meixner from SUSE. The model/vendor specific snippet for the download is a bottle neck, but otherwise we agreed that using hotplug (or similar) to trigger a firmware download was a good idea. Maybe we should just start coding :) I'm working on it, I hope to have a working loader for snapscan-supported scanners by the end of the week. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] Canon LiDE 20 vertical lines
On Sun, Aug 14, 2005 at 11:03:30PM +0200, Julien BLACHE wrote: I don't like the accusations you're making. This is not $RANDOM_DISTRO here with $RANDOM_MAINTAINER applying $RANDOM_PATCHES. The packages, as installed on my machine were, broken. The source I rolled by hand for pre-.13 were not. There was a brief period when the shipped package worked. I'm accusing nobody of anything other than 'at some point things broke'. Oh, I suppose I've also stated ...and it doesn't surprise me for various reasons that don't involve anyone's personal failings. There is a development/support model problem (not a huge one, but one that is breaking previously orking software) and I am frustrated by that. I want working things to stay working. The *hardware* hasn't changed any. Until then, shut up. And I mean it. If you had quality problems with 1.0.14 or 1.0.15 Debian packages, you should have reported that back then. Fine, I'll shut up then. It's my time and I'm uninterested in waving dicks. I wrote the code and that original code still works great for me. The rest of you can figure it out on your own. My scanner works. Terribly sorry for the offense. Monty
[sane-devel] Epson Perfection 3490 PHOTO
Oliver Schwartz writes: Hi, Does all this mean that I need to load some firmware onto the scanner before I can use it, or should it work out-of-the-box with the snapscan backend? Yes and no. The backend will download the firmware to the scanner automatically (as does the windows driver). See http://snapscan.sourceforge.net for more information. The firmware is only loaded into the internal RAM of the scanner. Once you switch off the scanner it is restored to it's original state. I see. It looks like I had to install the driver under Windows, then. Did a test scan in Windows and it worked. Then rebooted to Linux, and scanimage -L found device `snapscan:libusb:001:003' is a EPSON EPSON Scanner1 flatbed scanner and scanimage ran just fine, both the RPM version and the CVS version from 20050815. I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to /etc/sane.d and modified the firmware entry in snapscan.conf, and now it works even after rebooting both the scanner and the computer. Thank you Olaf and Oliver for the help, Bjorn.
[sane-devel] (no subject)
Hi, On Tue, Aug 16, 2005 at 02:58:24AM -, Gora Mohanty wrote: We need to support a HP 5550C Scanjet under SANE. From going through the list archives, I see that this scanner is not yet supported, but there is a note that it might be possible to adapt the genesys driver to support it. If no one else is working on that as yet, I should be able to devote some time to such a project starting from the end of this week. Please do let me know if someone has already started working on supporting this scanner. Have a look at the archive of this list and especially look for genesys and gl841. At least that's what we think the chipset is. There is ongoing discussion about the inclusion of that chipset in the genesys backend. Your scanner will need modifications, at least some code is laready there. Please send an output of sane-find-scanner -v -v of a recent sane-backends. Just to make sure it really uses a gl841 chipset. Bye, Henning
[sane-devel] Re: [sane-commit] CVS update of sane-backends (3 files)
[from sane-commit:] On Mon, Aug 15, 2005 at 06:56:55PM +, Oliver Schwartz wrote: Date: Monday, August 15, 2005 @ 18:56:55 Author: oliver-guest Path: /cvsroot/sane/sane-backends Modified: ChangeLog backend/snapscan-scsi.c backend/snapscan.c Added temporary debug code for 2480/2580 distinction -+ ChangeLog |6 ++ backend/snapscan-scsi.c | 40 +--- backend/snapscan.c |7 +-- 3 files changed, 48 insertions(+), 5 deletions(-) Maybe I'm doing something wrong but after cvs update and trying to make sane-backends I get: In file included from snapscan.c:210: snapscan-scsi.c: In function 'inquiry': snapscan-scsi.c:483: error: 'PERFECTION3590' undeclared (first use in this function) snapscan-scsi.c:483: error: (Each undeclared identifier is reported only once snapscan-scsi.c:483: error: for each function it appears in.) snapscan-scsi.c:485: warning: pointer targets in passing argument 2 of 'snapscani_debug_data' differ in signedness snapscan-scsi.c: In function 'calibrate_2480': [...] Bye, Henning
[sane-devel] [Fwd: Mustek 2400 CU Plus (PS2Dfw2.usb)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I'm using Debian Sarge 3.1r0a with sane 1.0.13-2 and sane-utils 1.0.16-1, the Mustek 2400CU Plus scanner. Well, I downloaded the PS2Dfw.usb firmware file as they say on their homepage, but managed to scan only the [distorted] half of the page. Then, I tried PS2Dfw2.usb file (diff says it's identical to what was shipped on the CD), and XSane just hangs for a short while and gives me 'Invalid argument'! Argh!!! I remember that problem existed in my previous installation, but I can't remember how I managed to fix it. Any help? - -- .---. | ^ ^ | Meow! I'm a little kitten trapped in this .signature cookie! | = v = | Let me out and I'll be your friend. | v---v | And remember: each time you use Windows, God kills a kitten! `---' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDAbtpoMxqz7LeBAgRAsmtAJ0SBfnlhnGWw5MMj8zbx5fJtEqvnQCg0uT1 IFHW5J5tRyApN27b+S9WYoU= =yQ35 -END PGP SIGNATURE- -- next part -- A non-text attachment was scrubbed... Name: yuri.vcf Type: text/x-vcard Size: 400 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050816/d88b5801/yuri.vcf From p...@smedley.info Tue Aug 16 11:18:39 2005 From: p...@smedley.info (Paul Smedley) Date: Tue Aug 16 11:19:06 2005 Subject: [sane-devel] Plustek hangs on OS/2 - part II In-Reply-To: 200508151706.09256.gerh...@gjaeger.de References: nojgv3kw.1122252543.2362200.p...@smedley.info 42f86416.5060...@smedley.info 42f88519.2050...@smedley.info 200508151706.09256.gerh...@gjaeger.de Message-ID: 4301cb8f.2080...@smedley.info Hi Gerhard! Gerhard Jaeger wrote: On Tuesday 09 August 2005 12:27, Paul Smedley wrote: Oh I forgot to mention - in the logs that 'beep' there's a return code (32772) from usbbulkread that says 'less data than requested returned'. In this case, 1 byte was requested and 0 returned. log excerpt below shows what the backend does when this occurs. [sanei_usb] sanei_usb_read_bulk: rc = 32772 [plustek] UIO error [plustek] Calibration file-name set to: [plustek] E:\tcpipapp\home/.sane/Canon-N670U_N676U_LiDE20.cal [SNIPSNAP] I also got this UIO error sometimes here on my linuxboxes, but they don't seem to disturb. Well in the meantime, I tried to figure out, when this UIO error occurs. In the end it only occurs during power-up of the scanner, directly after pluging it in. So I did some changes to the setup procedure and managed to make these UIO errors disappear on my boxes. Could you please checkout the latest CVS stuff and test on your OS/2 box? Thanks for the tar.gz of the plustek*.* Great news - the UIO error is gone - I still get a beep from the PC speaker the first time the device is accessed - however I've not seen any hangs on 10 or so scans - including unplugging/replugging the scanner to try and trigger it. Thanks for your help! Cheers, Paul.
[sane-devel] Scanning for VistA
Hi Nancy, I think your question already appeared on this list so you might have a look at the list archives. Il giorno sab, 13/08/2005 alle 09.44 -0400, Nancy Anthracite ha scritto: [...] All this leads up to my question. We have some volunteers working on developing the software to do that scanning now, and we are looking for a cross platform solution. We feel that using SANE is the logical choice, but we need some help choosing a scanner or group go scanners that can be used from both Windows and Linux and maybe even eventually with OS X as seamlessly as possible using SANE. We would like to choose scanners that have sheet feeders, and ideally, a range of scanners from high speed business to very small business type for no more than a $200. Having scanners that are easy to get running properly is much more important than having a wide range of choices. [...] Anyway I had very bad experiences using SANE on Windows with cheep scanners, mainly because these scanners require the libusb library. This library is working very well on linux but is absolutely not stable (at least for uwing it with SANE) on Windows. About scanner with ADF support, you might want to try the fujitsu (they have both USB and SCSI interface) and they are well supported by SANE, but they are expensive compared to what you asked. Regards, Giuseppe
[sane-devel] Re: Getting Mustek 1200 UB Plus scanner working
Followup # 1: - I have sane-backends-1.0.16 installed. For my RedHat 9 system the output of /proc/version , is, Linux version 2.4.20-31.9 (bhcomp...@daffy.perf.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Tue Apr 13 17:38:41 EDT 2004 SANE uses libusb and that library looks at all USB devices connected to the system. Devices are usually located in /proc/bus/usb/ . This file system must be mounted (see man sane-usb). I added this line to, /etc/fstab, none /proc/bus/usb usbfs defaults 0 0 Followup # 2: -- The scanner module is not needed anymore. You just need kernel USB support. What's the output of cat /proc/bus/usb/devices and sane-find-scanner -v -v? The output of cat /proc/bus/usb/devices, is, T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=e400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms The output of, sane-find-scanner -v , is, ... failed to open (Invalid argument) for all /dev/scanner?? BTW, the output of /proc/bus/usb/drivers is, usbdevfs hub 96-111: hiddev hid Folowup #3: SANE uses libusb and that library looks at all USB devices connected to the system. Devices are usually located in /proc/bus/usb/ . This file system must be mounted (see man sane-usb). How can I verify that the kernel is configured for USB suport, and that the devices are mounted? If not, what do I need to do, to make it so? Again thank you for your patience, I'll get my Mustek scanner working yet - I'm determined to do so! -Martin
[sane-devel] Re: Getting Mustek 1200 UB Plus scanner working
Hi, On Tue, Aug 16, 2005 at 12:22:46PM -0400, Martin wrote: The output of cat /proc/bus/usb/devices, is, T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=e400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms So your scanner is not detected by the kernel at all, only the root hub. Either the scanner is not plugged in or defective. Theoretically there could be a bug in the Linux kernel but as the root hub is detected this is rather unlikely. How can I verify that the kernel is configured for USB suport, and that the devices are mounted? It is mounted, otherwise you couldn't cat /proc/bus/usb/devices. And you have USB support, otherwise the hub wouldn't be detected. Bye, Henning
[sane-devel] Epson Perfection 3490 PHOTO
Hi, I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to /etc/sane.d and modified the firmware entry in snapscan.conf, and now it works even after rebooting both the scanner and the computer. Very good. Can you do some tests, e.g. do all resolutions work? Does the transparency unit work? Happy scanning, Oliver
[sane-devel] Re: [sane-commit] CVS update of sane-backends (3 files)
Hi, Maybe I'm doing something wrong but after cvs update and trying to make sane-backends I get: In file included from snapscan.c:210: snapscan-scsi.c: In function 'inquiry': snapscan-scsi.c:483: error: 'PERFECTION3590' undeclared (first use in this function) snapscan-scsi.c:483: error: (Each undeclared identifier is reported only once snapscan-scsi.c:483: error: for each function it appears in.) snapscan-scsi.c:485: warning: pointer targets in passing argument 2 of 'snapscani_debug_data' differ in signedness snapscan-scsi.c: In function 'calibrate_2480': [...] No, seems that was me :-( Checked in an older version by mistake. It's fixed now. /Oliver
[sane-devel] Umax Astra 2200 under OpenBSD?
I'm trying to get a Umax Astra 2200 (using USB) working under OpenBSD 3.6 using sane-backends-1.0.16. I'm not sure whether this backend tries to use libusb or not. sane-find-scanner finds a USB scanner but can't identify it. I have uscanner enabled in the kernel and the scanner gets found as /dev/uscanner0 as it seems it should. If I disable uscanner in the kernel it doesn't get found at all. /usr/src/sys/dev/usb/uscanner.c lists this among its devices but that may only be for the sake of identifying USB vendors and devices. The status of libusb is unknown. I installed libusb-0.1.7p2 from the OpenBSD ports collection, but Sane seems to not be finding or using it. Doing a locate libusb shows these files installed: /usr/local/bin/libusb-config /usr/local/lib/libusb.a /usr/local/lib/libusb.la /usr/local/lib/libusb.so.7.0 At first I didn't have libusb installed, but after installing it I did a gmake uninstall, then gmake distclean, then configured and installed Sane over again. According to sane-backends-1.0.16/README.openbsd I may have to add the vendor and device IDs to sys/devs/usb/uscanner.c and rebuild the kernel. I've made a couple of tries at that but I'm not quite sure where to put them. C isn't my favorite language, and I'm rusty at pointers to structs. It compiles and everything, but didn't seem to have any effect. I added these: 0x1606 0x0230 for vendor and device, or tried to. The machine is a Dell CPIa laptop. USB works well on it under OpenBSD, and I routinely use an external USB CD burner and a couple of those USB flash/pen drives. Those worked even without libusb. I'm not sure whether I should be trying to troubleshoot uscanner or libusb because I don't know whether libusb is used or not. It would be useful to have the backend description tell whether it uses libusb or not, but maybe it depends on the platform. Alan Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
[sane-devel] Umax Astra 2200 under OpenBSD?
Hi, On Tue, Aug 16, 2005 at 11:15:13AM -0700, alanco...@yahoo.com wrote: I'm trying to get a Umax Astra 2200 (using USB) working under OpenBSD 3.6 using sane-backends-1.0.16. I'm not sure whether this backend tries to use libusb or not. All USB backends use libusb, if available, through sanei_usb. Most backends (but not all) can also use the kernel scanner driver. sane-find-scanner finds a USB scanner but can't identify it. This means that you don't use libusb or libusb can't access the scanner. I have uscanner enabled in the kernel and the scanner gets found as /dev/uscanner0 as it seems it should. If I disable uscanner in the kernel it doesn't get found at all. /usr/src/sys/dev/usb/uscanner.c lists this among its devices but that may only be for the sake of identifying USB vendors and devices. The uscanner driver can only be used if only bulk-in and out transfers are used. Control messages or identifying devices is not supported by the BSD uscanner driver. You may need to add the USB device to umax.conf manually. The status of libusb is unknown. I installed libusb-0.1.7p2 from the OpenBSD ports collection, but Sane seems to not be finding or using it. Doing a locate libusb shows these files installed: /usr/local/bin/libusb-config /usr/local/lib/libusb.a /usr/local/lib/libusb.la /usr/local/lib/libusb.so.7.0 At first I didn't have libusb installed, but after installing it I did a gmake uninstall, then gmake distclean, then configured and installed Sane over again. Is /usr/local/include/usb.h available? The SANE configure script prints the libraries it has find near the end of its output, -lusb should be there. According to sane-backends-1.0.16/README.openbsd I may have to add the vendor and device IDs to sys/devs/usb/uscanner.c and rebuild the kernel. I've made a couple of tries at that but I'm not quite sure where to put them. C isn't my favorite language, and I'm rusty at pointers to structs. It compiles and everything, but didn't seem to have any effect. I added these: 0x1606 0x0230 for vendor and device, or tried to. I recommend to not use the kernel scanner driver at all. You scanner should be detected as /dev/ugen0 or similar when uscanner is not enabled. That device can be used by libusb. I'm not sure whether I should be trying to troubleshoot uscanner or libusb because I don't know whether libusb is used or not. It would be useful to have the backend description tell whether it uses libusb or not, but maybe it depends on the platform. Bye, Henning
[sane-devel] Re: [sane-commit] CVS update of sane-backends (3 files)
Hi, On Tue, Aug 16, 2005 at 07:21:15PM +0200, Oliver Schwartz wrote: No, seems that was me :-( Checked in an older version by mistake. It's fixed now. Ok, now I get this: In file included from snapscan.c:213: snapscan-options.c: In function 'init_options': snapscan-options.c:236: error: syntax error before '/' token I think that's a // which is not accepted by older compilers and by gcc with all warnings enabled. gcc --version gcc (GCC) 4.0.2 20050806 (prerelease) (Debian 4.0.1-4) Bye, Henning
[sane-devel] Epson 2480 Transparency Unit - not for me 8-(
Hi everybody, I replaced the firmware 1.14 with the 1.16 I received (thanks Simon and Ken), but I have no change in the behaviour of my scanner. When I address the transparency unit, it runs into a loop. The debug ends repeating the attached block below over and over. Any Ideas, any advice? thanks, Reinald [snapscan] atomic_usb_cmd(0,0x81dd3b8,66,0x0,0x0 (0)) [snapscan] usb_cmd(0,0x81dd3b8,66,0x0,0x0 (0)) [snapscan] usb_cmd: cmdlen=10, datalen=56 [snapscan] usb_write: writing: 0x24 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x38 0x00 [snapscan] Written 10 bytes [snapscan] usb_read: reading: 0xf8 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] usb_write: writing: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x30 0x00 0x00 ... [snapscan] Written 56 bytes [snapscan] usb_read: reading: 0xfb 0x02 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] usb_request_sense [snapscan] usb_cmd(0,0xbfffcb00,6,0xbfffcae0,0xbfffcad4 (20)) [snapscan] usb_cmd: cmdlen=6, datalen=0 [snapscan] usb_write: writing: 0x03 0x00 0x00 0x00 0x14 0x00 [snapscan] Written 6 bytes [snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] usb_read: reading: 0xf0 0x00 0x02 0x00 0x00 0x00 0x00 0x0b 0x00 0x00 ... [snapscan] Read 20 bytes [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] sense_handler(0, 0xbfffcae0, 0x8163f68) [snapscan] sense_handler: sense key: 0x02, asc: 0x04, ascq: 0x01, i1: 0x04, i2: 0x00 [snapscan] sense_handler: Not ready. [snapscan] sense_handler: Logical unit is in process of becoming ready. (4 seconds) [snapscan] sense_handler: Not ready. Am Dienstag, 16. August 2005 05:42 schrieb Ken Ramey: Great news!! Using Simon's firmware file results in a good scan with the transparency unit without colored bands! Thank you, Simon!! ken
[sane-devel] Epson 2480 Transparency Unit - not for me [Reinald Kirchner]
Reinald; I don't mean to be insulting, but did you remember to change snapscan.conf to point to the newer version of the firmware file? Also, depending on your particular installation, the firmware (along with the .conf file) may need to be in either /usr/local/etc/sane.d or /etc/sane.d. Because of all the testing I did of different vesions of everything, I wound up with files in both places and it took me a few tries to realize that my current installation is looking for the firmware and the conf file in /usr/local/etc/sane.d. instead of in /etc/sane.d Hope that helps. ken
[sane-devel] official ZETA port diffs
Hi, On Tue, Jul 12, 2005 at 03:58:09PM +0200, Fran?ois Revol wrote: - we don't have a libusb port, and I had a sm3600 around, so I ported the backend over to sanei (was it some kind of foreign code not fully ported ??), The sm3600 backend has been changed to use sanei_usb now instead of libusb directly. I've based the change in CVS on your patch. Thanks again! Bye, Henning
[sane-devel] Re: [sane-commit] CVS update of sane-backends (3 files)
Hi, In file included from snapscan.c:213: snapscan-options.c: In function 'init_options': snapscan-options.c:236: error: syntax error before '/' token Fixed, thanks for testing. /Oliver
