Hello ;=)
I’m trying to have my Ethernet Lexmark Platinum pro 905 printer being able to scan from openSUSE 42.1 Leap.
It does work from windows but under linux skanlite and xsane do not see the scanner (both tell me thay can’t find the scanner).
(print and copy are ok, but scanning is not for device is not seen by scanning softs 
)
I installed this driver from driverscollection.com : lexmark-inkjet-legacy-wJRE-1.0-1.x86_64.rpm.sh
I’m using static ip, which should help. Is Ethernet connection disturbing skanlite or xsane ?
How can i solve this ?
Hopefully xsane’s help gives me various options for peripheral not being detected, i’m thus investigating these :
1- no device supported by sane, how do i see which devices are supported ?
http://www.sane-project.org/sane-backends-1.0.24.html#S-LEXMARK shows a figure but only usb interface … i’m i stuck when using ethernet interface ?
2- supported devices are busy , ho do i see scanner or device state ? (cups status says Idle , does it suffice ?)
3-permissionsfor the device file do not allow to use it, try as root
what shall i try then ?
4-backend is not loaded by sane (man sane-dll)
still looking at this, but i have none dll.conf in /usr/lib64/sane.
i have /etc/sane.d/dll.conf which contains : lexmark, LexmarkLegacy_1_0_0, Lexmark_1_0_0, lexmark_nscan
do i need to add /etc/sane.d/dll.d file ? with which backend ?
5- backend is not configured correctly (man sane-“backendname”)
no clue how to be sure it is ok here.
6- more than one version is installed :
is this being the problem ?
i have this :
> rpm -qa | grep sane
xsane-0.998-25.2.x86_64
sane-backends-autoconfig-1.0.24-3.7.x86_64
sane-backends-32bit-1.0.24-3.7.x86_64
libksane0-15.08.3-1.1.x86_64
hplip-sane-3.15.11-132.1.x86_64
sane-backends-1.0.24-3.7.x86_64
With the help from someone on irc i also tried other ways but still ko :
- adding static ip in config files https://wiki.archlinux.org/index.php/SANE#Accessing_your_scanner_from_a_remote_workstation
- i tried various drivers from lexmark ( lexmark-printer-utility-1.0-1.x86_64,network-scan-linux-glibc2-x86_64, lexmark-PPD-Files-LMAD4-1.0-1.x86_64).
They offer 2015 driver versions but either i can’t print (cups says a file is missing ) , or i have a network scan driver that is not able to see the scan device (after adding static ip it says ip or host is wrong from xsane and skanlite).
is the last one (ppd) useful ? I haven’t tried it yet.
I went back to the legacy driver, it at least allows me to print and copy.
Thanks 
Here’s what i have :
zypper info xsane
Chargement des données du dépôt...
Lecture des paquets installés...
Informations sur package xsane :
--------------------------------
Dépôt : oss
Nom : xsane
Version : 0.998-25.2
Arch : x86_64
Fabricant : openSUSE
Installé : Oui
> ls -al /usr/lib/sane/ | grep lexmark
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so.1 -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so.1.0.18 -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 25 12 nov. 18:51 libsane-lexmark.so.1 -> libsane-lexmark.so.1.0.24
-rwxr-xr-x 1 root root 100856 25 oct. 13:58 libsane-lexmark.so.1.0.24
fabrice@openSUSE421:~> ls -al /usr/lib64/sane/ | grep lexmark
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so.1 -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 67 30 déc. 16:02 libsane-LexmarkLegacy_1_0_0.so.1.0.18 -> /usr/local/lexmark/legacy/lib/libsane-LexmarkLegacy_1_0_0.so.1.0.18
lrwxrwxrwx 1 root root 25 12 nov. 18:51 libsane-lexmark.so.1 -> libsane-lexmark.so.1.0.24
-rwxr-xr-x 1 root root 102080 25 oct. 13:56 libsane-lexmark.so.1.0.24
> 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-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1ea7/0x0026 at 003:003: Access denied (insufficient permissions)
could not open USB device 0x046d/0xc318 at 003:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
... in root :
# 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-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
