Hello, On Jan 26 10:44 ken wrote (shortened):
On Thu, 26 Jan 2006 14:27:56 +0100 (CET) Johannes Meixner <jsmeix@suse.de> wrote:
According to what I found on the SANE home page and in the sane-microtek2 man page there is only SCSI mentioned.
Could it be the case that you had it working via SCSI and now you try to use it via USB?
This is true. This scanner has ports for both SCSI and USB.
When I launch "Yast2 > Hardware > Scanner", in the "Autodetected Scanners" box I'm shown "USB Scanner (vendor=0x05da, product=0x20b0) at libusb:002:002". This, after making the changes already mentioned in this thread.
I don't know for sure if it is not supported by the microtek2 backend via USB but "sane-find-scanner" (that's also what YaST uses to find scanners) can detect USB scanners via special USB chipset detection (see "man sane-find-scanner") to distinguish scanners from other USB devices. In your case "sane-find-scanner" correctly detected that there is a USB scanner but this does not mean that it is supported by a driver in SANE, see "man sane-find-scanner": "sane-find-scanner will even find USB scanners, that are not supported by any SANE backend". Unfortunately I don't have exact information which SCSI+USB scanner is supported only via SCSI or only via USB so that I cannot show an appropriate message in YaST. There is an "interface" keyword in the SANE description files but I don't know for sure if this is always correct. I.e. if only "SCSI" is mentioned does this really mean that "USB" is not supported?
When I then click on "Configure" I'm given the list of drivers (="backends"?) and select the one for Microtek X12USL. Clicking on "Next", the next panel shows that "microtek2" as an "Active Driver", but lists no "Active Scanner". Telling me the same thing as "scanimage -L".
Guess which command is executed by YaST to determine an "Active Scanner"? Have a look at /usr/lib/YaST2/bin/*scanner* Summary: YaST does exactly what is in compliance with SANE to detect and set up a scanner. YaST uses only the SANE tools. YaST does not use selfmade magic. Therefore what you get with YaST should be (hopefully) exactly the same which you would get by using the SANE tools. What YaST not does is special changes in the backend config files (e.g. in /etc/sane.d/microtek2.conf). The reason is that the defaults in backend config files are such that it is safe. For excample you can enforce most backends to recognise any USB device as a scanner with arbitrary consequences, see for example /etc/sane.d/epkowa.conf: "... you may, at your own peril(!!), force the backend to recognise ..." I will not let any innocent user do such things via YaST.
Johannes, one part of the documentation I didn't understand concerned the libraries (found in /usr/lib/sane/). Perhaps you could clarify what needs to be done there and how to ensure it's been done (correctly).
Please be more specific which section in which part of the documentation you do not understand and what exactly your question is. I don't know what should be done in /usr/lib/sane/. Simply installing the package sane (YaST would force you to have "sane" installed when you set up a scanner and if necessary, YaST would install other neded packages like "iscan") and all should be o.k. in /usr/lib/sane/. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/