Koozali.org: home of the SME Server
Other Languages => Français => Topic started by: ecureuil on June 18, 2017, 04:32:06 PM
-
bonjour,
y-a-t-il des personnes qui se servent de smeserver-sane (pour scanner des documents)?
Cela ne fonctionne plus sur ma sme 9.2
lsusb
Bus 003 Device 020: ID 04b8:010f Seiko Epson Corp. GT-7200U [Perfection 1250/1250 PHOTO]
# 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.
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:003:020
found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:001:004
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# 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).
C'est bizarre
J'ai essayé de chercher dans les logs, rien trouvé de catastrophe
dans le log de message
Jun 18 16:39:37 tux kernel: usb 3-1: new full speed USB device number 21 using xhci_hcd
Jun 18 16:39:37 tux kernel: usb 3-1: New USB device found, idVendor=04b8, idProduct=010f
Jun 18 16:39:37 tux kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 18 16:39:37 tux kernel: usb 3-1: Product: EPSON Scanner 010F
Jun 18 16:39:37 tux kernel: usb 3-1: Manufacturer: EPSON
Jun 18 16:39:37 tux kernel: usb 3-1: configuration #1 chosen from 1 choice
J'ai branché le scanner sur ma debian, il scanne sans problème.
Donc le scanner est ok.
Si quelqu'un a une idée
Anne
-
je n'utilise pas, mais tout ce que je peux voir c'Est que tons canner est supporté d'Apres http://www.sane-project.org/sane-backends-1.0.21.html#S-PLUSTEK avec le backend plustek (0.52)
http://www.sane-project.org/man/sane-plustek.5.html
par contre pas supporté avec les backend epson et epson2
# yum install smeserver-sane --enablerepo=smecontribs
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
smeserver-sane noarch 0.3-1.el6.sme smecontribs 13 k
Installing for dependencies:
libexif x86_64 0.6.21-5.el6_3 base 350 k
libgphoto2 x86_64 2.4.7-5.el6 base 1.0 M
libieee1284 x86_64 0.2.11-9.el6 base 35 k
libv4l x86_64 0.6.3-2.el6 base 103 k
sane-backends x86_64 1.0.21-5.el6 base 1.0 M
sane-backends-libs x86_64 1.0.21-5.el6 base 2.0 M
smeserver-xinetd noarch 0.3-1.el6.sme smecontribs 12 k
xinetd x86_64 2:2.3.14-40.el6 base 122 k
# rpm -ql sane-backends-libs|grep plus
/usr/lib64/sane/libsane-artec_eplus48u.so
/usr/lib64/sane/libsane-artec_eplus48u.so.1
/usr/lib64/sane/libsane-artec_eplus48u.so.1.0.21
/usr/lib64/sane/libsane-plustek.so
/usr/lib64/sane/libsane-plustek.so.1
/usr/lib64/sane/libsane-plustek.so.1.0.21
/usr/lib64/sane/libsane-plustek_pp.so
/usr/lib64/sane/libsane-plustek_pp.so.1
/usr/lib64/sane/libsane-plustek_pp.so.1.0.21
donc cela devrait tourner ...
-
Je sais que c'est le driver plustek.
Cela fonctionnait bien il n'y a pas si longtemps avec mon serveur sme 9.2 en x86_64.
J'ai un serveur en i386 version sme 9.2
j'ai commencé par
yum install sane
puis j'ai testé avec le même scanner
# 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.
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:002:003
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
]# scanimage -L
device `plustek:libusb:002:003' is a Epson Perfection 1250/Photo flatbed scanner
# yum --enablerepo=smecontribs install smeserver-sane
=>
=============================================================================================================================================================================================================================================================================================================================
Paquet Architecture Version Dépôt Taille
=============================================================================================================================================================================================================================================================================================================================
Installation:
smeserver-sane noarch 0.3-1.el6.sme smecontribs 13 k
Installation pour dépendance:
smeserver-xinetd noarch 0.3-1.el6.sme smecontribs 12 k
]# expand-template /etc/xinetd.conf
# expand-template /etc/services
# expand-template /etc/hosts.allow
# expand-template /etc/sane.d/saned.conf
# service xinetd restart
Arrêt de xinetd : [ÉCHOUÉ]
Démarrage de xinetd : [ OK ]
J'ai testé avec ma debian qui a x-sane
Pas de souci
Par contre avec mon serveur sme 9.2 en x86_64.je n'arrive pas à comprendre pourquoi cela ne fonctionne pas
Anne
-
que donne la commande suivante ?
rpm -qa |grep sane |sort
-
sur x86_64
========
# rpm -qa |grep sane |sort
sane-backends-1.0.21-5.el6.x86_64
sane-backends-libs-1.0.21-5.el6.x86_64
smeserver-sane-0.3-1.el6.sme.noarch
# 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.
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F]) at libusb:003:014
found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:001:004
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# 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).
sur i686
======
# rpm -qa |grep sane |sort
sane-backends-1.0.21-5.el6.i686
sane-backends-libs-1.0.21-5.el6.i686
smeserver-sane-0.3-1.el6.sme.noarch
# 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.
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:002:003
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# scanimage -L
device `plustek:libusb:002:003' is a Epson Perfection 1250/Photo flatbed scanner
Je ne comprends pas pourquoi cela ne fonctionne plus sur mon serveur en x86_64
J'ai fait beaucoup de test en prenant d'autres paquets sans installer smeserver-sane-... pas mieux x86_64
sur le serveur en i686 pas de souci tout fonctionne
Anne-Marie
-
Je regarderais demain, mais cela doit etre un probleme de path de librairie lib versus lib64 a redefinir dans smeserver-sane en lisant ta derniere reponse.
-
je ne pense pas
j"ai essayé sans utiliser smeserver-sane, juste sane-backend* (de Centos et un autre avec version 22)
(même problème)
mais c'est certainement en relation avec sme x86_64 mais quoi?
Cela fonctionnait il y a un mois
Je vais être absente quelques jours.
Si tu trouves quelque chose je testerai à mon retour
Anne
-
pas de reference a lib dans le rpm, donc pas de ce coté là.
une autre chose que j'investiguerais est :
x64
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F]) at libusb:003:014
found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:001:004
vs
i686
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:002:003
en x64 tu as apparement un autre peripherique detecté. un e recherche rapide pointe vers un lecteur de carte
peux tu desactiver ce peripherique ?
verifier que le bon backend a été selectionné : https://wiki.archlinux.org/index.php/SANE#Multiple_backends_claim_scanner
probleme de permission ou ajout manuel du scanner: https://wiki.archlinux.org/index.php/SANE#Permission_problem
-
bonjour,
J'ai investi dans sane aujourd'hui.
Depuis une maj, impossible d'avoir accès au scanner sur celui en 64 bits.
J'avais donc brancher le scanner usb sur celui en 32 bits
Les commandes :
---
# 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.
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:003:017
found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:001:004
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
----
Il a bien trouvé mon scanner
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner
---
# 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).
---
Il ne le trouve plus.
Sur le serveur 32 bits
---
]# scanimage -L
device `plustek:libusb:002:004' is a Epson Perfection 1250/Photo flatbed scanner
---
Je suis en train d'essayer de comprendre le problème.
sur le serveur en 32 bits
---
# sane-find-scanner -v -v
...
<device descriptor of 0x04b8/0x010f at 002:003 (EPSON EPSON Scanner 010F)>
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255
bDeviceSubClass 0
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x04B8
idProduct 0x010F
bcdDevice 1.00
iManufacturer 1 (EPSON)
iProduct 2 (EPSON Scanner 010F)
iSerialNumber 0 ()
bNumConfigurations 1
<configuration 0>
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 192 (Self-powered)
MaxPower 2 mA
<interface 0>
<altsetting 0>
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0 ()
<endpoint 0>
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 3 (interrupt)
wMaxPacketSize 1
bInterval 16 ms
bRefresh 0
bSynchAddress 0
<endpoint 1>
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 (in 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<endpoint 2>
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 (out 0x03)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<trying to find out which USB chip is used>
checking for GT-6801 ...
this is not a GT-6801 (bDeviceSubClass = 0x0)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
this is not a MA-1015 (bcdUSB = 0x110)
checking for MA-1509 ...
this is not a MA-1509 (bDeviceSubClass = 0x0)
checking for LM983[1,2,3] ...
<This USB chip looks like a LM9832/3 (result from sane-backends 1.0.21)>
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F], chip=LM9832/3) at libusb:002:003
...
---
il a trouvé le chip LM9832/3.
sur le serveur 64 bits
----
# sane-find-scanner -v -v
...
<device descriptor of 0x04b8/0x010f at 003:015 (EPSON EPSON Scanner 010F)>
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255
bDeviceSubClass 0
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x04B8
idProduct 0x010F
bcdDevice 1.00
iManufacturer 1 (EPSON)
iProduct 2 (EPSON Scanner 010F)
iSerialNumber 0 ()
bNumConfigurations 1
<configuration 0>
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 192 (Self-powered)
MaxPower 2 mA
<interface 0>
<altsetting 0>
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0 ()
<endpoint 0>
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 3 (interrupt)
wMaxPacketSize 1
bInterval 16 ms
bRefresh 0
bSynchAddress 0
<endpoint 1>
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 (in 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<endpoint 2>
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 (out 0x03)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<trying to find out which USB chip is used>
checking for GT-6801 ...
this is not a GT-6801 (bDeviceSubClass = 0x0)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
this is not a MA-1015 (bcdUSB = 0x110)
checking for MA-1509 ...
this is not a MA-1509 (bDeviceSubClass = 0x0)
checking for LM983[1,2,3] ...
Couldn't access LM983x registers.
checking for GL646 ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL646_HP ...
this is not a GL646_HP (bDeviceSubClass = 0x0)
checking for GL660+GL646 ...
this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL84x ...
this is not a GL84x (bcdUSB = 0x110)
checking for ICM532B ...
this is not a ICM532B (check 3, bDeviceSubClass = 0x0)
checking for PV8630/LM9830 ...
this is not a PV8630/LM9830 (bDeviceClass = 255)
checking for M011 ...
this is not a M011 (bcdUSB = 0x110)
checking for RTS8822 ...
this is not a RTS8822 (bDeviceClass = 255)
checking for rts8858c ...
this is not a rts8858c (bDeviceClass = 255)
checking for SQ113 ...
this is not a SQ113 (bDeviceClass = 255)
checking for HP4500C/4570C/5500C/5550C/5590/7650 chipset ...
this is not a HP4500C/4570C/5500C/5550C/5590/7650 chipset (bcdUSB = 0x110)
checking for rts8801/rts8891 ...
this is not a rts8801/rts8891 (bDeviceClass = 255)
<Couldn't determine the type of the USB chip (result from sane-backends 1.0.21)>
found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F]) at libusb:003:015
...
---
Il ne trouve pas le chip
checking for LM983[1,2,3] ...
Couldn't access LM983x registers.
c'est quoi un register et pourquoi il n'y aurait pas accès
Si quelqu'un a une idée pour continuer les recherches...
merci
anne