Problèmes et questions concernant le noyau et le support matériel.
Répondre

scanner non reconnu

#1Messageil y a 4 ans

Bonjour, mon imprimante imprime des caractères ascii et le scanner n'est pas reconnu:

lsusb
Bus 002 Device 002: ID 04b8:1117 Seiko Epson Corp. XP-540 Series

sane-find-scanner -q
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x04b8, product=0x1117) at libusb:002:002
Je suis passé sur un noyau plus récent que celui par défaut mais ça n'a rien changé:

uname -a
Linux manjaro 5.3.6-1-MANJARO #1 SMP PREEMPT Sat Oct 12 09:30:05 UTC 2019 x86_64 GNU/Linux
Pouvez-vous m'aider?

scanner non reconnu

#2Messageil y a 4 ans

J'ai depuis peu une Epson xp355 et n'ai eu aucun soucis pour l'installer. Le scanner fonctionne nativement.
Je suis actuellement sur la route et te donnerai la liste des paquets installés concernant cette imprimante quand je serai rentré.
En attendant, vérifie que tu aies bien le paquet epson-inkjet-printer-escpr 1.7.4-1 dispo dans Aur.
Edit: Je vois que tu as aussi posté chez nos amis d' Archlinux.fr.
Essaye en installant un kernel plus récent comme par exemple le 5.3

scanner non reconnu

#3Messageil y a 4 ans

Comme mentionné dans mon message, je suis déjà sous ce noyau.
epson-inkjet-printer-escpr 1.7.4-1 est installé.
Merci de ton aide.

scanner non reconnu

#4Messageil y a 4 ans

Je précise que malgré tout mon problème n'est pas résolu!

scanner non reconnu

#5Messageil y a 4 ans

Bonjour.
J'ai regardé chez moi et en plus du pilote epson, j'ai aussi les paquets sane, iscan et iscan-data:

 
 extra/sane 1.0.28-1 [installed]
 community/iscan 2.30.3.1-2 [installed]
 community/iscan-data 1.39.0.1-2 [installed]
 aur/epson-inkjet-printer-201203w 1.0.0-9 [installed] (3) (0,89)
Si ça peut t'aider.

scanner non reconnu

#6Messageil y a 4 ans

Regarde si par hasard ton scanner ne serait pas décrit dans /lib/udev/rules.d//lib/udev/rules.d
moi, j'ai :

# EPSON XP-540 | EPSON XP-640 | EPSON PID 1117
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="1117", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
Les Ids correspondent à ce que tu as récupéré de ta commande
found USB scanner (vendor=0x04b8, product=0x1117) at libusb:002:002
J'ai eu ce problème avec mon scanner Canon, mais c'était il y a quelques temps.

scanner non reconnu

#7Messageil y a 4 ans

Bonsoir, en ce qui me concerne ce fichier semble vide.
Par contre la situation a évolué. Je me suis rendu compte que mon imprimante est gérée par imagescan, que j'ai dû installer, et je dois lancer le scanner par

$ utsushi
Depuis je peux imprimer et scanner, mais je ne peux pas enregistrer le fichier obtenu. Donc le problème n'est que partiellement résolu puisque je ne peux pas conserver le document scanné...

scanner non reconnu

#8Messageil y a 4 ans

J'ai vu qu'il y a un paquet imagescan-plugin-networkscan dans Aur....

scanner non reconnu

#9Messageil y a 4 ans

En fait j'ai déjà installé ce paquet:

yay -a imagescan                                                         
1 aur/imagescan-plugin-networkscan 1.1.3-1 (+15 1.07%) (Installed)

scanner non reconnu

#10Messageil y a 4 ans

Bonsoir, j'ai galéré pendant plusieurs mois avec une imprimante de cette marque. Normalement, nous devons installer le paquet spécifique de l'imprimante mais il n'est pas fourni dans Aur pour la XP-540. Le fait qu'imagescan reconnait ton scanner est une avancée significative dans la résolution mais, s'il est impossible d'enregistrer le document numérisé... :? Tu peux essayer le paquet

1 community/simple-scan
en croisant les doigts pour que la reconnaissance se fasse. Un tout petit paquet rapide à installer/désinstaller, selon le résultat, en désespoir de cause.

scanner non reconnu

#11Messageil y a 4 ans

Bonsoir Erwan, merci pour ta réponse mais hélas simple-scan, que j'ai déjà installé, ne reconnait pas mon scanner. :desole:

scanner non reconnu

#12Messageil y a 4 ans

Je ne sais pas si ça peut aider mais je constate que /etc/imagescan est absent...

scanner non reconnu

#13Messageil y a 4 ans

hapkin a écrit : il y a 4 ans Je ne sais pas si ça peut aider mais je constate que /etc/imagescan est absent...
Voici la liste des fichiers composant ce paquet:

$ pacman -Fl imagescan
imagescan etc/
imagescan etc/sane.d/
imagescan etc/sane.d/dll.d/
imagescan etc/sane.d/dll.d/utsushi
imagescan etc/udev/
imagescan etc/udev/rules.d/
imagescan etc/udev/rules.d/utsushi-esci.rules
imagescan etc/utsushi/
imagescan etc/utsushi/combo.conf
imagescan etc/utsushi/utsushi.conf
imagescan usr/
imagescan usr/bin/
imagescan usr/bin/utsushi
imagescan usr/include/
imagescan usr/include/utsushi/
imagescan usr/include/utsushi/array.hpp
imagescan usr/include/utsushi/buffer.hpp
imagescan usr/include/utsushi/condition-variable.hpp
imagescan usr/include/utsushi/connexion.hpp
imagescan usr/include/utsushi/constraint.hpp
imagescan usr/include/utsushi/context.hpp
imagescan usr/include/utsushi/cstdint.hpp
imagescan usr/include/utsushi/descriptor.hpp
imagescan usr/include/utsushi/device-info.hpp
imagescan usr/include/utsushi/device.hpp
imagescan usr/include/utsushi/exception.hpp
imagescan usr/include/utsushi/filter.hpp
imagescan usr/include/utsushi/format.hpp
imagescan usr/include/utsushi/functional.hpp
imagescan usr/include/utsushi/i18n.hpp
imagescan usr/include/utsushi/iobase.hpp
imagescan usr/include/utsushi/key.hpp
imagescan usr/include/utsushi/log.hpp
imagescan usr/include/utsushi/media.hpp
imagescan usr/include/utsushi/memory.hpp
imagescan usr/include/utsushi/monitor.hpp
imagescan usr/include/utsushi/mutex.hpp
imagescan usr/include/utsushi/octet.hpp
imagescan usr/include/utsushi/option.hpp
imagescan usr/include/utsushi/pattern/
imagescan usr/include/utsushi/pattern/decorator.hpp
imagescan usr/include/utsushi/preset.hpp
imagescan usr/include/utsushi/pump.hpp
imagescan usr/include/utsushi/quantity.hpp
imagescan usr/include/utsushi/range.hpp
imagescan usr/include/utsushi/regex.hpp
imagescan usr/include/utsushi/run-time.hpp
imagescan usr/include/utsushi/scanner.hpp
imagescan usr/include/utsushi/signal.hpp
imagescan usr/include/utsushi/store.hpp
imagescan usr/include/utsushi/stream.hpp
imagescan usr/include/utsushi/string.hpp
imagescan usr/include/utsushi/tag.hpp
imagescan usr/include/utsushi/thread.hpp
imagescan usr/include/utsushi/toggle.hpp
imagescan usr/include/utsushi/type-traits.hpp
imagescan usr/include/utsushi/value.hpp
imagescan usr/lib/
imagescan usr/lib/sane/
imagescan usr/lib/sane/libsane-utsushi.so
imagescan usr/lib/sane/libsane-utsushi.so.1
imagescan usr/lib/sane/libsane-utsushi.so.1.0.28
imagescan usr/lib/utsushi/
imagescan usr/lib/utsushi/doc-locate
imagescan usr/lib/utsushi/esci-interpreter
imagescan usr/lib/utsushi/get-text-orientation
imagescan usr/lib/utsushi/libcnx-hexdump.so
imagescan usr/lib/utsushi/libcnx-hexdump.so.0
imagescan usr/lib/utsushi/libcnx-hexdump.so.0.0.0
imagescan usr/lib/utsushi/libcnx-usb.so
imagescan usr/lib/utsushi/libcnx-usb.so.0
imagescan usr/lib/utsushi/libcnx-usb.so.0.0.0
imagescan usr/lib/utsushi/libdrv-combo.so
imagescan usr/lib/utsushi/libdrv-combo.so.0
imagescan usr/lib/utsushi/libdrv-combo.so.0.0.0
imagescan usr/lib/utsushi/libdrv-esci.so
imagescan usr/lib/utsushi/libdrv-esci.so.0
imagescan usr/lib/utsushi/libdrv-esci.so.0.0.0
imagescan usr/lib/utsushi/libflt-all.so
imagescan usr/lib/utsushi/libflt-all.so.0
imagescan usr/lib/utsushi/libflt-all.so.0.0.0
imagescan usr/lib/utsushi/libutsushi-gtkmm.so
imagescan usr/lib/utsushi/libutsushi-gtkmm.so.0
imagescan usr/lib/utsushi/libutsushi-gtkmm.so.0.0.0
imagescan usr/lib/utsushi/libutsushi.so
imagescan usr/lib/utsushi/libutsushi.so.0
imagescan usr/lib/utsushi/libutsushi.so.0.0.0
imagescan usr/lib/utsushi/sane/
imagescan usr/lib/utsushi/sane/libsane-utsushi.so
imagescan usr/lib/utsushi/sane/libsane-utsushi.so.1
imagescan usr/lib/utsushi/sane/libsane-utsushi.so.1.0.28
imagescan usr/lib/utsushi/utsushi-help
imagescan usr/lib/utsushi/utsushi-list
imagescan usr/lib/utsushi/utsushi-main
imagescan usr/lib/utsushi/utsushi-scan
imagescan usr/lib/utsushi/utsushi-scan-cli
imagescan usr/lib/utsushi/utsushi-scan-gtkmm
imagescan usr/lib/utsushi/utsushi-version
imagescan usr/share/
imagescan usr/share/locale/
imagescan usr/share/locale/de/
imagescan usr/share/locale/de/LC_MESSAGES/
imagescan usr/share/locale/de/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/en/
imagescan usr/share/locale/en/LC_MESSAGES/
imagescan usr/share/locale/en/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/es/
imagescan usr/share/locale/es/LC_MESSAGES/
imagescan usr/share/locale/es/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/es_MX/
imagescan usr/share/locale/es_MX/LC_MESSAGES/
imagescan usr/share/locale/es_MX/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/fr/
imagescan usr/share/locale/fr/LC_MESSAGES/
imagescan usr/share/locale/fr/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/it/
imagescan usr/share/locale/it/LC_MESSAGES/
imagescan usr/share/locale/it/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/ja/
imagescan usr/share/locale/ja/LC_MESSAGES/
imagescan usr/share/locale/ja/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/ko/
imagescan usr/share/locale/ko/LC_MESSAGES/
imagescan usr/share/locale/ko/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/nl/
imagescan usr/share/locale/nl/LC_MESSAGES/
imagescan usr/share/locale/nl/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/pt/
imagescan usr/share/locale/pt/LC_MESSAGES/
imagescan usr/share/locale/pt/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/pt_BR/
imagescan usr/share/locale/pt_BR/LC_MESSAGES/
imagescan usr/share/locale/pt_BR/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/ru/
imagescan usr/share/locale/ru/LC_MESSAGES/
imagescan usr/share/locale/ru/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/zh_CN/
imagescan usr/share/locale/zh_CN/LC_MESSAGES/
imagescan usr/share/locale/zh_CN/LC_MESSAGES/utsushi.mo
imagescan usr/share/locale/zh_TW/
imagescan usr/share/locale/zh_TW/LC_MESSAGES/
imagescan usr/share/locale/zh_TW/LC_MESSAGES/utsushi.mo
imagescan usr/share/utsushi/
imagescan usr/share/utsushi/drivers/
imagescan usr/share/utsushi/drivers/esci/
imagescan usr/share/utsushi/drivers/esci/DS-1610.dat
imagescan usr/share/utsushi/drivers/esci/DS-1630.dat
imagescan usr/share/utsushi/drivers/esci/DS-1660W.dat
imagescan usr/share/utsushi/drivers/esci/DS-310.dat
imagescan usr/share/utsushi/drivers/esci/DS-320.dat
imagescan usr/share/utsushi/drivers/esci/DS-360W.dat
imagescan usr/share/utsushi/drivers/esci/DS-40.dat
imagescan usr/share/utsushi/drivers/esci/DS-50000.dat
imagescan usr/share/utsushi/drivers/esci/DS-510.dat
imagescan usr/share/utsushi/drivers/esci/DS-520.dat
imagescan usr/share/utsushi/drivers/esci/DS-530.dat
imagescan usr/share/utsushi/drivers/esci/DS-535.dat
imagescan usr/share/utsushi/drivers/esci/DS-535H.dat
imagescan usr/share/utsushi/drivers/esci/DS-5500.dat
imagescan usr/share/utsushi/drivers/esci/DS-560.dat
imagescan usr/share/utsushi/drivers/esci/DS-570W.dat
imagescan usr/share/utsushi/drivers/esci/DS-575W.dat
imagescan usr/share/utsushi/drivers/esci/DS-60000.dat
imagescan usr/share/utsushi/drivers/esci/DS-6500.dat
imagescan usr/share/utsushi/drivers/esci/DS-70000.dat
imagescan usr/share/utsushi/drivers/esci/DS-7500.dat
imagescan usr/share/utsushi/drivers/esci/DS-760.dat
imagescan usr/share/utsushi/drivers/esci/DS-770.dat
imagescan usr/share/utsushi/drivers/esci/DS-775.dat
imagescan usr/share/utsushi/drivers/esci/DS-860.dat
imagescan usr/share/utsushi/drivers/esci/ES-200.dat
imagescan usr/share/utsushi/drivers/esci/ES-300W.dat
imagescan usr/share/utsushi/drivers/esci/ES-400.dat
imagescan usr/share/utsushi/drivers/esci/ES-500W.dat
imagescan usr/share/utsushi/drivers/esci/PX-M7050.dat
imagescan usr/share/utsushi/drivers/esci/PX-M7050FX.dat
imagescan usr/share/utsushi/drivers/esci/PX-M860F.dat
imagescan usr/share/utsushi/drivers/esci/WF-6590.dat
imagescan usr/share/utsushi/gtkmm/
imagescan usr/share/utsushi/gtkmm/about.xml
imagescan usr/share/utsushi/gtkmm/dialog.glade
imagescan usr/share/utsushi/gtkmm/dialog.rc
Pour info, l'option <F> de pacman permet de consulter en ligne un paquet sans l'avoir en local.
Il n'y a pas de /etc/imagescan...
[HS]Ma mère a une Lexmark en Wifi et on a le même souci. Je penche pour l'instant à un filtre lié à la box[/HS]

scanner non reconnu

#14Messageil y a 4 ans

Merci.
Ci-joint mon /etc/utsushi/utsushi.conf

#  devices.conf -- sample device configuration file
#  Copyright (C) 2013, 2015, 2016  SEIKO EPSON CORPORATION
#
#  License: GPL-3.0+
#  Author : EPSON AVASYS CORPORATION
#
#  This file is part of the 'Utsushi' package.
#  This package is free software: you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation, either version 3 of the License or, at
#  your option, any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#  You ought to have received a copy of the GNU General Public License
#  along with this package.  If not, see <http://www.gnu.org/licenses/>.

#  The configuration file format is quite straightforward and resembles
#  that of Windows INI files and Samba configuration files.  Lines that
#  start with a '#' (like this one) or a ';' are comments and ignored.
#  Empty lines are also ignored.  Non-empty lines consist of a
#
#    key  =  value
#
#  entry.  White space around the 'key' and 'value' is ignored.  White
#  space internal to a value is kept.  Key may not contain white space.
#  Key parts are separated by a '.', like so:
#
#    this.is.a.key
#
#  Key parts are strictly ASCII and consist of a letter followed by
#  zero of more letters or digits.  Values are UTF-8 text.
#
#  Keys with a common prefix of parts may be grouped in sections if
#  you find that more convenient.  So instead of saying:
#
#    common.prefix.key1 = val1
#    common.prefix.key2 = val2
#
#  you can just as well use
#
#    [common.prefix]
#    key1 = val1
#    key2 = val2
#
#  The section header, '[common.prefix]' above, is in effect until the
#  next section header, or the end of file.

#  Devices not automatically detected by Utsushi can be configured in a
#  [devices] section as shown below.  Each device is given an arbitrary
#  key that is used to tie together its configuration attributes.  The
#  only required attribute is the device's 'udi'.  The 'name', 'model'
#  and 'vendor' attributes are optional.  If not specified, an attempt
#  is made to obtain 'vendor' and 'model' information directly from the
#  device itself.  A 'name' will be generated from the other attributes
#  if not explicitly configured.
#
#  The 'udi' attribute's value uses a URL-like syntax.  It starts with
#  a driver name and a connection "class", followed by a string that is
#  dependent on the driver and connection values.  These three parts
#  are separated by a ':'.

[devices]

#dev1.udi  = esci:usb:/sys/devices/pci0000:00/0000:00:1a.7/usb9/9-5/9-5:1.0
#dev1.name = スキャナー

#  The 'dev1' device above will use the 'esci' driver and is connected
#  via a USB cable.  The string is an OS specific location that is
#  understood by Utsushi's USB support.  No vendor and model are set
#  so that information may be obtained from the device.  This could
#  use driver provided information as well as USB information.  The
#  name will be used as is and should appear in user visible places.
#  BTW, that name is just 'scanner' but in Japanese to show that you
#  should be able to use UTF-8 encoded values.
#  FIXME: UTF-8 values are currently ignored :-(

#dev2.udi    = esci:networkscan://192.168.0.2:1865
#dev2.model  = DS-5500
#dev2.vendor = EPSON

#  The 'dev2' device is set up to use a 'networkscan' connection (a
#  non-free plugin for networked EPSON devices) in combination with
#  the 'esci' driver to communicate with a device at the IP address
#  and port shown.  The configured model and vendor attributes will
#  be used to construct a name for use in the user interface.

#  The section below adds a third device taking full advantage of the
#  common prefix mechanism.  It does not specify a connection "class"
#  and leaves it up to a hypothetical 'sane' driver to connect to an
#  EPSON multi-function peripheral supported by the 'epkowa' backend
#  with USB vendor and product IDs as specified.  The device has been
#  nicknamed 'foo' and the model name been set so that the backend's
#  model name will be overridden (quite understandle considering its
#  length and ambiguity).

[devices.mfp1]

#udi    = sane::epkowa:usb:0x04b8:0x0848
#name   = foo
#model  = Stylus Office BX300F
J'ai commenté les lignes dev1 et dev2 pour que mon imprimante s'affiche dans le menu de l'interface.
Mais je ne sais pas comment trouver l'udi de mon Epson...

scanner non reconnu

#15Messageil y a 4 ans

Cette page indique comment modifier les fichiers de configuration pour installer une imprimante non reconnue: https://doc.ubuntu-fr.org/scanner_usb_n ... figuration
Mais /lib/udev/rules.d/40-libsane.rules n'existe pas dans mon système.
Existe-t-il un fichier de configuration spécifique à Manjaro?

scanner non reconnu

#16Messageil y a 4 ans

bonjour

/rules.d/ c'est normal qu'il n'y a rien : c'est un dossier on l'on peut mettre n'importe quel fichier de configuration (.rules) - le nom n'est pas pris en compte donc tu as peut-être déjà un fichier (avec un autre nom) qui gère cette solution ou tu peux librement en créer

scanner non reconnu

#17Messageil y a 4 ans

Répondre