6. Scanner specifics

6.1. HOW TO do my scanner

Many scanners have small howto's or FAQ's. Always try them. The fact, that a scanner is included in this list does not mean that I think the scanner specific howto or FAQ is insufficient or that the backend is buggy. It just means I got questions, and most came from the mailinglist,

Also, look at the USB, SCSI and paralell-port sections. Your problem might not be so scanner specific as you thought..

6.2. I need more information on HP scanners.

Take a look at: http://www.kirchgessner.net/sanehpfaq.html

6.3. Snapscan problems

There is a lot of development work going on. A separate testing-group has been formed.

Some hints:

1. Do not have a /dev/scanner link if your using USB. It just confuses to much of the current code.
2. Make a symbolic link from /dev/usb/scanner0 to /dev/usbscanner (if your scanner is really at scanner0).
3. Make sure you have modified your snapscan.conf file and have /dev/usbscanner listed in it.
4. Do not run scanimage from the backend directory (it will use the wrong snapscan.conf file).
5. run scanimage with -d snapscan:/dev/usbscanner
6. Try to recompile SANE with the LATEST backend (dates are inside the files) downloaded from Part of the problem is that the device name /dev/usbscanner is hardcoded in parts of the scapscan USB driver. http://sourceforge.net/projects/snapscan
7. If you use Mandrake, Edit /etc/sane.d/dll.conf, and double check that there is a line containing snapscan (NOT SnapScan !)

6.4. I can't get my USB snapscan to work. Where can I find more info?

http://www.ginko.de/user/oschwartz/snapscan

6.5. Microtek problems

6.6. It gives a line: "model 0x53 not supported" (or other number)

Try the latest version. If that doesn't work: set 'option dump 2' in the microtek2.conf file and post the contents of the inquiry block to the mailing-list (indicated by [inquiryresult] ). This will help to determine which backend should handle this model.

6.7. Epson

6.8. How to install the Epson Cx3200 scanner device without recompiling the whole kernel.

The present scanner module doesn't like multiple interfaces on the same device. A patch that allow accepting devices with more than one interface was accepted by the Linux USB maintainer so it will most likely fixed in one of the next kernel versions. But you probably don't have that kernel yet. So you have to do the following:

Make a backup of /usr/src/<kernelversion>/drivers/usb/scanner.c and /lib/modules/<kernelversion>/kernel/drivers/usb/scanner.o

Become root or su and edit /usr/src/<kernelversion>/drivers/usb/scanner.c as follows:

find the lines:

 if (dev->config[0].bNumInterfaces != 1) {
 
 info("probe_scanner: Only one device interface is supported.");
 
 return NULL;
 
 }

and make the lines inactive as shown below.

 /* if (dev->config[0].bNumInterfaces != 1) {
 
 * info("probe_scanner: Only one device interface is supported.");
 
 * return NULL;
 
 * }
 
 */

After this create a new directory to a place of your choice i.e: /usr/src/modules

Copy /usr/src/<kernelversion>/drivers/usb/scanner.c and /usr/src/<kernelversion>/drivers/usb/scanner.h to the above mentioned directory.

Then compile a new module as follows (kernelversions 2.4.x):

 gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/include -include /usr/src/linux/include/linux/modversions.h -c scanner.c

this will result in a scanner.o file. Copy this file to /lib/modules/<kernelversion>/kernel/drivers/usb Do a rmmod scanner as root. (might not be necessary if no scanner device was loaded) If the modules are compressed and look like scanner.o.gz ,remove the original file and create with gnozip or ark a new archive file called scanner.o.gz (yes, same as above) and add the scanner.o to it.

After this is finished insert the new module with:

modprobe scanner vendor=0x04b8 product=0x0802

This should be enough to get the scanner up.

You can select the scanner of choice in this case a Epson perfection 1200U.

6.9. UMAX problems

As I have an UMAX myself, there are many questions about the UMAX. Please send in logs of your experiences with other scanners.

6.10. After system boot, my scanner makes a fast loud clicking noise

TURN OFF THE SCANNER!!! QUICK!!

Leaving it on will seriously damage your scanner.

6.11. I can't get the scanner to work with the SCSI-interface that comes by default with this scanner

Don't use that card. Get a good SCSI-card for scanning.If you want to buy a new one, Oliver suggested a symbios logic 53c8xx.

If you really want to try: the UDS-IS11 is a DTC3181E-card based on the NCR5380-chip. On linux you may have the chance to get it work with the recent g_NCR5380-driver. The card does not have IRQ/DMA.

Try the following option for kernel:

 dtc 3181e=0x280,255

or

 dtc3181e=0x280,255

or use the following command:

 insmod g_NCR5380 ncr_irq=255 ncr_addr=0x280 dtc_3181e=1

or

 insmod g_NCR5380 ncr_irq=255 ncr_addr=0x280 dtc3181e=1

(some have reported with an underscore, but someone else without; I have no way to check which is correct for which version of kernel)

6.12. Will there be a support for the UMAX-parallel-port/UMAX-USB-scanners?

UMAX published their SCSI-protocol for scanners. However they have not so far published parallel port and USB protocols. Without the protocol documentation development will not be done.

The UMAX parallel port backend is part of SANE 1.0.6: http://umax1220p.sourceforge.net/ There is also a project for the UMAX ASTRA 1200u USB scanner: http://umax1220u-sane.sourceforge.net/

The Astra 2200W does work when connected via SCSI. It could work with SCSI-via-USB-driver and connected via USB, but that is not tested.

6.13. Does SANE and the umax backend work on LinuxPPC / big endian machine ?

There are people using the sane-umax on a LinuxPPC (big endian) machine. Other people write that they can not scan on a LinuxPPC. It looks like this is a problem with the driver of the scsi card. The "MESH" SCSI card is reported to work. The NCR53C94 SCSI card seems not to work.

6.14. I am using an AM53C974 based scsi card with a umax scanner, the system freezes when I start a scan, what can I do?

Try the recent driver for the scsi card, take a look at:

http://www.garloff.de/kurt/linux/dc390/index.html