Don't forget to re start xinetd :. If scanimage -L is unable to identify the scanner, it will look like this:. In most cases, the first step to take in resolving this issue is to run sane-find-scanner as root. If the output does not contain a line saying that the scanner was detected, it probably will not work with SANE.
Assuming sane-find-scanner does find the scanner, as in the example above, there are a few things to check. First, try running sane-find-scanner as a non-root user. If it fails to detect the scanner when run this way, that means the problem is most likely permissions on the device node. The man page for the device type will have more information on how to handle this. For USB scanners:. Make sure that the correct device was identified, e.
If not, it means that SANE is detecting something other than the scanner. If the correct device is detected, it may be necessary to edit the configuration file for the corresponding SANE backend.
The man page for the backend will have more information on what edits may be necessary, for example:. This will create the file outfile.
Note Users of systemd might not need to add users to the scanner group. However, please note that more development and testing is needed before all of these cameras will be supported by SANE backend. See gphoto2 5. See sane-dll 5. The SANE network daemon saned 8 provides access to scanners located on different computers in connection with the net backend.
See sane-net 5 and saned 8. PNM image reader pseudo-backend. The purpose of this backend is primarily to aid in debugging of SANE frontends. See sane-pnm 5. See sane-pint 5. Tests frontends and the SANE installation. It provides test pictures and various test options. See sane-test 5. See sane-v4l 5. By default, all SANE backends drivers are loaded dynamically by the sane-dll meta backend. If you have any questions about the dynamic loading, read sane-dll 5.
SANE frontends can also be linked to other backends directly by copying or linking a backend to libsane. It's not hard to write a SANE backend. It can take some time, however. You should have basic knowledge of C and enough patience to work through the documentation and find out how your scanner works.
Appended is a list of some documents that help to write backends and frontends. If you start writing a backend or frontend or any other part of SANE, please contact the sane-devel mailing list for coordination so that work is not duplicated. The shared libraries implementing the backends present on systems that support dynamic loading. If your device isn't found but you know that it is supported, make sure that it is detected by your operating system.
It prints one line for each scanner it has detected and some comments. If sane-find-scanner 1 finds your scanner only as root but not as normal user, the permissions for the device files are not adjusted correctly. If the scanner isn't found at all, the operating system hasn't detected it and may need some help. Depending on the type of your scanner, read sane-usb 5 or sane-scsi 5.
If your scanner or other device is not connected over the SCSI bus or USB, read the backend's manual page for details on how to set it up. Is your scanner detected by the operating system but not by SANE?
Try scanimage -L. Some backends are commented out by default. Remove the comment sign for your backend in this case. Also some backends aren't compiled at all if one of their prerequisites are missing. If you need one of these backends and it isn't available, read the build instructions in the README file and the individual manual pages of the backends.
Another reason for not being detected by scanimage -L may be a missing or incorrect configuration in the backend's configuration file. While SANE tries to automatically find most scanners, some can't be setup correctly without the intervention of the administrator.
Also on some operating systems auto-detection may not work. Check the backend's manual page for details. If your scanner is still not found, try setting the various environment variables that are available to assist in debugging. The environment variables are documented in the relevant manual pages.
The debug messages for the dll backend tell if the mustek backend was found and loaded at all. The mustek messages explain what the mustek backend is doing while the SCSI debugging shows the low level handling.
This command starts a scan for the default scanner with default settings. All the available options are listed by running scanimage --help.
If scanning aborts with an error message, turn on debugging as mentioned above. NOTE: You need the 64 bit. Run the following command to install the driver you just downloaded note: the example below is for the brscan2 package. You will have to change the file name to match what you downloaded dpkg -i --force-all brscan When you run that tool, you need to append the device name what you want to call it , the model number and the ip address of the scanner.
In the example below, we are using the "brsaneconfig2" tool, we calling the scanner " MyScanner ", the model we are installing is the MFCCN and the IP address is Each of these tools supports a different set of scanners, and you need to download the appropriate package for your scanner. Because it is possible to install many different scanners, you need to run the proper version of the brsaneconfig tool. If your scanner is supported by the brscan3 tool, you will need to run the brsaneconfig3 tool to configure it.
See the Ubuntu SANE Troubleshooting guide for specific instructions on troubleshooting these scanners using the symlink and udev rules. Partners Support Community Ubuntu.
0コメント