Source Priority Failing checks
<p>
SCSI scanners are normally detected.
If difficulties arise proceeding with <b>Add</b>,
check whether your scanner is shown by the command <tt>lsscsi</tt>.
If not, the SCSI system cannot communicate with the scanner.
Verify that an appropriate kernel module for the SCSI host adapter has been loaded.
</p>
Medium
<p>
Parallel port scanners cannot be configured with this tool
except for HP all-in-one devices.
Common parallel port scanners must be configured manually.
To set up the scanner unit in a HP all-in-one device,
which is connected to the parallel port,
you may have to run <tt>hp-setup</tt> via <b>Other</b> and <b>Run hp-setup</b>
before you can configure the scanner unit with this tool using <b>Add</b>.
</p>
Medium
<p>
Network scanners cannot be configured with this tool
except for HP all-in-one devices.
Network scanners must be configured manually.
A network scanner is a scanner that has a network interface
so it is directly accessible in the network.
In contrast, scanning via network means accessing a remote scanner
connected to another host in the network.
To set up the scanner unit in a HP all-in-one device,
which is connected via a built-in network interface,
you may have to run <tt>hp-setup</tt> via <b>Other</b> and <b>Run hp-setup</b>
before it works to configure the scanner unit with this tool using <b>Add</b>.
</p>
Medium
<p>
The table lists the configured drivers with their associated scanners.
Press <b>Add</b> to select model and driver and enable it.
Press <b>Edit</b> to select and enable a driver.
Press <b>Delete</b> to disable the driver.
If you press <b>Other</b>, you can restart the detection, test enabled drivers,
set up HP all-in-one devices, or set up scanning via network.
</p>
Medium
<p>
If a driver is set up but no scanner is recognized by the driver, possible reasons are:
The scanner is not connected or switched off,
the driver is not the right one for the particular model
(even small differences in model names or internal differences in
the same model series may require different drivers),
there are low-level (kernel related) device communication problems
(e.g. a low-level USB problem or a low-level SCSI problem).
</p>
Medium
<p>
<b><big>Scanner Model Selection</big></b><br>
All known scanner models, both supported and unsupported, are listed here.
Read all information carefully before selecting a model and pressing <b>Next</b>.
The information is based on data of the SANE project at
<tt>http://www.sane-project.org/</tt>.
</p>
Medium
<p>
A model is supported if there is at least one appropriate scanner driver available.
Most scanner drivers are from the SANE project and provided in the sane-backends package.
The support status for a particular model varies from minimal to complete.<br>
When a driver is shown as 'unmaintained', it does not mean that the driver does not work.
Even an unmaintained driver could work perfectly well.
But it means that there is no longer someone who knows about the driver internals
so that there is usually no help if there are issues with an unmaintained driver.
</p>
Medium
<p>
Even if a model has no driver available, the manufacturer might have a driver.
Therefore, you should ask the scanner manufacturer for a driver for an unsupported scanner.
</p>
Medium
<p>
When additional comments are available, they are shown in square brackets.
</p>
Medium
<p>
Use the <b>Search String</b> to find an appropriate entry quickly.
To find some text anywhere in the table, enter it in the field.
A more complicated search using a case-insensitive regular expression is also possible.
If the scanner was detected and the manufacturer name is available in this list,
the search string is preset with the manufacturer name, such as <tt>^Epson.*</tt>.
To refine the search results, append model-specific details to the search string.
For example, append a word that is part of the model name as in <tt>^Epson.*perfection</tt>
or append some digits that are part of the model name as in <tt>^Epson.*1200</tt>.
</p>
Medium
<p>
<b><big>Scanner and Driver Setup</big></b><br>
The driver is activated and the associated scanners are probed.
This may take a few seconds, so you must wait until you can press <b>Next</b>.
If you press <b>Back</b>, the driver is deactivated.
</p>
Medium
<p>
<b><big>Additional Packages</big></b><br>
If the package that provides the driver is not yet installed,
an appropriate dialog is shown to install the package.
Such packages may not be available for all architectures.
</p>
Medium
<p>
<b><big>Firmware Upload</big></b><br>
Some models require a firmware upload.
In this case, an appropriate explanatory text is shown.
</p>
Medium
<p>
<b><big>HP All-in-One Devices</big></b><br>
HP all-in-one devices may require a special setup.
In this case, an appropriate dialog is shown.
There are two software packages that provide support for HP all-in-one devices:
the outdated HPOJ software (package hp-officeJet which is no longer available),
which provides the PTAL system (with the ptal service) to access HP all-in-one devices,
and the up-to-date HPLIP software (package hplip), which provides the hpaio driver.
Both software packages can be installed at the same time
but the ptal service and the hpaio driver cannot run together.
Therefore either the patl service or the hpaio driver
must be used for all HP all-in-one devices.
</p>
Medium
<p>
<b><big>Scanning via Network</big></b><br>
Enter the appropriate information and press <b>Next</b>
to set up scanning via network.
</p>
Medium
<p>
<b><big>Server Settings</big></b><br>
If you have locally connected scanners and want to make them accessible via the network,
set up the saned network scanning daemon so that your host becomes a server.
In <b>Permitted Clients</b>, enter which client hosts are permitted to access saned on your server.
Enter a comma-separated list of client hosts (hostnames or IP addresses)
or subnets (CIDR notation, such as 192.168.1.0/24).
If no client hosts are permitted, saned is not activated.
If saned is activated, xinetd is also activated and set up for saned.
</p>
Medium
<p>
<b><big>Regarding Firewall</big></b><br>
A firewall is used to protect running server processes
on your host against unwanted access via network.
For using scanners via network the SANE network daemon (the saned)
is the server process which must run so that remote clients
can access scanners which are connected to your local host.
Client hosts contact the saned via the sane-port (TCP port 6566)
but scanning data is transferred via an additional random port.
Therefore only port 6566 is not sufficient for scanning via network.<br>
Do not open the sane-port 6566 or any other port
regarding using scanners for the external zone in the firewall.
This is dangerous because it allows access to the saned from foreign hosts
so that the firewall does no longer provide any protection for the saned.
Allowing access from the external network (i.e. for the external zone)
does not make sense because scanning documents requires
physical scanner access by trusted users.<br>
On the other hand the default firewall settings allow
any access from an internal (i.e. trusted) network.
To make the saned on your server accessible from an internal network,
assign the network interface which belongs to the internal network
to the internal zone of the firewall.
Use the YaST Firewall setup module to do this fundamental setup
regarding network security and firewall and scanning via network
will work without any further firewall setup.<br>
For details see the openSUSE support database
article 'CUPS and SANE Firewall settings' at<br>
http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings
</p>
Medium
<p>
<b><big>Client Settings</big></b><br>
If you want to access scanners connected to other hosts (servers) in the network,
set up the net metadriver to access them via the daemon running on the servers.
The saned and the firewall on the servers must permit the access.
In <b>Servers Used</b>, enter which servers should be used.
Enter a comma-separated list of servers (server names or IP addresses).
If no servers are entered, net is not activated.
</p>
Medium
<p>
<b><big>Local Host Configuration</big></b><br>
By using the loopback network, saned and the net metadriver
can be used even on your local host.
In this case, the server and client are the same machine (localhost).
Some scanners, such as parallel port scanners, require root privileges.
When you enter <tt>localhost</tt> for both the server and the client,
you can access such a scanner even as a normal user on your local host.
</p>
Medium
Initializing...
Medium
The error message is:

%1
Medium
Failed to determine the version of package %1.
Medium
The third-party Image Scan driver software from Epson/Avasys is required.
The Image Scan driver software is made and provided by Epson (formerly Avasys)
http://download.ebz.epson.net/dsc/search/01/search/?OSC=LXEpson
(formerly Avasys http://avasys.jp/eng/linux_driver/)
where RPM packages for 32-bit (i386) and 64-bit (x86_64) architecture
can be downloaded (if you accept the Epson/Avasys license agreements).
The Image Scan driver contains proprietary binary-only software.
For some models it is only available for 32-bit (i386) architecture
which does not work when you have a 64-bit system installation.
Some scanners are also supported by another (free-software) driver.
When your scanner model requires a DFSG non-free (proprietary) module,
you have to download and install two packages from Epson/Avasys:
The 'iscan' package for the base software and an additional
model dependant 'iscan-plugin' package with the proprietary module.
Medium
Required package %1 is not installed and there is no package repository available.
Medium
Required package %1 is not installed and not available in the repository.
Medium
Failed to install required package %1.
Medium
Failed to determine the active scanners.
If the net metadriver is activated while there is a problem
with the network, the 'scanimage -L' command may not respond. For example,
this may happen if communication with a server used by the net metadriver
gets distorted because a firewall drops some network traffic.
In this case, disable the net metadriver until the issue in the network is fixed.
Medium
Failed to determine the active scanners.
Medium
File %1 does not exist.
Medium
Failed to read %1.
Medium
Failed to determine the active drivers.
Medium
Failed to detect scanners automatically.
Medium
Initializing Scanner Configuration
Medium
Check installed packages
Medium
Read or create the scanner database
Medium
Determine active scanners
Medium
Determine active drivers
Medium
Detect scanners
Medium
Checking installed packages...
Medium
Reading or creating the scanner database...
Medium
Determining active scanners...
Medium
Determining active drivers...
Medium
Detecting scanners...
Medium
Finished
Medium
Creating scanner database...
Medium
Aborting: Failed to create the scanner database.
Medium
Aborting: Failed to read %1.
Medium
Writing Scanner Configuration
Medium
Save the actual environment
Medium
Saving the actual environment...
Medium