[sane-devel] Including the NIASH Backend...
Hi, On Thu, Jul 22, 2004 at 09:52:59AM +0200, Gerhard Jaeger wrote: Question: Why is it still not included? Because the niash maintainer hasn't told us to do so :-) If the backend is still maintained and the problems mentioned here: http://lists.alioth.debian.org/pipermail/sane-devel/2003-December/009756.html are solved I don't see a reason not to include it. Bye, Henning
[sane-devel] umax.desc problem
Hi, On Tue, Jul 20, 2004 at 01:08:19PM +0200, jose wrote: Hi, I have making a data base of scanner using the info in the desc files and I have found this problem in umax.desc: :model Jade :interface SCSI :status :good :comment OK, SCSI-ID=LinoHell Office :model Jade :interface SCSI :status :good :comment OK, SCSI-ID=LinoHell JADE both scanners looks the same and only have a comment diference, I dont know the reason of that but I have problems with the scripts, cause they dont know if there are 2 differents scanners. The scanners have the same name but use different SCSI ids. That's not too unusual. Maybe in other cases the different models are supported by different backends so it only happens in this special case. But I think the .desc is valid. Bye, Henning
[sane-devel] 'scanner busy' 'no devices found' etc.
Hi, On Sat, Jul 17, 2004 at 03:14:31PM +1000, Graeme Nichols wrote: I upgraded my RH8 system to FC2 day before yesterday and today I have been tidying up the install and setting my preferences and testing all my hardware. I ran Kooka and did some test scans and all were OK. I then tried scanimage which bash complained about. 'rpm -qi sane' resulted in the reply 'package sane not installed'. So... Kooka doesn't use sane it appears. That would explain why kooka worked before and scanimage didn't. Kooka must have its own backend etc. Are you sure? I rather think that sane contains frontends like xscanimage and scanimage and the actual backends are in sane-backends or Libsane. At least that's the case on Debian systems. Bye, Henning
[sane-devel] 'scanner busy' 'no devices found' etc.
Hi, On Wed, Jul 14, 2004 at 12:30:57PM +1000, Graeme Nichols wrote: The command '/sbin/fuser -v /dev/usb/scanner0' produces no output. My idea was that some application (e.g. a kde program) blocks the scanner and kooka can somewhow handle that but xsane can't. Usually if frontends behave that differently there are two versions of sane installed on the same system. And 1.0.8 is quite old anyway so make sure that you don't use 1.0.8 with scanimage/xsane and 1.0.something with kooka. Does scanimage -L show your scanner? No, the output follows:- [graeme@barney graeme]$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). SANE_DEBUG_EPSON=255 scanimage -L should show some debug messages. Bye, Henning
[sane-devel] Chinon DS-3000
Hi, On Tue, Jul 13, 2004 at 09:13:05AM -0400, James A. Littlefield wrote: I am probably the last person in the world who still has a working Chinon DS3000 scanner!It is, I think, about 15 years old. I have a working linux interface program and propose to make a sane backend for this scanner. Nice! I'll add that scanner to our lists and point users to you. Well, if there are any other users of that scanner in this universe :-) I have been reading the API documentation and FAQs and have installed the sane-devel rpm on my RH9 system. Better use sane-backends from CVS. Any other guidelines/resources/recommendations before proceeding w/ my DS3000 backend development? Looking at the source code of other backends may help. Please tell us once you have some code or a webpage we can link to. This is a list of serial devices supported by SANE: http://www.sane-project.org/cgi-bin/driver.pl?manu=model=bus=ser Bye, Henning
[sane-devel] Please subscribe to sane-devel if you post to this list
Hi everyone, This is just a reminder to everyone: Please subscribe to this list before posting to it. And please use the same address for subscribing and sending mails. Mails sent to this list by authors who aren't subscribed will be put on hold and wait for moderator approval. As this moderator doesn't permanently check the website for new hold posts, approval can take some time. So if you want to discuss, please subscribe so I don't have to moderate every second post. Bye, Henning
[sane-devel] problems in one or more man pages you maintain
Hi Eric, On Mon, Jul 12, 2004 at 11:12:54AM -0400, e...@thyrsus.com wrote: This is automatically generated email about problems in a man page for which you appear to be responsible. If you are not the right person or list, tell me and I will attempt to correct my database. Thanks for your report. Both sane-coolscan2.5 and sane-microtek2.5 have just been fixed in SANE CVS. If you don't get answers for the other sane-* manpages from their respective authors, you can also forward your patches for those files to sane-devel@lists.alioth.debian.org. Bye, Henning
[sane-devel] Canon LiDE30
Hi, On Mon, Jul 12, 2004 at 03:53:19PM +, Nobody Here wrote: I'm having trouble using my scanner. I've read the sane, sane-usb, and sane-plustek man pages, and looked for help at the quiet IRC channel. My scanner is found and correctly identified by sane-find-scanner, but not listed by scanimage -L . Even not as root? It is a CanonLIDE30 . To help it out, I edited the plustek.conf to tell it: device libusb:002:005 Don't do that. Next time you replug the scanner or you reboot the device number may be different. What's the output when you enable debugging (as root)? SANE_DEBUG_PLUSTEK=255 scanimage -L Bye, Henning
[sane-devel] sane.h misses extern C
Hi, On Mon, Jul 12, 2004 at 10:00:53AM +0200, Rene Rebe wrote: Is there a good reason why the installed sane.h misses the usual header lines needed for compilation with C++? Well, it's a C and not a C++ header and these #ifdefs are ugly :-) Isn't it a better solution to use the extern C when including the file in the C++ .C code if you really want to use sane.h in C++? Or do we get trouble this way because it includes the structs? May I just commit them to CVS? Please wait some time before doing that. Maybe someone else can tell us real reasons not to use the extern C stuff. Bye, Henning
[sane-devel] Problems with SANE 1.0.13 and HP ScanJet 5300C
Hi, On Tue, Jul 06, 2004 at 08:49:15PM +0200, Thomas Rösch wrote: I searched with Google and found many hints how to get a HP ScanJet 5300C to work with SANE, but I was either too stupid to apply the hints or they did not work at all. Having a look at the man page may also help :-) SANE-FIND-SCANNER as root: found SCSI scanner HP ScanJet 5300C 6.00 at /dev/sg0 Ok. found USB scanner (vendor=0x03f0, product=0x0701) at libusb:003:002 Also ok. SCANIMAGE -L as root: device `avision:/dev/sg0' is a Hewlett-Packard ScanJet 5300C flatbed scanner Looks fine. SANE-FIND-SCANNER as user: # No SCSI scanners found. If you expected something different, make sure chmod a+rw /dev/sg0 Or, if you use devfs, read man sane-scsi. found USB scanner (vendor=0x03f0, product=0x0701) at libusb:003:002 Still found as USB device. SCANIMAGE -L as user: No scanners were identified. If you were expecting something different, Probably the above mentioned permission problem. Obviously, SCANIMAGE does only detect a SCSI scanner, but I connected my scanner with USB and I even do not have a SCSI port in my PC. Your scanner is still a SCSI scanner. In fact, it's SCSI-over-USB. Also as a normal user SCANIMAGE does not find any scanner which seems to be an authorization problem. Yes, see above. Explanation: There is a Linux kernel driver (hpusbscsi) that emulates a SCSI device. So you can just use your scanner as if it were a SCSI device. The driver sends the SCSI commands through the USB. That's the reason why the scan applications think that your scanner is a SCSI scanner. Have you actually tried to scan with scanimage as root? As your scanner is also a USB device, it's also listed in the USB section of sane-find-scanner. As the scanner is calimed by the kernel driver hpusbscsi, you can't use it as a normal SCSI deveice as long as that kernel driver is loaded. That's the reason for the device busy messages in the log file. IIRC the debug messages even mention that a possible reason for this error is that a kernel driver is loaded. At least with sane 1.0.14 you can either use the hpusbscsi driver or direct USB access. If hpusbscsi doesn't work for you, rmmod that driver and try without. But when I start e. g. XSANE (0.92) I receive the message no devices available and the program closes again (it does not matter if I run it as root or as normal user). That's strange as usually SANE frontends behave the same way. Are you really sure that you run xsane as root? Bye, Henning
[sane-devel] Canon LiDE30
Hi, On Mon, Jul 12, 2004 at 07:09:39PM +0200, Thomas Rösch wrote: I have exactly the same problem with my HP ScanJet 5300C. It's a different scanner, a different backend and a different kernel. I'd be extremely surprised if it were the same problem. Bye, Henning
[sane-devel] 'scanner busy' 'no devices found' etc.
Hi, On Sun, Jul 11, 2004 at 04:03:30PM +1000, Graeme Nichols wrote: Hello Folks, I have been happily using xsane to do my scanning for quite a while. Now, for some inexplicable reason, when I start xsane it comes up with 'no devices available' If I enter the command scanimage -d epson:/dev/usb/scanner0' I get the error message 'scanner busy'. If I run 'sane-find-scanner' it tell me that it found the following:- Device busy? That usually means that another application or driver is using the scanner. Maybe some KDE stuff is locking the scanner in the background? To find out which application is blocking your scanner try that: fuser -v /dev/usb/scanner0 Does scanimage -L show your scanner? - The contents of this email and any attachments, which may be con- - - fidential, are sent for the personal attention of the addressee/s - - only. If you receive this email and are not the intended addressee - - please inform the sender and delete this email immediately. Use, - - copying, disclosure or forwarding of the contents of this email- - and/or any attachment/s is not authourised.- Such footers are rather stupid anyway but when sent to public mailing list they are just ridiculous. I know, it's done automatically by the mail gateway, but still... Bye, Henning
[sane-devel] Click by epson perfection 1260
Hi, On Sat, Jul 10, 2004 at 01:19:48AM +0200, paolo wrote: !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN Please don't use HTML on this list. I use suse 9.0br xsane 1.10 or kooka (kde)br xsane 1.10 doesn't exist yet. Which version of SANE do you use (scanimage --version)? but with preview or final scan I listen a click and after ten seconds a message appearsbr br /fontfont face=Times New Roman, Times, seriferrorb during readingbr error during I/O on periferal br If you use SANE 1.0.14, edit /etc/sane.d/dll.conf and comment out epson. Unplug and replug your scanner and try again. Bye, Henning
[sane-devel] Re: [save-devel] xscanimage font problem
Hi, On Fri, Jul 09, 2004 at 05:13:58PM -0700, Gene Stemple wrote: Progress... Installed new libc6 (version 2.3.2.ds1-13)... o.k. Installed matching locales (ver. 2.3.2.ds1-13) and then configured for support of en_US ISO-8859-1 AND en_US.UTF-8. Tried export LANG=en_US.UTF-8 (and ..-ISO-8859-1) prior to xscanimage microtek2:/dev/sg1 Try LC_ALL=C xscanimage. Bye, Henning
[sane-devel] scanner buttons
Hi, On Fri, Jul 09, 2004 at 09:21:01PM +0200, Rene Rebe wrote: Regarding SANE 2: Do you have any idea if coding on it will ever start ,-)? I mean, how long are we discussing proposals already? We can only start coding when the standard is finished (or at least the critical points are finished). While we have discussed some points I haven't seen a formal proposal (e.g. patch) for those point. IIRC there was no solution for generic error messages, generic message boxes and callbacks. But you've convinced me to summarize the open points/discussions and the (IMHO) open bugs in the stabdard. Hopefully I'll find time this weekend. Bye, Henning
[sane-devel] [ANNOUNCE] New mailing list for discussing the SANE standard
Hi everyone, I've just created a new mailing list: sane-stand...@lists.alioth.debian.org. Description: sane-standard -- Discussion about the SANE standard sane-standard is used to discuss about the SANE standard. Topics are the development of the new standard version 2 and missing features and bugs in existing SANE standards. See our mailing list page for details: http://www.sane-project.org/mailing-lists.html The idea is to keep away the massive amount of discussions that usually occur when the standard is the topic from sane-devel. If you are interested in finishing SANE 2 (e.g. button support, generic error messages etc.) please subscribe to that list. I'll also currently in the process of updating the SANE2 documentation and TODO pages. Bye, Henning
[sane-devel] different outputs
Hi, I'm cc'ing sane-devel again. YOu'll get more answers if you write to the mailing list, not only to me :-) On Sun, Jul 04, 2004 at 11:00:10PM -0700, j d wrote: Here is the sane output, Can you please also show us the /proc/bus/usb/devices output as you said they were different? now can you anyone tell me, what are those bRefresh and bSynchAddress are meant for? At least the first one is explained in the USB specification. configuration 0 bLength 9 bDescriptorType 2 wTotalLength 76 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 100 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x88 (in 0x08) bmAttributes 1 (isochronous) wMaxPacketSize0 bInterval 1 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 altsetting 1 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x88 (in 0x08) bmAttributes 1 (isochronous) wMaxPacketSize0 bInterval 1 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 Note: please forgive me for excluding the vendorid and product id, i am not permitted to let know anyone as per the copany which is allowed me to do my academic project, hope you understand, thank you Sound quite strange :-) Bye, Henning
[sane-devel] problems getting network access to scanner..
[cc'ed to sane-devel] Hi, On Tue, Jul 06, 2004 at 08:51:33AM +1000, debian-lap...@lists.debian.org wrote: Does the connection closed happen immediately? yes it does, I presume this is bad? Yes. saned isn't even started. So the machines seem to be talking.. Check the syslog of the server for messages. nothing appears in syslog.. That means that saned isn't running. Does it work if you disable saned in inetd.conf and run it manually (saned -d128)? [net] connect_dev: net_init (user=(null), local version=1.0.3) [net] connect_dev: argument marshalling error (Connection reset by peer) Strange. I'd expect [net] connect_dev: [0] failed to connect (Connection refused) if saned didn't run. Are you sure that the program that is run from saned is really saned? For me it looks like it's a script or other program that sends garbage to stdout. Bye, Henning
[sane-devel] Experience with brother backend?
Hi, On Mon, Jun 28, 2004 at 07:06:45PM +0200, Henning Meier-Geinitz wrote: Has anyone already tested the brother backend? Link: http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html As I haven't received a single positive report (and one negative) I've added all those scanners as untested to our lists now. Bye, Henning
[sane-devel] Some genesys logic backend questions...
Hi, On Fri, Jul 09, 2004 at 09:18:06AM +0200, Gerhard Jaeger wrote: I'm currently looking over the genesys logic backend and found that there are a lot of todo remarks inside. One of the is concerning the scanner_constanst structure, which is more or less the same like the Genesys_Model structure - is this correct? One comment there says - move to model settings The original approach was the scanner_constants structure. As the backend should support more than one scanner I added the more complete Genesys_model structure. That structure is based on the gt68xx code. So the idea is to move all scanner-dependent constants to Genesys_model. Also these constants should be in a usable unit/format, e.g. mm for the borders and not points at some resolution. As I haven't understand all the values of scanner_constants yet I haven't moved them. The idea was to get it scanning first and then clean up the code. Bye, Henning
[sane-devel] Support for the Plustek OpticPro ST24 (genesys-backend)
Hi, On Tue, Jul 06, 2004 at 08:56:09AM +0200, Gerhard Jaeger wrote: would you mind if I patch the genesys_low.c file to support the Plustek OpticPro ST24? The Patch only adds the base values for this device. Afterwards it's recongnized. At least I don't mind. Adding devices can be done by everyone. Only if bigger chunks of the code are deleted, please ask here :-) One question? Is there an easy way to switch off the calibration? It seems, that the scanner starts, does something and the fails, when reading a buffer. Same here. Once I tried to avoid the calibration but scanning didn'Ät work that way either. I think something is missing there. Bye, Henning
[sane-devel] sane-desc to xml (new patch)
Hi,
On Mon, Jul 05, 2004 at 11:45:47AM +0200, Jose Gato wrote:
Hi again, I have a new patch for the XML output of sane-desc:
- Now the XML document have a XML root.
- New tag for the document marked as new.
- Some bug fixed...
I have being using the XML output for make a perl parser and have all
the information in a sql database so I think the xml is correct.
It's in CVS now with some changes. See below for comments. Please test
if I haven't broken anything.
- Copyright (C) 2002-2004 Henning Meier-Geinitz henn...@meier-geinitz.de
+ Copyright (C) 2002, 2003 Henning Meier-Geinitz henn...@meier-geinitz.de
I didn't apply this part of the patch obviously :-)
+static char *
+clean_string(char *c)
+{
+ /*not avoided characters*/
+
+ char *aux;
+
+
+ aux=malloc(strlen(c)*sizeof(char)+100);
Oh, if *c has quite a lot of illegal chars that could break. I used
strlen(c)*sizeof(char)*6 now (length of longest encoding). If you know
something nicer...
@@ -1622,82 +1667,88 @@
backend_entry *be;
be = first_backend;
+ printf(backends\n);
while (be)
{
url_entry *url = be-url;
type_entry *type = be-type;
+ clean_string(be-name);
I've removed that last line. Please correct me if it was intentional.
Bye,
Henning
[sane-devel] Re: sane-devel digest, Vol 1 #398 - 7 msgs
Hi, On Mon, Jul 05, 2004 at 07:32:44AM -0400, Fritz Lang wrote: Hi, On Sun, Jul 04, 2004 at 11:37:05AM -0400, Fritz Lang wrote: I have a G3 450Mhz running Panther.3.2 on OEM video card. That's the interesting part of the log: That's the part of the mail I wrote. If you don't use quote characters () it's quite difficult to find out which part of the mail is written by you and which is just a quote. then there's this, but perhaps I've entered it wrong? sudo grep epson /etc/sane.d/dll/conf The file name is dll.conf not dll/conf. [sanei_debug] Setting debug level of epson to 255. [...] [epson] sane_init, usb Ok, that's your usb line. [epson] attach_one_usb() [epson] SANE Epson Backend v0.2.41 - 2004-02-01 [epson] attach(, 3) [epson] attach: opening [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0101 [epson] attach_one_usb(libusb:001:002-04b8-0101-ff-ff) [epson] SANE Epson Backend v0.2.41 - 2004-02-01 [epson] attach(libusb:001:002-04b8-0101-ff-ff, 3) [epson] attach: opening libusb:001:002-04b8-0101-ff-ff [sanei_usb] sanei_usb_open: trying to open device `libusb:001:002-04b8-0101-ff-ff' usb_os_open: 04b8:0101 usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access usb_set_configuration: called for config 1 USB error: usb_set_configuration(SetConfiguration): device not opened for exclusive access [sanei_usb] sanei_usb_open: libusb complained: usb_set_configuration(SetConfiguration): device not opened for exclusive access Looks like another application tries to scan at the moment. I remember that there was some discussion about that problem on MacOS X in this list. I don't remember the details, maybe a libusb problem? Try to find it in the sane-devel mailing list archive. Bye, Henning
[sane-devel] [frontends] scanadf no-overwrite patch
Hi, On Tue, Jul 06, 2004 at 01:35:29AM -0600, Paul Walmsley wrote: scanadf happily overwrites existing image files. This patch adds a command-line flag that will prevent scanadf from doing this. Thanks. I#ve applied your patch. I've only removed the no_overwrite variable as it doesn't seem to be used. I haven't checked but couldn't that option be also useful for scanimage? Bye, Henning
[sane-devel] USB-Scanner Medion 3810
Hi, On Tue, Jul 06, 2004 at 03:53:44PM +0200, Georg Halfas wrote: I'm working with the above mentioned scanner but I can't get it running with SuSE-Linux 9.1. As I could not find support within my distribution I tried to find out which scanner it exactly is with 'sane-find-scanner'. The result was: found USB scanner (vendor=0x0461, product=0x037b) at libusb:001:002 Could you please send us the result of sane-find-scanner -v -v? The USB-ID-list on 'www.linux-usb.org/usb.ids' says that it seems to be a Primax sanner but the device number is not mentioned in that section. The scanner is most probably not supported. The command: scanimage -L stated 'No scanners were identified' Does anybody has any solution I could try out? Start writing a backend. See our website for documentation on how to do that. Bye, Henning
[sane-devel] discussion: Future of SANE-project
Hi, On Tue, Jul 06, 2004 at 10:00:46AM -0400, David N. Paules wrote: I subscribed to this developer list to monitor and hopefully contribute to getting my lame UMAX Astra 2100U working natively on Mac OS X. Apparently that will never happen. I then noticed lots of messages about Epsons, and other 'big name' scanner vendors. This got me to wonder. While the SANE project is a fascinating and honorable goal, is anyone selling the benefits of SANE to the scanner manufacturers? There is a page pointed to manufactureres on our website: http://www.sane-project.org/manufacturers.html If you have any additions/corrections or comments, feel free to tell us. My point is that this project will constantly have to be supported from people like myself who are irritated that their scanner doesn't work on different hardware/ OSes than what the maker originally intended (or cares about). The problem with scanners in comparison to other hardware is that there are so many different chipsets and there is no standard for communicating with scanners. E.g. there is not even a way to identify a scanner on the USB. So you really have to start from scratch for every new chipset. However, if the SANE architecture is so much better than existing dominant TWAIN architecture, then someone should be pitching this story to the scanner manufacturers. If Epson, HP, UMAX, Dell, Primax, etc. agree to support this open source initiative (i.e, provide SANE backends), Epson does, Brother does. Mustek did for one scanner. Others provide information and support to SANE developers. the hope is that their scanners will be better supported on more hardware, reaching more customers and improving satisfaction with EVERY customer. That's what I tell manufacturers when I ask for information/source code etc. Otherwise, the developers on the SANE project will always be writing backends for 'old' scanners. In effect, they will ALWAYS be playing catch-up with what already works on at least one OS and driver config. Unfortunately some manufacturers seem to think that ~90% of the market is enough for them. So there is no reason to support non-Windows systems. Maybe this changes if MS Windows market share is only 80, 70 or 50%. The other option is to get the SANE architecture to be a standard on *nix boxes which means getting developers of the various *nix OSes to bundle pre-compiled SANE with their OS. I think that's pretty much the case. On the other hand, is there any commercial *nix (but MacOS X) that really has a bigger market share? Servers usually don't have scanners... Bye, Henning
[sane-devel] discussion: Future of SANE-project
Hi, On Tue, Jul 06, 2004 at 12:12:16PM -0400, m. allan noah wrote: that said, even if someone had the time to run around and convince vendors of the merits of sane, there would be at least two recurring sentiments: I'm not sure if these are real problems. While the manufacturers (or anyone else) may want to have such features, the bigger reason is in my opinion that the market share of non-windows systems is just to small and TWAIN simply works. Development is expensive... 1. sane spec is not complete, cause it does not support various LEDs, LEDs should be possible without trouble. buttons or sensors that the manufacturers believe add so much value (and brand distinction) to their products. If you really want Buttons are possible without violating the standard (see other discussions). 2. they are going to want more control over the gui so they can do things like show pictures and diagrams of the scanner, which means they are going to write their own front-end half the time. XSane can at least display a logo of the manufacturer :-) Anyway, they could use xsane or any other frontend and modify it to their needs. Well, they have to provide source but I don't think that's a problem in this case. 3. closed-source backends are much harder to debug/extend than free, even if you have the vendor to complain to. That's true but I guess most companies haven't found out that this is not only a disadvantage for their users but also for them. If the manufacturers really disliked SANE so much I guess they would just make their own standard on *nix. By the way: What about vuescan? Is that software programmed in cooperation with manufacturers? Do manufacturers provide vuescan on their driver discs? Bye, Henning
[sane-devel] discussion: Future of SANE-project
Hi, On Wed, Jul 07, 2004 at 11:45:50AM -0400, David N. Paules wrote: Perhaps I misunderstood SANE's goals. From what I've seen, the backends do not dictate what the front-ends look like, Right. only their capability. The capability of the scanners/backends. They don't dictate what the frontends do with the data (e.g. color correction...) or which options they do not display either. I don't understand why the bluster about multiple front-ends and more control over the gui. I was under the impression that one sane backend for a device will support multiple applications (front-ends) such as image capture, OCR, digital camera photo image acquisition, video acquisition from a digital camcorder, etc. True. But one of the ideas of SANE is to avoid writing one frontend per scanner as it is the case with TWAIN. Besides, the SANE project is open for review/suggestions for enhancement, so why not get some feedback from scanner makers on what makes SANE a non-option for the future? What 'minimum requirements' are missing from the current architecture? Go ahead and ask them! I can see your point about GPL'd backends. I agree it is easier to debug and extend them. But here's my point: Do you want to be the one always repairing and fixing scanners to work with SANE? Or do you want all the manufacturers to feel responsible for ensuring SANE compliance? If SANE is architected intelligently (i.e., backwards compliance with older backends), open source backends may not be necessary. Binaries are alway a problem. Think of new hardware platforms, changes in the kernel etc. And experience shows that manufacturers don't really care about their binaries once the devices are older than a few years. I constantly get questions from Windows users if I can send them a driver for their scanner for Windows 2000, XP whatever new Windows system. The reason is that the manufacturer doesn't provide the drivers for these systems and the old drivers don't work. The manufacturers will currently see the SANE org as a free resource for reaching other markets they didn't officially target (i.e. the *nix markets). There is no urgency or requirement for them to support SANE just because the project is open source. In fact, that is the number one reason they will NOT be concerned. 'Those hackers at SANE-project.org will make my device compliant with their software. And I don't have to pay for it.' If one of those hackers has already written a backend that assumption is true. But as there many unsupported devices that will probably not supported in future (e.g. many Canon and Microtek devices) manufacturers should have found out years ago that it doesn't work automatically. In many cases the backends that are part of SANE at the moment are based on some sort of data provided by the manufacturers or even based on their code. Some of the manufacturers that don't provide backend nor data should have found out that backends don't mystically appear :-) But, if the ultimate goal of SANE is to supplant TWAIN as the standard for accessing image devices, I'm not sure if SANE has a goal apart from providing a standardized interface to raster image hardware. My personal view is that I don't mind if SANE also runs on Windows (it does) but I won't put any effort into this. I just don't care. shouldn't more effort be put on making SANE the future standard. This route will cause scanner makers and their support network to conciously choose to either support or not support the new standard. The SANE project's developers should then concentrate on enhancing the architecture, ensure backwards compatibility, create and market compliance badges, There have already been some discussions about SANE compliant logos: https://alioth.debian.org/tracker/index.php?func=detailaid=300269group_id=1308atid=410366 create plugins for Adobe products (like existing TWAIN plugins), etc. and not write new backend modules for each new device that comes on the market. Free software developers usually do stuff that's interesting for them in some way. For me it looks like that Windows stuff is rather uninteresting for most of us. Perhaps working examples demonstrating how scanner makers can leverage their investment in TWAIN support while migrating to SANE might be useful for getting scanner makers to take notice of SANE. If an upgrade path was readily shown, techno-geeks at the manufacturer might prefer and sell the SANE idea to managers within the company. Please provide facts/information/data. I'll add it to our website. Formal propoganda of industry heavyweight support (a consortium of scanner makers and front-end application development houses) on the web-site might make other makers feel the need to join in. I don't like propaganda at all. I don't mind pointing to facts. Without this kind of direction, I simply see SANE as being a hobbyist-level effort which is why I questioned the future of it. SANE is (mostly)
[sane-devel] USB-Scanner Medion 3810 is actually a Medion MD 6190
Hi, On Wed, Jul 07, 2004 at 04:57:14PM +0200, Georg Halfas wrote: Am Mi, den 07.07.2004 schrieb Gerhard Jaeger um 10:25: Hi, regarding the results of our search-engine, which should always be consulted, the scanner is marked as not supported. Is there any support in sight. I mean this is a scanner sold by Aldi in Germany at a quite cheap price. So there might be a lot of people having the same problem as I do. That's good because that means that there are many people who can help you writing the backend. Have you already started? In this case I'd add a link to your web page where some more info or even code for the backend is found. In case you don't get what I'm talking about: :-) Backends for completely new chipsets are usually written by someone who owns such a device. Most of the time the current SANE developers don't start writing completely new backends as maintaining the older ones (and adding scanners to those) takes already wuite a lot of time. Documentation about writing backends can be found at the Contrbuting section of our website. Bye, Henning
[sane-devel] Drive question
Hi, On Fri, Jul 09, 2004 at 08:59:25AM +0800, walker.c...@microtek.com.tw wrote: My name is Walker Chen and I am a drive engineer. Welcome! I have some question about sane-devel and hope you can give me a hand. I have some drive on my hand and I have to make it could be executed by xsane. By drive you mean a scanner? But I don't have any idea about make it work by xsane and which drive source should be built in the .so. Because of the my scanner driver source is classified so I can't give you my scanner source code. You can use the SANE standard and write binary-only (non open source) backends. The standard itsself is public domain. Id on't recommend to do this, however, as it will always cause trouble as the binaries only run on one platform etc. Other options: Use a specification that describes all details of that scanner including how to actually scan. Build a SANE backend based on this spec. This way you won't need the original source. If you don't have such a spec yet, ask someone to write such a spec based on the code. SOmeone else can then write new code based on the spec... Pretty complicated. So the easiest way is to use the original code and make sure that it can be GPLed. Keep in mind that for SANE you only need the actual drive code, not the TWAIN application/GUI code. There are examples of free software backends by scanner manufacturers, e.g. Epson and Brother. These companies use binary-only libraries for some code they think is really really confident but the remaing stuff is open source. I don't like it but it's better than completely closed. If you can provide more info about which scanner you are talking and what you want to do exactly maybe we can help better. There is also some information for manufacturers here: http://www.sane-project.org/manufacturers.html Bye, Henning
[sane-devel] scanner buttons
Hi, On Fri, Jul 09, 2004 at 03:35:47PM +0200, Rene Rebe wrote: I also think we need some callback stuff for warmup notification. Hm - maybe callback stuff are too much changes for 1.x - maybe we should finally start working on SANE 2? There is no way to add callbacks to 1.0. In my last mail I already wrote that the HP 74xx have buttons to change the scan mode and copy count - this are also use cases where the option changed callbacks come handy. Callbacks are really difficult to implement (if not impossible) in SANE due to its network protocol. Unfortunately callbacks for options and messages and also the printing of generic information messages is not that easy. Please, everyon reread the older threads about that. I've also forgotten half of the details :-) bye, Henning
[sane-devel] scanner buttons
Hi, On Fri, Jul 09, 2004 at 09:45:03AM -0400, m. allan noah wrote: Hm - maybe callback stuff are too much changes for 1.x - maybe we should finally start working on SANE 2? can we do callbacks via options? thinking about a gui front-end: what about an 'led' that is red while the lamp is off, yellow when warming, and green when it is hot. this could be done via a read-only option that has a polling capability set. the front end could just loop thru all the options with poll set, and change the interface. if you gave that option a well-known name, like 'lamp-status' then the front-ends could do majic things like wait for it to become ready before displaying the scan button. That's an idea I like. In my last mail I already wrote that the HP 74xx have buttons to change the scan mode and copy count - this are also use cases where the option changed callbacks come handy. can you think of a case where a call-back is required? (i want to avoid them, if possible.) Warm up time 30 seconds - [BUTTON: Cancel]. E.g. if you know that the scanner is already warmed up. In this case a more intelligent warm-up code may be better :-) Bye, Henning
[sane-devel] scanner buttons
Hi, On Fri, Jul 09, 2004 at 10:09:45AM -0400, m. allan noah wrote: ok, here's a crazy idea- why not just reload the entire option array every few seconds? the backend then gets to decide what order to reload them in (i.e. load the 'mode' switch first, then change all the mode params, then load the 'scan' button press). is this nuts? Yes :-) Don't forget that option values may be bigger than a view bytes. E.g. gamma tables. And SANE also works over the net and constant polling of all options seems rather useless for me. I think it's not that complicated to mark the options whose values can change by hardware (buttons, switches, lamp status, what else?) You could use this auto-poll-every-option mode as a workaround as long as SANE 2 is not ready. But I don't recommend to put it into any real fontends, only special button programs. Bye, Henning
[sane-devel] Nikon Coolscan V
Hi, On Sun, Jul 04, 2004 at 07:48:24PM +0200, Ulrich Eckhardt wrote: ist the developement for the coolscan2 backend alive? I don't know but the author at least seems to be active. Try to contact him directly: Andras Major and...@users.sourceforge.net. Bye, Henning
[sane-devel] [fujitsu] Documentation patch: M3097G works
Hi, On Tue, Jul 06, 2004 at 01:00:33AM -0600, Paul Walmsley wrote: This documentation patch just adds the M3097G to the list of working Fujitsu scanners. fujitsu.desc should also be updated. Bye, Henning
[sane-devel] Finding libusb during compilation time...
Hi, On Mon, Jul 05, 2004 at 02:59:59PM +0200, Samuele Kaplun wrote: with kernel 2.6.x I'm no more able to use my usb scanner. I've installed libusb 0.1.8, but sane-backends configuration doesn't recognize it. I've looked through the code of configure (and config.log) and found that to seek for libusb, char usb_get_busses () is searched. But in usb.h the definition of this function is struct usb_bus *usb_get_busses(void). So the configure (and gcc) script can't find it. That shouldn't matter. My usb.h uses the same declaration and libusb is found here. Please show us your config.log file. Bye, Henning
[sane-devel] Microtek 3600 Fedora 2 UGH
Hi, On Thu, Jul 01, 2004 at 07:42:09PM -0700, Brennahn Chesteine wrote: Xsane can see my Microtek 3600 USB scanner with no problem. I can aquire preview just fine or I can scan the full image just fine. But if I aquire preview then select the portion of the image I wish to scan and click Scan I get this error. Failed to start scanner: error during device I/O I have torn google apart but cannot find a solution. Any ideas? To find out the cause of the error message, emable debugging: export SANE_DEBUG_SM3600=255 and try to scan. There have been wuite a lot of reports of general USB trouble on 2.6 so it may be worth to try with Linux 2.4. If you can't find out what's wrong, contact the author of that backend: Marian Eichholz eichh...@computer.org Bye, Henning
[sane-devel] use of ICC profiles
Hi, On Sat, Jul 03, 2004 at 12:42:16AM -0700, Peter Mark Guevarra wrote: Also, how can you post a reply in this forum so that it will fall under the same topic coz when I reply it always ends up being listed as if it is a new topic. Sorry about this =) This is not a forum but a mailing list. So can you use your mail program the same way as with normal mails. If you want to respond to the author only, just use reply. If you want to respond to the list use reply to list (or reply to group). The names of these functions may be different in your mail program. Bye, Henning
[sane-devel] different outputs
Hi, On Sat, Jul 03, 2004 at 03:40:29AM -0700, j d wrote: I wrote one sample probe with disconnect, it was compiled and i loaded it into kernel. But when i did cat /proc/bus/usb/device, at is showing one extra bulk out endpoint, where as sane-find-scanner -v -v showing only two endpoints, one in and one out, can anyone tell me, why is it showing different outputs? Thank you, Maybe a bug in sane-find-scanner? Could you please send us the two outputs? Bye, Henning
[sane-devel] [Canoscann5000F] Trying to analyse SniffUSB log
Hi, On Sat, Jul 03, 2004 at 08:44:22PM +0200, Thibault North wrote: I used sniffUSB while I plugged the scanner... and now I have to parse the log file. Someone here gave me a script, spike4.pl : but nothings happends when I call it using : perl spike4.pl filename Isn't it perl spike4.pl filename? I read that USB-robot was good, but unfortunately I cannot install it here : I always got errors compiling... USB robot can be used to send the USB commands to the scanner under Linux. It uses the sniffusb logfile to fo that. Could somebody help me ? I haven't used any of these tools so I can't talk about details. But you must understand the sniffusb output anyway if you want to understand the way how the host and the scanner communicate. Once you know the basics of that communication, you can small programs to filter out unneeded information. Bye, Henning
[sane-devel] VIA chipset and HP4100C USB scanner
Hi, On Thu, Jul 01, 2004 at 05:59:48PM -0700, Bill Moseley wrote: So under 2.4.21 I'm using the scanner module, but under 2.6.6 I'm using libusb, correct? So does that mean the problem is with libusb? Sorry, I don't really understand how the parts fit together. On 2.4 you can use the kernel scanner driver or libusb. In 2.6.something the kernel scanner driver was removed from the kernel so your only option is libusb. Bye, Henning
[sane-devel] Epson Perfection 660
Hi, On Wed, Jun 30, 2004 at 09:38:24AM -0700, Eelke Klein wrote: I'm trying to get my epson perfection 660 scanner to work. I have had it working on SuSE 8.2 but I have switched to gentoo and can't get it to work anymore. sane-find-scanner can find it but scanimage -L doesn't. I have the permissions in /proc/bus/usb automatically set by a hotplug script and have checked that the rights are actually set. I also tried it as root so the rights shouldn't be a problem anyway. Try enabling debug messages: SANE_DEBUG_SNAPSCAN=255 scanimage -L If you don't get any output, the snapscan backend isn't loaded for some reason. Bye, Henning
[sane-devel] VIA chipset and HP4100C USB scanner
Hi, On Tue, Jun 29, 2004 at 02:45:51PM -0700, Bill Moseley wrote: I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if my hardware is the problem or if there's other things to check. I'm able to sync a USB Palm device with Jpilot without any problems, but my scanner generates errors. Maybe it's hardware but I rather think it's a kernel problem. There have been many reports about similar trouble with 2.6 kernels and VIA hardware. Then I run sane-find-scanner and it reports: found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. and in syslog I see: Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 sane-find-scanner just looks for USB devices. It doesn't send any device-specific commands (at least in this case). So it's most probably not a SANE problem. Sometimes this works: moseley@bumby:~$ scanimage -L device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner and entries in syslog from scanimage: Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out Not sure why Linux video capture was loaded. I don't have any video capture cards. lsmod shows videodev. Is hotplug confused about what module should be loaded? SANE can also scan from video cards that are supported by video4linux. Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out But sometimes scanimage -L reports that a scanner can't be found, and sometimes scanimage -L hangs with the process in D status which can't be kill -9'ed (requires a reboot, so it seems). I've also had scanimage -L do this: moseley@bumby:~$ scanimage -L Segmentation fault Bad. I haven't seen reports about such behaviour until now. And that's where I'm stuck. Any suggestions? Ask the Linux kernel guys. As a workaround, use kernel 2.4.* I'm able to scan on my laptop, also runnning Debian Sid and same software. But, once in a while I do see similar problems -- so I wonder if it's a scanner issue. Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in Control timeouts mean that something went wrong with the communication of the host and the scanner. The reason can be a wrong command, but as these problems only occur on 2.6 it looks like a kernel issue for me. Unfortunately nobody has yet found out the real cause. Bye, Henning
[sane-devel] On what basis the device speciific structure will be defined??
Hi, On Wed, Jun 30, 2004 at 02:03:59AM -0700, j d wrote: How are you? Fine. But there are other people on this list :-) I have gone through the sample scanner drvier written by you, Could you explain which sample driver you mean? A specific SANE backend or the Linux kernel scanner driver? now my question for you is, on what basis you have been defined the Structure to hold all of our device specific stuff, if I need to define a same kind of structure for an another scanner, what are the things I need to take into consideration or can i blindly follow the same structure, what you have been defined? or can I use the one which is defined in usb-skelton.c? Hope to see an early and positive reply from you, Thank you, usb-skeleton.c is part of the kernel. So this mail is about the kernel scanner driver? Can you explain what you intend to achieve? Bye, Henning
[sane-devel] different scan outputs for different Linux distributions
Hi, On Mon, Jun 28, 2004 at 06:54:29PM -0700, Peter Mark Guevarra wrote: Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9. The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used.. Even if you use scanimage instead of xsane? scanimage doesn't do any automatic color correction. You have said in your previous reply that xsane should not modify gamma settings automatically..I`m quite confused with the use of the options..How may I be able to do this? In Preferences-Setup-Enhancement, disable autoenhance gamma and Autocorrect colors. Bye, Henning
[sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler)
Hi, On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: I've tried to compile and install xsane 0.94. When I start xsane from console, nothing happens, only the message Speicherzugriffsfehler (Memory access error) appears. Next I've downloaded a rpm from packman, and there the eula pops up, but with the click on accept the message above appears again. http://www.xsane.org/ First news item. If that's not your problem, tell us more details (which scanner, which backend?). Bye, Henning
[sane-devel] Experience with brother backend?
Hi, Has anyone already tested the brother backend? Link: http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html It seems to be based on an old SANE version without libusb support so it may be difficult to use on 2.6 :-/ It claims to supporte these models: DCP Models: DCP-1000 DCP-1400 DCP-8020DCP-8025D FAX Models: FAX1815C FAX1820C FAX1920CN FAX-2850FAX-2900 FAX-3800 FAX-4100 FAX-4750e FAX-5750e MFC Models: MFC3220C MFC3320CN MFC3420CMFC3820CN MFC-4800 MFC-6800 MFC-8220 MFC-8420MFC-8500MFC-8820D MFC-9030 MFC-9070 MFC-9160MFC-9180MFC-9660 MFC-9700 MFC-9760 MFC-9800MFC-9860MFC-9880 Any experiences with that backend? I'd like to add these scanners to our lists for external backends but first I want to know if the driver works at all. Bye, Henning
[sane-devel] Experience with brother backend?
Hi, On Mon, Jun 28, 2004 at 01:27:20PM -0400, m. allan noah wrote: an objdump on the .so, plus some comments in the faq make me think it uses libusb. Maybe it's used directly (without the use of sanei_usb). I haven't looked into the details. i have not used the code, though. i have a brother printer, but no mfc. i have a bigger question, though. is their packaging of gpl'd and lgpl'd and proprietary code together ok? I'm not really sure. Concerning the SANE license (e.g. sanei_usb.c) it *could* be ok, even if using parts of the sane distribution with proprietary backends wasn't the intention of the SANE exception. I haven't checked the implications of using their license in combination with GPL/SANE and LGPL, however. I'd never put such part of software on any of my website because of this license nightmare :-/ Bye, Henning
[sane-devel] a new function for sane-desc!
Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: Hi, finally I have made a new function in sane-desc to get an xml output. I think that only have to send the patch, if there is any problem please email me, this is the first time that I make something similar.. I've just comitted your patch to CVS. Thanks again! Bye, Henning
[sane-devel] Re: SANE/Avision the shifted image problem
Gi, On Sat, Jun 26, 2004 at 07:03:21PM +0200, Rene Rebe wrote: 2. scanimage -V gives: scanimage (sane-backends) 1.0.13; backend version 1.0.1 Hm - I wonder how 1.0.13 and 1.0.1 get mixed here. I guess you have two version installed in parallel, where the binary is from e.g. /usr/local/bin and the library from /usr/lib ?!? (Henning?) 1.0.13 is the version of sane-backends that was used to build scanimage. 1.0.1 is the SANE version number of the dll backend. At least on Linux scanimage is linked in a way that ensures linking with the correct libs. Therefore maybe it's just a cut-n-paste problem? Bye, Henning
[sane-devel] HP5370C still not working
Hi, On Fri, Jun 25, 2004 at 11:20:57PM +0200, Rene Rebe wrote: An unrelated bug showed the same timeouts: - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 and 2.4.25 with scanner.o(!) Reason: the epson backend tries to talk to this scanner You mean talking directly using libusb while the scanner module is loaded or so? Although this gives a permission denied or so for me, maybe with ohci this behaves differently? People with problems could take a look if either scanner or hpsubscsi was / is loaded ... and unload it just in case ... No, the problem in this case was that the epson backend thought that those scanners were supported by it. So the backend sent some commands to the scanner which the scanner didn't understand. -- timeout. That's fixed in CVS now. I haven't heard about any problem with scanner driver/ libusb interferences. However, there are problems with devices opened by libusb which are opened by other processed at the saame time. While the open fails, there still seems to be sent USB messages to the scanner and at least sometimes the scan process stops or images are corrupted. Bye, Henning
[sane-devel] sane-desc to xml
Hi, On Thu, Jun 24, 2004 at 11:37:15AM +0200, jose wrote: No Im thinking on add a new function to sane-desc to get a output in XML format (very easy to parser). I have the code done Ah, very nice. it but I need to know what should I do... I guess that I have to send the patch and then you say that its ok for including it... Yes, please send a unified diff. Bye, Henning
[sane-devel] check-usb-chip request for help
Hi, On Fri, Jun 25, 2004 at 12:16:27PM +0100, Ioan-Cosmin Pop wrote: Henning, you keep telling me about the protocol of the scanner, commands and registers. Can you please tell me what they mean? OK, I know this sounds stupid. I know what a protocol, command or register is. Back in the good ol' DOS days (well, not so good, but old for sure) I used to read/write to a specific port and mess with the device registers (an aquisition device in my case). I can only make some suppositions. Please tell me if I'm correct and if I'm on the right way. - for the protocol, I think this is something like: buffered or direct; No. What I mean by protocol is how the driver/backend communicates with the scanner. As an example, I'll describe the protocol of the GrandTech GT6801 chipset. Your scanner's protocol will be completely different most probably. Commands and data are sent to the scanner as USB control messages with a data size of 64 bytes. The request, request_type, value etc. depend on the type of command. E.g. you can send commands, receive results from commands, write data to scanner's RAM (firmware) and read from the RAM. This is an example for a command sent to the scanner (from a sniffusb log of a Mustek BearPaw 2400 TA Plus: | URB 525 going down | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = | (USBD_TRANSFER_DIRECTION_OUT, ~USBD_SHORT_TRANSFER The data is sent from the host to the scanner. | TransferBufferLength= 0040 64 bytes of data. | TransferBuffer = c1b6b000 | TransferBufferMDL = | : 20 01 0f 01 29 05 a4 00 58 02 82 20 64 00 01 00 The data itself. For the gt6801, the first byte is the command code. 0x20 means setup scan. The second byte is alway 01. Bytes 2+3 and 3+4 are the Y coordinates of the scan widow (Y0 + height). The first byte is the low byte. In this case the height is 0x0529 = 1321. As these coordinates are based on 1200 dpi, the height is 1.1 inches in this case. Byte 0x0a (82) means gray mode. Byte 0x0c (64) and 0x0d (00) are the resolution: 0x0064 = 100 dpi. | 0010: 64 00 73 00 0b 00 64 00 3c 00 00 00 00 00 00 00 | 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 More settings like lamp, backtracking, bytes per line etc. | UrbLink = | RequestTypeReservedBits = 00 | Request = 01 | Value = 2010 That means send a command. For writing firmware 200b would be used. | Index = 3f40 Not used here but for firmware writes that would be the memory address to write to. Now the data is sent. As confirmation you get the URB back from the (Windows) operating system (see the same URB number): | URB 525 coming back | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 0002 | (USBD_TRANSFER_DIRECTION_OUT, USBD_SHORT_TRANSFER_OK) | TransferBufferLength= 0040 | TransferBuffer = c1b6b000 | TransferBufferMDL = c1800880 | UrbLink = | SetupPacket : 40 01 10 20 40 3f 40 00 The setup packet is the same as above but this time it's not split in request, value etc. See the USB spec for details. Now we ask for the result of the command we just sent: |URB 526 going down | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = 0001 | (USBD_TRANSFER_DIRECTION_IN, ~USBD_SHORT_TRANSFER_ We want to receive data from the scanner (DIRECTION_IN). | TransferBufferLength= 0040 We want to get 64 bytes. | TransferBuffer = e3c09d1c | TransferBufferMDL = | UrbLink = | RequestTypeReservedBits = 00 | Request = 01 | Value = 2011 That means: Read result of command. | Index = 3f00 See above. Ok, now the result: |URB 526 coming back | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 0003 | (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK) | TransferBufferLength= 0040 | TransferBuffer = e3c09d1c | TransferBufferMDL = c1800880 | : 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The first 00 means that the command succeeded. The second byte 20 repeats the command we sent (setup scan). Other commands may return more data (e.g. the status of scan buttons or a flag if the scan head is at its home position). The actual scan data is read by bulk reads. That's
[sane-devel] donation / scanner support
Hi, On Thu, Jun 24, 2004 at 11:49:24AM +, Florent Aide wrote: I have a Dell A920 (rebranded Lexmark X1150) that is currently marked on the website as not supported. Since I have two of these little things I am willing to donate one of them to the project in order to see scanner support for it. Thanks for your offer! How can I do that ? Is someone willing to accept this donation and work on the scanner part of the Dell A920 ? Unfortunately there is no SANE backend yet for the RTS8852B chipset as far as I know. So you can't just send it to the backend maintainer. Maybe someone wants to start writing a backend for that scanner? Bye, Henning
[sane-devel] a new function for sane-desc!
Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: Hi, finally I have made a new function in sane-desc to get an xml output. I think that only have to send the patch, if there is any problem please email me, this is the first time that I make something similar.. Ah, there it is. I should really read all sane-devel messages before answering... Looks fine. If nobody objects I'll add it to CVS. Bye, Henning
[sane-devel] CanoScan5000F backend project beginning soon...
Hi, On Thu, Jun 24, 2004 at 07:19:50PM +0200, Thibault North wrote: I wanted to know if some of you where interested in helping us (if you have this scanner) or be available to answer our questions (using IRC ?) Ask on this list or ask on IRC (#sane on freenode.net). On IRC, be patient as questions may be answered hours later when someone wakes up :-) An adress used to communicate : http://gna.org/projects/canoscan5000F I have added a link to that page to our Canon 5000f page: http://www.sane-project.org/unsupported/canon-5000f.html P.S to Henning Meier-Geinitz : could you please send me the Perl script we spoke about which is able to filter the log file from SniffUSB ? I don't really remeber using such a perl script. I know that there is (or was) one, but I think I never really used it. Sometimes I use a C program to analyse sniffusb log files but that program is really specific for the GT6801 chipset and filters only some special commands so I think it's not useful for anyone else. Bye, Henning
[sane-devel] Automatic update of the Webpages...
Hi, On Thu, Jun 24, 2004 at 10:09:39AM +0200, Gerhard Jaeger wrote: how can the following site: http://www.sane-project.org/lists/sane-mfgs-cvs.html The contents itsself is updated automatically ... be updated? It contains currently the following sentence: The following table summarizes the devices supported by sane-backends-1.0.13-cvs., which is wrong... True. The reason is that with every CVS upload that changes a .desc file, make is run in the doc directory. However, for changing the version string, configure is also necessary. I don't want to do that everytime a commit is done so it's done manually. It's fixed now. The scripts for the automaic update of these lists (and a few other things) are in CVS (module CVSROOT) by the way. Bye, Henning
[sane-devel] Comprehensive overview...
Hi, On Thu, Jun 24, 2004 at 10:16:30AM +0200, Gerhard Jaeger wrote: while searching for some info about the HP2400c, I noticed, that it is not included in the unsupported.desc file... I'm also not really sure if putting all these genesys scanners into the genesys.desc file before they really work is a good idea. The search engine delivers a result, but for simple users who are not using the search engine, the information about the scanner will be not available... I think we need one page, where all the information we have is available, even if the scanner is supported by an external, experimental or no backend. That one page is the search engine. Years ago we had one big page that includes all the data ordered by backend only. The problem with that was that many simple users didn't notice that their scanner needed an external backend so they complained about the scanner not working even after installing sane-backends. That's the reason for the split between external and internal. The scanner search engine provides answers to the questions: What's known about that scanner? or Is my scanner supported at all? Stable/CVS manufacturer lists: Which scanners are (un)supported by the stable/CVS version of SANE? or: Is my scanner supported by the sane-backends distribution? Stable/CVS backend lists: Which scanners are supported by a specific backend? (mostly for developers) External backend lists: Which scanners don't work with sane-backends but have external backends? Older lists: Does my scanner work without updating my older version of sane? A lot of different lists but there is also a lot of different questions. I appreciate suggestions for a better presentation of that data. Bye, Henning
[sane-devel] check-usb-chip request for help
Hi, On Thu, Jun 24, 2004 at 12:05:26PM +0100, Ioan-Cosmin Pop wrote: I created the function check_SQ113 to check the chip (http://picosconsult.topcities.com/downloads/check-usb-chip.c). I test the device descriptor and the endpoints. After that, I try to write a value (a four bytes array), What is this command or data intended to do? but I get an error in usb_bulk_write() no matter what I do. I tried to chage the endpoint (not to use bulk but interrupt) but to no avail. First you must know what to send. I.e. you must know the protocol of the scanner and what commands to use or registers to set. Use a simple command (e.g. read the device identification or write and read a register value). So, my question is: can I get rid of this test? I see there are other functions that don't try to write/read something from the device. Is it safe to do this? Not really, at least if you want to be sure that you have correctly identified a chipset. The whole idea of the descriptor test is to avoid sending commands to a scanner that doesn't understand them. However, the final test if we really have found a secific chipset is done by communicating with the chipset. After some time, I looked over the page http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html and I saw some other chips: [...] Does this mean I have to include tests specific to those chips, or they behave exactly like SQ113C? They are all in the same scanner. Well, they ought to be there as somebody told me that they are there :-) Probably these chips are helper chips like a CCD driver, analog frontend, motor driver, RAM, EPROM, USB interface etc. So you don't need (and probably can't) test for them. Bye, Henning
[sane-devel] Backends Database
Hi, On Tue, Jun 22, 2004 at 01:00:44PM +0200, jose wrote: Hello, Im a developer of the Linux Hardware Database Unification Project(http://sourceforge.net/projects/linuxhard/), a part of this Database will include information about scanners and backends. I would like to know if there is some DB about this or if all the information is included on the frames of the webpage of sane, because It will be very dificult to mantein the hardware DB if we have to visit the tables of the web to see the changes... The information about supported (and not supported) scanners is contained in the *.desc files (e.g. doc/descriptions/mustek.desc). These files come with the sane-backends distribution. The current ones are in SANE CVS. Documentation of the format is in doc/descriptions.txt. The lists on the website are automatically generated from these lists by the tools/sane-desc program. It can also produce ASCI output. Maybe you can uses this output or modify that program to print the data you are interested in. Bye, Henning
[sane-devel] list
Hi, On Tue, Jun 22, 2004 at 12:23:15PM +0100, Major A wrote: Sorry I've been out of touch for a while. The main reason was that I was busy doing other things, but also that list message delivery stopped a while ago without me noticing. I've now subscribed with a different address and it appears to be working OK now. Strange. Unfortunately, alioth still doesn't sent any administrative messages (e.g. about mail problems) to me and all mails to sane-devel-admin are bounced. So I don't know the reason. Have there been any major events recently, especially related to the Coolscan2 driver? There are two bugs assigned to you in the bug tracker :-) Bye, Henning
[sane-devel] Canoscan Lide 80 and 5200F
Hi, On Sun, Jun 20, 2004 at 06:48:54PM +0200, nikolas.ar...@gmx.net wrote: Could someone please comment on this (tell me if you need help with an english translation)? I haven't ever gotten any reliable report that the Canon LiDE 50 or 80 do work. Some people told me that these scanners are supported but after looking at their log files I found out that their scanners had the USB ids of Canon Lide 20 or 30. And surprisingly the owners of these scanners noticed that they own a Lide 20 or 30 when I asked them to look again at the name plate. I've been also poited to that forum but nobody told me: yes, my Canon Lide 50 or 80 works with sane with the ... backend. So I think it's a hoax. Bye, Henning
[sane-devel] help with Epson 636U and Panther
Hi, On Sun, Jun 20, 2004 at 02:47:15PM -0400, Fritz Lang wrote: found USB scanner (vendor=0x04b8 [EPSON], product=0x0101 scanimage -L No scanners were identified. If you were expecting something different, SANE_DEBUG_EPSON=255 scanimage -L may print some more details. Bye, Henning
[sane-devel] Patching of maintained code by others...
Hi, On Mon, Jun 21, 2004 at 09:51:47AM +0200, Gerhard Jaeger wrote: while doing a CVS update this morning, I found my plustek code patched. In general, I do not have any problems on that, but I think that a short message on that would be of great help - or did I miss something? I also don't mind if others fix obvious bugs in my backends and also think that a notice to the backend maintainer is better. While I read the sane-commit mails that show the changes, I've already overlooked some of them. If many backends are changed, a mail to sane-devel is also ok in my opinion. Also, if a backend is developed in an external CVS the maintainer may overlook the previous change and just upload his newest version. So the fix gets lost. Bye, Henning
[sane-devel] different scan outputs for different Linux distributions
Hi, On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote: Has anyone encountered this problem wherein the same frontend, xsane or xscanimage for instance, has different outputs for RedHat, and SuSE or Mandrake? Same settings were used in the frontend but different outputs resulted for different distributions, one is darker/brighter than the other. I haven't heard about such a behaviour. Can you reproduce it with scanimage? Maybe the scanner wasn't warmed up completely in one of the tests? Also, in the case of using only one Linux Distribution, RedHat for example, is it expected to have the same output for the different SANE frontends given the default settings for each frontend? Yes, if you don't use any of the color enhancement settings. E.g. make sure that xsane doesn't modify your gamma settings automatically. Bye, Henning
[sane-devel] Epson Perfection 2400 Photo scanner problems
Hi, On Mon, Jun 21, 2004 at 05:36:25PM -0600, br...@biology.nmsu.edu wrote: I'm slowly tracking down parts of the problem with my scanner. When I tried the NetBSD kernel scanner devices (/dev/uscanner*) I identified an issue with sane-find-scanner. It lacks any definition for NetBSD-specific kernel devices. I submitted a bug report (category tools) that provides a patch that fixes that. I've added that patch to CVS. Next time, please attach the patch to the bug report (upload), that way the patch can be downloaded and applied directly. Could you try if it works in the CVS version of sane now? The remaining issue with using the kernel devices is getting the scanner information from the device driver. I'm looking into that, but if I hack in a hard-coded response to match the correct scanner everything works perfectly. Some backends can cope with the kernel scanner driver not returning USB ids. E.g. by setting options in backend.conf or by otherwise telling the backend which scanner is actually connected. Bye, Henning
[sane-devel] [ANNOUNCE] New release of gt68xx backend
Hi everyone, I've just updated the gt68xx backend in CVS to version 1.0-61. The new version has quite a lot of changes so please test it if you own a scanner supported by this backend. Most important changes: - Mustek ScanExpress A3 USB is supported better now Warm-up and calibrationm should work now, however, some vertical stripes are still present - several minor fixes for other scanners - calibration in general avoids loops so it should be faster in some situations - CIS calibration should be better in avoiding stripes now. That work is not finished, however. - backtracking should occur less often - it's possible to select the color that's used to scan in gray/lineart mode now. More changes: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.CHANGES Unfortunately there are still some bugs. See the TODO list: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.TODO Download As usual from SANE CVS or the gt68xx page: http://www.meier-geinitz.de/sane/gt68xx-backend/ Or from a complete CVS snapshot: http://www.sane-project.org/snapshots/ Bye, Henning
[sane-devel] Re: xsane-0.91
Hi, On Thu, Jun 17, 2004 at 06:40:57AM -0700, Don wrote: chmod a+rw /proc/bus/usb/002/002 did the trick but I guess it's temporary. How do I make it permanent? man sane-usb, README.linux: http://www.sane-project.org/README.linux Bye, Henning
[sane-devel] LaserJet 3380
Hi, On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamriško wrote: I have a problem with HP LaserJet 3380 printer. Hpoj recognized it successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it at all. Can someone help me with this? Which kind of device is it (USB)? Please show us the output from sane-find-scanner -v -v If the device is detected by the hpoj backend, there is no need for sane-find-scanner. Bye, Henning
[sane-devel] Canon FS4000: image data is sensor data, not RGB?
Hi, On Thu, Jun 17, 2004 at 11:59:18AM -0400, Dave Burns wrote: I am making good progress reverse-engineering the SCSI protocol for this film scanner. I now have a short test program in C that scans film and I now have the challenge of decoding the image data returned. It appears to be raw sensor data. I don't have experience with many other scanners: is this typical of scanners to return raw data? Or maybe typical of film scanners but not flatbed? What do you mean exactly by raw sensor data? The format of the image data varies with the scanner chipset. Some scanners provide the calibrated and even gamma corrected data in the resolution you have selected. For others , calibration and gamma correction must be done by the backend. Also, the image data appears to contain more data than expected. I.e. there is more data then there should be if I consider the size of my scanning window and work out the math. Is this typical and is it normal to have to interpolate to provide the user with expected results? Most scanners can only do some fixed resolutions, e.g. 100, 300, and 600 dpi. So other resolutions are done by using the higher resolution and downsampling the result. Well, some windows drivers use the lower resolution and interpolate the missing pixels... This downsampling is sometimes done in the scanner, som,etimes it must be done by the backend. Some scanners can only scan in fixed window steps, e.g. the number of pixels must be a multiple of 64 or similar. Bye, Henning
[sane-devel] Installation oddities...
Hi, On Thu, Jun 17, 2004 at 08:55:16AM +0200, Gerhard Jaeger wrote: on my SuSE distributions, I used to overwrite the existing and always outdated SANE-RPMs, by using the following configure command: ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info This works pretty well up to sane-1.0.13, while checking 1.0.14 I noticed, that the links in /usr/lib/sane to the new libs are no longer updated during the installation step - did anything change there? No. As far as I can see there is no change in the install target of backend/Makefile.in that could cause such a behaviour. In 1.0.11 we created such links manually but this is done by libtool nowerdays: lrwxrwxrwx1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so - libsane.so.1.0.14 lrwxrwxrwx1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so.1 - libsane.so.1.0.14 -rwxr-xr-x1 root staff 84752 2004-06-16 18:09 /usr/local/lib/libsane.so.1.0.14 Bye, Henning
[sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u!
Hi, On Sun, Jun 13, 2004 at 03:53:21PM -0700, Victoria Welch wrote: I still have to choose between the tv tuner card and the flatbed. Would be just as happy if the tv tuner didn't show up since xsane doesn't seem to like it enough to do anything with it. If you delete the .drc for the tv card, it re-establishes itself as soon as you run xsane :-(. To disable v4l completely, edit /etc/sane.d/dll.conf and comment out v4l. To start xsane with your scanner directly (without chosing): xsane yourbackend (e.g. xsane plustek). -d, --device-settings file load device settings from file (without .drc) Seems to be ignored :-(. Really? It justs loads the settings for one device. It doesn't set the default device to use. Bye, Henning
[sane-devel] I can't get my scanner to work.
Hi, On Fri, Jun 11, 2004 at 01:52:33AM -0700, Philip V. Neves wrote: I am trying to get my scanner to work with sane. I have a Canon LIDE20 usb scanner. sane-find-scanner sees the scanner but when I run scanimage -L nothing comes up. Its as if the scanner isn't there. 77 Here is what I get when I run sane-find-scanner. If someone could please point me in the right direction I would greately appreciateit. Which operating system and version are you using? Which SANE version? [...] device descriptor of 0x04a9/0x220d at 001:002 (Canon CanoScan) [...] trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bDeviceSubClass = 0x0) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x110) checking for MA-1509 ... this is not a MA-1509 (bDeviceSubClass = 0x0) checking for LM983[1,2,3] ... Couldn't claim interface: could not claim interface 0: Device or resource busy This USB chip looks like a LM983x? Something else is caliming the scanner. So either another program has already opened the scanner or there is a kernel bug. Or you are using Linux 2.4 and the kernel scanner driver has claimed the scanner. SANE_DEBUG_PLUSTEK=255 scanimage -L will print why scanimage doesn't detect the scanner. But I guess it's the same problem: device busy. Bye, Henning
[sane-devel] SANE driver for NEC Petiscan scanner
Hi, On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: As far as I can tell, without further digging into the guts of the scanner, there are two chips which say JIC (?) ES52099S 9919-LHIJ I was not able to find data on this chip. Google finds some references but no spec or explanation. Winbond W24512AJ-15 919SA290732601CE Chip specs: http://www.chipdocs.com/pndecoder/datasheets/WBOND/W24512AJ-15.html So that's RAM. No other chips? In this c ase the JIC must be the scan chip. It occurred to me that this scanner will run off another computer I have access to, but only in MacOS9. Might there more data that I can access from a computer that will actually run the scanner, versus this laptop with which I want to ultimately run the scanner, but only uses MacOSX? You need software that can listen to the USB commands send to the scanner (sniffer). While some programs are available for Windows I don't know if that's the case for MacOS9. Bye, Henning
[sane-devel] scanner HP 4600
Hi, On Mon, Jun 14, 2004 at 12:18:17PM +0200, François Patte wrote: Is it possible to have a Hewlett-Packard Scanjet 4600 working under linux with sane? No. At least that's what our search engine says: http://www.sane-project.org/cgi-bin/driver.pl?manu=hewmodel=4600bus=any Bye, Henning
[sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, result); /* got 00 */
Hi, On Wed, Jun 09, 2004 at 08:15:01PM +0200, ins...@piments.com wrote: As you can see communication seems to go quite well at first but then gets stuck in a loop with no apparent timeout. I have had a quick look at the sourcecode and think the loop happens at backend/canon630u-common.c, line 374 ff. The backend asks the scanner how many scan data it can provide. The scanner say 0. The backend tries for 60 seconds but the scanner still doesn't have any scan data. So it should time out after 60 seconds. But that's just my guess. However, I don't know why there is no scan data. Bye, Henning
[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)
Hi, On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: Hate when I do that . . here's the xsane logs described in my previous email Ok, let's look at the second log. The preview scan looks ok (but I don't know the details of the plustek backend). The real scan also starts fine and then we see this: [plustek] sane_read - read 3750 bytes [saned] do_scan: read 3750 bytes from scanner [plustek] usb_ScanReadImage() done, result: 0 [plustek] usb_ReadData() [plustek] usb_ScanReadImage(3760) [plustek] usb_ScanReadImage() done, result: 0 [saned] do_scan: trying to write 3754 bytes to client [saned] do_scan: wrote 3754 bytes to client [saned] do_scan: trying to read 1521 bytes from scanner [plustek] sane_read - read 1521 bytes [saned] do_scan: read 1521 bytes from scanner Now these 1521 bytes should be sent to the frontend... [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: bad status 22 saned thinks something has been sent to it by the control (not data) connection. But when trying to decode what was sent it gets an error when reading the first word. 22 is invalid argument. That means that no data could be read. Maybe xsane has crashed on the clent side meanwhile? Usually during the scan nothing is sent to the control file descriptor. Anyway. As sane_cancel isn't called the reader_process in the plustek backend isn't killed and the plustek backend gets confused. So my impression is that the problem is with xsane (or the net frontend on windows) and the scanner lockup is just a consequence. But I don't know why xsane (or the net backend) crashes. So maybe finding out the details here may help- E.g. gdb xsane on the client or enabling debugging for xsane and the net backend and looking at the last few lines before the crash. Maybe the xsane and plustek maintainers can have a look at the logfiles, too? Bye, Henning
[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)
Hi, On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: What sort of steps are availble for me to take debugging-wise on the windows end? If xsane is started from the command prompt, are there any swithces available to generate debugging output at the command prompt? I don't know how setting environment variables works on windows but with bash you'd do export XSANE=DEBUG=255 export SANE_DEBUG_NET=255 XSANE_DEBUG will produce a huge amount of debug messages. Bye, Henning
[sane-devel] NEC Petiscan driver for MacOSX possible?
Hi, On Tue, Jun 08, 2004 at 10:17:36PM -0700, Allan Kaplan wrote: As far as sane-find-scanner goes, am I to assume that I have to be running Linux, or can I use the Terminal program on the Mac and do this in Unix? MacOS X is ok. Any system that runs SANE should work. And can I further assume that Mattias Ellert's MacOSX downloads will not be applicable in this case? If they conatin sane-find-scanner, they should work. Bye, Henning
[sane-devel] Howto update sane and xsane?
Hi, On Wed, Jun 09, 2004 at 01:26:58AM +0200, Erik P. Olsen wrote: I am running FC2 and want to upgrade xsane and sane-?ends to latest level, but being new to linux I am unsure of how I should do this. Since they exist as rpm installed packages should they then be removed from the system before installation or is it safe to let them stay and install the new levels on top of them? Maybe you can use the RPMs from http://rpmfind.net/linux/rpm2html/search.php?query=sane-backends ? Even if you can't, building your own RPM based on the 1.0.14 source RPM is probably the cleanest way. The latest levels do not yet come in rpm format so I assume that if I let them stay then the up2date process may later catch up if an even newer level comes out in rpm format - or is this a false assumption? If you do not want or can't make an RPM yourself there are some other options: 1) Remove the existing SANE RPMs. You may get trouble trying this as other software may depend on them. You can try to force rpm to remove the packages that will break dependencies and you may get trouble later. 2) Overwrite the current installation. Linux distributions usually put their software into /usr, so configure --prefix=/usr --sysconfdir=/etc should work (check the syntax). This isn't a clean solution either and your sane installation may be destroyed when your distribution is updated. 3) Ignore the current installation and install SANE in /usr/local/. That's the default. It works but graphical frontends generally use the old installation in /usr, not the new one in /usr/local. /usr/local/bin/scanimage knows where to find the new libs, however. You can try some tricks to use the new libs, e.g. change the search order in /etc/ld.so.conf, use LD_PRELOAD=/usr/local/lib/libcane.so xsane or link /usr/lib/libsane.so to /usr/local/lib/libsane.so. Bye, Henning
[sane-devel] Re: How to configure sane, xsane, etc.
Hi, On Wed, Jun 09, 2004 at 10:08:32AM +0200, François Patte wrote: I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): 1- I have a scanner Nikon LS-2000. The first person who ran xsane was not root and it now impossible to change the owner and right of the device /dev/sg0. This device has been set with owner didier and group root with permissions 600 and whatever root can do to change this is destroyed by the next use of xsane: ownership, group and permission are reset as previously defined So nobody but didier can use xsane and the scanner! xsane doesn't change any access permissions. In fact it doesn't even know which device file to use. The sane libraries (sane-backends) themselves also don't touch permissions. So your problem is most probably caused by some automatic procedure introduced by Fedora. I remember that there is some stuff to change permissions based on who logs into the computer locally. man sane-scsi : When using a SCSI scanner, ensure that the access permission for the generic SCSI device is set appropriately. We recommend to add a group scanner to /etc/group which contains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at generic SCSI device /dev/sg0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/sg0 $ chmod 660 /dev/sg0 This is now impossible to do! Where are the configuration files responsible for this awful behavior? It works quite fine, I'm doing it on this system. Really looks like a Fedora problem. Better look at their docs or ask on their mailing lists for help. 2- Even for didier the use of xsane is not easy: every time he asks for xsane he has to accept the license xsane asks for accepting the liability exclusion only on the first start (and when xsane is updated to a newer version). So if that happens more than once, maybe the directoriy ~/.sane/xsane can't be written? and to wait about 10/15 minutes for the research of peripherics That shouldn't happen. Which version of sane do you use (scanimage --version)? The scan takes about 1 to5 seconds at least with newer versions of SANE. As a workaround, you can disable everything but coolscan in /etc/sane.d/dll.conf. And, worse, he has to wait also if he wants to use gimp: gimp hangs on xsane plug-ins If you don't need the xsane gimp plugin, remove the link to xsane. I would like to understand how this can happen and how to corrct this windows like behavior: unix systems were done for many users, it is more and more difficult to use them like this. The behaviour you describe isn't the normal SANE behaviour. 1) is not cause by SANE and 2) is caused by the kernel trying to load drivers for hardware that doesn't exist. That shouldn't happen with current sane versions anymore. Bye, Henning
[sane-devel] HP5370C still not working
Hi, On Wed, Jun 09, 2004 at 03:40:39PM +0200, Gilles Sadowski wrote: So, what is the final word about this timeout problem? The reason is unknown as of now. It's not that easy as these timeouts may have several reason. Every wrong command that's sent to the scanner can cause timeouts. It doesn't seem to be a general SANE problem. I've tried several scanners on Linux 2.6.7-rc2 with UHCI, OHCI and EHCI USB host controllers and can't reproduce the timeouts. So someone who does see the timeouts needs to investigate the details. E.g. if there is a specific SANE version that does work without trouble. If that's the case, identify the change that causes problems. If it depends on kernel versions, identify the kernel version that started showing those timeouts. I'll try to summarize what I've read here and in the bug tracking system: Timeouts: - HP5370C (avision) on UHCI VIA, Linux 2.6.5 - HP7450C (avision), sane-backends 1.0.14 (also tried latest avision code), Linux 2.6.5 - HP7400 (avision) on UHCI (Intel Corp. 82371AB/EB/MB PIIX4 USB) Asus board, sane-backends 1.0.14, Linux 2.6.3, 2.6.5, 2.6.6 and 2.6.7-rc2-bk7 - HP7450C (avision), there was a hint about the hpusbscsi driver making trouble in that case - Epson Perfection 1670 (snapscan) on UHCI VIA, sane-backends 1.0.14, Linux 2.6.5-mm2 No timeouts: - Several Mustek+Plustek scanners (mustek_usb, plustek, gt68xx), sane-backends 1.0.14, on OHCI + UHCI (VIA PCI card) on Linux 2.6.7-rc2 and Linux 2.4.26 - Avision scanners, on OHCI, sane-backends 1.0.14 + latest avison code on Linux 2.6.3 (UltraSparc +iBook) Typical log: Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 An unrelated bug showed the same timeouts: - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 and 2.4.25 with scanner.o(!) Reason: the epson backend tries to talk to this scanner There are some other reports about USB trouble but it's unclear if they are related. All these bug reports are newer than 6 weeks. So it's either the new SANE, kernel, libusb release or some other part of software that got changed recently. All but one reports are about the avision backend. Maybe the trouble is located there and the Epson 1670 problem has a different reason? Bye, Henning
[sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts.
Hi, On Wed, Jun 09, 2004 at 04:48:51PM +0100, Tom Schutzer-Weissmann wrote: I had problems using the Epkowa libraries (libsane-epkowa) and the iscan frontend with my usb scanner in kernel 2.6. The scanner was closed after each operation. Once closed, nothing could be read from it, and I got lots of BULK TIMEOUTs, although there were no errors when the device was reopened. By modifying the code so that usb_reset() was always called before usb_release_interface() and usb_close(), I solved the problem. Doesn't usb_reset() cause a renumeration and therefore the device gets a new device file? I guess this isn't the default for closing USB devices. Maybe the usb_reset just hides a bug in the SANE backend, libusb or the kernel. Bye, Henning
[sane-devel] OS/2 specific patch for sane-backends/backend/dll.c
Hi, On Tue, Jun 08, 2004 at 12:24:51AM +0200, Franz Bakan wrote: It still works, only a cosmetic issue: Linebreaks now are (hex) 0D 0D 0A instead of 0D 0A (after getting the .cmd via cvs) Hehe, CVS is not intelligent enough, emacs is too intelligent :-) I used your file with 0d 0a and edited it so emacs thought ha, that's for DOS, I'll keep 0d 0a. I checked it into CVS and it has 0d 0a in cvs. cvs on your local system knows that all this crap is unix (0a only) and converts every 0a to a 0d 0a even if it already is a 0d 0a. It's fixed in CVS now (0a only). Bye, Henning
[sane-devel] XSane tweaks settings by its own :-(
Hi, On Tue, Jun 08, 2004 at 12:15:54PM +0200, Gerhard Jaeger wrote: I'm currenlty trying to add more frontend configurable options to the Plustek backend and have some problems with xsane now. There's a value whose range is from -1..63. At the default state, when starting xsane, it is properly displayed: -1. When changing once to i.e. 6 and changing it back to -1, xsane stores it as 0 and also displays it after the next startup as 0.. Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, the contraint_type is SANE_CONTRAINT_RANGE... The configfile of xsane shows, that this value is stored as 0 and not as -1... How does the definition of the constraint look like? Bye, Henning
[sane-devel] NEC Petiscan driver for MacOSX possible?
Hi, On Tue, Jun 08, 2004 at 08:21:27AM -0700, Allan Kaplan wrote: Having recently purchased an NEC Petiscan unit, I've discovered the driver is not supported by MacOSX, and the Classic emulator won't hook up through the USB port. Please forgive my naivete, but is it possible to use SANE to fabricate one, Uaually it's possible to write a backend for any scanner. and is there anyone out there who might be game to do it?? I guess that would be you :-) And if it is possible but no one's interested, any chance of getting some coaching? Just ask this list, if you have specific questions. Some docu about backend writing is here: http://www.sane-project.org/contrib.html Could you please send us more information about this device so we can add it to our lists? E.g. if NEC Petiscan is the full name and the output of sane-find-scanner -v -v when the scanner is connceted to your computer? Bye, Henning
[sane-devel] saned + win32-xsane problem
Hi, On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: Hi, On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: No seg fault on the saned end. Its happily running, waiting to finish up. Xsane itself remains responsive. Ok. So you sent the logfile when both xsane and saned were still running? In this case the log file looks ok. Can you please retry and after the scan, close xsane? saned should also closes itsself. Thanks. I would expect xsane to close the fd used to access the scanner though. sane_close() will be called when xsane is closed. Some backends close the device file (or use the equivalent call to libusb) after the scan has finished but not all. Anyway, generated a log with a scan followed by closing xsane. saned exited as expected. As you'll see in the log, saned quits however, I never see any entry regarding the closing of the active fd. Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print messages about closing but from your log I expect that the devices are actually closed. The plustek messages should show that. In that case we must have a closer look at the communication. thanks for all your work . . looks like you've been busy as of late 8^( Fortunately I've two weeks of holidays and a lot of that time is used for SANE :-) Bye, Henning
[sane-devel] niash:libusb:002:005 failed: Device busy
Hi, On Tue, Jun 08, 2004 at 07:42:04PM +0200, ins...@piments.com wrote: Nice post. Sadly this does not seem to help for all scanners. You can't fix a problem that doesn't exist. As most scanners don't return wrong lengths of string descriptors, that workaround is just not necessary for most scanners. I did the change you suggested , recomp, reboot and my scanner locks up just the same. He suggested that workaround for niash users. Shame it did not do it for canoscan. I thought you got timeouts, not EBUSY? I would suggest you look into the code a bit more seriously before suggesting it as a fix to be integrated into the kernel. You cant just hack code like that without looking at the consenquences. At least not if you expect to have a stable kernel. That's true. As the kernel has conatined the code that is proposed here earlier, it doesn't seem to be that far off. Maybe a more intelligent way is needed, e.g. inspect the contents of tbuf[0] and if it's invalid, use 255. Maybe that is why devs at that have not done it yet. The evenual code fix will need to be more thorough. As far as I can see the proposed code does actually fix the problem for niash users. It may not be good enough for general use but that shouldn't stop niash users from trying it. Bye, Henning
[sane-devel] scanimage: timeout
Hi, On Mon, Jun 07, 2004 at 01:01:45PM +0200, Nyitrai Tamas wrote: I have got an Epson Perfection 1260 scanner. It always work right, but about a month ago it stopped working under Linux. Edit /etc/sane.d/dll.conf (or /usr/local/etc/sane.d/dll.conf) and comment out epson. See the postings in this mailing list and the bug tracking systems for the reason. Bye, Henning
[sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble
Hi, Everyone who gets timeouts/USB errors with these two scanners and sane-backends 1.0.14 please use the following workaround: Comment out the epson line in dll.conf (/etc/sane.d/ or /usr/local/etc/sane.d/). The epson backend seems to try to talk to these scanners because they are Epson scanners. As they are supported by the plustek backend (not epson) the scanners don't like the epson commands and USB errors occur. See bug 300751 for details: https://alioth.debian.org/tracker/index.php?group_id=1308atid=410366 I guess that bug didn't show up before the 1.0.14 release because the automatic detection for USB scanners in the epson backend wasn't turned on. Bye, Henning
[sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble
Hi, On Sun, Jun 06, 2004 at 09:25:29AM -0400, Karl Heinz Kremer wrote: The Epson backend does not have information about these scanners (this means no product ID), You mean: no internal product id? The USB product id of these scanners are actually listed in your code. so they should not be recognized and therefore the backend should not try to send any data. The only way this would happen is, if somebody explicitly uses the usb 0x4b8 0xXXX entry in epson.conf to manually add this scanner to the list of known scanners. I'll try to understand what happens: usb is in epson.conf so sane_init() calls attach_one_usb(). By the way, the attach_string related code seems to be unused in that function. Now attach() is called. As isLibUSB is false and dev_name is empty, for every known device sanei_usb_find_devices() is called. As The 1260 and 1250 are known (see epson_usb.conf) attach_one_usb() and attach () is called again, this time with the full libusb name. There is another test if the scanner is in the list of ids and it actually is. After that, commands like reset() and get_identity_information() are sent to the scanner. These commands will crash scanners that don't speak the epson protocoll. I may have missed something in this analysis, however. So the ids of these scanners should just be removed from epson_usb.c. I don't have these scanners, so I cannot test this. I do however know that if I add an EPSON scanner that is not yet supported (this was e.g. the case with the Perfection 4850), the new scanner is not recognized, and skipped during the scanner detection. Maybe you added it to epson_usb.c but in epson.conf there was no usb? Or the scanner just didn't mind being sent some epson protocol commands? There may be something else doing on, but I don't know what yet. I need a debug log for this case to find out what's going on. Unfortunately the author of the bug report did not leave an email address, so I hope that either my comment in the bug database, or this mail reaches the author. Henning, do you know how to get in touch with Jan? No. But as he has responded to my previous questions I guess he reads the bug tracker from time to time. By the way: there are some other bug/wish list reports for your backend that could use some comments (or fixes if possible): https://alioth.debian.org/tracker/index.php?group_id=1308atid=410366 Thanks, Henning
[sane-devel] HP 7450C libusb problems
Hi, On Sun, Jun 06, 2004 at 07:10:49AM -0700, George Garvey wrote: I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and 2.6.6-1.422 and this scanner. Jun 6 06:33:03 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 6 06:33:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 110 is connection timed out. I still think this type of problem is kernel-related as it only seems to happen with 2.6.5 and 2.6.6. Please try 2.6.7-rc2. It works for me (with different scanners) but I haven't tested 2.6.5 nor 2.6.6. Bye, Henning
[sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble
Hi, On Sun, Jun 06, 2004 at 09:36:42AM -0700, Keith Clayton wrote: In my case, w/problems scanning from win32-xsane across the network using an Epson Perfection 1250, I commented out all backends except net and plustek from dll.conf. This had no impact on my problem, where I could sucessfully scan once but then the scanner is left in an unusable state and and additional scan from any other machine fails. Not all problems are caused by that bug :-) If your problem was caused by that bug, you wouldn't be able to scan locally. Bye, Henning
[sane-devel] saned + win32-xsane problem
Hi, On Sat, Jun 05, 2004 at 11:00:23AM -0700, Keith Clayton wrote: scanimage -d net:localhost:plustek works perfectly. Can scan as many times consecutively as I'd like. win32-xsane continues to fail on the 2nd scan. After power-cycling the scanner I ran win32-xsane first then scanimage from the local machine. Scanimage failed in this case. First pass of win32-xsane is evidently leaving the scanner in a bad state. Used the debug flags as you suggested and captured the output. Something is definitely going wrong at the end of the win32-xsane/saned scan. I've attached the gzip output of running saned as you suggested with debugging on and xinetd disabled. I X'd out any host, IP info from the top of the log files but otherwise they're exactly what the debug kicked out. Local: [...] [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 20s [saned] process_request: waiting for request [saned] process_request: got request 3 [plustek] sane_close [saned] process_request: waiting for request [saned] process_request: got request 10 [plustek] sane_exit [plustek] Shutdown called (dev-fd=-1, libusb:001:013) [plustek] Waiting for scanner-ready... [plustek] Switching lamp off... [plustek] REG[0x5b] = 0x94 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x0001 [plustek] Switching Lamp off [plustek] usb_switchLampX(ON=0,TPA=0) [plustek] Switch Lamp: 0, regs[0x5b] = 0x14 [plustek] REG[0x5b] = 0x14 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x [plustek] Lamp-Timer stopped [saned] quit: exiting Looks sane :-) The scan is cancelled, the device is closed and then sane_exit is called. net: [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 88s [saned] process_request: waiting for request [saned] process_request: got request 5 [saned] process_request: waiting for request [saned] process_request: got request 5 [...] After sane-cancel() neither sane_close nor sane_exit() is called. That may cause a scanner to hang. The rquest 5 which is repeated some times is sane_control_option. Not too unusual, but xsane just seems to crash at that point so sane isn't closed correctly. Or saned crashes but you should get a segmentation fault or similar at that point. However, it's strange that [saned] quit: exiting is missing. Bye, Henning
[sane-devel] HP 7450C libusb problems
Hi, On Sun, Jun 06, 2004 at 07:42:42PM +0200, Rene Rebe wrote: So I am afraid the problem still persists, with my HP7400C anyway. Have you tried if it works on your side with an older kernel? Say 2.6.3 or so? The gt68xx backend once had a bug that caused timeouts and frozen scanners. However, that bug only occured with some scanners and only with UHCI host controllers. As I used an OHCI controller at that time, I couldn't reproduce the bug at all. But it did exist. So looking at which kind of host controller the bug shows up and even which mainboard is used may help to find out what's actually going on. Bye, Henning
[sane-devel] HP 7450C libusb problems
Hi, On Sun, Jun 06, 2004 at 08:12:51PM +0200, ins...@piments.com wrote: Yes this seems to be a pretty broad issue with sane/libusb and more recent 2.6.x kernels I am getting very similar behaviour from my canoscan FB636U on Athlon-XP/Gentoo/2.6.6 kernel. That scanner is listed as untested so you were lucky if it worked. [ebuild R ] media-gfx/xsane-0.93 [ebuild R ] media-gfx/sane-backends-1.0.14-r2 [ebuild R ] dev-libs/libusb-0.1.8 Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8 The following scanners do work without any trouble: Mustek 1200 CU (mustek_usb) Mustek BearPaw 1200 CU (gt68xx) Mustek BearPaw 2400 CU Plus (gt68xx) Plustek OpticPro U16B (gt68xx) Plustek Opticpro UT16 (plustek) It was scanning briefly at one stage and I think I was running early 2.6 kernels at that time although I can not be precise. I does not appear to be a problem in the kernel itself since vuescan works perfectly on this system. That may be a hint, but needn't as SANE may trigger a bug in the kernel by accessing the scanner differently. If sane is going to continue to be an option it appears some dev work is needed to resolve this issue. First, we need to find out when this bug happens and in which part of SANE or the kernel it is. Could someone remind me what the debug line is for this scanner so I can get more detailed output. export SANE_DEBUG_CANON630U=255 For USB debug messages try also: export SANE_DEBUG_SANEI_USB=255 Bye, Henning
[sane-devel] HP 7450C libusb problems
Hi, On Sun, Jun 06, 2004 at 08:25:52PM +0200, Henning Meier-Geinitz wrote: Yes this seems to be a pretty broad issue with sane/libusb and more recent 2.6.x kernels As already mentioned on this list and in the bug tracking system (https://alioth.debian.org/tracker/index.php?func=detailaid=300759group_id=1308atid=410366) scanning fails with libusb if the scanner is accessed during that scan. This access can even be caused by sane-find-scanner. Maybe these two problems are in fact the same? E.g. when some hotplugscript tries to access the scanner while it's opened by sane? I don't know if it's at least theoretically possible to cause the double access bug by a bug in sane. As the libusb device is claimed by sane, it shouldn't be possible to send anything to the device while the interface is claimed. Bye, Henning
[sane-devel] sane :: plustek opticslim m12
Hi, On Sun, Jun 06, 2004 at 12:49:23PM -0700, Ciprian Manea wrote: ps. yes, OpticSlim M12 it's an AutoFeed scanner (small format, marketted as a notebook scanner :) This is the first autofeed scanner that will (hopefully) be supported by the gt68xx backend so you'll need some more effort than for a flatbed scanner. I tried to fix the source, Please send a patch of the changes you did so far, especially gt68xx_devices.c. and make scanimage ignore this 'power' stuff, The next gt68xx version will have a flag to disable that test as it doesn't work with other Plustek scanners, either. but then the scanning is verry erratic. it will feed the page, too fast to do any scanning I guess (indicator light will be solid green. usually under Win the light is blinking during operation/scanning); then it will properly eject the page (that is, feeding it much faster to the 'exit' :) Any advice on what should be done from this point? thanks! Make a logfile of the windows scan process using the sniffusb program. Anaylze the log file and add the changes to the gt68xx backend. Check especially the 20 01 (setup scan) command and the move mohme commands. [gt68xx] gt68xx_device_generic_req: command=0x3f [gt68xx] 3f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] sane_open: power control failure: check power plug! Just disable this test. Bye, Henning
[sane-devel] OS/2 specific patch for sane-backends/backend/dll.c
Hi, On Wed, Jun 02, 2004 at 10:31:30PM +0200, Franz Bakan wrote: On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote: What about tools/? There is already a script called by the Makefile. You could call it from backend/Makefile if the install target is run on OS/2. tools/ is fine. I've added the script to the tools directory. If you want to call it automatically from backend/Makefile please send a patch for the install traget that only executes when os2 is used. I'd change the license to just GPL. E.g. at the moment, nobody is allowed to use your script (only copy, distribute and modify it) :-) Change it to what you think is best. I am not shure if a license is necessary at all for such a short script, but I'm not a lawyer and don't know if there are sane-project-specific rules for these things. Better add a license to everything to avoid discussions. I've used GPL in this case. Please check if the script still works. By the way, your website says: Optionally you can remove support for scanners you don't need to make compiling faster and libsane.dll smaller. For this purpose you have to modify sane-backends-1.0.14/backend/Makefile.in and remove the scanners you don't need from the list which starts with: PRELOADABLE_BACKENDS = That doesn't work anymore. Just run configure like this: BACKENDS=net mustek whatever ./configure Or modify backend/Makefile after it was generated by configure. Also --enable-translations has been the default setting for some time now. Bye, Henning
[sane-devel] canon lide 80
Hi, On Sun, May 30, 2004 at 07:56:07PM +0200, Mark Pustjens wrote: i wanted to confirm that the canon lide 80 indeed has the GL841 chip output from sane-find-scanner -v -v: found USB scanner (vendor=0x04a9 [Canon], product=0x2214 [CanoScan], chip=GL841) at libusb:003:004 Thanks. I've added that to our lists. Bye, Henning
