So i was trying to setup my scanner(HP scanjet 5300c usb) with debian sarge kernel 2.6.8-2-386. I did googling and edited avision.conf file in /etc/sane.d and execute sane-find-scanner as root. It detects it. But when i scanimage -L or xsane at command line(also as root) scanner can't be found.
mutuski:~#sane-find-scanner found USB scanner (vendor=0x03f0, product=0x0701) at libusb:001:002 # 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. mutuski:~#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). Then I did: mutuski:~# export SANE_DEBUG_AVISION=255 mutuski:~#scanimage -L [sanei_debug] Setting debug level of avision to 255. [avision] sane_init: parsing config line "" [avision] sane_init: config file line 1: ignoring empty line [avision] sane_init: parsing config line "# This are the possible options. Normally any scanner" [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line "# should work just fine without them - and they are only" [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line "# needed for test and debugging. So if you experience problems" [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line "# and you solve them with enabling options here, please notify" [avision] sane_init: config file line 5: ignoring comment line [avision] sane_init: parsing config line "# the SANE/Avision maintainer." [avision] sane_init: config file line 6: ignoring comment line [avision] sane_init: parsing config line "" [avision] sane_init: config file line 7: ignoring empty line [avision] sane_init: parsing config line "#option disable-gamma-table" [avision] sane_init: config file line 8: ignoring comment line [avision] sane_init: parsing config line "#option disable-calibration" [avision] sane_init: config file line 9: ignoring comment line [avision] sane_init: parsing config line "#option old-calibration" [avision] sane_init: config file line 10: ignoring comment line [avision] sane_init: parsing config line "#option one-calib-only" [avision] sane_init: config file line 11: ignoring comment line [avision] sane_init: parsing config line "#option force-a4" [avision] sane_init: config file line 12: ignoring comment line [avision] sane_init: parsing config line "#option disable-c5-guard" [avision] sane_init: config file line 13: ignoring comment line [avision] sane_init: parsing config line "" [avision] sane_init: config file line 14: ignoring empty line [avision] sane_init: parsing config line "scsi AVISION" [avision] sane_init: config file line 15: trying to attach SCSI: scsi AVISION'[avision] sane_init: parsing config line "scsi FCPA" [avision] sane_init: config file line 16: trying to attach SCSI: scsi FCPA' [avision] sane_init: parsing config line "scsi MINOLTA" [avision] sane_init: config file line 17: trying to attach SCSI: scsi MINOLTA'[avision] sane_init: parsing config line "scsi MITSBISH MCA-S600C" [avision] sane_init: config file line 18: trying to attach SCSI: scsi MITSBISH MCA-S600C' [avision] sane_init: parsing config line "scsi MITSBISH MCA-SS600" [avision] sane_init: config file line 19: trying to attach SCSI: scsi MITSBISH MCA-SS600' [avision] sane_init: parsing config line "scsi HP" [avision] sane_init: config file line 20: trying to attach SCSI: scsi HP' [avision] sane_init: parsing config line "scsi hp" [avision] sane_init: config file line 21: trying to attach SCSI: scsi hp' [avision] sane_init: parsing config line "" [avision] sane_init: config file line 22: ignoring empty line [avision] sane_init: parsing config line "#scsi /dev/scanner" [avision] sane_init: config file line 23: ignoring comment line [avision] sane_init: parsing config line "usb libusb:001:002" [avision] sane_init: config file line 24: trying to attach USB:`usb libusb:001:002' [avision] sane_init: parsing config line "#usb 0x03f0 0x0701" [avision] sane_init: config file line 25: ignoring comment line [avision] sane_init: parsing config line "" [avision] sane_init: config file line 26: ignoring empty line [avision] sane_init: Trying to find USB device 638 a24 ... [avision] sane_init: Trying to find USB device 638 a23 ... [avision] sane_init: Trying to find USB device 638 a18 ... [avision] sane_init: Trying to find USB device 638 a16 ... [avision] sane_init: Trying to find USB device 638 a13 ... [avision] sane_init: Trying to find USB device 638 a18 ... [avision] sane_init: Trying to find USB device 638 a16 ... [avision] sane_init: Trying to find USB device 3f0 701 ... [avision] attach: (Version: 1.0 Build: 99) [avision] attach: opening libusb:001:002 [avision] attach: open failed (Invalid argument) [avision] sane_init: Trying to find USB device 3f0 701 ... [avision] attach: (Version: 1.0 Build: 99) [avision] attach: opening libusb:001:002 [avision] attach: open failed (Invalid argument) [avision] sane_init: Trying to find USB device 3f0 801 ... [avision] sane_init: Trying to find USB device 3f0 b01 ... [avision] sane_init: Trying to find USB device 638 26a ... [avision] sane_init: Trying to find USB device 686 4004 ... [avision] sane_init: Trying to find USB device 638 268 ... [avision] sane_get_devices: 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). [avision] sane_exit: Hmmmm....why is it unable to open libusb:001:002? Does anyone why it is acting strange? For information the output of some commands are given below: mutuski:~#lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c Bus 001 Device 001: ID 0000:0000 mutuski:~#cat /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0701 Rev= 0.01 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I'm using libsane 1.0.15-9 and avision.conf backend. Thanks for your time. --Anthony -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060807/d3f875e6/attachment.html From jsm...@suse.de Tue Aug 8 10:45:39 2006 From: jsm...@suse.de (Johannes Meixner) Date: Tue Aug 8 10:46:30 2006 Subject: [sane-devel] sane-find-scanner detects smartcard reader as scanner Message-ID: <pine.lnx.4.64.0608081233430.1...@wotan.suse.de> Hello, sane-find-scanner from sane-backends 1.0.17 detects the following USB smartcard reader as a scanner: idVendor 0x0c4b Reiner SCT Kartensysteme GmbH idProduct 0x0300 cyberJack pinpad(a) I don't have the device to test it with sane-backends 1.0.18 but I guess it is also detected with sane-backends 1.0.18. For the details see https://bugzilla.novell.com/show_bug.cgi?id=197513 in particular https://bugzilla.novell.com/attachment.cgi?id=95324&action=view By the way: Nowhere in the sources of sane-backends 1.0.17 I can find the USB vendor ID (neither 'c4b' nor 'C4B'). Which magic lets sane-find-scanner detect this device as a scanner? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
